I have a case that I have set to resubmit 5 times, writing a restart file at the end of each run:
I'm not absolutely sure that this usage is correct, but it does seem to output what I've intended: a 2-year startup run, followed by five 2-year resubmissions, for a total simulated time of 12 years.
If I clone this case with CIME's
I am then manually performing
for the clones case. I created the clone with the
Is this the intended behavior of
Thanks!
./xmlchange STOP_OPTION=ndays./xmlchange STOP_N = 720./xmlchange REST_OPTION=ndays./xmlchange REST_N=720./xmlchange RESUBMIT=5I'm not absolutely sure that this usage is correct, but it does seem to output what I've intended: a 2-year startup run, followed by five 2-year resubmissions, for a total simulated time of 12 years.
If I clone this case with CIME's
create_clone, I get unexpected behavior. It was my understanding that create_clone should create a case that is identical to the "parent" case in its configuration. I see that all of the options above do indeed match the parent case, except that RESUBMIT = 0.I am then manually performing
./xmlchange RESUBMIT=5for the clones case. I created the clone with the
--keep-exe flag, so I do not rebuild.Is this the intended behavior of
create_clone? Is RESUBMIT intended to be reset to zero? Is it alright to change RESUBMIT without rebuilding the model? If yes, do I need to rerun case.setup or anything else?Thanks!