Difference between revisions of "ntimes"
m (Text replacement - "ocean.in" to "roms.in") (change visibility) |
|||
| Line 4: | Line 4: | ||
---- | ---- | ||
'''ntimes''' (set by <span class="blue">NTIMES</span> keyword in the [[ | '''ntimes''' (set by <span class="blue">NTIMES</span> keyword in the [[roms.in]] file) is the total number of baroclinic timesteps in the current run. In a strictly barotropic configuration (i.e CPP option [[Options#SOLVE3D|SOLVE3D]] is undefined) '''ntimes''' is the total number of barotropic timesteps. | ||
'''Note that ntimes determines the timestep on which the run will ''end'''''. Be aware that time step counting does not necessarily always start from 1. This could be so if [[ocean_time]] in the initial conditions file is not zero such as when: | '''Note that ntimes determines the timestep on which the run will ''end'''''. Be aware that time step counting does not necessarily always start from 1. This could be so if [[ocean_time]] in the initial conditions file is not zero such as when: | ||
Latest revision as of 15:13, 17 July 2019
- ntimes
- Total number time-steps in current run. If 3D configuration, ntimes is the total of baroclinic time-steps. If only 2D configuration, ntimes is the total of barotropic time-steps.
- option =
- routine = mod_scalars.F
- keyword = NTIMES
- input = roms.in
ntimes (set by NTIMES keyword in the roms.in file) is the total number of baroclinic timesteps in the current run. In a strictly barotropic configuration (i.e CPP option SOLVE3D is undefined) ntimes is the total number of barotropic timesteps.
Note that ntimes determines the timestep on which the run will end. Be aware that time step counting does not necessarily always start from 1. This could be so if ocean_time in the initial conditions file is not zero such as when:
- You restart a crashed run from a Restart or History file
- You chose a reference time for ocean_time that precedes the time range you wish to simulate.
For example, if your forcing file data uses ocean_time = "seconds since 2006-01-01 00:00:00", but you wish only to model the period from 2006-04-01 onward, you would set ocean_time = 7776000 (90 days since 2006-01-01 multiplied by 86400 seconds per day) in the initial conditions netcdf file. For dt of 180 seconds (480 timesteps per day) ntimes = 7776480 would cause the run to conclude on 2006-04-02, i.e. it would only run for 1 day of simulated time. If you set ntimes = 480 thinking this would be 1 day of simulation you will find ROMS will simply end immediately saying it is already done because the end time you requested predates the initial conditions.
However, see dstart for more information on how to shift the internal time keeping in ROMS without upsetting your ocean_time = "seconds since yyyy-mm-dd HH:MM:SS" convention.
