-
Notifications
You must be signed in to change notification settings - Fork 174
JP-1793: Standardize wfs_combine Step #6376
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-1793: Standardize wfs_combine Step #6376
Conversation
Codecov Report
@@ Coverage Diff @@
## master #6376 +/- ##
==========================================
+ Coverage 77.60% 77.65% +0.04%
==========================================
Files 408 408
Lines 34881 34941 +60
==========================================
+ Hits 27068 27132 +64
+ Misses 7813 7809 -4
*This pull request uses carry forward flags. Click here to find out more.
Continue to review full report at Codecov.
|
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
I am presuming the stpipe
issue will need to be implemented before this is merged? Has an issue been filed against stpipe
and is it linked to jp-1793?
The stpipe issue does need to be in first, as this uses the new Step.output_use_format parameter. I've tried to dot my github i's and cross the JIRA t's, but I'm not sure the linking of the stpipe issue to JP-1793 has gone through - I may need another link somewhere? The stpipe issue is here and the PR here |
* flake8 * name the model not the container * Allow for ModelContainer as input * might as well output a ModelContainer instead of a list of models? not sure * stpipe changed new Step parameter name
Closes #5511
Resolves JP-1793
Description
This PR addresses issues with the Step/Pipeline identity crisis that calwebb_wfs-image3 - err, wfs_combine - found itself in.
The step now uses datamodels.open() instead of load_as_level3_asn() - this should allow the step to take a ModelContainer as input, though the formatting will need to follow the level 3 associations, i.e. presence of member pairs under products, expnames provided, etc. Documentation might be on the to-do list to make this clear...
The step now follows a more traditional structure for saving results, though this requires an stpipe PR to be merged that allows for Step instances to access the save_model(format=...) parameter.
Checklist