I am wanting to know what to do if I want to restart an ACCESS-CM2 simulation where it left off? Can you use warm restart to do this?
For example you have a run of 10 years beginning in 0951, and I want to restart the model directly following the end can keep generating files the same way (1 year/file).
What will the model basis time be?
What will the restart date be
Restart id/directory will be for the suite that was run for this simulaltion right?
Thanks in advance, and
If the job was successful finished at the year 0960 (ten year run) and you want to extend to run another 10 years, then you can try two steps:
change 10 years to 20 years under your suite ID:
restart the job by using this commend:
rose suite-run --restart
This is the most easy case. But if you want to start a new job based on the finished 10 years job then you will need to again two steps:
same under your rose-suite.conf file:
WARM_RESTART_DIR=‘where your previous 10 years job location is’
WARM_RESTART_RUNID=‘your previous 10 year job ID’
rose suite-run --new
By the way some of my lazy alias:
alias rcgui='rose suite-gcontrol ’ # turn on the RC GUI
alias rcnew='rose suite-run --new ’ # start a new job
alias rcrd='rose suite-run --reload ’ # if you modified anything, you need to reloaded/update to the job
alias rcrg='rose suite-run --reload --no-gcontrol ’ # same as previous one but dont show the GUI
alias rcst='rose suite-run --restart ’ # if the job stop not due to crashed, restart your job
OK thankyou so much for that!
I will try the first option as I am wanting to just extend the run from where I left off after testing the experiment is working as expected.
Before I use
rose suite-run --restart do i need to use the
--reload option that you have written down below in the alias commands?
If I encounter any error with this I will update.
Do you know if there is any difference with how the model works when restarting from the different methods?
No no no please use “rose suite-run --restart”
Those reload commands apply if the job is running, and in case you change the stop date or modify the namelist, then you will need to use the reload option. This will ensure that at the next time step, the job will incorporate the changes you have made. However, this is not applicable to your case.
Those two methods should got identical results.
By the way, Shayne McGrager asked me to use GODAS data, and I found it in your folder. For the sake of my lazinessssssssss , can I just use your data instead of downloading it again?
Thanks so much. I modified the run length and just used the --restart option. It seems to be running with no issues now. Thanks again
Yeah sure please use them if they are useful email or pm me if you need permissions changed. The variables for pottmp, ucur, vcur, dzdt, thflux should all be in