NCL Home > Documentation > Functions > Date routines

ut_inv_calendar

Converts a a UT-referenced date to a mixed Julian/Gregorian date.

Prototype

	function ut_inv_calendar (
		year       : integer,  
		month      : integer,  
		day        : integer,  
		hour       : integer,  
		minute     : integer,  
		second     : numeric,  
		units      : string,   
		option [1] : integer   
	)

	return_val [dimsizes(year)] :  double

Arguments

year

An array or scalar integer representing years.

month

An array or scalar integer representing months. Must be same size as year.

day

An array or scalar integer representing days. Must be same size as year.

hour

An array or scalar integer representing hours. Must be same size as year.

minute

An array or scalar integer representing minutes. Must be same size as year.

second

An array or scalar numeric representing seconds. Must be same size as year.

units

A string representing a formatted time unit specification. Valid strings include:

seconds
minutes
hours
days
months
years

The following units qualifiers may also be used:

since
after
from
ref

Examples:

time@units = "days after 0049-09-01 00:00:00"
time@units = "hours ref 1-1-1 00:00:0.0"
time@units = "months from 1-1-1"

option

A scalar integer indicating the format of the output. Not currently used.

Return value

A double array of the same size as year. Contains a units attribute that contains the temporal units.

Description

Converts a a UT-referenced date to a mixed Julian/Gregorian date. To quote the Udunits man page:

The udunits(3) package uses a mixed Gregorian/Julian calendar system. Dates prior to 1582-10-15 are assumed to use the Julian calendar, which was introduced by Julius Caesar in 46 BCE and is based on a year that is exactly 365.25 days long. Dates on and after 1582-10-15 are assumed to use the Gregorian calendar, which was introduced on that date and is based on a year that is exactly 365.2425 days long. (A year is actually approximately 365.242198781 days long.) Seemingly strange behavior of the udunits(3) package can result if a user-given time interval includes the changeover date. For example, ut_calendar and ut_inv_calendar can be used to show that 1582-10-15 *preceded* 1582-10-14 by 9 days.

The following excerpt from the Udunits documentation explains the time@units encoding by example:

    The specification:

        seconds since 1992-10-8 15:15:42.5 -6:00

    indicates seconds  since October 8th, 1992 at 3 hours, 15 minutes and
    42.5 seconds in the afternoon in the time zone which is six hours to
    the west of Coordinated Universal Time (i.e.  Mountain Daylight Time).
    The time zone specification can also be written without a colon using
    one or two-digits.

See Also

ut_calendar

Examples

Example 1

To see how the inverse function ut_inv_calendar works, simply take the output from ut_calendar and plug it back into ut_inv_calendar:

  date = ut_inv_calendar(year,month,day,hour,minute,second,time@units, 0)

The arrays date and time should be identical.