-
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
Add Roman jump detection to ramp fitting #215
Add Roman jump detection to ramp fitting #215
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
Codecov ReportAttention:
📢 Thoughts on this report? Let us know!. |
8a0738e
to
a8a6ab6
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.
This looks good to me. I made a bunch of minor comments. Some summary:
- Let's get rid of all of the _ma_table routines. We only ever need read_pattern; the ma_table pattern was something I made up for the simulator before read_pattern existed, and it doesn't need to continue existing.
- It will be good to see that this matches Sanjib's results, but the current tests look good and I'm optimistic.
- The final test in test_find_jumps would be more convincing if it were phrased in terms of the chi^2/dof. That's slightly annoying in that case since the degrees of freedom are 8 resultants - ~2 flagged - (2, 3, or 4 depending on where the jump landed). But I think it's not that bad and would make for a strong demo that both the ramps and their variances were good.
09e01d9
to
ca58304
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.
This looks great. Two questions:
- Can we modify dq in place? I have been trying to avoid making any new things that are nresultants x npixel in size elsewhere in the pipeline.
- I am missing some bit in one of the tests where I expect some false positives. Are there really none or am I confused?
tests/test_jump_cas22.py
Outdated
|
||
|
||
RNG = np.random.default_rng(619) | ||
ROMAN_READ_TIME = 3.04 |
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.
Really, I just feel like we'd like this to be mission independent, so I think I'm just asking to delete ROMAN_. But obviously this is minor and I don't feel strongly.
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, thanks.
6adb227
to
32f1d78
Compare
de09119
to
0178b75
Compare
1f08368
to
40303d2
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.
not knowing the details of jump detection, lgtm
This PR adds the Roman jump detection to the roman ramp fitting algorithm.
Checklist
CHANGES.rst
(either inBug Fixes
orChanges to API
)