...
Conversely, if you don't want to run a restart but want to repeat the run, do delete the rcf file (and the srf files). If you don't the model will attempt to continue the run according to the namelist in the rcf file.
How to use a specific restart
This can be done by careful editing of the NAMELIST NAMRCF contained in the 'rcf' file and best explained by an example. In order to restart successfully you must have all the restart files for the model tasks; there is one restart file per task.
Suppose the model has been run for two hours and a restart created every hour (say at T21 with a 10min timestep). The model will write out restart files with names:
srf00000100.0001 and srf00000200.0001 (the format is srf<day:dddddd><hour:hh><min:mm>).
The file 'rcf' will always refer to the latest restart. The top of the file looks like:
| Code Block |
|---|
&NAMRCF
CSTEP=" 12",
CTIME="00000200 ",
|
In this case '12' is the number of timesteps at which the restart was written and 'CTIME' refers to the string following the 'srf' part of the restart filename. In this case, it means 2hrs (12 steps x 10min timestep).
Edit this file to look like:
| Code Block |
|---|
&NAMRCF
CSTEP=" 6",
CTIME="00000100 ",
|
and rerun the model. It will now start from timestep '6' and look for files called 'srf00000100' to restart
...
from.
Note:
- if restarting from an earlier restart, the model will overwrite any existing output and restart files for the subsequent timesteps.
- always keep the 'rcf' and 'srf' files together. The rcf namelist contains important information about the grid decomposition and mass fixes to ensure an exact restart.
Model code
The key subroutines for restarts are:
...