6d6mseed generates fragmented and two day-long mseed files #7
Description
When generating mseed files using 6d6mseed some of the files end up fragmented, eg. (a day of one horizontal component with extreme fragmentation where the timings seem to overlap - ~5 samples - for some parts):
channel | start time | end time | samples
Y 2020-03-29T00:00:00.000200Z 2020-03-29T01:02:21.692200Z 935424
Y 2020-03-29T01:02:21.730400Z 2020-03-29T01:02:25.758400Z 1008
Y 2020-03-29T01:02:25.727200Z 2020-03-29T01:34:53.179200Z 486864
Y 2020-03-29T01:34:53.193200Z 2020-03-29T01:34:57.221200Z 1008
Y 2020-03-29T01:34:57.214700Z 2020-03-29T19:32:50.490700Z 16168320
Y 2020-03-29T19:32:50.500400Z 2020-03-29T19:32:54.528400Z 1008
Y 2020-03-29T19:32:54.510300Z 2020-03-29T23:05:23.690300Z 3187296
Y 2020-03-29T23:05:23.703800Z 2020-03-29T23:05:27.731800Z 1008
Y 2020-03-29T23:05:27.723000Z 2020-03-29T23:37:55.175000Z 486864
Y 2020-03-29T23:37:55.216100Z 2020-03-29T23:37:59.244100Z 1008
Y 2020-03-29T23:37:59.210500Z 2020-03-29T23:59:59.998500Z 330198
Another issue is that a couple of mseed files contain two days (while the following day file is missing completely in the export), e.g.:
channel | start time | end time | samples
Z 2019-07-29T00:00:00.000400Z 2019-07-31T00:00:00.036400Z 43200010
Not all days are affected by this, but it happened for all the stations and all the channels (not necessarily the same days). The question does this come from the raw file or is this something that happens during the export using 6d6mseed?