-
Notifications
You must be signed in to change notification settings - Fork 22
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
RAD-161: Bit Mask to Resample #401
RAD-161: Bit Mask to Resample #401
Conversation
for more information, see https://pre-commit.ci
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #401 +/- ##
=======================================
Coverage 95.38% 95.38%
=======================================
Files 4 4
Lines 195 195
=======================================
Hits 186 186
Misses 9 9 ☔ View full report in Codecov by Sentry. |
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'm curious why is this only in resample? The first input for the good_bits string is in outlier_detection_step. Shouldn't this be in both places? Are the resample good_bits independent of those in outlier detection?
@schlafly @mairanteodoro Can you reply? |
I think @ddavis-stsci is correct; the |
What are you proposing for the additional resample keywords? |
Perhaps |
Thanks Dave, Paul, Mairan. Yes, I agree with Dave & Mairan that we need this. It's a little frustrating because I don't think there are any situations where we would want to allow these keywords to be different, but we do have them as separate steps so we should track them separately. The resample bit is only in the L3 products but the outlier rejection occurs on L2 images. The outlier rejection bit should definitely be optional since we don't intend any of the products we actually archive to have that keyword. The individual image metadata in an L3 file would include it, though, in principle; I don't know if that argues for something about how it is included in the metadata. I think I'd argue for something like meta.outlier_detection.good_bits in the WFI image schema. If we keep this optional, as I think we should, I think we could go ahead and merge this one and make an issue for adding something parallel for outlier detection, since that wouldn't be a schema-breaking change? |
@mairanteodoro and I chatted about this yesterday, and he requested we simply import the whole resample group within outlier detection (as a "sub-folder" named resample), which would be optional. Accordingly, good_bits would come along for the ride. Do you and @ddavis-stsci agree with this approach? |
@PaulHuwe I think we can go with @schlafly's suggestion and have only |
@schlafly @mairanteodoro @ddavis-stsci Another wrinkle: there is no outlier_detection keyword group in RAD. Do we want to make one, or do we want to put its good_bits elsewhere? |
Yes, I'm suggesting adding it parallel to source detection.
…On Wed, Apr 3, 2024, 13:39 Paul Huwe ***@***.***> wrote:
@schlafly <https://github.com/schlafly> @mairanteodoro
<https://github.com/mairanteodoro> @ddavis-stsci
<https://github.com/ddavis-stsci> Another wrinkle: there is no
outlier_detection keyword group in RAD. Do we want to make one, or do we
want to put its good_bits elsewhere?
—
Reply to this email directly, view it on GitHub
<#401 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAK2E4J4XOR66TREWEOQYCLY3Q5EZAVCNFSM6AAAAABFSGWBPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVGIYDEMBQGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
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, @PaulHuwe! Thanks.
My only suggestion is to mention the new outlier detection group in CHANGES.rst.
type: string | ||
propertyOrder: [good_bits] | ||
flowStyle: block | ||
required: [good_bits] |
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.
Just making sure I understand---good_bits is required if outiler_detection is specified, but outlier_detection is not required in wfi_image. I think that's what you've written and that sounds right to me, but just checking!
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.
Correct, that is what I intended with my implementation.
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 RAD-161
Closes #399
This PR adds a bit mask field to resample.
Checklist
CHANGES.rst
under the corresponding subsection