time ref - Revision history

Robertson at 20:46, 24 February 2020

2020-02-24T20:46:32Z

← Older revision		Revision as of 20:46, 24 February 2020
Line 26:		Line 26:
	units = "seconds since 0000-01-01 00:00:00"		units = "seconds since 0000-01-01 00:00:00"

	There are several user postings about time keeping in ROMS on the [http://~~marine~~.~~rutgers~~.~~edu/po/users~~/forum/viewtopic.php?t=69 User Forum]		There are several user postings about time keeping in ROMS on the [http://www.myroms.org/forum/viewtopic.php?t=69 User Forum]

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

2019-07-17T15:13:48Z

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

← Older revision		Revision as of 15:13, 17 July 2019
Line 8:		Line 8:
	For so-called realistic applications where the model time corresponds to a certain calendar date, '''time_ref''' will be a floating point number > 0 in the format (yyyymmdd.f)		For so-called realistic applications where the model time corresponds to a certain calendar date, '''time_ref''' will be a floating point number > 0 in the format (yyyymmdd.f)

	For example, setting <span class="blue">TIME_REF</span>=20020115.5 in your [[~~ocean~~.in]] will yield the following [http://www.cgd.ucar.edu/cms/eaton/cf-metadata/CF-1.0.html CF-Comliant] time units attribute:		For example, setting <span class="blue">TIME_REF</span>=20020115.5 in your [[roms.in]] will yield the following [http://www.cgd.ucar.edu/cms/eaton/cf-metadata/CF-1.0.html CF-Comliant] time units attribute:

	units = "seconds since 2002-01-15 12:00:00"		units = "seconds since 2002-01-15 12:00:00"

Robertson at 19:46, 31 March 2008

2008-03-31T19:46:11Z

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

			----

	Reference time used to define the "units" attribute written to the output netcdf files.		Reference time used to define the "units" attribute written to the output netcdf files.

	For so-called realistic applications where the model time corresponds to a certain calendar date, ~~TIME_REF~~ will be a floating point number > 0 in the format (yyyymmdd.f)		For so-called realistic applications where the model time corresponds to a certain calendar date, '''time_ref''' will be a floating point number > 0 in the format (yyyymmdd.f)

	For example, TIME_REF=20020115.5 will yield the following ~~CF-compliant~~ [http://www.cgd.ucar.edu/cms/eaton/cf-metadata/CF-1.0.html] time units attribute:		For example, setting <span class="blue">TIME_REF</span>=20020115.5 in your [[ocean.in]] will yield the following [http://www.cgd.ucar.edu/cms/eaton/cf-metadata/CF-1.0.html CF-Comliant] time units attribute:

	units = "seconds since 2002-01-15 12:00:00"		units = "seconds since 2002-01-15 12:00:00"

	There are some default special values for TIME_REF:		There are some default special values for <span class="blue">TIME_REF</span>:

	If TIME_REF = -2, model time and DSTART are in modified Julian		If <span class="blue">TIME_REF</span> = -2, model time and [[dstart\|DSTART]] are in modified Julian days units. The "units" attribute becomes:
	days units. The "units" attribute becomes:

	units = "since 1968-05-23 00:00:00 GMT:		units = "since 1968-05-23 00:00:00 GMT:

	If TIME_REF = -1, model time and DSTART are in a calendar		If <span class="blue">TIME_REF</span> = -1, model time and [[dstart\|DSTART]] are in a calendar with 360 days in every year (30 days each month). The "units" attribute is:
	with 360 days in every year (30 days each month). The "units"
	attribute is:

	units = "seconds since 0000-01-01 00:00:00"		units = "seconds since 0000-01-01 00:00:00"

	If TIME_REF = 0, model time and DSTART are in a common year		If <span class="blue">TIME_REF</span> = 0, model time and [[dstart\|DSTART]] are in a common year calendar with 365.25 days. The "units" attribute is:
	calendar with 365.25 days. The "units" attribute is:

	units = "seconds since 0000-01-01 00:00:00"		units = "seconds since 0000-01-01 00:00:00"

			There are several user postings about time keeping in ROMS on the [http://marine.rutgers.edu/po/users/forum/viewtopic.php?t=69 User Forum]
	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

Robertson: TIME REF moved to time ref: We are listing these under variable names not .in keywords

2008-03-31T19:36:36Z

TIME REF moved to time ref: We are listing these under variable names not .in keywords

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

Wilkin: /* TIME_REF */

2006-12-14T14:29:28Z

TIME_REF

← Older revision		Revision as of 14:29, 14 December 2006
Line 26:		Line 26:

	units = "seconds since 0000-01-01 00:00:00"		units = "seconds since 0000-01-01 00:00:00"


			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

Wilkin at 16:25, 11 December 2006

2006-12-11T16:25:16Z

New page

= TIME_REF =

Reference time used to define the "units" attribute written to the output netcdf files.

For so-called realistic applications where the model time corresponds to a certain calendar date, TIME_REF will be a floating point number > 0 in the format (yyyymmdd.f)

For example, TIME_REF=20020115.5 will yield the following CF-compliant [http://www.cgd.ucar.edu/cms/eaton/cf-metadata/CF-1.0.html] time units attribute:

units = "seconds since 2002-01-15 12:00:00"

There are some default special values for TIME_REF:

If TIME_REF = -2, model time and DSTART are in modified Julian
days units. The "units" attribute becomes:

units = "since 1968-05-23 00:00:00 GMT:

If TIME_REF = -1, model time and DSTART are in a calendar
with 360 days in every year (30 days each month). The "units"
attribute is:

units = "seconds since 0000-01-01 00:00:00"

If TIME_REF = 0, model time and DSTART are in a common year
calendar with 365.25 days. The "units" attribute is:

units = "seconds since 0000-01-01 00:00:00"