-
Notifications
You must be signed in to change notification settings - Fork 9
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
Detector coordinates in cluster object #146
Comments
The calculation of the r and phi between the detectors is correct. However, the initial adding of the detector coordinates is wrong. It uses the ENU reference frame of the reference station, keeping the radius/alpha plane within the station parallel to that EN plane. It should use a locally horizontal frame. |
@153957: I looked through some of the code, and to me it seems an unavoidable side-effect from using ENU coordinate systems: The detectors are added relative to a translated (but not rotated) ENU-coordinate system 'attached to' the GPS of the station. I agree that the detectors should use a locally horizontal frame (translated and rotated) but I fail to see how that would be implemented in a KISS way. Will you provide a PR? ;-) (I'm thinking we should leave this "as is") |
I wont fix this, since this is mostly an issue for stations at large distances, at the moment not my problem 😉. I do think this could be fixed 'easily' (i.e. the required transformation functions already exist). |
In the example below the horizontal station distances are correctly different, however, the detector distances are equal, which is incorrect. Though their total distance should not change, the horizontal distance should be different because the station is further from the ENU origin, and the different ENU plane has a different tilt. This is related #142. This mostly reinforces the argument for using local Cluster objects for coincidence reconstruction and other analyses.
The text was updated successfully, but these errors were encountered: