The namelist responsible for determining the start and end of a cycle for NEMO is namelist_cfg, where the important parameters are
To convert the timesteps into model time, you need to determine how many timesteps there are per day. There are a few ways you can do this. One is if you know the dump cycle is 10 days, which is usually is, then divide the value of nn_write by 10. For ORCA1 this probably gives 320 / 10 = 32 timesteps per day (a 45 minute timestep). The equations for nn_it000 and nn_itend are therefore
nn_it000 = (days since start) * (timesteps per day) + 1
and
nn_itend = (days since start + cycle length in days) * (timesteps per day)
The submission scripts calculate the value of nn_it000 and nn_itend by taking the namelist from last successful cycle which is archived at share/data/History_Data/NEMOhist/namelist_cfg, and our new nn_it000 is calculated by adding 1 to the value of nn_itend in the archived namelist_cfg. The new nn_itend is calculated by adding the number of timesteps for a complete cycle (calculated using TASKLENGTH from rose suite) to the archived nn_itend.
The UM read the history file, share/data/History_Data/<job id>.xhist, to determine the dump to start from and runs until it reaches run_target_end, where run_target_end is set in the rose-suite using the variable TASKEND.
I've been getting a number of crashes in MPI_Finalize and I've asked Yongming for instructions for restarting.