FITS Keywords
for DSN Radio Spectroscopy1


Last updated by Tom Kuiper on 2000 June 28.

Contents


1 Thanks

Special thanks to the members of the FITS e-mail group who gave valuable advice, including Steve Allen (UCO Lick), Mark Calabretta (ATNF), Thierry Forveille (CFHT), Eric Greisen (NRAO), Phil Hodge (STScI), Doug Mink (Harvard CfA), Mike Nolan (Arecibo), Bill Pence (HEASARC, GSFC), and Arnold Rots (HEA, SAO)

Existing Definitions

An important issue is compatibility with existing data reduction packages. These include This is not to claim that our files will be fully compatible with all these packages, but we do aim towards convergence. Accordingly, we will follow existing standards as closely as possible. At present, these include among others:

In selecting keywords for local DSN use, we try to avoid duplication by using local keywords used at other institutions or by existing software packages when no ambiguity can result:

The Astrophysics Data Centers Coordinating Council FITS Coordination Group maintains a current list of FITS keyword dictionaries.

DSN Spectroscopy Keywords

Introduction

Raw spectroscopic data go through a number of processing steps before they are turned into useful calibrated spectra. At many institutions, these steps are performed automatically and the observer does not usually consider them. The DSN environment is more R&D-oriented than service-oriented for spectroscopy. Because the hardware and software are constantly evolving and with few resources for testing and validation, the adopted strategy is to keep the data in a raw a form as possible, and to keep track of the processing steps applied to them. In this way, it is possible to recover from software errors.

Three strategies for recording data modifications were identified.

The latter seems to be the most versatile strategy and is adopted for use in the DSN. Besides using the changing state of the keywords (defined below), the standard HISTORY keyword will be used to record details associated with each step.

Autocorrelator Keywords

The following figure shows the processing steps which convert autocorrelator data into spectra. Also shown are proposed keywords using the STScI scheme.

Depending on the type of correlator being used, the data acquisition software would initially set these keywords to either 'perform' or 'omit' as appropriate. During the processing steps, those with values of 'perform' would get changed into 'complete'.

At the completion of autocorrlator data processing, one has a spectrum similar to that obtained from other instruments, with the except that spectra obtained from autocorrelators are normalized, that is, the average value of the spectrum is 1. Multiplying this with a scaling constant (e.g. system temperature in K, spectral flux density in W/hz, etc.) yields a calibrated total power spectrum.


Local Spectrum Processing Keywords

In general, only three types of spectra are of interest:

TypePurpose Processing Required
rawDiagnose equipment none
total power monitor receiver performance, RFI, etc. normalize and scale to physical units
difference measure weak signals various, depending on observing mode and spectrometer capability

The following figure shows all the possible ways in which spectra might be processed to obtain calibrated data.

The usual procedure is for the observatory staff to determine how the desired data type is obtained from each instrument, given its capabilities, the capabilities of the receiver to which it is connected, and the observing mode.


DATATYPE Keyword

Background

The IRAF package uses a keyword DATA-TYP with values of 'BIAS', 'DOME FLAT', 'SKY FLAT', 'OBJECT', 'COMPARISON', 'DARK'. It is used at least by the University of Victoria and by NRO. Such a keyword is also needed for radio spectroscopy, and then a subset of these keyword values might serve:
DATA-TYP =Radio Equivalent
object "sig" or "on-source"
comparison "ref" or "sky"
dark "ambient load"
bias "LNA or front-end off"
The risk of this strategy is that if one used an IRAF-based package written elsewhere to process DSN data, this keyword and its values might trigger unwanted operations. SEST La Silla uses the keyword OBSTYPE for a similar purpose and, because it is a radio observatory, might be closer to our needs:
OBSTYPE =Probable Meaning
SIG "sig" or "on-source"
REF "ref" or "sky"
CAL calibration on or ambient load?
DAR dark? ambient load, or IF off?
COM commutating?
AVE ?

DATATYPE Keyword Definition

It seems safer to choose an equivalent but different local keyword -- DATATYPE -- with our own defined values:

DATATYPE =Meaning
sig data with the putative signal present
ref data with the signal absent or frequency-shifted
switched sig-ref differenced in hardware, or at least not in the data acquisition program
amb-load data taken on the ambient load
cal-source data with a noise diode on
test could be anything; look in the COMMENT fields
zero data with the front-end disabled

With this convention, the initial values of the reduction keywords will depend on observing mode and data type.


Keywords for Integration Time

Keyword Source Meaning Example
ELAPTIME UCO/Lick The duration in seconds of the scan (starttime - stoptime) For a single sweep of a (non-averaging) spectrum analyzer, ELAPTIME is the sweep time.
OBSTIME SEST
COMB
The amount of time, in seconds, that each resolution element collected useful data. For a multichannel spectrometer, OBSTIME = ELAPTIME.
For a scanning spectrum analyzer, OBSTIME is the resolution bandwidth divided by the sweep rate. (The sweep rate is the span divided by the sweep time.)
N-SPEC   The number of spectra comprising this scan. For a spectrometer with an inherently short integration time, OBSTIME may consist of many spectra. For an integrating spectrum analyzer, this is the number of sweeps comprising a displayed spectrum.
EXPOSURE SDF Effective integration time so that the radiometer equation is satisfied. For a Dicke-switched spectrum,
EXPOSURE = OBSTIME/4

Examples

Position Switching, Total Power Raw Spectra, Noise Diode Calibration

Three scans are required to produce a calibrated difference spectrum. The initial keyword values will be:

Keyword Cal Scan Ref Scan Sig Scan Notes
FRONTENDKa-core Ka-core Ka-core The core Ka-band front end at DSS-13 has only a single horn
BACKEND WBSA WBSA WBSA The Wide Band Spectrum Analyzer is a digitial FT spectrometer which accumulates only total power spectra
OBSMODE LINE+PSSWLINE+PSSWLINE+PSSW  
DATATYPEcal ref sig  
TCAL-DIFomit omit perform process with the pink equation in the above figure
CALSCALEomit omit perform process with the brown equation in the above figure

Frequency switching will be the same except for the OBSMODE keyword.

Position Switching, Total Power Raw Spectra, System Temperature Calibration

Two scans are required to produce a calibrated difference spectrum. The initial keyword values will be:

Keyword Ref Scan Sig Scan Notes
FRONTENDKa-core Ka-core  
BACKEND WBSA WBSA  
OBSMODE LINE+PSSWLINE+PSSW  
DATATYPEref sig  
TSYS-DIFomit perform process with the blue equation in the above figure
CALSCALEomit perform process with the brown equation in the above figure

Frequency switching will be the same except for the OBSMODE keyword.

Position Switching, Autocorrelator, System Temperature Calibration

Two scans are required to produce a calibrated difference spectrum. The initial keyword values will be:

Keyword Ref Scan Sig Scan
FRONTENDKa-core Ka-core
BACKEND SP500-512SP500-512
AC-NORM perform perform
FOURIER perform perform
OBSMODE LINE+PSSWLINE+PSSW
DATATYPEref sig
TSYS-DIFomit perform
CALSCALEomit perform

Note that the order of the keywords TSYS-DIF and CALSCALE is significant. Performed in the order shown here, the average baseline value will be zero. If the order is reversed, the average baseline value will be the Tsys difference between the "sig" and "ref" scans.

Beam Switching, Raw Difference Spectra, System Temperature Calibration

Two scans are required to produce a calibrated difference spectrum. The initial keyword values will be:

Keyword Ref Scan Switched Scan
FRONTENDK K
BACKEND SpectraData SpectraData
OBSMODE LINE+BMSWLINE+BMSW
DATATYPEref switched
TSYS-RATomit perform
CALSCALEomit perform