While the ACS image headers for WFC, HRC, HRC-ACQ, and SBC observations have very similar formats, two main differences are apparent. MAMA (SBC) headers require a slightly modified structure from the CCD (WFC, HRC) headers, and HRC-ACQ headers require several unique keywords.
ACS header keywords can be viewed in several ways. If you know the names of keywords you wish to look up, you can use the STSDAS tasks
hedit or
hselect tasks to query the images. The examples below show how these tasks are used to get the values for group (or extension) keywords
CCDCHIP,
CRVAL1, and
CRVAL2. The contents of the entire primary or group header can be viewed on-screen, or by directing the output to a text file, using the task
imheader.
ACS image header keywords are described in Tables 2.6 and
2.7. If you were to display the header using
imheader, you’ll notice that the keywords are grouped together by their type, for example, “Target Information,” “Science Instrument Configuration,” “Calibration Switches,” and “Calibration Reference files.”
Extension or group header keywords (FITS extensions > 0), as shown in Table 2.7, contain parameter values that are specific to the image group (however, many primary header keyword values are also accessible when querying an image group header).
Most of the keywords described in Tables 2.6 and
2.7 are “user” keywords, i.e., keywords with values directly recorded in the image headers. A few keywords in the tables have the prefix “i_”; these are “standard” keywords. They cannot be accessed by tasks like
eheader and
imheader, but when queried by
hedit and
hselect, the values of standard keywords are determined on-the-fly by IRAF.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PODPS fill present (T/F). (Indicates if there are missing packets in the data stream; in such cases, the OPUS pipeline inserts fill packets so that the image can be processed by analysis software.)
|
|
|
Science telemetry fill data present? (T=1/F=0). (Indicates if errors were found in the science dataset at the Space Telescope Data Capture Facility; if there are missing packets or failed segments, fill data is inserted as placeholders.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Serious data quality flags. (Bad pixels that are not included in calculations for header keyword image statistics, e.g., GOODMEAN, NGOODPIX.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A_0_2, B_0_2, A_1_1, B_1_1, A_2_0, B_2_0, A_0_3, B_0_3, A_1_2, B_1_2, A_2_1, B_2_1, A_3_0, B_3_0, A_0_4, B_0_4, A_1_3, B_1_3, A_2_2, B_2_2, A_3_1, B_3_1, A_4_0, B_4_0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|