ntimes - Revision history

Robertson: Text replacement - "ocean.in" to "roms.in"

2019-07-17T15:13:43Z

Text replacement - "ocean.in" to "roms.in"

← Older revision		Revision as of 15:13, 17 July 2019
Line 4:		Line 4:
	----		----

	'''ntimes''' (set by <span class="blue">NTIMES</span> keyword in the [[~~ocean~~.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.		'''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:

Wilkin at 13:02, 20 August 2015

2015-08-20T13:02:22Z

← Older revision		Revision as of 13:02, 20 August 2015
Line 13:		Line 13:


	However, see [[~~Variables#dstart\|~~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.		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.

Robertson at 19:26, 31 March 2008

2008-03-31T19:26:48Z

← Older revision		Revision as of 19:26, 31 March 2008
Line 1:		Line 1:
	<div class="title">ntimes</div>		<div class="title">ntimes</div>
			{{#lst:Variables\|ntimes}}

			----

	'''ntimes''' (set by <span class="blue">NTIMES</span> keyword in the [[ocean.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.		'''ntimes''' (set by <span class="blue">NTIMES</span> keyword in the [[ocean.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.

Robertson at 19:12, 31 March 2008

2008-03-31T19:12:07Z

← Older revision		Revision as of 19:12, 31 March 2008
Line 1:		Line 1:
	= ~~NTIMES =~~		<div class="title">ntimes</div>

	NTIMES 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.		'''ntimes''' (set by <span class="blue">NTIMES</span> keyword in the [[ocean.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:
			:# 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.

	(1) ~~You restart a crashed~~ run ~~from a Restart or History file~~		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 [[Variables#dt\|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.

	(2) You chose a reference time for [[ocean_time]] that preceeds 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 becuase 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.		However, see [[Variables#dstart\|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.

Robertson: NTIMES moved to ntimes: We are listing these under variable names not .in keywords

2008-03-31T18:36:44Z

NTIMES moved to ntimes: We are listing these under variable names not .in keywords

← Older revision	Revision as of 18:36, 31 March 2008
(No difference)

Wilkin: /* NTIMES */

2006-12-14T14:59:07Z

NTIMES

← Older revision		Revision as of 14:59, 14 December 2006
Line 1:		Line 1:
	= NTIMES =		= NTIMES =

	NTIMES		NTIMES 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.
	NTIMES determines the timestep on which the run will '''~~end~~'''. This is ~~an important distinction~~
			'''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:

			(1) You restart a crashed run from a Restart or History file

			(2) You chose a reference time for [[ocean_time]] that preceeds 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 becuase 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.

Wilkin: /* NTIMES */

2006-12-14T14:28:55Z

NTIMES

← Older revision		Revision as of 14:28, 14 December 2006
Line 1:		Line 1:
	= NTIMES =		= NTIMES =

	~~There are several user posting about time keeping in ROMS~~ on the ~~User Forum at http://marine.rutgers.edu/po/users/forum/viewtopic~~.~~php?t=69~~		NTIMES
			NTIMES determines the timestep on which the run will '''end'''. This is an important distinction

Wilkin at 14:26, 14 December 2006

2006-12-14T14:26:15Z

New page

= NTIMES =

There are several user posting about time keeping in ROMS on the User Forum at http://marine.rutgers.edu/po/users/forum/viewtopic.php?t=69