-
Notifications
You must be signed in to change notification settings - Fork 4
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
Coincidences download always yield -999 for event zenith, azimuth #272
Comments
Because we do not yet have reconstruction of coincidences in the ESD/processing. That would be a task to be added here: Just like for events: |
See #145 |
In the download the zenith/azimuth is supposed to be the 'event' zenith/azimuth (all other data is 1-to-1 copied from ESD event data). The reconstructed coincidence zenith/azimuth should be another/different field and documented... Some more work. Priority not high. |
I think one of the main issues with this was the orientation of the ENU plane, as described in that other issue. I think that normally when reconstruction coincidences the reference location/station of the Cluster object used for reconstructions is the origin of the ENU plane. This may need to be made local/center of mass to the current coincidence being examined to prevent an angle offset because of that. |
Ah I see what you mean! ok that is a different issue than I was describing. |
Reported by @josst:
events in coincidence download always return -999, -999 for reconstructed zen,azi while these values are available in separate event download.
affected line:
https://github.com/HiSPARC/publicdb/blob/master/publicdb/raw_data/views.py#L682
The text was updated successfully, but these errors were encountered: