You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Offsets are NaN because of missing and/or bad data, but also NaN well before and well after such periodes. We should be able to (or try to) determine station timing offsets just before and just after "gaps in the data".
The text was updated successfully, but these errors were encountered:
tomkooij
changed the title
Station timing offsets for 102, 104 ref 105 are NaN
Station timing offsets for 102, 104 ref 105 are NaN for large periods
Oct 24, 2016
Station timing offsets for 102, 104 with reference 105 is mostly NaN between:
september 22nd, 2013 and march 15th, 2016.
Probably related to HiSPARC/sapphire#147 and HiSPARC/datastore#9
Offsets are NaN because of missing and/or bad data, but also NaN well before and well after such periodes. We should be able to (or try to) determine station timing offsets just before and just after "gaps in the data".
The text was updated successfully, but these errors were encountered: