I have created a CIME case, which has been setup and built. As I understand, the namelist files user_nl_xxxx can be edited post-build. If I want to vary a namelist setting X across several runs, I can do that by
1) Running CESM
2) editing X=... in user_nl_xxxx
3) Run again
Two problems...
1) this will overwrite the output of the first run unless I manually intervene
2) I cannot do this in the event that jobs 1) and 3) are being submitted to a queueing system, unless I awkwardly wait to edit user_nl_xxxx until after job 1) has begun running
It would make sense if a particular case build were *not* uniquely associated with a particular namelist file and output directory, so that runs with new namelist choices can be executed without needing to either (a) duplicate the entire case or (b) manually supervise the jobs and move files around
Is there a way to specify at execution custom namelist file locations and desired output location of a run? As far as I can tell, the expectation that the namelist files take precisely the form user_nl_xxxx, where xxxx is a known component, is hard-coded, as well as the location of the output directory. Though the ability to "plug and play" with different user_nl_xxxx files seems like a common use-case. Specifically, I am trying to do this with user_nl_cam.
1) Running CESM
2) editing X=... in user_nl_xxxx
3) Run again
Two problems...
1) this will overwrite the output of the first run unless I manually intervene
2) I cannot do this in the event that jobs 1) and 3) are being submitted to a queueing system, unless I awkwardly wait to edit user_nl_xxxx until after job 1) has begun running
It would make sense if a particular case build were *not* uniquely associated with a particular namelist file and output directory, so that runs with new namelist choices can be executed without needing to either (a) duplicate the entire case or (b) manually supervise the jobs and move files around
Is there a way to specify at execution custom namelist file locations and desired output location of a run? As far as I can tell, the expectation that the namelist files take precisely the form user_nl_xxxx, where xxxx is a known component, is hard-coded, as well as the location of the output directory. Though the ability to "plug and play" with different user_nl_xxxx files seems like a common use-case. Specifically, I am trying to do this with user_nl_cam.