-
Notifications
You must be signed in to change notification settings - Fork 32
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-3448: Always flag at least one group when showers are detected #237
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #237 +/- ##
==========================================
+ Coverage 85.94% 85.98% +0.04%
==========================================
Files 35 35
Lines 6523 6542 +19
==========================================
+ Hits 5606 5625 +19
Misses 917 917 ☔ View full report in Codecov by Sentry. |
based on suggestion Co-authored-by: Howard Bushouse <[email protected]>
uses suggestion Co-authored-by: Howard Bushouse <[email protected]>
addressed comments in PR
…ays_flag_one_shower_grp
I tried fixing obvious errors (like mismatching argument names) to get this PR to pass CI tests, but it's still failing CI's with both differences in unit test results and a real error "UnboundLocalError: cannot access local variable 'total_showers' where it is not associated with a value". So something still needs fixing in the basic code. |
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 now and all CI tests are passing.
Resolves JP-3448
Closes spacetelescope/jwst#8030
This PR addresses the problem that the shower flagging is not including the flagging of the primary shower as a minimum. The code was updated to match the input parameter which is the time to flag groups after the primary shower. The current default values and code lead to no flagging in MIRI slow mode.
Checklist
CHANGES.rst
(either inBug Fixes
orChanges to API
)