pint.observatory
Machinery to support PINT’s list of observatories.
This code maintains a registry of observatories known to PINT. Observatories are added to the registry when the objects are created. For the observatories defined in PINT, these objects are created when the relevant module is imported.
PINT’s built-in observatories are loaded when anyone imports the modules
pint.observatory.topo_obs
and
pint.observatory.special_locations
. This automatically happens
when you call pint.observatory.Observatory.get()
,
pint.observatory.get_observatory()
, or
pint.observatory.Observatory.names()
(pint.observatory.Observatory.names_and_aliases()
to include aliases).
Satellite observatories are somewhat different, as they cannot be
created until the user supplies an orbit file. Once created, they will
appear in the list of known observatories.
Normal use of pint.toa.get_TOAs()
will ensure that all imports have been
done, but if you are using a different subset of PINT these imports may be
necessary.
Functions
|
Read a tempo2 observatories.dat file and compare with PINT |
|
Read a tempo obsys.dat file and compare with PINT. |
|
Compute the distance between two EarthLocations. |
|
Locate and return a ClockFile in one of several places. |
Check BIPM servers for the most recent version of TT(BIPMYYYY) |
|
|
Convenience function to get observatory object with options. |
Print out a list of the last MJD each clock correction is good for. |
|
|
Obtain an up-to-date version of all clock files. |
Classes
|
Observatory locations and related site-dependent properties |
Routines for reading and writing various formats of clock file. |
|
Tools for working with clock corrections obtained from a global location. |
|
Observatories at special (non-Earth) locations. |
|
Special locations that are not really observatories. |
|
Ground-based fixed observatories read in from |