Repository navigation
Update to ensemble increment postprocessing: make all options optional - #1262
Merged
Merged
Conversation
Collaborator
|
I'm surprised you are able to make a PR; Github is having issues all morning. I can't even see branches or the changes proposed in PRs.. Can't even use emojis :( |
Collaborator
Author
|
I know, I think this is literally the only thing that worked for me this morning. |
Dooruk
approved these changes
Aug 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
On develop, ensemble increment postprocessing always requires having steric height adjustment in the yaml. It's convenient, however, to have all options for increment postprocessing optional, so one e.g. can just set bounds to temperature/salinity and not adjust steric height. This PR makes all options optional.
Checklist