Closed tclements closed 3 years ago
Working on this now. I don't think there's an error with the mini-SEED reader; everything I've used to analyze the file suggests that the last packet has one sample.
I can guess why the one-sample case occurs. The channel went offline at around 9 AM that day; it looks like data transmission resumed exactly at midnight (presumably the network did the latter manually). So, why one sample? Well, I'd bet that there's a small time correction by the seismic network. At fs = 1.0 Hz, if the sample times are corrected by at least 0.076 s, you'll have exactly one sample on the previous day ... and subsequently, it'll be included in a data request that ends at midnight.
I think the most recent commits fix this. Check to verify; if so, I can close this.
Fixed in SeisIO v1.2.0.
Here's an data/reading problem. I'm not sure if this file is corrupted or is being read incorrectly.
I came across an mseed file where SeisIO says there is a gap in a file but there is no data following that gap:
This claims there is a gap of
53539997700
but there isn't any data afterwards.When I go to
ungap
these data, the gap is still therebecause
ungap!
only checks if the size of the time matrix in the first dimension is 2, so this isn't caught.This could create a problem when trying to determine the endtime of the file
as it should be
We might want to check that
t[2,2] == 0
whenungap
ping to catch this sort of thing. Here is the file:mseed-file.zip