-
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-3708, JP-3771, JP-3791 #318
JP-3708, JP-3771, JP-3791 #318
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #318 +/- ##
==========================================
+ Coverage 86.38% 86.66% +0.28%
==========================================
Files 49 49
Lines 8899 8934 +35
==========================================
+ Hits 7687 7743 +56
+ Misses 1212 1191 -21 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
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.
Looking good!
Testing on the sample data that failed in #304, I no longer see the processing hang with the optional output + multiprocessing. Optional output looks the same with and without multiprocessing now, and also shows only minor differences from output with the main branch + algorithm = 'OLS'.
Did you run regression tests for jwst and romancal? If so, can you please link them here?
Here is a link to the regression tests I ran on these PRs: https://github.com/spacetelescope/RegressionTests/actions/runs/11820513473 These changes don't effect RomanCal, but I will ask a RomanCal maintainer to run regression tests against these changes. |
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.
Regression tests for jwst look good. Docs are building cleanly now -- thanks for the change notes fix!
I have a couple more minor copy editing suggestions for the change note, but I will approve now, from my perspective. We should still wait to make sure romancal tests are clean.
The romancal regression tests pass and are at |
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 left a few comments - all minor some just for my benefit.
It all seems reasonable to me. There are a lot of changes in the PR.
…p fitting C-extension.
…e problem with segmentation faults and freezes.
…optional results product. Still need to check return value.
…reating the optional results product.
26d7cd5
to
104b8d8
Compare
Resolves JP-3708
Resolves JP-3771
Resolves JP-3791
JP-3708: Add the CRMAG parameter to the optional results product in the C-extension. This wasn't implemented with the C-extension, nor was it properly handled for multiprocessing.
JP-3771: Corrected bugs exposed by adding multiprocessing regression tests to the JWST regression testing suite. The primary bug found was incorrect dimension sizes for internal arrays used for the optional results product. The internal arrays should have dimensions of
(nints, nrows, ncols)
, but they had dimensions(ngroups, nrows, ncols)
. These incorrect dimensions caused memory corruption causing processes to freeze or segfault.JP-3791: Corrected the CHARGELOSS recomputation of the read noise variance. For multiprocessing the DQ flags were not being properly sliced and passed to the C-extension for recomputation.
Tasks
docs/
pageno-changelog-entry-needed
)changes/
:echo "changed something" > changes/<PR#>.<changetype>.rst
(see below for change types)"git+https://github.com/<fork>/stcal@<branch>"
)jwst
regression testromancal
regression testnews fragment change types...
changes/<PR#>.apichange.rst
: change to public APIchanges/<PR#>.bugfix.rst
: fixes an issuechanges/<PR#>.general.rst
: infrastructure or miscellaneous change