C-20
The second time scale is Universal Time (UT1), which is based on the rotation of the Earth.
It is needed for computing sidereal time [sidereal_time] or the Earth Rotation Angle (ERA or
θ) [era], which in turn allows one to compute hour angles, altitude and azimuth, or other
topocentric quantities. UT1 is also obtained from UTC: UT1 = UTC + (UT1−UTC). The
value of UT1−UTC is available in a daily-interval tabulation on the IERS web site
13
Bulletin B
(data
marked “P” are predictions); IERS publishes historical values in .
14
A few of the lower-level NOVAS functions use time arguments based on Barycentric
Dynamical Time (TDB). [
The values of
UT1−UTC often change at the millisecond level over one day. In computing the topocentric
direction of a celestial object with respect to Earth-fixed axes (e.g., altitude and azimuth),
1-arcsecond accuracy in the final angles requires 67-ms accuracy in UT1. Because
UT1−UTC can have an absolute value up to 900 ms, it is an important correction for all but
the crudest applications; that is, in most cases, it is not acceptable to approximate UT1 as
being equal to UTC.
e_tilt, precession, ephemeris, solarsystem] TDB differs from TT
only by periodic variations (due mainly to the Earth’s elliptical orbit and described by
General Relativity), the largest of which has an amplitude of 1.6 ms and a period of one year.
[tdb2tt] The difference between the two time scales can often be neglected in practice as
noted in the function preambles where appropriate. TDB is equivalent to T
eph
,
the barycentric
coordinate time argument of the Jet Propulsion Laboratory (JPL) planetary and lunar
ephemerides.
As previously mentioned, time is specified within NOVAS as Julian dates, which can be used
for any of the above time scales. Julian dates are a simple count of days since noon on 4713
BC January 1, so that any date in recorded human history has a positive JD. Over 2.4 million
days have elapsed since JD 0, and thus, for current dates, seven digits of precision are taken
up just by the day count; if the JD is given by a standard double-precision floating-point
number, about 9 digits are left to represent the time of day. Therefore, we expect a double-
precision floating-point JD can represent time to a precision of about 10
-9
day ≈ 100 μs.
However, after further examination, Kaplan, Bartlett, and Harris (2011) determined that the
actual precision is closer to 20.1 μs. In those NOVAS functions where more precision is
appropriate, the JD can be split between two input arguments, one that carries the high-order
part of the JD (e.g., the day count) and the other that carries the low-order part (e.g., the
fraction of a day). Note that for 0h (TT, UT1, or TDB), the fractional part of the Julian date
is 0.5. An online calendar-date-to-Julian-date converter is available at the AA Department
web site.
15
The epoch J2000.0 is considered to be an event at the geocenter at Julian date 2451545.0 TT,
which is 2000 January 1, 12h TT.
NOVAS has utility functions to convert between calendar date and Julian date
and vice versa. They work for any time scale; that is, their input and output arguments should
be considered to be just different ways of expressing the same instant within the same time
scale. [julian_date, cal_date]
13
http://maia.usno.navy.mil/ser7/mark3.out
14
http://www.iers.org/IERS/EN/Publications/Bulletins/bulletins.html
15
http://www.usno.navy.mil/USNO/astronomical-applications/data-services/cal-to-jd-conv