Add RUN_POSTPROCESSING variable to env_run.xml #537
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
This variable will be FALSE by default, but setting it to TRUE will (eventually) run some postprocessing scripts as part of the default workflow. In that respect, its behavior will be similar to how DOUT_S controls the short-term archiver.
jedwards4b
approved these changes
Feb 4, 2025
This was referenced Feb 11, 2025
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
A new variable named
RUN_POSTPROCESSINGhas been added toenv_run.xml. This variable will beFALSEby default, but setting it toTRUEwill (eventually) run some postprocessing scripts as part of the default workflow. In that respect, its behavior will be similar to howDOUT_Scontrols the short-term archiver.This is part of the CESM push to add CUPiD to the CESM workflow. @rljacob asked that we keep the name generic (so this is not
RUN_CUPID_ANALYSIS😄), and the CUPiD team is definitely willing to change this to something else. It's not entirely clear that CMEPS is the best place to define this variable, as it stands it will show up inenv_case.xmlfor all models using CMEPS but setting it toTRUEwon't do anything in any of them except CESM.Specific notes
Contributors other than yourself, if any: @TeaganKing @billsacks @jedwards4b and @ekluzek all contributed during a recent hackathon
CMEPS Issues Fixed (include github issue #): N/A
Are changes expected to change answers? bfb
Any User Interface Changes (namelist or namelist defaults changes)? None
Testing performed
Please describe the tests along with the target model and machine(s)
If possible, please also added hashes that were used in the testing