gfang2@masonlive_gmu_edu
New Member
Dear All, I would like to save monthly restart files for my control run (CESM1.1.2). I did some tests and browsed the Forums. It seems that people usually do it like this (100-year control run): ./xmlchangeSTOP_OPTION=nmonth,STOP_N=1,RESUBMIT=1200,DOUT_S_SAVE_INT_REST_FILES=TRUE. I tried it and it did work. However, it would stand in the queue for each resubmit, which was very low efficient. I did something to the REST_OPTION and REST_N and it did not work (only yearly restart files): ./xmlchange STOP_OPTION=nmonths,STOP_N=12,RESUBMIT=100,REST_OPTION=nmonth,REST_N=1,DOUT_S_SAVE_INT_REST_FILES=TRUE.
Does it mean that within the continuous 12-month run, the model considers it does not need to save the monthly restart files and only need to save restart files at the end of each job? Thus, should I leave REST_OPTION and REST_N untouched (should be the same value with STOP_OPTION and STOP_N)? If so, why do they put these parameters here?
Is there a standard way to save monthly restart files?
Many thanks!
Does it mean that within the continuous 12-month run, the model considers it does not need to save the monthly restart files and only need to save restart files at the end of each job? Thus, should I leave REST_OPTION and REST_N untouched (should be the same value with STOP_OPTION and STOP_N)? If so, why do they put these parameters here?
Is there a standard way to save monthly restart files?
Many thanks!