Description
Returns 1 if the input time is within a leap year.
Timing Precision Mode
This page describes functionality in millisecond timing precision mode. Millisecond timing precision mode is deprecated and will be removed in a future release. We recommend that you migrate your Mission Plans to nanosecond timing precision mode.
Click here to see the documentation for this object in nanosecond timing precision mode.
Method Signature
Arguments
time
|
|
Description:
|
The time to consider.
|
Units:
|
day
|
timeSystem
|
|
Description:
|
The system of the time to consider.
|
Valid Values:
|
Value
|
Label
|
"TAI"
|
International Atomic Time
|
"UTC"
|
Coordinated Universal Time
|
"TDT"
|
Terrestrial Dynamical Time
|
"TDB"
|
Barycentric Dynamical Time
|
"UT1"
|
Universal Time Principle Form
|
"GPS"
|
Global Positioning System Time
|
|
timeReference
|
|
Description:
|
The reference of the time to consider.
|
Valid Values:
|
Value
|
Label
|
"Julian Date"
|
Julian Date (Jan 1 4713 BCE 12:00:00.000 TAI)
|
"MJD GSFC"
|
GSFC Modified Julian Date (Jan 05 1941 12:00:00.000 TAI)
|
"MJD USNO"
|
USNO Modified Julian Date (Nov 17 1858 00:00:00.000 TAI)
|
"MJD GPS"
|
GPS Modified Julian Date (Jan 06 1980 00:00:00.000 UTC)
|
"MJD 1950"
|
Besselian Date 1950.0 (Dec 31 1949 22:09:46.862 TAI)
|
|
Return Value
Returns 1 if the input time is within a leap year.
Syntax
myVariable1 = TimeTools.IsInLeapYear(myVariable2, myString1, myString2);
|
See also
TimeUtilities Object
Parsing Dates and Times
|