-
Notifications
You must be signed in to change notification settings - Fork 156
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
JP-3499: Handle too much masked data for NIRISS SOSS extractions in extract_1d #8265
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #8265 +/- ##
==========================================
- Coverage 75.20% 75.15% -0.06%
==========================================
Files 470 470
Lines 38578 38604 +26
==========================================
Hits 29013 29013
- Misses 9565 9591 +26
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…cetelescope#8225) Co-authored-by: Ned Molter <emolter@stsci.edu> Co-authored-by: Howard Bushouse <bushouse@stsci.edu>
…#8187) Co-authored-by: Howard Bushouse <bushouse@stsci.edu>
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.
LGTM
Resolves JP-3499
Closes #8166
This PR addresses a bug that would cause a cryptic ValueError traceback inside the SOSS ATOCA 1-d spectrum extraction for only a few specific integrations out of many on a given target. Bug occurs when the jump step flags the majority of the detector in that integration, such that no valid data exist in the order 2 region. The PR checks for too little overlap between order 2 wavelength space and valid data, and if this is the case, sets all flux values in order 2 to NaN.
Checklist for maintainers
CHANGES.rst
within the relevant release sectionHow to run regression tests on a PR
Jenkins run links full run here ; fixed deploy truthfile, no code changes. soss tests only