Changeset 1771 for trunk/doc/pslib/psLibADD.tex
- Timestamp:
- Sep 9, 2004, 2:40:42 PM (22 years ago)
- File:
-
- 1 edited
-
trunk/doc/pslib/psLibADD.tex (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/pslib/psLibADD.tex
r1760 r1771 1 %%% $Id: psLibADD.tex,v 1.4 5 2004-09-09 20:17:05price Exp $1 %%% $Id: psLibADD.tex,v 1.46 2004-09-10 00:40:42 price Exp $ 2 2 \documentclass[panstarrs]{panstarrs} 3 3 … … 880 880 881 881 882 883 882 \paragraph{Universal Time (UT1)} 884 883 \label{sec:ut1} … … 888 887 from UT0 which does not involve corrections for polar motion. UT1 may 889 888 be calculated from UTC through a table lookup of the appropriate value 890 of UTC - UT1 (\S\ref{sec:tables}).889 of UTC - UT1. 891 890 892 891 \paragraph{Julian Day and Modified Julian Day} … … 982 981 The polar coordinates, $x_p$ and $y_p$, required for \code{SLA_AOPPA} 983 982 (and hence the \code{psGrommit}s), may be calculated through table 984 lookups (\S\ref{sec:tables}). 985 986 \paragraph{Table Lookups} 987 \label{sec:tables} 988 989 The offset of UTC from UT1, $\Delta$ UT1 = UTC - UT1, as well as the 990 pole coordinates, $x_p$ and $y_p$, may be determined from table 991 lookups. Tables are available covering different time periods and 992 with different time resolution: 993 994 \begin{itemize} 995 \item \code{ftp://maia.usno.navy.mil/ser7/ser7.dat} 996 \item \code{ftp://maia.usno.navy.mil/ser7/finals.all} with explanatory 997 guide at \code{ftp://maia.usno.navy.mil/ser7/readme.finals} . See also 998 the web page \code{http://maia.usno.navy.mil/}. 999 \item \code{http://hpiers.obspm.fr/eoppc/eop/eopc01/eopc01.1900-2004} 1000 (contains estimates prior to 1972). 1001 \end{itemize} 1002 1003 For the present time, it should be assumed that these tables reside on 1004 local disk in known locations (i.e., there is no need that they are 1005 downloaded from the internet and parsed by PSLib), containing the 1006 minimum required information in a format that may be read quickly by 1007 PSLib as required. 1008 1009 The location of these files, their priority order, and the ``from'' 1010 and ``to'' dates of applicability will be known beforehand. 1011 \tbd{Later, the location of these files, as well as the order of their 1012 specification, will be made configurable.} 1013 1014 When a value is required, the table with the highest priority shall be 1015 checked to see if the date is within the range of applicability for 1016 the table. If not, the table with the next highest priority shall be 1017 checked. If a table is found that is applicable, then the appropriate 1018 value shall be derived from linear interpolation between the nearest 1019 entries in the table. If no table is found that is applicable, and 1020 the required date is later than those in the table, a warning shall be 1021 generated, and a formula shall be applied (specifically, the formula 1022 contained in the Bulletin A, 1023 \code{ftp://maia.usno.navy.mil/ser7/ser7.dat}); the formula must be 1024 easily configurable (i.e., not requiring recompilation, as the formula 1025 will likely change with each Bulletin A). For dates prior to those 1026 covered in the tables, the function shall generate a warning and 1027 assume that TDT is identical to UTC (which, from Reingold \& 1028 Dershowitz Figure 12.2 appears accurate to $\sim 10$ sec to about 1029 1700), and that the polar motion ($x_p,y_p$) are zero. 1030 Archeoastronomy is not a perceived PSLib application, so there is no 1031 need for high precision at such early dates. 1032 1033 The tables shall be read in only when required by the user, and shall 1034 remain in memory until the termination of the program. An additional 1035 function, \code{psTimeTableReset} should be provided in order to force 1036 the reloading of the time tables. 1037 983 lookups. 1038 984 1039 985 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Note:
See TracChangeset
for help on using the changeset viewer.
