Dear all,I'm using CESM1_1 and would like to continue a run (compset: F_AMIP_CAM5), but add additional variables to the output. If I add them to fincl in user_nl_cam, they are listed successfully in atm_in, but the new model output only contains the variables that were already present in the exiting run. How then do I add variables to the output of a continuation run? thanks!AndreasNCAR HAO / CU Aerospace Engineering Sciences
Continuation runs: adding output variables to fincl / user_nl_cam
- Thread starter andreasb
- Start date
YOu can add extra variables in a continuation run. You need to do a branch run. You can keep the same name as you original run (if you want) by setting BRNCH_RETAIN_CASENAME to TRUE. Basically, if you have a case called case01 that is 10 years long and you want to add extra output after this, you do: ./xmlchange -file env_run.xml -id RUN_TYPE -val branch
./xmlchange -file env_run.xml -id RUN_REFCASE -val case01
./xmlchange -file env_run.xml -id RUN_REFDATE -val 0011-01-01
./xmlchange -file env_run.xml -id BRNCH_RETAIN_CASENAME -val 'TRUE'
./xmlchange -file env_run.xml -id RUN_REFCASE -val case01
./xmlchange -file env_run.xml -id RUN_REFDATE -val 0011-01-01
./xmlchange -file env_run.xml -id BRNCH_RETAIN_CASENAME -val 'TRUE'
YOu can add extra variables in a continuation run. You need to do a branch run. You can keep the same name as you original run (if you want) by setting BRNCH_RETAIN_CASENAME to TRUE. Basically, if you have a case called case01 that is 10 years long and you want to add extra output after this, you do: ./xmlchange -file env_run.xml -id RUN_TYPE -val branch
./xmlchange -file env_run.xml -id RUN_REFCASE -val case01
./xmlchange -file env_run.xml -id RUN_REFDATE -val 0011-01-01
./xmlchange -file env_run.xml -id BRNCH_RETAIN_CASENAME -val 'TRUE'
./xmlchange -file env_run.xml -id RUN_REFCASE -val case01
./xmlchange -file env_run.xml -id RUN_REFDATE -val 0011-01-01
./xmlchange -file env_run.xml -id BRNCH_RETAIN_CASENAME -val 'TRUE'
Thanks! Just adding this for future reference of other forum users:It appears that CONTINUE_RUN takes precedence over RUN_TYPE, so one more xmlchange appears to be required if the reference case is a "continued" run:./xmlchange -file env_run.xml -id CONTINUE_RUN -val 'FALSE'
Thanks! Just adding this for future reference of other forum users:It appears that CONTINUE_RUN takes precedence over RUN_TYPE, so one more xmlchange appears to be required if the reference case is a "continued" run:./xmlchange -file env_run.xml -id CONTINUE_RUN -val 'FALSE'
Hello Andreas,What I would have recommended (and what I think Cécile intended to recommend) would be to create a *new* case, which branches from the original.Simply changing the original case to a branch of itself, and setting CONTINUE_RUN=FALSE, seems like it should have the same effect in most cases. But I can imagine that it might cause problems if you're not careful. I don't think that we test the scripts in such a way as to guarantee that there wouldn't be a glitch if you switch the RUN_TYPE halfway through...
Hello Andreas,What I would have recommended (and what I think Cécile intended to recommend) would be to create a *new* case, which branches from the original.Simply changing the original case to a branch of itself, and setting CONTINUE_RUN=FALSE, seems like it should have the same effect in most cases. But I can imagine that it might cause problems if you're not careful. I don't think that we test the scripts in such a way as to guarantee that there wouldn't be a glitch if you switch the RUN_TYPE halfway through...