POSTPROC_HIST fix; change EXPDIR to absolute path #42
Conversation
This file contains 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
|
All tests passed. |
gmao-rreichle
changed the title
gmao-rreichle
approved these changes
May 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR addresses issues with POSTPROC_HIST options 1 and 2, reported by @stefanocasirati and @gmao-jkolassa.
In a nutshell, POSTPROC_HIST did not finish properly. One reason may have been a confusion of relative and absolute paths after user edits of lenkf.j after ldas_setup. Another reason may be increased execution times for POSTPROC_HIST on NCCS/Discover.
cc: @biljanaorescanin