JP-4000: Persistence Flagging for Large Events #423
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves JP-4000
This PR is a first pass at addressing persistence flagging for large events. A persistence flag and an optional persistence file name parameter has been added to the
jump_dataclass in the jump step. With default settings this will not affect the current processing of the jump step.These parameters allow for persistence flagging when the persistence flag is set to
True. If a persistence file name is passed, the file is opened and a 2-Duint8array is retrieved to beor'd into each group. If a file name is not passed, a 2-Duint8array is created and populated from the first integration, which persists through all subsequent integrations.Currently, these changes will not affect
JWSTprocessing and are not accessible from that pipeline. To access these options, theJumpDataclass needs to be directly modified and thejumpfunction inSTCALjumpmodule called.Tests have not been developed, yet.
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>")jwstregression testromancalregression 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