-
Notifications
You must be signed in to change notification settings - Fork 180
JP-3888: Turn on bright_use_group1 in firstframe; flag any affected pixels #9807
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
f10c511 to
42f8f46
Compare
|
Regression tests: Diffs in the MIRI image and MIRI dark pipeline are because bright_use_group1 is now True by default and there are a handful of pixels that are affected by the change. I looked into why there are many more diffs in the pixeldq than in the groupdq for the MIRI image diffs. It looks like in nearly all cases, the DO_NOT_USE bit was already set for pixels affected by the bright_use_group1 parameter, for other reasons. For this test exposure, there are 174 pixels now marked FLUX_ESTIMATED, but only 9 of them were not already DO_NOT_USE in the pixeldq image. Since this is an informational flag, I think it's still probably useful to apply the flag to all pixels that qualify, regardless of whether or not they'll eventually be used, but let me know if anyone thinks differently. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9807 +/- ##
==========================================
+ Coverage 83.38% 83.41% +0.03%
==========================================
Files 366 366
Lines 37770 37786 +16
==========================================
+ Hits 31493 31520 +27
+ Misses 6277 6266 -11 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
jemorrison
left a comment
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.
This look fine. I have no suggestions.
42f8f46 to
2593cc7
Compare
|
Updated regtests for okifying: |
tapastro
left a comment
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!
Resolves JP-3888
Turn on bright_use_group1 by default for the firstframe step. Also, flag any affected pixels in the pixeldq image with the FLUX_ESTIMATED flag.
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_regteststo update the truth files