Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Station timing offsets for 102, 104 ref 105 are NaN for large periods #154

Closed
tomkooij opened this issue Oct 24, 2016 · 1 comment
Closed

Comments

@tomkooij
Copy link
Member

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".

>>> Station(104).station_timing_offsets(105)
[...]
      (1379721600, 3.6, 2.73), (1379808000, nan, nan),
       (1380585600, 2.8, 2.93), (1382486400, nan, nan),
       (1458000000, 7.4, 1.32), (1458518400, 6.8, 0.99),
[...]
@tomkooij 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
@tomkooij
Copy link
Member Author

This is because of PySPARC issues HiSPARC/datastore#9 (station 102) and because of failing MPV fits for station 105 (wrong PMT Voltages, no 'gamma peak' : http://data.hisparc.nl/show/stations/105/2016/1/11/)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant