-
Notifications
You must be signed in to change notification settings - Fork 31
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
Change name of dms_corner() #187
Comments
I second this: I wrote |
The actual DMS corners should already be available in pysiaf under the 'sci' coordinate system, so I don't think we need to add that. |
The sci coordinate system is based on the subarray itself though. e.g. For SUB320, the coordinates go from 0 to 319. What I think of as DMS corners are the coordinates in the full frame coordinate system, with the detector in the DMS orientation. So on the NIRCam A1 detector, the lower left corner of the SUB320 subarray would be (x, y) = (1728, 1728), and the upper right corner is (x, y) = (2048, 2048). I don't see any methods in pysiaf currently to calculate these values. This is what the function in Mirage calculates. |
The name of the
dms_corner
attribute of a SIAF aperture is misleading. It appears that this function actually returns the OSS corner coordinates for one of the aperture corners. It would be helpful to rename the attribute tooss_corner
or something similar.The Mirage package contains a function (written by Johannes Sahlmann) to return the DMS coordinates of the aperture corners. Feel free to steal it and use it for the
dms_corner
attribute if that's convenient.https://github.com/spacetelescope/mirage/blob/master/mirage/utils/siaf_interface.py#L223
The text was updated successfully, but these errors were encountered: