Open ingridc2051 opened 1 month ago
Before this PR can be opened up for review and merged in:
generate_cupid_config.py
needs to under version control (probably in CUPiD?)tools/CUPiD
?)case.cupid
from the template instead of .case.cupid
A second PR to make CUPiD more usable would include
RUN_CUPID_ANALYSIS
flag to env_run.xml
(default FALSE
)case.cupid
to the default workflow, dependent on DOUT_S
and RUN_CUPID_ANALYSIS
both being true@jedwards4b What controls whether template.cupid
becomes case.cupid
(visible) or .case.cupid
(hidden)? It's currently the latter, but I think we want it to be visible?
I think that case.st_archive might be a hardcoded special case in the python - I'll look at the code tomorrow and let you know.
In utils.py at line 2533. I think that we should remove that and make it an option in the config_workflow.xml file instead.
Cool, I'll make do with the file being hidden for now but we can talk about what it would look like to add a hide_script
option to config_workflow.xml
and then let CIME's get_batch_script_for_job()
depend on that. I assume we'd want the default to be True
and case.st_archive
(and case.cupid
) would set it to False
?
Create a new workflow to allow users to run CUPiD after the short-term archiver.