Seitosh issueshttps://git.scc.kit.edu/Seitosh/Seitosh/-/issues2017-11-14T20:47:14+01:00https://git.scc.kit.edu/Seitosh/Seitosh/-/issues/1anyextract GAP analysis: apparent false alarm2017-11-14T20:47:14+01:00we7765anyextract GAP analysis: apparent false alarmGAP report produced by anyextract:
SPECIAL MODE: find gaps in input data - do not extract data
step 1: collect matching index entries
data selection:
first sample: 060 01.03.2015 12:00:00.000000
...GAP report produced by anyextract:
SPECIAL MODE: find gaps in input data - do not extract data
step 1: collect matching index entries
data selection:
first sample: 060 01.03.2015 12:00:00.000000
last sample: 062 03.03.2015 00:00:00.000000
duplicate input samples are a break condition
station: .*
channel: .*
instrument: .*
auxid: .*
** open next index file: /data/BFO_index/index/data/BFO/seedlink/2015/XS/BFO/LHE.D/XS.BFO.00.LHE.D.2015.061.idx
** open next index file: /data/BFO_index/index/data/BFO/seedlink/2015/XS/BFO/LHE.D/XS.BFO.00.LHE.D.2015.062.idx
** open next index file: /data/BFO_index/index/data/BFO/seedlink/2015/XS/BFO/LHE.D/XS.BFO.00.LHE.D.2015.063.idx
** open next index file: /data/BFO_index/index/data/BFO/seedlink/2015/XS/BFO/LHE.D/XS.BFO.00.LHE.D.2015.060.idx
step 2: sort collected index entries
step 3: define copy operations
! GAP (BFO ,LHE,XS:0): 061 02.03.2015 00:01:48.069538 (expected) < 061 02.03.2015 00:01:48.069539 (actual)
step 4: report contiguous data
chunks of contiguous data:
BFO LHE XS:0 01.03.2015 12:00:00.069538 - 02.03.2015 00:01:47.069538
BFO LHE XS:0 02.03.2015 00:01:48.069539 - 03.03.2015 00:00:00.069539
analysis period: 01.03.2015 12:00:00.000000 - 03.03.2015 00:00:00.000000
gaps present in input data:
stream: LHE:BFO:XS:0 dt=000d 00h 00m 01.000000s
061 02.03.2015 00:01:48.069538: break in contiguous data
: 0 samples are missing
number of breaks / number of gaps / number of missing samples / completeness:
1 / 0 / 0 / 99.99%
summary of entire analysis:
number of breaks / number of gaps / number of missing samples / completeness:
1 / 0 / 0 / 99.99%
Break condition is triggered by a mismatch of one microsecond at the beginning of a new data file.
This happen although a timing tolerance of three microseconds is set:
content of /data/BFO_index/index/data/BFO/seedlink/2015/XS/BFO/LHE.D/XS.BFO.00.LHE.D.2015.061.idx
/data/BFO/seedlink/2015/XS/BFO/LHE.D/XS.BFO.00.LHE.D.2015.061 1 mseed:ttolerance=3
WIDX 2015/03/02-00:01:48.069539 BFO LHE XS:0 NSP 86464 r 1.0e+00 -1.0e+00 -1.0e+00 -1.0e+00 -1.0e+00
we7765we7765https://git.scc.kit.edu/Seitosh/Seitosh/-/issues/2stuploxx: desired options for text scaling2017-11-14T20:47:14+01:00we7765stuploxx: desired options for text scaling[stuploxx](src/ts/stuploxx) should offer options to scale axis labels.
The are already defined but not yet implemented (see [help_text.txt](src/ts/stuploxx/help_text.txt)).[stuploxx](src/ts/stuploxx) should offer options to scale axis labels.
The are already defined but not yet implemented (see [help_text.txt](src/ts/stuploxx/help_text.txt)).we7765we7765https://git.scc.kit.edu/Seitosh/Seitosh/-/issues/8libdatrwxx: handle full SeismicUnix headers2017-11-14T20:47:14+01:00we7765libdatrwxx: handle full SeismicUnix headersThis refers to tickets [#81](http://gpitrsvn.gpi.uni-karlsruhe.de:8000/TFSoftware/ticket/81) and [#82](http://gpitrsvn.gpi.uni-karlsruhe.de:8000/TFSoftware/ticket/82) in TFSoftware:
libdatrwxx looses the rich content of SeismicUnix he...This refers to tickets [#81](http://gpitrsvn.gpi.uni-karlsruhe.de:8000/TFSoftware/ticket/81) and [#82](http://gpitrsvn.gpi.uni-karlsruhe.de:8000/TFSoftware/ticket/82) in TFSoftware:
libdatrwxx looses the rich content of SeismicUnix headers upon reading data files. By passing the contents in the trace FREE block in well formatted character strings they could be made available to the SeismicUnix writing functions and thus could appropriately be restored in the output file. SeismicUnix input/output is provided in source code found at [src/libs/libdatrwxx/su](src/libs/libdatrwxx/su). The SU module in libdatrwxx currently does neither produce trace free blocks of type sff::FREE (in function void isustream::readheader()) not does it write such blocks (in function void osustream::writetrace(const Tfseries::Tcoc& series)). Appropriate evaluation of Seismic Unix trace header fields and conversion to and from sff::FREE containers should be implemented as member function of datrw::su::SUheader in [src/libs/libdatrwxx/su/suheader.cc](src/libs/libdatrwxx/su/suheader.cc).
Niklas, if you plan to work on this, a discussion of implementation strategy and data containers provided and used in libdatrwxx might be helpful or even necessary.
A remark taken from TFSoftware ticket [#81](http://gpitrsvn.gpi.uni-karlsruhe.de:8000/TFSoftware/ticket/81):
Since the different header fields are of different variable type, the functions behind suascii are quite elaborate. Although they are straight forward, it would require an additional amount of code to implement this functionality. Its usefulness within the framework of libdatrwxx is questionable.
See
SU41/src/su/main/suascii.c
and
SU41/src/su/lib/hdrpkge.c
as well as
SU41/src/su/include/hdr.h
SU41/src/su/include/Makefile
SU41/src/su/include/mkhdr.c
SU41/src/su/include/mkprehdr.sh
SU41/src/su/include/offsets.h
and others.niklas.thielniklas.thielhttps://git.scc.kit.edu/Seitosh/Seitosh/-/issues/10lisousi: improve program documentation and usage advice2017-11-14T20:47:14+01:00we7765lisousi: improve program documentation and usage adviceEach time I use the program after being absent for some time, I find all the options to use non-intuitive and difficult to match with the three primary approaches defined in the underlying paper. The usage documentation should be improve...Each time I use the program after being absent for some time, I find all the options to use non-intuitive and difficult to match with the three primary approaches defined in the underlying paper. The usage documentation should be improved respectively. Maybe the definition of command line argument patterns for the three approaches would be helpful.we7765we7765https://git.scc.kit.edu/Seitosh/Seitosh/-/issues/15stuploxx: plot panel margin2017-11-14T20:47:14+01:00we7765stuploxx: plot panel marginThe per-file option sf: should adjust a panel margin relative to the actual value range used in the panel. This currently is not the case, since margins are calculated from signal values.The per-file option sf: should adjust a panel margin relative to the actual value range used in the panel. This currently is not the case, since margins are calculated from signal values.we7765we7765https://git.scc.kit.edu/Seitosh/Seitosh/-/issues/18gremlin: maintainer documentation2017-11-14T20:47:14+01:00we7765gremlin: maintainer documentationSubdirectories of [src/green/gremlin1](src/green/gremlin1) contain README files which are partly outdated or incomplete. They should give a clear account of the purpose of the programs of the available make targets and prerequisites.
...Subdirectories of [src/green/gremlin1](src/green/gremlin1) contain README files which are partly outdated or incomplete. They should give a clear account of the purpose of the programs of the available make targets and prerequisites.
Branch [i18_gremlin_mdoc](../../tree/i18_gremlin_mdoc/src/green/gremlin1) is the place to work on this.
Files to work on:
- [ ] [gremlin1/README](../../tree/i18_gremlin_mdoc/src/green/gremlin1/README)
- [ ] [gremlin1/cxx/README](../../tree/i18_gremlin_mdoc/src/green/gremlin1/cxx/README)
- [ ] [gremlin1/docu/README](../../tree/i18_gremlin_mdoc/src/green/gremlin1/docu/README)
- [ ] [gremlin1/libs/README](../../tree/i18_gremlin_mdoc/src/green/gremlin1/libs/README)
- [ ] [gremlin1/tools/README](../../tree/i18_gremlin_mdoc/src/green/gremlin1/tools/README)we7765we7765https://git.scc.kit.edu/Seitosh/Seitosh/-/issues/19gremlin: provide proper user documentation2017-11-14T20:47:14+01:00we7765gremlin: provide proper user documentationUser documentation for gremlin currently is scattered all over the place and partly provided in German only. Make documentation consistent and complete or at least provide proper references to all relevant locations.
Branch [i19_greml...User documentation for gremlin currently is scattered all over the place and partly provided in German only. Make documentation consistent and complete or at least provide proper references to all relevant locations.
Branch [i19_gremlin_mdoc](../../tree/i19_gremlin_udoc/src/green/gremlin1) is the place to work on this.
@sb5563: I open this issue as a place to cooperate on the improvement of elementary user documentation. we7765we7765https://git.scc.kit.edu/Seitosh/Seitosh/-/issues/20gremlin: provide a toy example2017-11-14T20:47:14+01:00we7765gremlin: provide a toy exampleUser new to gremlin require a to example with appropriate users guide.
Branch [i20_gremlin_example](../../tree/i20_gremlin_example/src/green/gremlin1) is the place to work on this.
@sb5563: I plan to add a documented toy example. T...User new to gremlin require a to example with appropriate users guide.
Branch [i20_gremlin_example](../../tree/i20_gremlin_example/src/green/gremlin1) is the place to work on this.
@sb5563: I plan to add a documented toy example. This is the place to cooperate and discuss this issue (#20).we7765we7765https://git.scc.kit.edu/Seitosh/Seitosh/-/issues/24libdatrwxx: MiniSEED format specification2017-11-14T20:47:13+01:00we7765libdatrwxx: MiniSEED format specificationGive a proper account of MiniSEED format specifications, which the library relies on. Tell which exceptions are known and which exceptions are handled by the library.
Possibly rework the reading module, such that becomes flexible and ...Give a proper account of MiniSEED format specifications, which the library relies on. Tell which exceptions are known and which exceptions are handled by the library.
Possibly rework the reading module, such that becomes flexible and conforms to the format definition more closely. Consider the read full binary records from the files and to present them to different decoding units.
II-data for the iSTS1 is written in
encoding format: IEEE double precision floating point (5)
Consider to implement this.we7765we7765https://git.scc.kit.edu/Seitosh/Seitosh/-/issues/27stuploxx: origin of time scale shall be adjusted dynamically in interactive mode2021-11-09T11:14:48+01:00we7765stuploxx: origin of time scale shall be adjusted dynamically in interactive modeBehavior in interative mode:
reload (r): data is regenerated and reloaded. The displayed time window remains unchanged, the new data may (partially or completely) lie outside the displayed time window. This behavior appears reasonable.
...Behavior in interative mode:
reload (r): data is regenerated and reloaded. The displayed time window remains unchanged, the new data may (partially or completely) lie outside the displayed time window. This behavior appears reasonable.
timewindow init (t-i): The displayed time window is adapted to the available data. Now all the data that have been read in are shown in the time window. The timescale is correct.
The problem reported here relates to the origin of the time axis from which the counting starts (midnight on a specified date). This origin remains unchanged with a reload or t-i. If a seismogram window in interactive mode remains open for several days, time is counted from an origin far in the past. That makes the timescale difficult to read.
Whether this is a feature or a bug can be discussed. In practice we rarely use persistent interactive windows. Whether the main goal of interactive windows is to stay open for days can also be discussed.
However, it is also a fact that windows in auto-refresh mode dynamically adjust their time origin. So: it works (just needs to be implemented).we7765we7765