IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changeset 3428


Ignore:
Timestamp:
Mar 15, 2005, 2:29:31 PM (21 years ago)
Author:
jhoblitt
Message:

misc. Time cleanups

Location:
trunk/doc/pslib
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/pslib/ChangeLogADD.tex

    r3179 r3428  
    2727  \code{PS_RESAMPLE_LAGRANGE}.
    2828\item Added section on FITS WCS.
     29\item Renamed TDT to TT plus misc. cleanups in the Time section.
    2930\end{itemize}
  • trunk/doc/pslib/psLibADD.tex

    r3213 r3428  
    1 %%% $Id: psLibADD.tex,v 1.63 2005-02-14 21:06:55 eugene Exp $
     1%%% $Id: psLibADD.tex,v 1.64 2005-03-16 00:29:31 jhoblitt Exp $
    22\documentclass[panstarrs]{panstarrs}
    33
     
    783783\subsubsection{Time}
    784784
    785 Correct time representation is critical in astronomical software.
    786 PSLib uses the \code{psTime} structure to represent time values.  This
    787 structure represents a time which is consists of seconds and fractions
    788 of seconds in a time system defined by the \code{psTimeType} element
    789 \code{type}.  Two possible time systems are currently available: TAI
    790 and UTC.  Both are defined in terms of the reference epoch
    791 1970-01-01T00:00:00Z, but with minor modifications for leap seconds as
    792 needed.  The first represenatation, TAI (International Atomic Time),
    793 has seconds of uniform length and no leap seconds.  The exact zero
    794 reference is 1970/01/01,00:00:10 UTC.  The second representation is
    795 UTC, which has seconds of uniform length and leap seconds as needed to
    796 adjust it to remain within 0.9 seconds of the Earth's rotation.  It
    797 has a zero-point of exactly 1970/01/01,00:00:00 UTC.
     785Correct time representation is \emph{critical} in astronomical software.  PSLib
     786uses the \code{psTime} structure to represent time values.  This structure
     787represents a time which is consists of seconds and fractions of seconds in a
     788time system defined by the \code{psTimeType} element \code{type}.  Two possible
     789time systems are currently available: TAI and UTC.  Both are defined in terms
     790of the reference epoch ``1970-01-01T00:00:00Z'', but with minor modifications
     791for leap seconds as needed.  The first represenatation, TAI (International
     792Atomic Time), has seconds of uniform length (SI seconds) and no leap seconds.
     793The exact zero reference is ``1970-01-01T00:00:10Z'' UTC.  The second
     794representation is UTC, which has seconds of uniform length and leap seconds as
     795needed to adjust it to remain within 0.9 seconds of the Earth's rotation.  It
     796has a zero-point of exactly ``1970-01-01T00:00:00Z'' UTC.
    798797
    799798\paragraph{Coordinated Universal Time (UTC)}
     
    803802insertion of leap second whenever UTC-UT1 $\ge$ 0.9s.  By definition
    804803UTC-TAI is an integer number of seconds.  UTC went into effect on
    805 "1972-01-01T00:00:00" and is defined as being TAI-UTC = 10s on that
     804``1972-01-01T00:00:00Z'' and is defined as being TAI-UTC = 10s on that
    806805date.  For dates prior to 1972-01-01 a fixed offset of 10s relative
    807806to TAI will be assumed.
     
    811810\end{equation}
    812811
    813 Leapseconds are declared by the International Earth Rotation and
    814 Reference Systems Service (IERS).  Leapseconds only occur in the UTC
    815 time system and cannot be accurately predicted due to variations in
    816 the Earth's rotational period.  To determine the number of leapsecond
    817 in a given UTC date a table of leapseconds as annouced by the IERS
    818 must be consulted.  This table will have to be updated each time a new
    819 leapsecond occurs.
    820 
    821 For ease of conversion, UTC should be represented as the number of
    822 seconds since the UNIX epoch of "1970-01-01T00:00:00".
     812Leapseconds are declared by the International Earth Rotation and Reference
     813Systems Service (IERS).  Leapseconds only occur in the UTC time system and
     814cannot be accurately predicted due to variations in the Earth's rotational
     815period.  To determine the number of leapsecond in a given UTC date a table of
     816leapseconds as annouced by the IERS must be consulted.  This table will have to
     817be updated each time a new leapsecond occurs.
     818
     819For ease of conversion, UTC should be represented as the number of seconds
     820since the UNIX epoch of ``1970-01-01T00:00:00Z''.  \emph{Times will always be
     821expressed in the 'UTC' timezone.  Use of the local timezone is forbidden.}
    823822
    824823\paragraph{International Atomic Time (TAI)}
     
    982981\end{verbatim}
    983982
    984 $2451545.0$ JD $= 51544.5$ MJD is equivalent to "2000-01-01T00:00:00".
     983$2451545.0$ JD $= 51544.5$ MJD is equivalent to ``2000-01-01T00:00:00Z''.
    985984
    986985\begin{equation}
     
    988987\end{equation}
    989988
    990 \paragraph{Terrestrial Dynamical Time (TDT)}
    991 
    992 Terrestrial Dynamical Time (TDT) is defined as a fixed offset from
    993 TAI.  Its only purpose as far as we are concerned is for its utility
    994 in obtaining the GMST.
    995 
    996 \begin{equation}
    997 {\rm TDT} = {\rm TAI} + 32.184{\rm s}
    998 \end{equation}
    999 
    1000 \paragraph{TDT as Julian Centuries since J2000.0}
    1001 
    1002 The algorithm for calulating GMST requires TDT formated in Julian centruies
     989\paragraph{Terrestrial Time (TT)}
     990
     991Terrestrial Time (TT) is defined as a fixed offset from TAI.
     992
     993\begin{equation}
     994{\rm TT} = {\rm TAI} + 32.184{\rm s}
     995\end{equation}
     996
     997\paragraph{TT as Julian Centuries since J2000.0}
     998
     999The algorithm for calulating GMST requires TT formated in Julian centruies
    10031000since the J2000.0 epoch.
    10041001
    1005 \begin{equation}
    1006 t_u = \frac{{\rm JD}_{\rm TDT} - 2451545.0}{36525}
     1002\begin{equation} t_u = \frac{{\rm JD}_{\rm TT} - 2451545.0}{36525}
    10071003\end{equation}
    10081004
    10091005\paragraph{UT1 as Julian Centuries since J2000.0}
    10101006
    1011 The algorithm for calulating GMST requires UT1 be formated in Julian
    1012 centuries since the J2000.0 epoch.
     1007The algorithm for calulating GMST requires UT1 be formated in Julian centuries
     1008since the J2000.0 epoch.
    10131009
    10141010\begin{equation}
     
    10181014\paragraph{Greenwich Mean Sidereal Time (GMST)}
    10191015
    1020 Greenwich Mean Sidereal Time (GMST) is caclulated from UT1 and TDT.
    1021 This algorithm requires that both time inputs are expressed as Julian
    1022 centuries since J2000.0.
     1016Greenwich Mean Sidereal Time (GMST) is caclulated from UT1 and TT.  This
     1017algorithm requires that both time inputs are expressed as Julian centuries
     1018since J2000.0 \footnote{Expressions to implement the IAU 2000 definition of UT1
     1019- http://www.edpsciences.org/articles//aa/abs/2003/30/aa3487/aa3487.html}.
    10231020
    10241021Here $t_u$ is UT1 expressed in Julian centuries since J2000.0, and $t$
    1025 is TDT expressed in Julian centuries since J2000.0.
     1022is TT expressed in Julian centuries since J2000.0.
    10261023
    10271024\begin{eqnarray}
     
    10341031Gives $GMST00$ in seconds.
    10351032
     1033
    10361034\paragraph{Longitude}
    10371035
     
    10451043\paragraph{Local Mean Sidereal Time (LMST)}
    10461044
    1047 Local Mean Sidereal Time (LMST) is Greenwich Mean Sideral Time (GMST)
    1048 plus the observer's location in East longitude. Calculating LMST
    1049 requires the input of Universal Time (UT1), Terrestrial Dynamical Time
    1050 (TDT) and a longitude (measured East of Greenwich).
     1045Local Mean Sidereal Time (LMST) is Greenwich Mean Sideral Time (GMST) plus the
     1046observer's location in East longitude. Calculating LMST requires the input of
     1047Universal Time (UT1), Terrestrial Dynamical Time (TT) and a longitude (measured
     1048East of Greenwich).
    10511049
    10521050\begin{equation}
Note: See TracChangeset for help on using the changeset viewer.