Added code to make st-archive handle DART files #3084
Conversation
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
ekluzek
added
the
next
wwieder
removed
the
next
|
Erik will bring this to b4b-dev |
github-project-automation
bot
moved this to Ready to start (or start again)
in CTSM: Upcoming tags
wwieder
moved this from Ready to start (or start again)
to In progress - b4b-dev
in CTSM: Upcoming tags
|
We should rebase this to b4b-dev and bring it in there. |
ekluzek
added
enhancement
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.
Description of changes
Make st_archive handle compressed (.gz) CLM output files.
Specific notes
This is very helpful for (large multi-instance, multiple short hindcast) data assimilation experiments.
config_archive.xml already handles DART's .e. files.
Contributors other than yourself, if any: none
CTSM Issues Fixed (include github issue #): #3082
Are answers expected to change (and if so in what way)? No
Any User Interface Changes (namelist or namelist defaults changes)? No
Does this create a need to change or add documentation? Did you do so? I don't believe so at this time.
Later it may be useful to add documentation about how DART files are archived, to help users find them.
Testing performed, if any:
I ran a B compset built from the tags in .gitmodules, but no development branches checked out.
I ran st_archive on the output to confirm that it handled all files correctly.
I checked out a feature branch based on master, added the code changes, and pushed to the fork
on kdraeder.
See CIME PR #4788 for details.