--------------------------------- Page 1 --------------------------------- Archive Interface Control Document Deep Impact Flight Data HRI IR Spectrometer (HRII) Raw and Calibrated Science Data Products Prepared by: Deep Impact Archive Team University of Maryland, Astronomy Department College Park, MD 20742 January 29, 2005 Last revised September 27, 2007 --------------------------------- Page 2 --------------------------------- Modification History -------------------- Date Name Description 2005-01-29 S. McLaughlin Created draft 2006-01-31 S. McLaughlin Updated draft to reflect changes to FITS-formatted data, file names, data set IDs, and PDS labels 2006-06-12 S. McLaughlin Updated for resolution of liens from the April 2006 PDS peer review of VIS flight data. 2006-10-17 S. McLaughlin Added items to Project Documents and Science References sections 2007-02-20 S. McLaughlin Updated for version 2.0 of the reduced data set 2007-09-27 S.McLaughlin Corrected INTEGRATION_DURATION calculation for VIS modes 4,6,7,8. --------------------------------- Page 3 --------------------------------- Table of Contents 1 INTRODUCTION .........................................................5 1.1 PURPOSE AND SCOPE ................................................5 1.2 APPLICABLE DOCUMENTS..............................................5 1.2.1 EXTERNAL STANDARD REFERENCES..................................5 1.2.2 PROJECT DOCUMENTS.............................................5 1.2.3 SCIENTIFIC REFERENCES.........................................6 1.3 CONTACT NAMES AND ADDRESSES.......................................7 2 INSTRUMENT DESIGN AND DATA PRODUCT GENERATION.........................8 2.1 INSTRUMENT OVERVIEW - HRII........................................8 2.1.1 INSTRUMENT MODES.............................................10 2.2 DATA SET AND DATA PRODUCT OVERVIEW...............................11 2.3 DATA PRODUCT GENERATION AND LABELING.............................12 2.3.1 CALIBRATION PROCESS..........................................12 2.3.2 IMAGE ORIENTATION AND PIXEL READOUT ORDER....................16 2.4 DATA SET ORGANIZATION............................................19 2.4.1 BROWSE.......................................................19 2.4.2 CALIB........................................................19 2.4.3 CATALOG......................................................21 2.4.4 DATA.........................................................22 2.4.5 DOCUMENT.....................................................23 2.4.6 INDEX........................................................23 2.5 DATA FILE NAMING CONVENTIONS AND PRODUCT IDS.....................24 2.6 STANDARDS USED IN DATA PRODUCT GENERATION........................25 2.6.1 PDS STANDARDS................................................25 2.6.2 TIME STANDARDS...............................................25 2.6.3 REFERENCE FRAME STANDARDS....................................25 2.6.4 IMAGE ORIENTATION............................................25 3 DETAILED SPECIFICATIONS OF DATA PRODUCTS.............................26 3.1 SAMPLE PDS LABELS................................................26 3.1.1 SCIENCE LEVEL 2 (RAW) HRII DATA PRODUCT .....................26 3.1.2 SCIENCE LEVEL 3/4 (CALIBRATED) HRII DATA PRODUCT.............30 3.2 PDS OBJECT AND KEYWORD DEFINITIONS...............................36 4 USING THE DATA PRODUCTS..............................................49 --------------------------------- Page 4 --------------------------------- 4.1 INDEX FILES......................................................49 4.2 RELATED DATA SETS................................................49 4.3 FLIGHT HARDWARE CONSIDERATIONS...................................49 4.4 KNOWN ANOMALIES..................................................50 4.5 RECOMMENDED SOFTWARE TO READ DATA PRODUCTS.......................51 4.5.1 IDL..........................................................51 4.5.2 PDS-SBN TOOLS................................................51 5 TECHNICAL/PROGRAMMING INFORMATION....................................52 5.1 BRIEF DESCRIPTION OF ODL USED FOR PDS LABELS.....................52 5.2 ARCHITECTURE NOTES...............................................52 5.2.1 INTERNAL REPRESENTATION OF DATA TYPES........................52 5.2.2 FILE SYSTEM (ISO 9660).......................................52 5.3 FILE COMPRESSION FORMATS.........................................53 5.4 NAIF/SPICE.......................................................53 6 APPENDICES...........................................................54 6.1 GLOSSARY.........................................................54 6.2 ACRONYMS.........................................................55 6.3 DATA PROCESSING LEVELS ..........................................56 --------------------------------- Page 5 --------------------------------- 1 Introduction 1.1 Purpose and Scope The purpose and scope of this document is to define the PDS products for the HRII science data acquired during the cruise and encounter phases of the DI mission. This document is intended to provide enough information to enable users to understand and use the data products. This document includes information about how the data were processed, formatted, labeled, and identified. The structure of the data sets and an example of a raw and calibrated spectral image data product are included. This document is not intended to provide a detailed description of the HRII instrument nor does it provide methods for interpreting HRII data. A thorough discussion of the IR spectrometer is provided by Hampton, et al. 2005 [4]. Klaasen, et al. 2005 [5] and Klaasen, et al. 2006 [15] provide an overview of the flight data and the calibration process. For discussions of expected scientific results and the properties of the comet 9P/Tempel 1, see Sunshine, et al. 2005 [6], Belton, et al. 2005 [7], Lisse et al, 2005 [8], Thomas, et al. 2005 [9], Richardson, et al. 2005 [10], and Schultz, et al. 2005 [11]. For the history and dynamics of mission target, see Yeomans, et al. 2005 [12]. For overviews of the mission and scientific objectives, see A'Hearn, et al. 2005 [13] and Blume, 2005 [14]. 1.2 Applicable Documents 1.2.1 External Standard References All of these documents are included in the Deep Impact Documentation Set (PDS volume ID DIDOC_0001): [1] PDS Standards Reference, JPL, D-7669, Version 3.6, August 1, 2003 and PDS Standards Reference, JPL, D-7669, Version 3.7, March 20, 2006 [2] PDS Data Dictionary, JPL, D-7116, Revision E, August 28, 2002 and the Deep Impact Local Data Dictionary created from the PDS Full Data Dictionary generated on December 6, 2006 (Version OPS) 1.2.2 Project Documents [3] Deep Impact Project Data Management Plan, JPL, D-21386 [4] An Overview of the Instrument Suite for the Deep Impact Mission, Hampton et al, Space Science Reviews, 2005 [5] Deep Impact: The Anticipated Flight Data, Klaasen, et al. Space Science Reviews, 2005 --------------------------------- Page 6 --------------------------------- [6] Expectations for Spectroscopy of Tempel 1 from Deep Impact, Sunshine, et al. Space Science Reviews, 2005 [7] Properties of the Nucleus of Comet 9P/Tempel 1: Target of the Deep Impact Mission, Belton, et al. Space Science Reviews, 2005 [8] The Coma of Comet 9P/Tempel 1, Lisse, et al. Space Science Reviews, 2005 [9] Comet Geology with Deep Impact Remote Sensing, Thomas, et al. Space Science Reviews, 2005 [10] Impact Cratering Theory and Modeling for the Deep Impact Mission: From Mission Planning to Data Analysis, Richardson, et al. Space Science Reviews, 2005 [11] Expectations for Crater Size and Photometric Evolution from the Dee Impact Collision, Schultz, et al. Space Science Reviews, 2005 [12] This History and Dynamics of Comet 9P/Tempel 1, Yeomans, et al. Space Science Reviews, 2005 [13] Deep Impact: A Large-Scale Active Experiment on a Cometary Nucleus, A'Hearn, et al. Space Science Reviews, 2005 [14] Deep Impact Mission Design, Blume, Space Science Reviews, 2005 [15] Deep Impact Instrument Calibration, Klaasen, et al. 2006, submitted to Optical Engineering [16] Autonomous Navigation for the Deep Impact Mission Encounter with Comet Tempel 1, Mastrodemos, et al. Space Science Reviews, 2005 [17] Deep Impact Navigation Images Report, Carcich, 2006 [18] Deep Impact Spacecraft Clock Correlation, Carcich, 2006 1.2.3 Scientific References Publications of results from Deep Impact will be provided here. The journal Icarus will publish a special edition of the results from Deep Impact. Ground-and space-based results will be included. The special edition should be published in 2007. [A] Deep Impact: Excavating Comet Tempel 1, A'Hearn, et al. 2005, Science, 310, 258-264 [B] Deep Impact: Observations from a Worldwide Earth-based Campaign, Meech, et al. 2005, Science, 310, 265-269 [C] Parent Volatiles in Comet 9P/Tempel 1: Before and After Impact, Mumma, et al. 2005, Science, 310, 270-274 [D] Subaru Telescope Observations of Deep impact, Sugita, et al. 2005, Science, 310, 274-278 --------------------------------- Page 7 --------------------------------- [E] The Dust Grains from Comet 9P/Tempel 1 Before and After the Encounter with Deep Impact, Harker, et al. 2005, Science, 310, 278-280 [F] Deep Impact Observations by OSIRIS Onboard the Rosetta Spacecraft, Keller, et al. 2005, Science, 310, 281-283 [G] Exposed Water Ice Deposits on the Surface of Comet 9P/Tempel 1, Sunshine, set al. 2006, Science, 311, 1453-1455 1.3 Contact Names and Addresses Michael A'Hearn Deep Impact Principal Investigator and PDS Small Bodies Node Manager Department of Astronomy University of Maryland College Park, MD 20742 301-405-6076 Stephanie McLaughlin Deep Impact Archive Team and PDS Small Bodies Node Staff Department of Astronomy University of Maryland College Park, MD 20742 301-405-3605 --------------------------------- Page 8 --------------------------------- 2 Instrument Design and Data Product Generation 2.1 Instrument Overview - HRII The High Resolution Imager (HRI) consisted of a long-focal-length telescope followed by a dichroic beam splitter that reflected (0.3 to 1.0 microns) light through a filter wheel to a CCD for direct, optical imaging. The beam splitter transmitted the near infrared (1 to 5 microns) to a 2-prism spectrometer. For convenience, we considered these as two separate instruments, HRIV and HRII, sharing the telescope since the two focal planes operated in parallel asynchronously. The HRI telescope was a classical Cassegrain design with the following parameters: Primary aperture : 30.0 cm diameter, round Primary focal ratio : 4.5 Secondary Obscuration : 9.7 cm diameter, round Secondary magnification : 7.8x (net Cassegrain focal length 105.0 cm) Back focal distance: : 30.0 cm The beam-splitter was a dichroic with equal transmission and reflection occurring at about 1.05 microns and was placed in front of telescope focal plane. The spectrometer was a 2-prism design, one of calcium fluoride (CaF_2) and one of zinc selenide (ZnSe) to maximize etendue and problems with order separation. The camera and collimator led to a net demagnification of 3 times, for an effective f/ratio of f/12 and effective focal length of 360 cm in the final beam. The entrance slit subtended on the sky 2.53 milliradians by 10 microradians (0.145 degrees by 2 arcseconds), filling the 512-pixel height of the IR array. The slit width matched the binned pixel (2x2) used for most observations. The near-infrared detector was a 1024 (wavelength) x 512 (spatial) pixel mercury cadmium telluride (HgCdTe) device manufactured by Rockwell using the multiplexer originally developed under contract from the University of Hawaii for deployment in the WFC3 on HST. Physically, it was a 1024 x 1024 device, but only half of the device was active. Pixels were 18 microns square and normal operations included 2x2 binning (post-readout). Spectral resolving power, because of the 2-prism design, varied from greater than 740 at 1.04 microns down to 210 at 2.6 microns, and back up to 385 at 4.8 microns. Due to probable saturation problems in warm areas of the nucleus, the central quarter of the detector was covered with a neutral density filter. When operated in the 512 x 256 pixel, 2x2 binning mode, the HRII instrument had the following field-of-view characteristics: Spatial Physical Pixel Size : 36 micrometers Effective Pixel FOV : 10.0 microradians Effective FOV : 2.5 milliradians or 0.15 degrees --------------------------------- Page 9 --------------------------------- Spectral Effective Pixel FOV : 10.0 microradians Effective FOV : 10.0 microradians (slitwidth) The three instruments on the flyby spacecraft, HRII, HRIV and MRI, were mounted on a separate instrument platform together with the star trackers. The three instruments were nominally co-aligned. The HRII instrument was calibrated by using in-flight data as well as pre-launch data taken during thermal-vacuum tests (TV1, TV2, and TV4), performed in 2002 and 2003. The calibration of the HRII instrument is discussed by Klaasen et al. 2006 [15]. The HRI focus failed to meet a mission requirement. Early in the mission, calibration images of stars showed the HRI telescope was significantly out of focus, affecting the HRIV visible images. However, the effect is negligible for HRII spectral images. Most of the resolution can be gained back by deconvolving HRIV images by as discussed by Klaasen et al. 2006 [15]. Otherwise, the HRII instrument generally performed as expected during flight. Small changes in instrumental temperatures affected the dark current more than expected from ground thermal-vacuum tests. For more information, see Klaasen et al. 2006 [15]. --------------------------------- Page 10 --------------------------------- 2.1.1 Instrument Modes The instrument or imaging modes for the HRII instrument are provided below. The IR detector had several reference columns (line samples) and rows (lines) around the edge of the array. Pixels in the reference areas were excluded from the MINIMUM and MAXIMUM values in the PDS labels. See Hampton, et al. 2005 [4] for more details about the instrument modes and the number of reference rows and columns for each instrument mode. Min Frame-to Mode Stored Exp frame for # Mnemonic Mode Image Size Time(s) min exp(s) - -------- ----------------------------- ----------- ------- --------- 1 BINFF Binned Full Frame 512 x 256 2.86 2.862 2 BINSF1 Binned Sub-Frame 1 512 x 128 1.43 1.432 3 BINSF2 Binned Sub-Frame 2 512 x 64 0.71 0.717 4 UBFF Un-binned Full Frame 1024 x 512 2.86 2.862 5 ALTFF Alternating Binned Full Frame 512 x 256 1.43 2.868 6 DIAG Diagnostic 1024 x 512 1.43 1.432 7 MEMCK Memory Check 1024 x 512 N/A 2.862 --------------------------------- Page 11 --------------------------------- 2.2 Data Set and Data Product Overview For the PDS archive, flight data are grouped into two, general mission phases: Phase Start Date End Date Targets --------- ----------- ----------- ------------------------------- CRUISE 12 Jan 2005 30 Apr 2005 In-flight Calibrations ENCOUNTER 01 May 2005 13 Jul 2005 Tempel 1 Imaging, In-flight Calibrations HRII data products for the flight phase of the DI mission are grouped into the following data sets in the PDS archive: DIF-CAL-HRII-2-9P-CRUISE-V1.0 - Cruise - Raw, calibration data in units data number - 2-D FITS spectral images (*.fit) with an extension for a quality flag map DIF-C-HRII-2-9P-ENCOUNTER-V1.0 - Encounter - Raw comet spectra and calibration data in units of data number - 2-D FITS spectral images (*.fit) with an extension for a quality flag map DIF-C-HRII-3/4-9P-ENCOUNTER-V2.0 - Encounter - Version 2.0 supersedes version 1.0 below. The calibration process was improved for dark subtraction and new bad pixel maps were provided. Also, the final version of the archived SPICE kernels was used to calculate geometric parameters. Only calibrated comet data in physical units of radiance, (not cleaned and reversible [RADREV] or cleaned and not reversible [RAD]); Includes only data from June 20 onward (starting with exposure ID 6002005), because pointing was off-target for all earlier data; Includes calibration files such as darks, bad pixel maps, and instrumental parameters used to calibrate raw flight data. - 2-D FITS spectral images with extensions for a quality flag map, a wavelength map, a spectral bandwidth map, and a signal-to-noise map, (*.fit). Calibration files: Nominally, FITS image files (*.fit) and ASCII tables in the /CALIB subdirectory DIF-C-HRII-3/4-9P-ENCOUNTER-V1.0 - Superseded by version 2.0 above - Encounter - Only calibrated comet data in physical units of radiance, (not cleaned and reversible [RADREV]); Includes only data from June 20 onward (starting with exposure ID 6002005), because pointing was off-target for all earlier data; Includes calibration files such as darks, bad pixel maps, and instrumental parameters used to calibrate raw flight data. - 2-D FITS spectral images with extensions for a quality flag map, a wavelength map, a spectral bandwidth map, and a signal-to-noise map, (*.fit) Calibration files: Nominally, FITS image files (*.fit) and ASCII tables in the /CALIB subdirectory. --------------------------------- Page 12 --------------------------------- 2.3 Data Product Generation and Labeling All HRII raw and calibrated FITS spectral image files are produced in the DI data pipeline that is maintained by the DI SDC at Cornell University. The data pipeline takes raw telemetry with imbedded data, as downloaded from the DI flyby spacecraft, and constructs raw FITS spectral image files. The data pipeline inputs the raw FITS files, calibrates the data, and outputs calibrated FITS spectral images. The calibration process is described below. For details about the SDC, the flow of data, and the calibration pipeline refer to the DI PDMP [3], Klaasen, et al. 2005 [5], and Klaasen et al. 2006 [15]. Calibration files, such as bad pixel maps, were the result of the DI science team's analysis of ground-based thermal-vacuum and in-flight calibration data. Calibration files were stored at the DI SDC and used by the calibration portion of the DI data pipeline. Calibration files used to reduced HRII images are included in the reduced Deep Impact data sets. PDS data labels and index tables for raw and calibrated data products were generated by Applied Coherent Technology Corporation (ACT) of Herndon, Virginia. All PDS data labels are detached. 2.3.1 Calibration Process The goal of the data calibration process for the HRII instrument is to: - Convert the raw data numbers (DNs) returned from each pixel in each image or spectrum to absolute scientific units of scene radiance (RADREV or RAD). - Determine from where in the scene or its surroundings the photons originated that produced the signal in each pixel. The analysis of ground-based and in-flight calibration data and the resulting calibration pipeline is presented in the DI Calibration Pipeline paper by Klaasen et al. 2006 [15] and in the DI Anticipated Flight Data publication by Klaasen, et al. 2005 [5]. The following excerpt from the DI Calibration paper [15] is provided here as an overview of the pipeline: --------------------------------- Page 13 --------------------------------- Figure 0 - A flowchart describing the data processing pipeline used to calibrate Deep Impact images. Some modules are not applied to all instruments. Input calibration files, such as the Lookup tables for decompression, are identified by red text. ''Standard Steps'' For each image, there is a standard set of procedures and settings applied in our pipeline processing in order to calibrate the images automatically (see Figure 0). In general, these default settings are the best the science team has been able to derive for the data set as a whole and thus do not necessarily reflect the best possible processing for any particular image. However, there are some observations around encounter, especially with the IR spectrometer, that contain very valuable scientific information but are not processed optimally by the default settings. For these cases, the automated pipeline has the ability to specify special settings for particular observations. --------------------------------- Page 14 --------------------------------- The standard pipeline begins by decompressing the image if it was compressed on the spacecraft. Images can be compressed using one of four 14-bit to 8-bit lookup tables optimized for different types of exposures. To uncompress the images, a reverse lookup table is used which maps each 8-bit value to median of all corresponding 14-bit values. All saturated pixels are flagged in the quality map. Then an IR image is linearized. A VIS image does not need this step because the instrument responds linearly. Next, a dark frame is subtracted from the image. If a dark frame was created by the science team for the specific observation, then it is subtracted. Otherwise, a dark model is used to generate the frame. After the dark subtraction, a flat field is only applied to unbinned IR images because the best binned-mode flat field does not seem to provide any noticeable improvement in SNR. After bad pixels are flagged, the image is radiometrically calibrated to produce a radiance image in W/[m2 sr um] and an I/F image. For a VIS image, this is simply done by dividing the image by integration time and then multiplying by the appropriate conversion factor for the given filter and desired output. For an IR image, the procedure is more complicated as the absolute calibration is wavelength dependent, which in turn is temperature dependent. First, the wavelength and bandwidth for each pixel are calculated. Then, each pixel is multiplied by the appropriate wavelength-dependent calibration factor and divided by integration time and the pixel's spectral bandwidth. Once this radiance image is created, a copy is converted to I/F by dividing by the solar spectrum at the target's distance from the sun and then multiplying by pi. I/F data are Unitless. I/F data were not generated nor archived for the IR instrument. At this point, two reversible data products have been created, one radiance image and one I/F image, and copies are run through the rest of the pipeline, which performs a series of non-reversible steps. First, the data are interpolated over the bad pixels and gaps. For a VIS image, this interpolation is performed using thin plate splines anchored by the valid data around the edges of each hole. For an IR image, a linear interpolation is performed in the spatial dimension only. Next, a despiking routine is applied in order to remove cosmic rays. This routine performs a sigma filter by calculating the median of each NxN box, where N is odd, and then replacing the central pixel with the median if it is more than M median deviations from the median. By default, both M and N are set to 3. The median deviation of a set S is defined as: Med(| S - Med(S) |). Lastly, a VIS image is deconvolved if this option is turned on for the pipeline. This is especially important for the HRIVIS instrument that is out of focus. --------------------------------- Page 15 --------------------------------- Optional Steps Beyond the automated calibration pipeline described above, a manual calibration can be performed where the user can specify his/her own settings and calibration files for each step. Also, any processing module can be disabled, and there are two extra ones that can be enabled. The first such module is a noise-reduction module that is applied after the despiking routine. This applies the BayesShrink wavelet thresholding algorithm (Chang,, et al. 2000) with a robust mean noise estimator (Johnston and Silverman, 1997) to remove some of the noise. The other step that can be enabled applies a rubber sheet geometric distortion correction. This is not normally applied as the optical distortion though the telescope is minimal.'' See the instrument calibration document [15] for a detailed description of the image quality, spectral wavelength, spectral bandwidth, and signal-to-noise maps created by the pipeline and appended to the primary FITS image as image extensions. --------------------------------- Page 16 --------------------------------- 2.3.2 Image Orientation and Pixel Readout Order The following section was excerpted from the DI Calibration Pipeline paper by Klaasen et al. 2006 [15]. ''In order to understand the data from the instruments at the level of calibrations, it is important to understand both the way in which pixels are read out from the detector and also the way in which they are stored in the resultant FITS/PDS images. Throughout this paper we identify the four physical quadrants of the detectors as A through D (or just A and B in the case of the IR detector, which only uses 2 of the quadrants on the physical detector). The nomenclature in Figures 1, 2, and 3 assumes the standard convention for displaying FITS files: The faster-varying index in the data file (for line samples) is displayed to the right and the slower varying index (for lines) is displayed up (in PDS images the directions are controlled by keywords, which for our images are set to match the standard FITS display). Thus, the first byte of the FITS/PDS file appears in the lower-left corner of the window and the last byte in the FITS/PDS file appears in the upper-right. All FITS/PDS archival images are structured to display a true image of the sky, with arbitrary rotation about the center of the image (ecliptic north is to the right in this particular image), rather than a mirror image of the sky. The header information in the downlinked data is always written in the first 100 bytes of quadrant A. Figure 1. A full-frame, HRIV frame taken shortly before impact, displayed with the FITS convention. This orientation reproduces a true sky image. The first and last bytes are those read from the FITS file and are not connected with the order of readout. Quadrants A, B, C and D noted throughout this paper are labeled in the image. --------------------------------- Page 17 --------------------------------- In Figure 1 we show an in-flight, visible image from HRI, in which the directions in the labels are referred to by the order of the bytes (pixels) in the archived data files. The images from the thermal-vacuum calibrations have the same orientation. For MRI and ITS, the different number of reflections in the optical path of the instruments lead to a right-left mirroring between the physical quadrants and the image of the sky and also a mirroring between the thermal-vacuum calibrations and the in-flight data. Since the quadrant labeling refers to physical quadrants, the thermal-vacuum calibrations have the same orientation of the quadrants for all three instruments (A in upper left and D in lower right) but they have different orientations for in-flight data, i.e., the in-flight data for MRI and ITS have quadrant A in the upper right and quadrant D in the lower left for normally displayed FITS images. Thus the quadrants for in-flight images from MRI and ITS are shown in Figure 2. Figure 2. A full-frame, MRI frame taken at nearly the same time as the HRIV image in Figure 1. Displayed with the FITS convention, a true sky image is reproduced. The first and last bytes are those read from the FITS file and are not connected with the order of readout. Quadrants A, B, C and D noted throughout this paper are labeled in the image. The readout order of the pixels is independent of the order of bytes in the FITS images since each quadrant is read out independently in parallel and the bytes are then rearranged into an image. The direction of the split-frame rapid transfer is up and down in Figures 1 and 2, symmetric about the centerline. This affects the smear of bright sources in short exposures. After shifting to the shielded region of the detector, the top and bottom rows are read out first (top and bottom of the relevant subframe when only a subframe is read), and in each of these --------------------------------- Page 18 --------------------------------- rows the outermost pixels are read out first. The rows immediately above and below the centerline are read out last, and within these two rows, the pixels immediately adjacent to the centerline are read out last. The header information is overwritten on the first 100 bytes of quadrant A (upper left quadrant for HRI inflight images and upper right quadrant for in-flight images with MRI and ITS) after the image is constructed. Overclocked pixels and rows are read out after the true pixels, but they are moved to the outside of the FITS/PDS image to preserve the contiguity of the image in normal displays. The situation for the near-IR spectrometer is shown in Figure 3. The normally displayed image, whether using the FITS standard display convention or displaying via the relevant PDS keywords, will have wavelength increasing from left to right and the long spatial dimension of the slit oriented vertically. The vertical spatial direction in the spectrometer image is the same as in the HRI visible image, terminator at the top and limb at the bottom for a spectrum at the time of Figure 1. There are only two quadrants used although the actual detector has two additional quadrants that are not exposed to light and are not read out. The orientation is the same both for in-flight data and for thermal-vacuum calibrations, with A on the left in a standard FITS/PDS display while B is on the right. When the image is constructed, the header information is overwritten on the first 100 bytes of quadrant A. Figure 3. A full-frame, HRII frame taken shortly before impact, displayed with the FITS convention. For this FITS display, the wavelength increases as the fastest-varying axis increases to the right. The slowest-varying axis is the spatial direction along the slit. The first and last bytes are those read from the FITS file and are not connected with the order of readout. IR quadrants A and B noted throughout this paper are labeled in the image. Since the IR detector is reset and read out on a pixel-by-pixel basis, the readout order affects the actual time at which a pixel is exposed, unlike the situation for the visible CCDs. Each pixel has the same exposure duration, but the exposure of the last pair of pixels read out does not start until one delay-time before the first pair of pixels is read out. As with the lower half of the visible images, the bottom row is read out first and within that row the outermost (leftmost and rightmost) pixels are read out first. The spectral row at the upper end of the slit in this standard display is read out last and, within that row the two pixels on either side of the center-line are read out last. The header information is again written over the first 100 bytes of quadrant A, now in the lower left of a normal display. --------------------------------- Page 19 --------------------------------- 2.4 Data Set Organization HRII flight data sets are organized using the subdirectories recommended by the PDS standards: - Browse - Calib - Catalog - Data - Document - Index 2.4.1 Browse This directory contains a 80x40 pixel thumbnail file and a full-size JPEG file of each HRII spectral image found in the /data/radrev/ directory. The browse images are grouped by the observation day of year. 2.4.2 Calib This directory contains the files used to calibrate raw Tempel 1 data and is only included in the reduced data set. The DI science team produced these files as a result of the analysis of thermal-vacuum and in-flight calibration data. The calibration files are grouped into the following subdirectories: ABSCALIR - This subdirectory contains one table of the absolute calibration constants for each instrument (image) mode. The first column specifies the wavelength for the reading. The second column specifies the conversion factor for areas not under the anti-saturation filter. The last column contains the conversion factors for areas under the anti-saturation filter. Two identical files, one with a placeholder of '000' and another with '999' were created for the pipeline to allow existing processes to correctly execute. ADCLUT - This subdirectory contains a lookup table for the correcting for uneven bit weighting caused by the analog-to-digital conversion. The single table applies to all instrument modes. As of this archive, the corrections had not been derived. Therefore, the input pixel values are the same as the output values to prevent the automated calibration pipeline from changing the data. BADPIX - This subdirectory contains maps that identify bad pixels for each instrument mode. These are master maps where a pixel is flagged bad it was determined to be bad in the four in-flight science calibrations. Bad pixels are set to a value of 1. Also, the reference rows and columns around the edges of the array are set to 1. Good pixels are set to 0. --------------------------------- Page 20 --------------------------------- BIAS - This subdirectory contains a dummy bias correction map for each instrument mode. All bias maps are set to zero to prevent the automated calibration pipeline from changing data. DARK - This subdirectory contains dark frames for specific IR exposures. The exposure ID to which this dark frame can be applied is specified in the file name. These darks were created by averaging the frames within the specified exposure ID that were not on the target (i.e., background frames). DECOMPRS - This subdirectory contains the four lossy lookup tables used to decompress raw data. DRKMODEL - This subdirectory contains master dark frames for each instrument mode. FLAT- This subdirectory contains dummy flat fields for each instrument mode. Flat fields were derived from the linearity of each pixel. Some flats are dummies (all ones) as required by the calibration pipeline. LINDN - This subdirectory contains mode-specific maps of the four coefficients used in a polynomial to linearize the raw data numbers. Mode 5 must use the mode 1 file. Modes 6 and 7 must use the mode 4 file. PSF - This subdirectory contains a dummy point-spread function used by the calibration pipeline when one is not available. It is simply a centered delta function to prevent any changes to the data. SPECMAP - This subdirectory contains temperature-dependent, pixel-by-pixel, spectral registration maps for each instrument mode. The first dimension provides the wavelength; the second provides the spectral resolution (delta wavelength). The temperature string in the file names refers to the temperature of the IR spectrometer for which a map is applicable. SUNSPEC - This subdirectory contains two tables, based on different sources that provide the solar spectral irradiance at 1 AU for the given wavelengths. XTALK - This subdirectory contains tables that specify the amount of gain from electronic cross talk that occurs between all possible combinations of the two quadrants of the IR array. There is one table for each instrument mode. The crosstalk is across IR quadrants is negligible, thus the table values are set to zero the automated calibration pipeline from changing data. --------------------------------- Page 21 --------------------------------- 2.4.3 Catalog This directory contains catalog files required by PDS: - DATASET.CAT - Description of the data set - HRII.CAT - Description of the HRII instrument - DIF.CAT - Description of the Flyby spacecraft - DEEP_IMPACT.CAT - Description of the mission - PERSON.CAT - Contact information for personnel who created the data set - REFERENCE.CAT - List of publications cited in the catalog files - 9P_TEMPEL_1_1867_G1.CAT - Catalog file for the mission target - CALIBRATION.CAT - Generic catalog file for calibration targets (TARGET_DESC keywords in the PDS data labels provides the specific target name such as Jupiter or Canopus) --------------------------------- Page 22 --------------------------------- 2.4.4 Data This directory contains the raw and calibrated HRII spectral image data grouped by the year, day of year of the observation, and level of calibration (for calibrated data only): /data//// where: - year is 4 digits - day of year is 3 digits - level = not used for raw data, RADREV for calibrated but uncleaned data in units of radiance (calibration steps can be reversed to get back to the raw DN) and RAD for calibrated and irreversibly cleaned data in units of radiance. Calibration products for the HRII instrument are located in the /CALIB directory of the calibration data set and are grouped by type of calibration file, for example: /data/{type}/ where: - type = FLAT or BADPIX, for example --------------------------------- Page 23 --------------------------------- 2.4.5 Document A separate volume, DIDOC_0001, provides documentation pertaining to the raw and reduced HRII data sets, as well the entire DI archive, and nominally includes: - Image logs with notes from the encounter, starting at 28 hours before impact - Log of HRII pointing and scan directions from June 20 through July 6, 2005 - HRII slit/HRIV context images; For each HRII frame taken during impact and lookback, the location and size of the IR slit was superimposed on an HRIV image taken close in time to the IR frame - The instrument calibration paper by Klaasen et al. 2006 [15] - A report about the known limitations of the IR calibration pipeline and the resulting reduced data (version 1.0) - Chapters in Deep Impact Mission: Looking Beneath the Surface of a Cometary Nucleus, published by Space Science Reviews - A report about the known discrepancy between the two spacecraft clocks and UTC - A description of the quaternion found in the PDS labels - A day of year calendar for 2005 (converts day of year to month and day) - The IDL programs used for the calibration pipeline (provided only as documentation; the programs are not supported) - The DI local Data Dictionary which consists of the full PDS Data Dictionary plus keywords specific to DI, such as DEEPIMPACT:IMAGE_MID_TIME - The Project Data Management Plan for the mission - This Archive Interface Control Document 2.4.6 Index This directory contains a file that serves as an index into the products in the data directory. Index file includes all of the values found in the data label that are relevant to science, such as INSTRUMENT_IMAGE_MODE, INTEGRATION_DURATION, etc. --------------------------------- Page 24 --------------------------------- 2.5 Data File Naming Conventions and Product IDs The naming convention for the products in the data directory for the raw and calibrated data sets is: hicccccccccc_sssssss_nnn{_xx}.fit or .lbl where: - hi = instrument (''hi'' for the HRI IR Spectrometer) - p = spacecraft clock parition, an integer - cccccccccc = spacecraft clock count at the mid-point of the exposure, without the clock partition string - ssssssss = exposure ID - nnn = image number with exposure ID - xx = r for RAD, rr for RADREV, not used for RAW Since file names are unique within a data set, PRODUCT_IDs are formed from the FITS file name, where the period before the extension is replaced with an underscore. --------------------------------- Page 25 --------------------------------- 2.6 Standards Used in Data Product Generation 2.6.1 PDS Standards The version 3, PDS3, of the PDS Standards Reference [1] and revision E of the PDS Data Dictionary and the Deep Impact Local Data Dictionary [2] were followed when generating the data products. 2.6.2 Time Standards Times given in the PDS labels are UTC, unless otherwise specified. 2.6.3 Reference Frame Standards PDS labels for raw and calibrated HRII spectral image data products contain geometry keywords and values based on the inertial reference frames Earth mean equator J2000 (EMEJ2000). The exception is the ECLIP_NORTH_CLOCK_ANGLE which in the Ecliptic J2000 frame (ECLIPJ2000). Definitions of geometry keywords are defined in section 3.2 of this document and explicitly refer the appropriate reference frames. 2.6.4 Image Orientation For consistency, raw and reduced images, as produced by the DI data pipeline and analyzed by the science team, are stored in this PDS archive. In particular, the spectrometer's slit is vertical such that the top of the slit in an HRII image corresponds to the top of an HRIV and MRI image. The LINE_DISPLAY_DIRECTION and SAMPLE_DISPLAY_DIRECTION keywords in the product labels describe how the data should be displayed. For raw and calibrated images, samples are displayed from left to right and lines from the bottom to the top, such that the first pixel read from the FITS file is displayed in the lower-left corner of a graphics window and the last pixel in the upper-right. Although this orientation provides views ''as seen'' by the spacecraft, it places ecliptic north approximately to the right and the sun towards the bottom for all images from approach to shield mode at encounter. As the flyby spacecraft came out of shield mode, it turned and looked back at Tempel 1. Therefore, all post-images have ecliptic north approximately to the left and the sun approximately towards the top. This topic is discussed in Klaasen et al. 2006 [15]. See section 2.3.2 for more information. --------------------------------- Page 26 --------------------------------- 3 Detailed Specifications of Data Products 3.1 Sample PDS Labels This section provides sample PDS labels for raw and calibrated HRII spectral image FITS data. 3.1.1 Science Level 2 (Raw) HRII Data Product PDS_VERSION_ID = PDS3 RECORD_TYPE = "FIXED_LENGTH" RECORD_BYTES = 2880 FILE_RECORDS = 562 ^HEADER = "HI0173631726_9000001_001.FIT" ^IMAGE = ("HI0173631726_9000001_001.FIT", 14) ^EXTENSION_QUALITY_HEADER = ("HI0173631726_9000001_001.FIT", 379) ^EXTENSION_QUALITY_IMAGE = ("HI0173631726_9000001_001.FIT", 380) DATA_SET_ID = "DIF-C-HRII-2-9P-ENCOUNTER-V1.0" INSTRUMENT_HOST_NAME = "DEEP IMPACT FLYBY SPACECRAFT" INSTRUMENT_HOST_ID = "DIF" INSTRUMENT_NAME = " DEEP IMPACT HIGH RESOLUTION INSTRUMENT - IR SPECTROMETER" INSTRUMENT_ID = "HRII" /***** PRODUCT INFORMATION *****/ PRODUCT_ID = "HI0173631726_9000001_001_FIT" PRODUCT_NAME = " DI FLIGHT DATA, RAW HRII, HI0173631726_9000001_001.FIT" PRODUCT_CREATION_TIME = 2006-06-14T20:16:07 PRODUCT_TYPE = "EDR" /***** TIME INFORMATION *****/ START_TIME = 2005-07-03T03:04:55.859 STOP_TIME = 2005-07-03T03:04:58.979 DEEPIMPACT:IMAGE_MID_TIME = 2005-07-03T03:04:57.419 START_JULIAN_DATE_VALUE = 2453554.6284243 STOP_JULIAN_DATE_VALUE = 2453554.6284605 MID_JULIAN_DATE_VALUE = 2453554.6284424 SPACECRAFT_CLOCK_START_COUNT = "1/0173631725.033" SPACECRAFT_CLOCK_STOP_COUNT = "1/0173631728.064" DEEPIMPACT:SPACECRAFT_CLOCK_MID_COUNT = "1/0173631726.177" DEEPIMPACT:TIME_FROM_IMPACT_VALUE = -95978.402 EARTH_RECEIVED_TIME = 2005-07-03T03:12:17.958 /***** OBSERVATION INFORMATION *****/ MISSION_PHASE_NAME = "9P ENCOUNTER" DEEPIMPACT:MISSION_ACTIVITY_TYPE = "CONTINUOUS COMET IMAGING" OBSERVATION_TYPE = "CONTINUOUS COMET IMAGING" TARGET_NAME = "9P/TEMPEL 1 (1867 G1)" TARGET_DESC = "9P/TEMPEL 1 (1867 G1)" INSTRUMENT_MODE_ID = 4 DEEPIMPACT:COMPRESSED_IMAGE_VALUE = "UNCOMPRESSED" COMPRESSOR_ID = "N/A" OBSERVATION_ID = 9000001 IMAGE_NUMBER = 1 DEEPIMPACT:COMMANDED_IMAGE_COUNT = 50 FILTER_NUMBER = "N/A" FILTER_NAME = "N/A" CENTER_FILTER_WAVELENGTH = "N/A" DEEPIMPACT:MINIMUM_EXPOSURE_DURATION = 2861.330 --------------------------------- Page 27 --------------------------------- DEEPIMPACT:COMMANDED_EXPOSURE_DURATION = 259.000 DEEPIMPACT:INTERFRAME_DELAY_DURATION = 0.000 DEEPIMPACT:INTEGRATION_DURATION = 3120.330 INSTRUMENT_TEMPERATURE = ( 301.061 , 300.546 , 293.094 , 299.333 , 271.879 , 170.253 , 137.887 , 136.701 , 129.825 , 136.834 , 84.172 ) INSTRUMENT_TEMPERATURE_POINT = ( "INSTRUMENT CONTROLLER PROCESSING BOARD", "CCD SIGNAL PROCESSING BOARD", "IR SIGNAL PROCESSING BOARD", "LVPS SIGNAL PROCESSING BOARD", "CCD PREAMP BOX", "CCD ON-CHIP SENSOR", "PRISMS", "PRIMARY MIRROR", "SECONDARY MIRROR", "SPECTRAL IMAGING MODULE COVER", "IR FPA ON-CHIP SENSOR" ) INSTRUMENT_VOLTAGE = ( 1.205 , 1.213 , 1.204 , 1.217 , 5.124 , 5.121 , 5.111 , 5.102 , 5.028 , -5.020 , 5.003 , -9.189 , 0.245 , 0.740 , 3.407 , "UNK" ) INSTRUMENT_VOLTAGE_POINT = ( "CCD OFFSET FROM ADC REF QUAD A", "CCD OFFSET FROM ADC REF QUAD B", "CCD OFFSET FROM ADC REF QUAD C", "CCD OFFSET FROM ADC REF QUAD D", "CCD OUTPUT AMP DRAIN QUAD A", "CCD OUTPUT AMP DRAIN QUAD B", "CCD OUTPUT AMP DRAIN QUAD C", "CCD OUTPUT AMP DRAIN QUAD D", "CCD SERIAL CLOCK POSITIVE", "CCD SERIAL CLOCK NEGATIVE", "CCD PARALLEL CLOCK POSITIVE", "CCD PARALLEL CLOCK NEGATIVE", "IR RESET", "IR SUBSTRATE", "IR BIASGATE", "IR CALIB LAMP" ) /***** IMAGE INFORMATION *****/ HORIZONTAL_PIXEL_SCALE = "N/A" VERTICAL_PIXEL_SCALE = 9886.267 /***** GEOMETRY PARAMETERS *****/ NOTE = " Earth Mean Equator and Vernal Equinox J2000 is the inertial reference system used to specify observational geometry. Geometric parameters are based on the best available SPICE data at the time this product was created. Refer to the Deep Impact SPICE archive for the most current observational geometry. The spacecraft clock count at the middle of the exposure was used to derive the geometry." RIGHT_ASCENSION = 201.438770174 --------------------------------- Page 28 --------------------------------- DECLINATION = 25.032945845 CELESTIAL_NORTH_CLOCK_ANGLE = 133.7346 SOLAR_NORTH_POLE_CLOCK_ANGLE = 108.048 QUATERNION = (0.827629258579, 0.289245616426, -0.452512218465, -0.163093457450) QUATERNION_DESC = "QUATERNION_DESC.ASC" DEEPIMPACT:INST_EMEJ2000_VELOCITY_VECTOR = (-7.059765342840E-009 ,2.912641748180E-006 , 2.388730630490E-006 ) DEEPIMPACT:TARGET_SC_POSITION_VECTOR = (833897.894 , 327145.601 , -418297.418 ) DEEPIMPACT:TARGET_SC_VELOCITY_VECTOR = (-8.6863 , -3.4080 , 4.3569 ) TARGET_CENTER_DISTANCE = 988626.6598 SC_SUN_POSITION_VECTOR = (89455143.956 , 189836387.826 , 80825682.044 ) SPACECRAFT_SOLAR_DISTANCE = 224884120.828 TARGET_SUN_POSITION_VECTOR = (90289041.851 , 190163533.427 , 80407384.626 ) TARGET_SUN_VELOCITY_VECTOR = (-27.0136 , 8.4540 , 9.6158 ) TARGET_HELIOCENTRIC_DISTANCE = 225343355.851 SC_EARTH_POSITION_VECTOR = (119056355.934 , 52972679.154 , 21494161.633 ) DEEPIMPACT:SC_GEOCENTRIC_DISTANCE = 132070131.405 EARTH_TARGET_POSITION_VECTOR = (-119889808.178 , -53299820.698 , -21078395.953 ) EARTH_TARGET_VELOCITY_VECTOR = (-1.7298 , -13.6711 , -11.8768 ) TARGET_GEOCENTRIC_DISTANCE = 132886175.982 PHASE_ANGLE = 62.210 /***** PROCESSING_HISTORY_TEXT *****/ PROCESSING_HISTORY_TEXT = "RAW" OBJECT = HEADER BYTES = 37440 HEADER_TYPE = "FITS" INTERCHANGE_FORMAT = "BINARY" RECORDS = 13 DESCRIPTION = " FITS format defined in NASA/Science Office Standards Technology 100-1.0 " END_OBJECT = HEADER OBJECT = IMAGE LINE_SAMPLES = 1024 LINES = 512 SAMPLE_BITS = 16 SAMPLE_TYPE = "MSB_INTEGER" AXIS_ORDER_TYPE = "FIRST_INDEX_FASTEST" LINE_DISPLAY_DIRECTION = "UP" SAMPLE_DISPLAY_DIRECTION = "RIGHT" UNIT = "DATA NUMBER" MINIMUM = -150 MAXIMUM = 16232 MEDIAN = 2287.0 STANDARD_DEVIATION = 540.5 END_OBJECT = IMAGE OBJECT = EXTENSION_QUALITY_HEADER BYTES = 2880 HEADER_TYPE = "FITS" INTERCHANGE_FORMAT = "BINARY" RECORDS = 1 DESCRIPTION = " This extension contains a quality map for the primary image array. Each of the one-byte pixels in this map is composed of eight bits. Each bit represents a specific characteristic about the corresponding pixel in the primary image array. For a raw image, only the bit for a missing data value is set (bit 1 below). The remaining 7 bits apply only to --------------------------------- Page 29 --------------------------------- a calibrated image and are thus set to zero for a raw image. The bits are described below and are listed from the least-significant (0) to most-significant (7): 0 = Bad 1 = Data for this pixel was not received from the spacecraft or this pixel is one of the image header bytes. 2 = Despiked 3 = Interpolated 4 = Partially saturated 5 = Mostly saturated 6 = ADC saturated 7 = Ultra compressed " END_OBJECT = EXTENSION_QUALITY_HEADER OBJECT = EXTENSION_QUALITY_IMAGE LINE_SAMPLES = 1024 LINES = 512 SAMPLE_BITS = 8 SAMPLE_TYPE = "MSB_UNSIGNED_INTEGER" AXIS_ORDER_TYPE = "FIRST_INDEX_FASTEST" LINE_DISPLAY_DIRECTION = "UP" SAMPLE_DISPLAY_DIRECTION = "RIGHT" END_OBJECT = EXTENSION_QUALITY_IMAGE --------------------------------- Page 30 --------------------------------- 3.1.2 Science Level 3/4 (Calibrated) HRII Data Product This is an example of a PDS label for reversible, calibrated HRII spectral image FITS, in units of radiance: RADREV (reversible calibrations and not cleaned) or RAD (irreversible and cleaned). PDS_VERSION_ID = PDS3 RECORD_TYPE = "FIXED_LENGTH" RECORD_BYTES = 2880 FILE_RECORDS = 3120 ^HEADER = "HI0173631726_9000001_001_RR.FIT" ^IMAGE = ("HI0173631726_9000001_001_RR.FIT", 18) ^EXTENSION_QUALITY_HEADER = ("HI0173631726_9000001_001_RR.FIT", 747) ^EXTENSION_QUALITY_IMAGE = ("HI0173631726_9000001_001_RR.FIT", 748) ^EXTENSION_WAVELENGTH_HEADER = ("HI0173631726_9000001_001_RR.FIT", 931) ^EXTENSION_WAVELENGTH_IMAGE = ("HI0173631726_9000001_001_RR.FIT", 932) ^EXTENSION_SPEC_BANDWIDTH_HEADER = ("HI0173631726_9000001_001_RR.FIT", 1661) ^EXTENSION_SPEC_BANDWIDTH_IMAGE = ("HI0173631726_9000001_001_RR.FIT", 1662) ^EXTENSION_SNR_HEADER = ("HI0173631726_9000001_001_RR.FIT", 2391) ^EXTENSION_SNR_IMAGE = ("HI0173631726_9000001_001_RR.FIT", 2392) DATA_SET_ID = "DIF-C-HRII-3/4-9P-ENCOUNTER-V2.0" INSTRUMENT_HOST_NAME = "DEEP IMPACT FLYBY SPACECRAFT" INSTRUMENT_HOST_ID = "DIF" INSTRUMENT_NAME = " DEEP IMPACT HIGH RESOLUTION INSTRUMENT - IR SPECTROMETER" INSTRUMENT_ID = "HRII" /***** PRODUCT INFORMATION *****/ PRODUCT_ID = "HI0173631726_9000001_001_RR_FIT" PRODUCT_NAME = " DI FLIGHT DATA, REDUCED HRII, HI0173631726_9000001_001_RR.FIT" PRODUCT_CREATION_TIME = 2006-11-14T14:43:13 PRODUCT_TYPE = "RDR" /***** TIME INFORMATION *****/ START_TIME = 2005-07-03T03:04:55.859 STOP_TIME = 2005-07-03T03:04:58.979 DEEPIMPACT:IMAGE_MID_TIME = 2005-07-03T03:04:57.419 START_JULIAN_DATE_VALUE = 2453554.6284243 STOP_JULIAN_DATE_VALUE = 2453554.6284605 MID_JULIAN_DATE_VALUE = 2453554.6284424 SPACECRAFT_CLOCK_START_COUNT = "1/0173631725.033" SPACECRAFT_CLOCK_STOP_COUNT = "1/0173631728.064" DEEPIMPACT:SPACECRAFT_CLOCK_MID_COUNT = "1/0173631726.177" DEEPIMPACT:TIME_FROM_IMPACT_VALUE = -95976.846 EARTH_RECEIVED_TIME = 2005-07-03T03:12:17.958 /***** OBSERVATION INFORMATION *****/ MISSION_PHASE_NAME = "9P ENCOUNTER" DEEPIMPACT:MISSION_ACTIVITY_TYPE = "CONTINUOUS COMET IMAGING" OBSERVATION_TYPE = "CONTINUOUS COMET IMAGING" TARGET_NAME = "9P/TEMPEL 1 (1867 G1)" INSTRUMENT_MODE_ID = 4 DEEPIMPACT:COMPRESSED_IMAGE_VALUE = "UNCOMPRESSED" COMPRESSOR_ID = "N/A" OBSERVATION_ID = 9000001 IMAGE_NUMBER = 1 DEEPIMPACT:COMMANDED_IMAGE_COUNT = 50 FILTER_NUMBER = "N/A" FILTER_NAME = "N/A" CENTER_FILTER_WAVELENGTH = "N/A" DEEPIMPACT:MINIMUM_EXPOSURE_DURATION = 2861.330 DEEPIMPACT:COMMANDED_EXPOSURE_DURATION = 259.000 DEEPIMPACT:INTERFRAME_DELAY_DURATION = 0.000 --------------------------------- Page 31 --------------------------------- DEEPIMPACT:INTEGRATION_DURATION = 3120.330 INSTRUMENT_TEMPERATURE = ( 301.061 , 300.546 , 293.094 , 299.333 , 271.879 , 170.253 , 137.887 , 136.701 , 129.825 , 136.834 , 84.172 ) INSTRUMENT_TEMPERATURE_POINT = ( "INSTRUMENT CONTROLLER PROCESSING BOARD", "CCD SIGNAL PROCESSING BOARD", "IR SIGNAL PROCESSING BOARD", "LVPS SIGNAL PROCESSING BOARD", "CCD PREAMP BOX", "CCD ON-CHIP SENSOR", "PRISMS", "PRIMARY MIRROR", "SECONDARY MIRROR", "SPECTRAL IMAGING MODULE COVER", "IR FPA ON-CHIP SENSOR" ) INSTRUMENT_VOLTAGE = ( 1.205 , 1.213 , 1.204 , 1.217 , 5.124 , 5.121 , 5.111 , 5.102 , 5.028 , -5.020 , 5.003 , -9.189 , 0.245 , 0.740 , 3.407 , "UNK" ) INSTRUMENT_VOLTAGE_POINT = ( "CCD OFFSET FROM ADC REF QUAD A", "CCD OFFSET FROM ADC REF QUAD B", "CCD OFFSET FROM ADC REF QUAD C", "CCD OFFSET FROM ADC REF QUAD D", "CCD OUTPUT AMP DRAIN QUAD A", "CCD OUTPUT AMP DRAIN QUAD B", "CCD OUTPUT AMP DRAIN QUAD C", "CCD OUTPUT AMP DRAIN QUAD D", "CCD SERIAL CLOCK POSITIVE", "CCD SERIAL CLOCK NEGATIVE", "CCD PARALLEL CLOCK POSITIVE", "CCD PARALLEL CLOCK NEGATIVE", "IR RESET", "IR SUBSTRATE", "IR BIASGATE", "IR CALIB LAMP" ) /***** IMAGE INFORMATION *****/ HORIZONTAL_PIXEL_SCALE = "N/A" VERTICAL_PIXEL_SCALE = 9884.886 /***** GEOMETRY PARAMETERS *****/ NOTE = " Earth Mean Equator and Vernal Equinox J2000 is the inertial reference system used to specify observational geometry. Geometric parameters were calculated using version 1.0 of the Deep Impact SPICE data set archived in PDS." SPICE_FILE_NAME = ("NAIFSTARNAMES_2005321_V01.TPC", "IMPACTTOI_0006.TPC", "NAIF0008.TLS", "PCK00008.TPC", "DI_TEMPEL1_V01.TPC", --------------------------------- Page 32 --------------------------------- "DIF_SCLKSCET_00015_SCIENCE.TSC", "DII_SCLKSCET_00008_SCIENCE.TSC", "DI_V16.TF", "DIF_HRI_V10.TI", "DIF_MRI_V10.TI", "DII_ITS_V10.TI", "DIF_SC_050112_050809.BC", "DIF_SC_050225_HIGHRATE.BC", "DIF_SC_050704_HIGHRATE.BC", "DII_SC_050112_050703.BC", "DII_SC_050703_050704.BC", "STARS_2005321_V01.BSP", "JUP164_20YEAR.BSP", "DII_PREENC174_NAV_V1.BSP", "DIF_PREENC174_NAV_V1.BSP", "DI_TEMPEL1_SSD_V1.BSP", "DI_FINALENC_NAV_V3_TO2006048.BSP") RIGHT_ASCENSION = 201.438770174 DECLINATION = 25.032945845 CELESTIAL_NORTH_CLOCK_ANGLE = 133.7346 SOLAR_NORTH_POLE_CLOCK_ANGLE = 108.0476 QUATERNION = (0.827629258579, 0.289245616426, -0.452512218465, -0.163093457450) QUATERNION_DESC = "QUATERNION_DESC.ASC" DEEPIMPACT:INST_EMEJ2000_VELOCITY_VECTOR = (-7.059765342840e-009 ,2.912641748180e-006 , 2.388730630490e-006 ) DEEPIMPACT:TARGET_SC_POSITION_VECTOR = (833780.958 , 327100.865 , -418239.182 ) DEEPIMPACT:TARGET_SC_VELOCITY_VECTOR = (-8.6863 , -3.4080 , 4.3569 ) TARGET_CENTER_DISTANCE = 988488.5809 SC_SUN_POSITION_VECTOR = (89455143.961 , 189836387.843 , 80825682.044 ) SPACECRAFT_SOLAR_DISTANCE = 224884120.845 TARGET_SUN_POSITION_VECTOR = (90288924.919 , 190163488.707 , 80407442.861 ) TARGET_SUN_VELOCITY_VECTOR = (-27.0136 , 8.4540 , 9.6159 ) TARGET_HELIOCENTRIC_DISTANCE = 225343292.041 SC_EARTH_POSITION_VECTOR = (119056355.934 , 52972679.154 , 21494161.633 ) DEEPIMPACT:SC_GEOCENTRIC_DISTANCE = 132070131.405 EARTH_TARGET_POSITION_VECTOR = (-119889691.238 , -53299775.963 , -21078454.191 ) EARTH_TARGET_VELOCITY_VECTOR = (-1.7298 , -13.6711 , -11.8768 ) TARGET_GEOCENTRIC_DISTANCE = 132886061.775 PHASE_ANGLE = 62.210 /***** PROCESSING HISTORY *****/ PROCESSING_HISTORY_TEXT = " FILEVERN= 1.10 / Version number of file format PGMNAME = 'DICAL ' / Program name that produced this file PGMVERN = 5.00 / Version number of the above program DATAQUAL= -999 / Data quality (1=good, etc) TMPVLTUP= F / Physical temps and voltages updated (T/F) TMPVLTV = ' ' / Valid date of physical temps ,voltages used SMOBENT = 137.497 / Smoothed over time version of OPTBENT [K] CMPRESSN= F / Decompression performed (T/F) LUTTABLE= ' ' / Lossy lookup table/algorithm applied CMPRMETH= -999 / Decompress method. 1=avg,2=gauss,3=uniform SATPIX = T / Saturated pixels flagged (T/F) SMSATVL = 8000 / DN value where some pixels are saturated MSTSATVL= 11000 / DN value where most pixels are saturated ADCSATVL= 16383 / DN value where the ADC encoder is saturated BITCORR = F / Uneven bit weighting corrected (T/F) BITLUT = ' ' / Bit weighting lookup table used DARKCORR= T / Dark subtration (T/F) DARKALG = 'MODEL ' / Algorithm used to create dark DARKFN = 'HRIIR_050620_1_4.FIT' / File name for frame/model used --------------------------------- Page 33 --------------------------------- BIASFN = ' ' / Filename of bias frame used XTALK = T / Electrical crosstalk removed (T/F) XTALKFN = 'HRIIR_050112_2_4.FIT' / Filename of crosstalk gains used GAINCORR= F / Quadrant Gain correction performed (T/F) GAINFN = ' ' / Filename of gain values used FLATCORR= F / Flat fielded FLATFILE= ' ' / Name of flat field applied BPIXFL = T / Bad pixels flagged (T/F) BPIXFILE= 'HRIIR_050627_2_4_999.FIT' / Name of bad pixel map applied CLEAN = F / Cleaned/fill small gaps (T/F) CLEANV = -999 / Max filled gap size; -999999=>fill failed CLNBAD = F / Bad pixels cleaned CLNMISS = F / Missing data cleaned DESPIKE = F / Despiking applied (T/F) DESPIKET= -999 / Despiking threshold used (sigma) DESPIKEI= -999 / Number of iterations of despiking DESPIKEB= -999 / Boxsize for despiking DESPIKEM= ' ' / Metric used for despiking. Mean or Median DENOISE = F / Denoising applied (T/F) DENOISEV= ' ' / Denoise parameter applied DECON = F / Deconvolution performed (T/F) DECONPSF= ' ' / Deconvolution psf used DECONALG= ' ' / Deconvolution algorithm used DECONV = ' ' / Deconvolution algorithm-specific parameter LINEARIZ= T / Linearization applied (T/F) LINAC0 = 'HRIIR_050115_3_4.FIT' / Quad A additive constant for linearization LINAC1 = 'HRIIR_050115_3_4.FIT' / Quad A coefficient for x term LINAC2 = 'HRIIR_050115_3_4.FIT' / Quad A coefficient for x-squared term LINAC3 = 'HRIIR_050115_3_4.FIT' / Quad A coefficient for x-cubed term LINAC4 = -999.000000000 / Quad A coefficient for x-4th term LINBC0 = 'HRIIR_050115_3_4.FIT' / Quad B additive constant for linearization LINBC1 = 'HRIIR_050115_3_4.FIT' / Quad B coefficient for x term LINBC2 = 'HRIIR_050115_3_4.FIT' / Quad B coefficient for x-squared term LINBC3 = 'HRIIR_050115_3_4.FIT' / Quad B coefficient for x-cubed term LINBC4 = -999.000000000 / Quad B coefficient for x-4th term MDARKVER= 2.00000 / Master dark frame version DRKPMODE= '* ' / Mode of the previous set taken DARKISG = -0.999000 / Inter-sequence gap [msec] DARKA0 = 3.0060000E+10 / Dark level temp coef A_0 DARKA1 = -3384.4000 / Dark level temp coef A_1 DARKB0 = 65630000. / Dark level temp coef B_0 DARKB1 = -2002.0000 / Dark level temp coef B_1 DARKC0 = 0.0583000 / Dark level temp coef C_0 DRKTMSCL= 1.00000 / Dark scaling factor for time dependency DARKPLAT= F / Dark plateau reached DARKMSCL= -999.000000000 / Manually derived scaling factor CALCORR = T / Calibration Applied (T/F) CALCONST= -999.000000000 / Calibration Constant Applied CALNUMB0= 0 / Number of ZERO calibration factors found CALMAP1 = 'HRIIR_050112_9_4_999.FIT' / Calibration constant map interped (1) CALMAP2 = 'HRIIR_050112_9_4_000.FIT' / Calibration constant map interped (2) SPECMAP1= ' ' / Spectral map interpolated over (1) SPECMAP2= ' ' / Spectral map interpolated over (2) HLUTFN = ' ' / H lambda lookup table used " /***** IMAGE STATISTICS *****/ DEEPIMPACT:BAD_PIXEL_COUNT = 18088 DEEPIMPACT:MISSING_PIXEL_COUNT = 50 DEEPIMPACT:DESPIKED_PIXEL_COUNT = 0 DEEPIMPACT:INTERPOLATED_PIXEL_COUNT = 0 DEEPIMPACT:PARTIAL_SATURATED_PIXEL_COUNT= 726 DEEPIMPACT:SATURATED_PIXEL_COUNT = 261 DEEPIMPACT:ADC_SATURATED_PIXEL_COUNT = 0 DEEPIMPACT:ULTRA_COMPRESSED_PIXEL_COUNT = 0 OBJECT = HEADER BYTES = 48960 HEADER_TYPE = "FITS" INTERCHANGE_FORMAT = "BINARY" RECORDS = 17 --------------------------------- Page 34 --------------------------------- DESCRIPTION = " FITS format defined in NASA/Science Office Standards Technology 100-1.0 " END_OBJECT = HEADER OBJECT = IMAGE LINE_SAMPLES = 1024 LINES = 512 SAMPLE_BITS = 32 SAMPLE_TYPE = "IEEE_REAL" AXIS_ORDER_TYPE = "FIRST_INDEX_FASTEST" LINE_DISPLAY_DIRECTION = "UP" SAMPLE_DISPLAY_DIRECTION = "RIGHT" UNIT = "W/[M**2 SR UM]" MINIMUM = -1.41313e+002 MAXIMUM = 4.36080e+002 MEDIAN = 9.91119e-002 STANDARD_DEVIATION = 2.54276e+000 END_OBJECT = IMAGE OBJECT = EXTENSION_QUALITY_HEADER BYTES = 2880 HEADER_TYPE = "FITS" INTERCHANGE_FORMAT = "BINARY" RECORDS = 1 DESCRIPTION = " This extension contains a quality map for the primary image array. Each of the one-byte pixels in this map is composed of eight bits. Each bit represents a specific characteristic about the corresponding pixel in the primary image array. For a raw image, only the bit for a missing data value is set (bit 1 below). The remaining 7 bits apply only to a calibrated image and are thus set to zero for a raw image. The bits are described below and are listed from the least-significant (0) to most-significant (7): 0 = Bad 1 = Data for this pixel was not received from the spacecraft or this pixel is one of the image header bytes. 2 = Despiked 3 = Interpolated 4 = Partially saturated 5 = Mostly saturated 6 = ADC saturated 7 = Ultra compressed " END_OBJECT = EXTENSION_QUALITY_HEADER OBJECT = EXTENSION_QUALITY_IMAGE LINE_SAMPLES = 1024 LINES = 512 SAMPLE_BITS = 8 SAMPLE_TYPE = "MSB_UNSIGNED_INTEGER" AXIS_ORDER_TYPE = "FIRST_INDEX_FASTEST" LINE_DISPLAY_DIRECTION = "UP" SAMPLE_DISPLAY_DIRECTION = "RIGHT" END_OBJECT = EXTENSION_QUALITY_IMAGE OBJECT = EXTENSION_WAVELENGTH_HEADER BYTES = 2880 HEADER_TYPE = "FITS" INTERCHANGE_FORMAT = "BINARY" RECORDS = 1 DESCRIPTION = " This extension is the wavelength map for the primary image array. " END_OBJECT = EXTENSION_WAVELENGTH_HEADER OBJECT = EXTENSION_WAVELENGTH_IMAGE LINE_SAMPLES = 1024 LINES = 512 SAMPLE_BITS = 32 SAMPLE_TYPE = "IEEE_REAL" --------------------------------- Page 35 --------------------------------- AXIS_ORDER_TYPE = "FIRST_INDEX_FASTEST" UNIT = "MICROMETER" LINE_DISPLAY_DIRECTION = "UP" SAMPLE_DISPLAY_DIRECTION = "RIGHT" END_OBJECT = EXTENSION_WAVELENGTH_IMAGE OBJECT = EXTENSION_SPEC_BANDWIDTH_HEADER BYTES = 2880 HEADER_TYPE = "FITS" INTERCHANGE_FORMAT = "BINARY" RECORDS = 1 DESCRIPTION = " This extension is the spectral bandwidth map for the primary image array. " END_OBJECT = EXTENSION_SPEC_BANDWIDTH_HEADER OBJECT = EXTENSION_SPEC_BANDWIDTH_IMAGE LINE_SAMPLES = 1024 LINES = 512 SAMPLE_BITS = 32 SAMPLE_TYPE = "IEEE_REAL" AXIS_ORDER_TYPE = "FIRST_INDEX_FASTEST" UNIT = "MICROMETER" LINE_DISPLAY_DIRECTION = "UP" SAMPLE_DISPLAY_DIRECTION = "RIGHT" END_OBJECT = EXTENSION_SPEC_BANDWIDTH_IMAGE OBJECT = EXTENSION_SNR_HEADER BYTES = 2880 HEADER_TYPE = "FITS" INTERCHANGE_FORMAT = "BINARY" RECORDS = 1 DESCRIPTION = " This extension is the signal-to-noise map for the primary image array. " END_OBJECT = EXTENSION_SNR_HEADER OBJECT = EXTENSION_SNR_IMAGE LINE_SAMPLES = 1024 LINES = 512 SAMPLE_BITS = 32 SAMPLE_TYPE = "IEEE_REAL" AXIS_ORDER_TYPE = "FIRST_INDEX_FASTEST" LINE_DISPLAY_DIRECTION = "UP" SAMPLE_DISPLAY_DIRECTION = "RIGHT" END_OBJECT = EXTENSION_SNR_IMAGE END