-
Notifications
You must be signed in to change notification settings - Fork 272
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
Rename confusing Hillas angular parameters #2272
Comments
This is a duplicate of #1078 |
It's not really a duplicate: I saw that issue, but it relates to the algorithm implementation not the naming of the data model . That one should probably be closed as the algorithm was already implemented. The only thing else in that issue is to add more documentation, but it's related. This issue is more about the fact that we have had a few bugs due to how easy it is to misspell or confuse phi/psi |
Strange, the first sentence in that issue is:
|
Yeah, the title of that issue is confusing, It references however this comment, which is basically this issue. We can maybe close #771 and #1078 (though 1078 also has some interesting info in it, even if not a naming scheme). This issue was meant to replace both, |
Still think that #1078 is exactly the same as this and it has the relevant discussions, so I am closing here |
Right now we have
hillas.phi
andhillas.psi
, which are somewhat easy to confuse without reading the descriptions. It might be better to rename them to wordier, but more descriptive versions:Something along the lines of:
Image axis angle:
hillas.psi
→hillas.image_axis_angle
(orposition_angle
- see below)Polar coordinates of the centroid:
hillas.phi
→hillas.centroid_polar_angle
hillas.r
→hillas.centroid_polar_radius
"Cartesian" (locally) position of the centroid
hillas.fov_lat
→hillas.centroid_fov_lat
hillas.fov_lon
→hillas.centroid_fov_lon
We might also consider the term Position Angle, which is how astronomers refer to 2D rotation angles on the sky sphere (not 3D angular coordinates).
Any other suggestions?
The text was updated successfully, but these errors were encountered: