Is your feature request related to a problem? Please describe.
The defaults in config_component.xml are hardcoded to certain values. It would be more useful and general if they were set based on compset and grid. And in some cases if they used other case variables so that the values were more general.
Describe the solution you'd like
I think these should be set to the given case variable:
CUPID_STARTDATE=$RUN_STARTDATE
CUPID_STOP_OPTION=$STOP_OPTION
CUPID_STOP_N=$STOP_N
Then some things can be set according to grid and compset such as:
CUPID_BASELINE_CASE
CUPID_RUN_TYPE
CUPID_RUN_ALL?
Describe alternatives you've considered
I tried setting the values in CTSM in it's config files, but I couldn't get that to work (neither component nor compset)
We can get these things set in shell_commands for our CUPiD user-mod, but it's not as slick or robust
as setting it here.
Setting it here does have the downside of changes that a component needs requires a change to CUPiD. So we should only do this for things that we don't envision changing that often.
Another option would be to set some of these based on the compset period (1850, 2000, HIST etc.) some of the climo settings might lend themselves to being set that way.
Additional context
It's true that users may want to set stop and start options differently from the case. But, a reasonable starting point is to use the case variables. I feel like these settings are generally more useful than the current hardcoded ones.
Is your feature request related to a problem? Please describe.
The defaults in config_component.xml are hardcoded to certain values. It would be more useful and general if they were set based on compset and grid. And in some cases if they used other case variables so that the values were more general.
Describe the solution you'd like
I think these should be set to the given case variable:
CUPID_STARTDATE=$RUN_STARTDATE
CUPID_STOP_OPTION=$STOP_OPTION
CUPID_STOP_N=$STOP_N
Then some things can be set according to grid and compset such as:
CUPID_BASELINE_CASE
CUPID_RUN_TYPE
CUPID_RUN_ALL?
Describe alternatives you've considered
I tried setting the values in CTSM in it's config files, but I couldn't get that to work (neither component nor compset)
We can get these things set in shell_commands for our CUPiD user-mod, but it's not as slick or robust
as setting it here.
Setting it here does have the downside of changes that a component needs requires a change to CUPiD. So we should only do this for things that we don't envision changing that often.
Another option would be to set some of these based on the compset period (1850, 2000, HIST etc.) some of the climo settings might lend themselves to being set that way.
Additional context
It's true that users may want to set stop and start options differently from the case. But, a reasonable starting point is to use the case variables. I feel like these settings are generally more useful than the current hardcoded ones.