IRAC Instrument Handbook - IRSA - California Institute of Technology
IRAC Instrument Handbook - IRSA - California Institute of Technology
IRAC Instrument Handbook - IRSA - California Institute of Technology
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
6 Data Products<br />
<strong>IRAC</strong> <strong>Instrument</strong> <strong>Handbook</strong><br />
This section describes the basic data products the observer will receive from the Spitzer Heritage Archive.<br />
The available data products consist <strong>of</strong> Level 0 (raw) data, Level 1 (BCD) data, calibration files, log files,<br />
and Level 2 (post-BCD) data. <strong>IRAC</strong> data are supplied as standard FITS files.<br />
Each file consists <strong>of</strong> a single data collection event (i.e., a single exposure), and contains one image<br />
corresponding to one <strong>of</strong> the four <strong>IRAC</strong> arrays (the exception being post-BCD products, described below).<br />
The FITS headers are populated with keywords including (but not limited to) physical sky coordinates<br />
and dimensions, a photometric solution, details <strong>of</strong> the instrument and spacecraft including telemetry when<br />
the data were taken, and the steps taken during pipeline processing.<br />
6.1 File-Naming Conventions<br />
Table 6.1 lists the <strong>IRAC</strong> data files produced by the <strong>IRAC</strong> data reduction pipelines, together with brief<br />
descriptions <strong>of</strong> these files. The Basic Calibrated Data (BCD) are the calibrated, individual images. These<br />
are in array orientation and have a size <strong>of</strong> 256 x 256 pixels for the full array images, and 64 planes times<br />
32 x 32 pixels for the subarray images. These data are fully calibrated and have detailed file headers. The<br />
Post-BCD pipeline combines the BCD images into mosaics (per wavelength and per frame time).<br />
Calibration observations designated as darks or flats go through a similar but separate pipeline that<br />
generates the products listed in the last section <strong>of</strong> Table 6.1.<br />
Note that because <strong>of</strong> the “first frame effect,” the first frame <strong>of</strong> every Astronomical Observation Request<br />
(AOR) has a different delay time and it cannot be calibrated correctly. Therefore, the first frame <strong>of</strong> every<br />
AOR with a frame time greater than 2 seconds is taken in HDR mode which causes the first frame to be<br />
0.6 seconds or 1.2 seconds in duration instead <strong>of</strong> the full frame time. This first frame usually has a name<br />
such as SPITZER_I1_11111111_0000_0000_2_bcd.fits and has no associated cosmic ray mask (brmsk<br />
file). The observer is encouraged not to use this first short frame. The pipeline mosaicker does not use it<br />
either when building the mosaic.<br />
The BCD uncertainty files (listed below) are rough uncertainty estimations and do not include all <strong>of</strong> the<br />
systematic effects associated with <strong>IRAC</strong> detectors, nor do they include the absolute flux uncertainty.<br />
These uncertainty images are generated as follows. They begin as an estimate <strong>of</strong> the read noise (one<br />
number in electrons for the whole image) and the shot-noise due to the sky (proportional to the squareroot<br />
<strong>of</strong> the number <strong>of</strong> electrons in the image). Then each module propagates the uncertainty image<br />
forward, including the uncertainties in dark and flat calibration files. The pipeline modules use the<br />
uncertainty image as a way to quantitatively estimate the quality <strong>of</strong> the sky estimate given by the value <strong>of</strong><br />
a pixel. In the end, the uncertainty images overestimate the formal uncertainty <strong>of</strong> the image, because the<br />
net propagated uncertainty is much higher than the observed pixel-to-pixel fluctuations in the images. We<br />
therefore recommend that the uncertainty images only be used for relative weights between pixels, for<br />
example when performing outlier rejection or making a weighted mosaic that combines multiple input<br />
frames that view the same sky mosaic pixel.<br />
Data Products 97 File-Naming Conventions