-
Notifications
You must be signed in to change notification settings - Fork 174
JP-488 and JP-1920: NIRSpec bounding_box
is sometimes too large.
#6257
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
Conversation
f59f65c
to
8d31ab3
Compare
Codecov Report
@@ Coverage Diff @@
## master #6257 +/- ##
==========================================
- Coverage 76.68% 75.74% -0.94%
==========================================
Files 405 405
Lines 35330 37483 +2153
==========================================
+ Hits 27093 28393 +1300
- Misses 8237 9090 +853
*This pull request uses carry forward flags. Click here to find out more.
Continue to review full report at Codecov.
|
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 left some minor comments, mostly to clean and clarify the code.
Co-authored-by: Nadia Dencheva <nadia.astropy@gmail.com>
7910ed8
to
1c94d55
Compare
…pacetelescope#6257) * Using, `slit2detector.inverse` to narrow `bounding_box` range. * Updated inverse call to fit actual inverse interface. * Tried to solve the inverse issues. * Brute force y_range * Added padding to y coords * Fixed bug when guessed bounding_box ranges are bad. * Fixed broken test * Updated change log. * Apply suggestions from code review Co-authored-by: Nadia Dencheva <nadia.astropy@gmail.com> * Removed commented lines. Co-authored-by: Nadia Dencheva <nadia.astropy@gmail.com>
Closes #5736
Closes #2958
Resolves JP-488 and JP-1920
Description
The
bounding_box
for NIRSpec is sometimes significantly oversized in height (y
direction). This was because the~jwst.assign_wcs.compute_bounding_box
was very naive in how it computed the range of acceptabley
values. The changes here take the bounding box "guessed" by this naive method and evaluate the transform, and then finds the exact bounds of where the spectral trace actually lands (the non-NaN values). These bounds are then used to compute an improved bounding box.Checklist