-
Notifications
You must be signed in to change notification settings - Fork 177
Fix logging message in NIRSpec assign_wcs and turn all invalid interval warning into error #9412
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
Fix logging message in NIRSpec assign_wcs and turn all invalid interval warning into error #9412
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9412 +/- ##
=======================================
Coverage 75.63% 75.63%
=======================================
Files 368 368
Lines 36900 36900
=======================================
Hits 27908 27908
Misses 8992 8992 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Note to self:
|
For the logging message - I think we want the original message to stay as it is, for its primary use in assign_wcs. We just want the messages from msa_flagging to say something different. I was envisioning something like temporarily turning off the log while calling the assign_wcs function, and separately logging the total number of failed open shutters. |
Thanks for the clarification, @melanieclarke . What about the side discussion on "Invalid interval"? Should I ignore that for now or you want that fixed in the same PR? |
Let's go ahead and get that fixed too. |
5a32d08
to
ab437d9
Compare
ab437d9
to
170ec57
Compare
3f7f196
to
1fc83a9
Compare
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.
I think this looks good now, thanks!
Can you please add a change log, though? This will change the user-facing logs and addresses a long-standing request for the pipeline, so I think it's worth noting.
Capture log and emit different message and catch RuntimeWarning.
for these tests
c35c549
to
87cd18e
Compare
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.
Latest regtests are clean. Thanks!
Resolves JP-3932
This PR addresses #3116
I don't think this needs a change log?
Tasks
Build 12.0
(use the latest build if not sure)no-changelog-entry-needed
)changes/
:echo "changed something" > changes/<PR#>.<changetype>.rst
(see changelog readme for instructions)docs/
pageokify_regtests
to update the truth files