next up previous contents index
Next: 5.6 Detector Performance Up: 5. ISO In-Orbit Performance Previous: 5.4 Pointing Performance


5.5 Satellite Timing

ISO contained several on-board clocks: one for each instrument and one for the satellite itself. Several time keys derived from these on-board clocks, and also from ground-based clocks, are present in the ISO data ( ISO Architectural Design Document, [85]). The most prominent ones are the UTC (Universal Time(Coordinated)), the UTK (Uniform Time Key) and the ITK (Instrument Time Key). Also in widespread use is the Ground Station Time (GST), the time when data were received. Note that the abbreviations UTC and GST are often used interchangeably and that GST does NOT refer to Greenwich Sidereal Time.

The GST is contained in each record of the Telemetry Data Format (TDF) archive; it is the time of reception of the start of the format by a ground station. This time is expressed in the Universal Time Coordinated (UTC) scale as two I*4 integers; the first holding the whole number of seconds since midnight at the beginning of 1989; the second holding the remainder in units of $10^{-7}$ seconds. In some other data structures, the UTC is expressed in other ways, namely `yydddhhmmss' and the Modified Julian Date offset in days from 2000.0. These are all exactly equivalent in physical meaning within the given precision; in particular all of them `stand still' during a leap second.

The spacecraft on-board time is contained in frame zero of each TDF format. It is read from the same oscillator that drives the telemetry encoding, and therefore increments by a fixed amount per TDF format. Experience with other missions has shown that although ideally the spacecraft clock is a very convenient quantity for a time scale and easy for software to manipulate, it may be subject to discontinuous jumps or resets, and therefore it cannot be used where it is necessary to label data with a unique time, or where a uniformly increasing time is required. The on-board time is thus not used within the Off-Line Processing (OLP) software.

As an alternative that does not suffer such disadvantages, an artificial on-board time called the uniform time key, or UTK, is derived from the GST. It is the UTK that is used to index all products derived from spacecraft telemetry as distinct from instrument telemetry.

The uniform time key (UTK) is defined as follows:

-
a normal signed I*4 quantity,
-
increasing at a rate of 24 Hz,
-
divisible by 48 on a format boundary,
-
initialised to zero at a time close to ISO launch,
-
having a constant linear relation to the real spacecraft time, as long as the latter increments nominally,
-
guaranteed to increase with time, even across a jump of the real spacecraft clock or in the absence of telemetry frame 0.

A continuously increasing time scale is also necessary for labelling instrument telemetry records. While each of the four instruments had its own way to synchronise data with spacecraft telemetry, these have been unified by defining for each an Instrument Time Key (ITK) as follows:

-
a normal signed I*4 quantity,
-
valid at least over one Target Dedicated Time (TDT), the time spent in one observation of a target,
-
set to an arbitrary initial value to ensure that the key does not overflow,
-
having a constant linear relation during the TDT to the UTK defined above.

The four ITKs have been defined as follows:

-
The CAM ITK is derived from CAM's internal time word in telemetry and the UTK and is expressed in CAM Time Units. This unit is subject to empirical measurement; the value for products before OLP v7.0 was 0.14000498 seconds, after which it was changed to 0.13999950 seconds. The CAM ITK is unique over the whole mission.
-
The LWS ITK is in units of $2^{-14}$ seconds (approximately $6\times 10^{-5}$ seconds) and is calculated as a scaled difference of two UTK times. The LWS ITK is unique over a revolution (ISO orbit).
-
The PHT ITK is in units of $2^{-14}$ seconds and is calculated by combining the UTK and the times contained in PHT floating blocks. The PHT ITK is unique over a revolution.
-
The SWS ITK is the UTK and is thus in units of $1/24$ seconds. The SWS ITK is unique over the whole mission.

For CAM and SWS it is thus possible to label data records with a time key that is unique for the whole mission; for LWS and PHT, the time key should be used in combination with the TDT number.

The relationships between (i) UTC and UTK, and (ii) UTK and ITK are both established for every observation at the beginning of data processing and recorded in the Compact Status file. DERIVE_ERD, which reformats an observation's raw data into Edited Raw Data (ERD), makes the appropriate clock calibrations easily available in FITS header keywords and labels all ERD records with an instrument time key.

Attention is drawn to possible irregularities in the relations between UTC and UTK and ITK over one observation. The UTC-UTK relationship may not be entirely stable or constant, for one or more of the following reasons:

1)
During pre-launch ground tests the UTC, which is the TDF format arrival time, was very occasionally not exactly 2 seconds after the preceding format. We are not aware that this ever occurred during operations but users should be aware of the possibility.
2)
There is a slow systematic change in the UTC due to orbital motion, related to the changing distance between the earth and the spacecraft.
3)
The UTC is `real-world' time and thus includes any so-called `leap seconds' that were added by decree to the last second of a day at the end of June 30 or December 31, in much the same way that leap-years have an extra day. No attempt has been made to deal with such 1-second clock jumps.

Therefore, the following should be borne in mind:

-
the TREFxxxx keywords in main science ERD product FITS headers refer only to a single reference time in the observation and cannot be extrapolated to other points in the observation with high precision.
-
the UTC should not be used in place of the UTK or ITK for any ISO data analysis purposes.
-
the UTC may be used roughly to correlate ISO data with external events, taking account of the heliocentric correction available in the TREFHELx keywords if necessary.
-
the UTC can be derived from the UTK only to a precision that reaches 2 seconds in the worst case.

Users should also be aware that a small fraction of data was lost due to regular if infrequent small gaps in the telemetry stream, although most observations escaped such losses.


next up previous contents index
Next: 5.6 Detector Performance Up: 5. ISO In-Orbit Performance Previous: 5.4 Pointing Performance
ISO Handbook Volume I (GEN), Version 2.0, SAI/2000-035/Dc