-
Notifications
You must be signed in to change notification settings - Fork 63
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
Update to read SI pixelscales directly from pysiaf #626
Update to read SI pixelscales directly from pysiaf #626
Conversation
ea8f08c
to
1163f2c
Compare
@obi-wan76 FYI this is a PR that I submitted in December, a simple bite-size standalone minor improvement. |
Huh, this was working in December. Something seems to have broken in the rebase onto current develop. I'll investigate. |
1163f2c
to
fb5ca14
Compare
Updated and improved. This now works as intended to automatically read pixelscales from SIAF, per each aperture, but also to retain the ability for a user to set a custom pixelscale (and have that custom pixelscale not be overwritten by SIAF values). This is now ready for review @obi-wan76 Example: |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #626 +/- ##
===========================================
+ Coverage 55.21% 55.28% +0.07%
===========================================
Files 14 14
Lines 6122 6132 +10
===========================================
+ Hits 3380 3390 +10
Misses 2742 2742
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, I was able to run the example code and some other apertures.
A small improvement in precision: use the measured pixel scale values from on orbit when computing PSFs. This should (slightly) improve the computed PSFs.
Note, this still retains the idealized assumptions of (a) square pixels, same scale in X and Y, and (b) all of NRC, FGS, NIS detectors are precisely unrotated with respect to the OTE V frame. The non-ideal departures from that, as recorded in pysiaf, continue to be handled in the rotation step and distortion model used to make the OVERDIST and DET_DIST extensions 3 and 4.
This also retains the ability to override the pixel scale with a custom value. If the user does this, then that custom value will be retained afterwards even if you switch apertures (i.e. setting a custom pixelscale disables the behavior for auto updating the pixelscale).