-
Notifications
You must be signed in to change notification settings - Fork 171
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-3667: Add safeguards for NSClean on background/imprint members #8809
JP-3667: Add safeguards for NSClean on background/imprint members #8809
Conversation
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 pending regression tests showing no unexpected failures
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #8809 +/- ##
==========================================
+ Coverage 61.76% 61.78% +0.02%
==========================================
Files 377 377
Lines 38785 38836 +51
==========================================
+ Hits 23955 23996 +41
- Misses 14830 14840 +10 ☔ View full report in Codecov by Sentry. |
05d209e
to
701573c
Compare
701573c
to
9c68fc3
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.
LGTM as well, sorry I missed this on the last one.
My fault, trying to do too many things too fast! Thanks for reviewing. |
Regression tests look good. I will merge when CI is complete. |
Resolves JP-3667
Follow up to #8786 to fix some unexpected interactions between badpix_selfcal and nsclean, causing a failure in the badpix_selfcal regression tests. If badpix_selfcal is run, the background members are datamodels instead of filenames.
I also noticed in testing this that setting the output file for nsclean on the background/imprint members caused them to be saved by default, so I added a check for that as well.
Tasks
Build 11.3
(use the latest build if not sure)CHANGES.rst
within the relevant release section (otherwise add theno-changelog-entry-needed
label to this PR)docs/
pageokify_regtests
to update the truth files