Ability to control ncdiag output by iteration number - #240
Merged
Conversation
rtodling
added
the
0 diff
mathomp4
previously approved these changes
Jul 24, 2026
mathomp4
added
0 diff structural
mathomp4
approved these changes
Jul 24, 2026
Contributor
Author
|
Thanks |
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
2 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.
This allows for more flexible control of ncdiags output.
The fact is that these data are typically only used to allow converting GSI obs output to IODA and aid JEDI's development. Having the ability to restrict the writing of ncdiags to say, the first H application, save time and disc space.
Without any loss, the default in the jedi-related RC files is to output ncdiags only for jiter=1.