Cassini Imaging Science Subsystem (ISS) Tour VICAR Image Data File and Detached Planetary Data System (PDS) Label Software Interface Specification (SIS) ____________________________________ Charles Avis ISS Instrument Operations Task Lead ____________________________________ Carolyn Porco ISS Team Lead ____________________________________ Sue LaVoie PDS Imaging Node Manager Tour Version 1.2 JPL D-24724, DOIS-002 Custodian: A. Culver, March 10, 2006 Paper copies of this document may not be current and should not be relied upon for official purposes. The current version is available from the Cassini Electronic Library at https://cel.jpl.nasa.gov/cedr/home/mcdl.html. TABLE OF CONTENTS Change Log 1. INTRODUCTION o 1.1 Overview o 1.2 Scope o 1.3 Applicable Documents o 1.4 Configuration Management 2. SOURCE 3. FILE NAMING o 3.1 PDS Detached Label File o 3.2 Image Data File 4. STRUCTURE CONVENTIONS 5. SOURCE OF DATA VALUES 6. PDS LABEL INTERFACE SPECIFICATIONS o 6.1 Introduction o 6.2 PDS File Characteristics and Pointers to Objects o 6.3 Label Keywords o 6.4 PDS Objects 7. IMAGE DATA FILE INTERFACE SPECIFICATIONS o 7.1 Image Data File Structure o 7.2 VICAR Label Description 7.2.1 Introduction 7.2.2 System Label Items 7.2.3 Property Label Items o 7.3 Binary Telemetry Header Record 7.3.1 Introduction o 7.3.2 Record Structure o 7.4 Line Records o 7.4.1 Introduction o 7.4.2 Record Structure 8. APPENDIX A - Tables 9. APPENDIX B - Acronyms 10. APPENDIX C - Sample Image Data File Label 11. APPENDIX D - Sample Detached PDS Label 12. APPENDIX E - Overclocked and Extended Pixel Values Change Log: Date Author of Changes Description May, 2000 Amy Culver Replaced property label keyword tables (Section 6.2.3) with version negotiated and accepted by PDS Central and Imaging Nodes. Updated formatting and content of other tables for consistency. Jul, 2000 Amy Culver Updated catalog-based sources to reflect new field names in Cassini tables. Aug, 2000 Amy Culver Added new keywords. May, 2001 Amy Culver Modified description of BIAS_STRIP_MEAN. Updated binary line prefix to describe overclocked pixel data returned by new version of flight software. Sep, 2002 Amy Culver Initial Release for Tour. Where changes are noted, they are relative to the Cruise VICAR label SIS (D-18976 Changed title, D#, Fortified Introduction - Overview. Incorporated detached PDS label and added PDS signatory. Removed the following keywords: CALIBRATION_LAMP_DURATION, NOTE. Changed definition of the following keywords: - IMAGE_TIME now reflects midpoint of exposure, instead of shutter close time. - NOTE renamed to DESCRIPTION, now 255 chars instead of previous PDS limit of 60 chars. - Added valid values for IMAGE_OBSERVATION_TYPE. - Corrected valid range of values for blocks per GOB in both INST_CMPRS_PARAM and binary header. - Updated valid values of keywords affected by a missing extended header. - Changed source of FLIGHT_SOFTWARE_VERSION_ID MISSION_PHASE_NAME. Included references to MIPL Tour database where appropriate. - Updated range of valid values for COMMAND_SEQUENCE_NUMBER. - Changed valid values of DATA_SET_ID, MISSION_NAME and MISSION_PHASE_NAME. Added the following keywords: - EXPECTED_MAXIMUM(full well, max DN) - EXPECTED PACKETS - INST_CMPRS_RATE (expected, actual) - METHOD_DESC - RECEIVED PACKETS - TARGET_DESC - TELEMETRY_FORMAT_ID - VALID_MAXIMUM(full well, max DN). Includes new table in Appendix A. Clarified description of bit & byte ordering. Added wavelengths to FILTER_NAME table in Appendix A. Made OPTICS_TEMPERATURE a two-valued array pertaining to front and rear optics temps. Added acronyms to Appendix B. Removed "Defaults" column, migrated info to "Valid Values" column. Sep 30, 2002 Amy Culver Modified valid value of DATA_SET_ID per PDS recommendation. Updated sample labels. Corrected typos. Included configuration management section. Oct 3, 2002 Amy Culver with IO/ISS Team/PDS at Boulder Changed reference to PERCENT_FULL_WELL and PERCENT_MAX_DN to EXPECTED_MAXIMUM_* to reflect changes in IOI file. Changed file naming convention for products and labels to conform to PDS standards. Added ORDER_NUMBER, SEQUENCE_NUMBER and TARGET_LIST keywords. Updated source for items from IOI which moved from header to param set table. Made IMAGE_OBSERVATION_TYPE a multivalued array. Updated descriptions of MISSING_LINES, MISSING_PACKET_FLAG, SEQUENCE_TITLE. Updated VALID_MAXIMUM table in Appendix A. Reverted to previous definition of IMAGE_TIME (same as STOP_TIME). Added new keyword, IMAGE_MID_TIME. Updated example labels. Oct 18, 2002 Amy Culver Revised to clarify/clean up as needed: Returned SHUTTER_STATE_ID keyword to Section 6.3 (inadvertently deleted during 10/3/02 editing.) Returned INSTRUMENT_MODE_ID keyword to Table 7.2.3.5 (inadvertently deleted during 10/3/02 editing.) For IMAGE_OBSERVATION_TYPE, VICAR requires list to be specified within parenthesis, not curly braces (as is the case for the PDS label.) Updated VICAR sections accordingly. Updated range for EXPECTED_PACKETS in PDS label (should be 1-2277 as in VICAR label.) Updated Table 8.5 per Vance Haemmerle/ Bob West. Table now reflects minimum full well saturation (to be used as VALID_MAXIMUM) which may exceed 4095. Cleaned up wording about case when shutter is inhibited for IMAGE_TIME and IMAGE_MID_TIME. Added clarification about filenames for preliminary products created without predict information. Nov, 2002 Amy Culver Updated source of fields coming from MIPL database to reflect actual field names. Nov 22, 2002 Amy Culver Clarified source of keyword values when extended header is missing Clarified source of INSTRUMENT_DATA_RATE Updated sample labels to reflect two valued array for OPTICS_TEMPERATURE. Also corrected order of keywords to be alphabetical. Added default value for TELEMETRY_FORMAT_ID. Corrected quote formatting used in tables to describe IMAGE_OBSERVATION_TYPE. (Single vs. double quotes reversed for PDS and VICAR label.) Dec 5, 2002 Amy Culver Corrected example preliminary file names (removed colons) Corrected references for NBB, NLB (should be sections 7.4.2 and 7.3.2) Dec 1, 2004 Amy Culver Modified the following fields due to ISS FSW 1.4 changes (ECR 103650): - DARK_STRIP_MEAN description in Tables 6.3 and 7.2.3.4 - The PDS pointer to the LINE_PREFIX_STRUCTURE in Table 6.4. - The binary line prefix extended pixel value in Table 7.4.2 - Updated the BLTYPE in the VICAR label to reference new binary line prefix format. Added annotation to PDS sample label DETECTOR_TEMPERATURE so value does not conflict With PDS Data Dictionary definition. Added Appendix E to clarify BIAS_STRIP_MEAN and DARK_STRIP_MEAN contents depending on the FLIGHT_SOFTWARE_VERSION_ID. Corrected erroneous PRODUCT_ID in the sample labels. Removed trailing "Z" from PRODUCT_CREATION_TIME in sample labels, as this time is local, not UTC. Clarified descriptions for BIAS_STRIP_MEAN, DELAYED_READOUT_FLAG, INST_CMPRS RATIO, INSTRUMENT_DATA_RATE, PRODUCT_CREATION_TIME, TARGET_DESC. Corrected values, conversion mapping and field Locations in the Binary Header (Table 7.3.2). Updated READOUT_CYCLE_INDEX (Table 8.4) to reflect Total readout time for single camera events. March, 2005 Amy Culver Modified Binary Header (Table 7.3.2) to reflect PCVoltage and Video Offset (incorporated in Extended Header by 1.4 FSW upgrade). March, 2006 Amy Culver Updated descriptions of INST_CMPRS_RATE, INST_CMPRS_RATIO and MISSING_LINES keywords for partial, lossy compressed images. Changed source of TELEMETRY_FORMAT_ID (to derive it from the INSTRUMENT_DATA_RATE when possible). 1. INTRODUCTION 1.1 Overview This Software Interface Specification describes the content and format of the Imaging Science Subsystem (ISS) image data files and detached Planetary Data System (PDS) labels generated by the Instrument Operations (IO) ISS operations software. There is a one-to-one-correspondence between image data files and detached PDS labels. The PDS label file contains pointers to the associated image data file. Each product delivery from IO to the ISS Science Team consists of both files. The files generated by IO and conforming to this SIS are operational versions of the images and labels. They resemble archive products as closely as possible, and the contents have been negotiated and accepted by the signatories, plus the Cassini Archive Engineer. There are areas where the operational products will need slight modifications in order to generate the final archive products - potentially the OBSERVATION_ID and the TARGET_NAME keywords. These label keywords are addressed in Sections 6 and 7. Each product data file has been reconstructed from telemetry packets into an image. The image has not been radiometrically or geometrically corrected. These image data files are considered to be "Level 2" according to the Committee on Data Management and Computation (CODMAC), and processing "Level 0" according to NASA. The ISS Science Team will provide and archive software to perform radiometric correction on archive versions of these product files. The product data files and labels, in combination with the radiometric correction software and calibration files form a product the Cassini Project currently refers to as "Level 1A". For background information about the camera operations, consult the "Cassini Imaging Science Subsystem Instrument Operations Handbook" (see References). 1.2 Scope This specification applies to ISS data collected after January, 2003, including Saturn Approach Science, Saturn Orbit Insertion, and Tour Operations. This SIS is intended to provide enough information to enable users to read and understand the data product. This SIS is intended for use by the ISS team scientists who will analyze and ultimately archive the data, the Navigation Team and Principle Investigators who request Support Imaging products. 1.3 Applicable Documents* * ISS Flight Software: Software Requirements Document, M. Girard, 10/15/93, D-10750 * EGSE Functional Requirements Document, J. Gerhard, 11/6/92, ISS Document Number 8.3.2. * /VICAR File Format * /, R. Deen, JPL Inter Office Memorandum IPSD:384-92-196, 9/25/92 EGSE VICAR Image Data File, JPL D-15683, 1 April 1998 * "Planetary Data System Standards Reference", Version 3.4, June 15, 2001, JPL D-7669, Part 2 * "Cassini Imaging Science Subsystem Instrument Operations Handbook", Version 1.0, JPL D-18628, 1 May 2000 * "Cassini Imaging Science Subsystem Southwest Research Institute Boulder, CO/Instrument Operations Instrument Operations Interface", J. Diehl and E. Sayfi, 09/17/02, Version 2.2, D-18981 * "Imaging Science Subsystem Calibration Report", Charles Avis and James Gerhard, JPL D-15133 * "Cassini/Huygens Program Archive Plan for Science Data", Version 1, August 3, 2000, JPL D-15976, PD 699-068. 1.4 Configuration Management This document is controlled by Cassini configuration management. Changes to the scope of this document must be requested via the Cassini project Engineering Change Request (ECR) process. Under this process, ECRs are impacted by the IO ISS/VIMS Manager and the ISS Team Lead, and approved by Project management. 2. SOURCE The image data files described herein are constructed by the IO ISS operations software from raw telemetry packets extracted from the Telemetry Delivery Subsystem (TDS). The images have not been radiometrically or geometrically corrected. 3. FILE NAMING The image data file associated with any given PDS label file contains identical information in the filename, with the exception of the "lbl" portion. 3.1 Detached PDS Label File The filename of the detached label is: Innnnnn_v.lbl where I is an instrument identifier ('N' or 'W'), nnnnnn is the numeric value of the spacecraft clock at the time of shutter close, v is the version number of the label file, and lbl is the literal string "LBL". Example: W1832898283_4.LBL NOTE: In some cases, a preliminary product may be generated without all the corresponding predicted information (due to a mismatch of parameters or incomplete information.) Once the parameter mismatch is resolved, and predicted information is updated in the IO/MIPL database if needed, a final version of the label will be generated following the file naming convention described above. During the interim, the preliminary label will be uniquely identified as follows: Innnnnn.DOY-HHMMSS.lbl where I is an instrument identifier ('N' or 'W'), nnnnnn is the numeric value of the spacecraft clock at the time of shutter close, DOY is the day of year the label was created, HH is the hour, MM is the minutes and SS is the seconds portion of the time the label was created, and lbl is the literal string "LBL". Example: W1832898283.294-133021.LBL 3.2 Image Data File The external filename of the image data file will consist of a string which incorporates information about the instrument name, the spacecraft clock and version. The instrument name is required because the spacecraft clock will not be unique for simultaneous exposures. The version is required because the same image may be built multiple times due to multiple downlinks, or multiple TDS queries, etc. The following format will be followed: Innnnn_v.img, where I is an instrument identifier ('N' or 'W') nnnnn is the numeric value of the spacecraft clock at the time of shutter close v is the version number of the file, and img is the literal string "IMG". Example: W1832898283_4.IMG NOTE: In some cases, a preliminary product may be generated without all the corresponding predicted information (due to a mismatch of parameters or incomplete information.) Once the parameter mismatch is resolved, and predicted information is updated in the IO/MIPL database if needed, a final version of the product will be generated following the file naming convention described above. During the interim, the preliminary product will be uniquely identified as follows: Innnnnn.DOY-HHMMSS where I is an instrument identifier ('N' or 'W'), nnnnnn is the numeric value of the spacecraft clock at the time of shutter close, DOY is the day of year the product was created, HH is the hour, MM is the minutes and SS is the seconds portion of the time the product was created. Example: W1832898283.294-133021 4. STRUCTURE CONVENTIONS All data will be written in the IO platform's native data representation style. The current platform is a Sun workstation, which makes the representation Most Significant Byte first (MSB) or "big endian". The ordering of bits and bytes is only significant for pixel data; all other labeling information is in ASCII. This ordering follows both the PDS and VICAR file format conventions. For PDS, the SAMPLE_TYPE label in the IMAGE object defines which ordering is used in the file. For VICAR, the INTFMT and REALFMT labels in the System label define the ordering. Both file formats specify that bit 0 is the least significant bit of a byte. 5. SOURCE OF DATA VALUES Each Image data file contains both pixel data and accompanying label and header data values, and is constructed from Cassini Science Packets..In Sections 6 and 7, keywords and values are described for the PDS and Image Data file label items. In these sections, the following notation is used to indicate the source of label items: "TLM" means the label item is returned via telemetry (either housekeeping or science data). "Packet" means the item came from the Cassini Secondary Packet header of the ISS science packets. "SH" means the label item came from the Standard ISS Science Header. "XH" means the label item came from the Extended ISS Science Header. "SFDU Header" means the label item came from the SFDU Header. "MIPL" or "MIPL catalog" mean the label item was derived during telemetry processing at the Multimission Image Processing Laboratory. "PDS" means the label item was pre-designated by the PDS and remains fixed for the entire dataset. "TL via IOI file and MIPL catalog" means the label item was specified by the Team Lead in the Instrument Operations Interface (IOI) file and migrated to the product label through the MIPL catalog. The specific catalog table and field names are noted: tableName.fieldName. "PEF via MIPL catalog" means the label item was extracted from the Predicted Events File during the uplink process and migrated to the product label through the MIPL catalog. The specific catalog table and field names are noted: tableName.fieldName. 6. PDS LABEL INTERFACE SPECIFICATIONS 6.1 Introduction Corresponding to each Image Data file is a detached ASCII PDS label file which is included in order to make the products PDS compliant. The following three sections describe the PDS label in further detail. Section 6.2 describes the file characteristics and pointers to structures within the Image Data file. Section 6.3 describes the PDS label keywords which map exactly to keywords in the associated Image Data file. Section 6.4 describes pointers and further detail on objects within the Image Data File. 6.2 PDS File Characteristics and Pointers to Objects This section describes keywords required by PDS and pertains to overall file characteristics. It also describes pointers to structures in the associated Image Data File. TABLE 6.2 PDS FILE CHARACTERISTICS AND POINTERS TO OBJECTS PDS/VICAR Label Keyword Description Type Valid Values Source PDS_VERSION_ID The PDS standard being used. STRING PDS3 PDS RECORD_TYPE Style of records used in this data file. STRING FIXED_LENGTH MIPL RECORD_BYTES Number of bytes per record in this data file. INTEGER 280,536,1048,2072 MIPL FILE_RECORDS Number of records in this data file. INTEGER MIPL IMAGE_HEADER Pointer to file and record where Image Header starts. (STRING, INTEGER) MIPL Example: ("N12345678_1.IMG",1) TELEMETRY_TABLE Pointer to file and record where Telemetry Header starts.(STRING, INTEGER) MIPL Example: ("N12345678_1.IMG",3) LINE_PREFIX_TABLE Pointer to file and record where Line Prefix data starts.(STRING, INTEGER) MIPL Example: ("N12345678_1.IMG",4) IMAGE Pointer to file and record where Image Pixel data starts.(STRING, INTEGER) MIPL Example: ("N12345678_1.IMG",4) 6.3 PDS Label Keywords This section describes the PDS detached label keywords and values. These keywords are identical to their counterparts of the same name in the Image Data File VICAR Property labels (see Section 7.2.3). 6.4 PDS Objects This section describes keywords required by PDS and pertains to the structure of objects in the associated Image Data File. 7. IMAGE DATA FILE INTERFACE SPECIFICATIONS 7.1 Image Data File Structure Each image data file contains fixed length records and consists of the the following items which will be described in the subsequent sections in more detail. See Figure 7.1 for a graphic representation of the image data file structure: * ASCII VICAR Label which is included to facilitate image processing and allow easy validation of products using existing VICAR software. This item is described in further detail in Section 7.2. * Binary Label Header (also known as the Binary Telemetry Header) contains information about the image as a whole and is populated directly from the telemetry available for the product. This item is described in further detail in Section 7.3. * Image Line Records which are comprised of 24 bytes of Binary Line Prefix plus pixel data. This item is described in further detail in Section 7.4. * An optional End-of-Dataset Label (EOL). Inherent to the VICAR label is the possibility of an ASCII EOL label being appended after the binary data in order to handle label modifications. This item is described in further detail in Section 7.2. FIGURE 7.1 IMAGE DATA FILE STRUCTURE 7.2 VICAR Label Description 7.2.1 Introduction The VICAR Label is a set of ASCII "keyword=value" sets of information describing the important characteristics of the image. The Label is designed to be human-readable because it often is used to annotate products derived from the image, such as prints or plots. In addition, it is maintained through the various processed versions of the image to allow traceability with the original data. Also, the Label items may be extracted by software modules in order to guide automated processing procedures. The VICAR Label contains required System items (such as image size information) and History items (recording processing history for the file), and optional Property items (such as items describing gain states, etc.). A detailed definition of the structure of VICAR labels is found in the /VICAR File Format/ (see References). 7.2.2 System Label Items The System portion of the VICAR Label describes to humans or software the format, size and other structural characteristics of the image data file. Table 7.2.2 defines the keywords and values of these VICAR-required items. See the /VICAR File Format/ for more detail. 7.2.3 Property Label Items VICAR Label keywords are grouped into "Property" sets containing similar types of keywords. The Property portions of the VICAR Label contain all of the instrument-specific items necessary for the interpretation of the image data. The VICAR Property labels used to support Cassini ISS are: COMMAND, COMPRESSION, IDENTIFICATION, IMAGE, INSTRUMENT and TELEMETRY. Table 7.2.3.1 through Table 7.2.3.5 define the PDS compliant keywords, values, and data types of these instrument-related items. 7.3 Binary Telemetry Header Record 7.3.1 Introduction This record holds machine-readable information which is applies to the image as a whole. Many of these items are in the VICAR Label as well, but non-VICAR sites may ignore the VICAR Label and use the Binary Telemetry Header to construct their own human-readable label. This record contains 60 bytes of information and is subsequently padded out to the image record length with zeroes. Items in this header are copied directly from the Extended ISS Science header returned in telemetry, 7.3.2 Record Structure Table 7.3.2 describes each item in the Binary Telemetry Header Record in terms of its name, size, definition and possible values. 7.4 Line Records 7.4.1 Introduction There is one Line Record for each image line. Each contains a Binary Prefix of 24 bytes followed by the 8- or 16-bit pixel data for the line. The Prefix contains machine-readable information about the image line derived from the telemetry. This information may vary from line to line and thus is not placed in the Binary Telemetry Header. In the event of Lossy compressed data, the data are no longer associated with lines. The number of records received depends on compression efficiency, but there is no way to associate a given record with a line number. In this case, the Binary Line Prefix contains information extracted from the lossy records received. 7.4.2 Record Structure Table 7.4.2 describes each item in the image Line Records in terms of its name, size and description. The Prefix is composed of the Line Number from the Standard Header, the Extended and Overclocked pixels from the Line Header and values indicating the location of received pixel data.. The pixels in a given line may come from up to 4 packets. Therefore, a line could appear to have as many as 2 line segments of good data accompanied by line segments zero-filled missing data. The Prefix specifies the location of beginning and end of these good line segments. 9. APPENDIX B: Acronyms DB Database IO Instrument Operations IOI Instrument Operations Interface file ISS Imaging Science Subsystem ISSNA ISS Narrow Angle Camera ISSWA ISS Wide Angle Camera MIPL Multimission Image Processing Laboratory NAC (ISS) Narrow Angle Camera PDS Planetary Data System PEF Predicted Events File SH Standard ISS Science Header SIS Software Interface Specification TL Team Lead TLM Telemetry VICAR Video Image Communications And Retrieval WAC (ISS) Wide Angle Camera XH Extended ISS Science Header 10. APPENDIX C: Sample VICAR Label ************ File /project/cassini/casIss/N1347929960_1.IMG ************ 3 dimensional IMAGE file File organization is BSQ Pixels are in HALF format from a SUN-SOLR host 1 bands 1024 lines per band 1024 samples per line 1 lines of binary header of type CAS-ISS3 24 bytes of binary prefix per line ---- Property: INSTRUMENT ---- ANTIBLOOMING_STATE_FLAG='ON' CALIBRATION_LAMP_STATE_FLAG='N/A' DELAYED_READOUT_FLAG='NO' DETECTOR_TEMPERATURE=-89.2435 EXPOSURE_DURATION=2600.0 FILTER_NAME=('CL1', 'MT3') FILTER_TEMPERATURE=-84.3428 FLIGHT_SOFTWARE_VERSION_ID='1.2' GAIN_MODE_ID='29 ELECTRONS PER DN' INSTRUMENT_DATA_RATE=182.784 INSTRUMENT_MODE_ID='FULL' LIGHT_FLOOD_STATE_FLAG='ON' METHOD_DESC='MANUAL , MAXIOF IS 0.00000001, ISSPT_V4.2' OPTICS_TEMPERATURE=(0.712693, 0.54321) PREPARE_CYCLE_INDEX=4 READOUT_CYCLE_INDEX=7 SENSOR_HEAD_ELEC_TEMPERATURE=-83.5755 SHUTTER_MODE_ID='NACONLY' SHUTTER_STATE_ID='ENABLED' ---- Property: IMAGE ---- BIAS_STRIP_MEAN=0.0 DARK_STRIP_MEAN=14.3623 DATA_CONVERSION_TYPE='12BIT' MISSING_LINES=0 ---- Property: COMMAND ---- COMMAND_FILE_NAME='trigger_286_3.ioi' ORDER_NUMBER=4 COMMAND_SEQUENCE_NUMBER=286 ELECTRONICS_BIAS=112 PARALLEL_CLOCK_VOLTAGE_INDEX=9 ---- Property: IDENTIFICATION ---- DATA_SET_ID='CO-J-ISSNA/ISSWA-2-EDR-V1.0' DESCRIPTION='N/A' IMAGE_MID_TIME='2000-262T00:48:43.223Z' IMAGE_NUMBER='1347929960' IMAGE_OBSERVATION_TYPE=('CALIBRATION','ENGINEERING') IMAGE_TIME='2000-262T00:48:44.523Z' INSTRUMENT_HOST_NAME='CASSINI ORBITER' INSTRUMENT_ID='ISSNA' INSTRUMENT_NAME='IMAGING SCIENCE SUBSYSTEM NARROW ANGLE' MISSION_NAME='CASSINI-HUYGENS ' MISSION_PHASE_NAME='SCIENCE CRUISE' OBSERVATION_ID='ISS_C22ST_FOMALHAUT' PRODUCT_CREATION_TIME='2000-270T14:18:51.000' PRODUCT_ID='1_N1347929960.123' PRODUCT_VERSION_TYPE='FINAL' SEQUENCE_ID='C22' SEQUENCE_NUMBER=27 SEQUENCE_TITLE='STAR CALIBRATION' SPACECRAFT_CLOCK_CNT_PARTITION=1 SPACECRAFT_CLOCK_START_COUNT='1347929957.223' SPACECRAFT_CLOCK_STOP_COUNT='1347929960.123' START_TIME='2000-262T00:48:41.923Z' STOP_TIME='2000-262T00:48:44.523Z' TARGET_DESC='88 AQR' TARGET_LIST='N/A' TARGET_NAME='FOMALHAUT' ---- Property: TELEMETRY ---- EARTH_RECEIVED_START_TIME='2000-263T01:18:59.627Z' EARTH_RECEIVED_STOP_TIME='2000-263T01:19:36.171Z' EXPECTED_PACKETS=275 MISSING_PACKET_FLAG='NO' RECEIVED_PACKETS=295 SOFTWARE_VERSION_ID='ISS V3.1 9-20-2000' TELEMETRY_FORMAT_ID='S_N_ER_3' ---- Property: COMPRESSION ---- EXPECTED_MAXIMUM=(100.0, 100.0) VALID_MAXIMUM=(4095,4095) INST_CMPRS_PARAM=('N/A', 'N/A', 'N/A', 'N/A') INST_CMPRS_RATE=(1.5,1.35) INST_CMPRS_RATIO=5.92038 INST_CMPRS_TYPE='LOSSLESS' 11. APPENDIX D: Sample Detached PDS Label PDS_VERSION_ID = PDS3 /* FILE CHARACTERISTICS */ RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 2072 FILE_RECORDS = 1027 /* POINTERS TO DATA OBJECTS */ ^IMAGE_HEADER = ("N1347928997_1.IMG",1) ^TELEMETRY_TABLE = ("N1347928997_1.IMG",3) ^LINE_PREFIX_TABLE = ("N1347928997_1.IMG",4) ^IMAGE = ("N1347928997_1.IMG",4) /* IDENTIFICATION DATA ELEMENTS */ ANTIBLOOMING_STATE_FLAG = "ON" BIAS_STRIP_MEAN = 0.000000 CALIBRATION_LAMP_STATE_FLAG = "N/A" COMMAND_FILE_NAME = "trigger_286_3.ioi" COMMAND_SEQUENCE_NUMBER = 286 DARK_STRIP_MEAN = 14.443359 DATA_CONVERSION_TYPE = "12BIT" DATA_SET_ID = "CO-J-ISSNA/ISSWA-2-EDR-V1.0" DELAYED_READOUT_FLAG = "NO" DESCRIPTION="N/A" DETECTOR_TEMPERATURE = -89.243546 EARTH_RECEIVED_START_TIME = "2000-263T01:05:33.312Z" EARTH_RECEIVED_STOP_TIME = "2000-263T01:06:05.425Z" ELECTRONICS_BIAS = 112 EXPECTED_MAXIMUM=(100.0,100.0) EXPECTED_PACKETS=275 EXPOSURE_DURATION = 2600.000000 FILTER_NAME = ("UV1","CL2") FILTER_TEMPERATURE = -84.342690 FLIGHT_SOFTWARE_VERSION_ID = "1.2" GAIN_MODE_ID = "29 ELECTRONS PER DN" IMAGE_MID_TIME="2000-262T00:48:43.223Z" IMAGE_NUMBER = "1347928997" IMAGE_OBSERVATION_TYPE = {"CALIBRATION","ENGINEERING"} IMAGE_TIME = "2000-262T00:32:41.530Z" INSTRUMENT_DATA_RATE = 182.783997 INSTRUMENT_HOST_NAME = "CASSINI ORBITER" INSTRUMENT_ID = "ISSNA" INSTRUMENT_MODE_ID = "FULL" INSTRUMENT_NAME = "IMAGING SCIENCE SUBSYSTEM NARROW ANGLE" INST_CMPRS_PARAM = ("N/A","N/A","N/A","N/A") INST_CMPRS_RATE=(1.5,1.35) INST_CMPRS_RATIO = 5.962934 INST_CMPRS_TYPE = "LOSSLESS" LIGHT_FLOOD_STATE_FLAG = "ON" METHOD_DESC="MANUAL, MAXIOF IS 0.00000001, ISSPT_V4.2" MISSING_LINES = 0 MISSING_PACKET_FLAG = "NO" MISSION_NAME = "CASSINI-HUYGENS " MISSION_PHASE_NAME = "SCIENCE CRUISE" OBSERVATION_ID = "ISS_C22ST_FOMALHAUT" OPTICS_TEMPERATURE = (0.712693, , 0.54321) ORDER_NUMBER=4 PARALLEL_CLOCK_VOLTAGE_INDEX = 9 PREPARE_CYCLE_INDEX = 4 PRODUCT_CREATION_TIME = "2000-270T14:12:03.000" PRODUCT_ID = "1_N1347928997.123" PRODUCT_VERSION_TYPE = "FINAL" READOUT_CYCLE_INDEX = 7 RECEIVED_PACKETS=295 SENSOR_HEAD_ELEC_TEMPERATURE = -83.575539 SEQUENCE_ID = "C22" SEQUENCE_NUMBER=27 SEQUENCE_TITLE = "STAR CALIBRATION" SHUTTER_MODE_ID = "NACONLY" SHUTTER_STATE_ID = "ENABLED" SOFTWARE_VERSION_ID = "ISS V3.1 9-20-2000" SPACECRAFT_CLOCK_CNT_PARTITION = 1 SPACECRAFT_CLOCK_START_COUNT = "1347928994.223" SPACECRAFT_CLOCK_STOP_COUNT = "1347928997.123" START_TIME = "2000-262T00:32:38.930Z" STOP_TIME = "2000-262T00:32:41.530Z" TARGET_DESC="88 AQR" TARGET_LIST="N/A" TARGET_NAME = "FOMALHAUT" TELEMETRY_FORMAT_ID="S_N_ER_3" VALID_MAXIMUM=(4095, 4095) OBJECT = IMAGE_HEADER INTERCHANGE_FORMAT = ASCII HEADER_TYPE = VICAR2 BYTES = 2072 RECORDS = 1 ^DESCRIPTION = "VICAR2.TXT" END_OBJECT = IMAGE_HEADER OBJECT = TELEMETRY_TABLE INTERCHANGE_FORMAT = BINARY ROWS = 1 COLUMNS = 2 ROW_BYTES = 2072 ^STRUCTURE = "TLMTAB.FMT" OBJECT = COLUMN NAME = NULL_PADDING DATA_TYPE = MSB_UNSIGNED_INTEGER START_BYTE = 61 BYTES = 2011 END_OBJECT = COLUMN END_OBJECT = TELEMETRY_TABLE OBJECT = LINE_PREFIX_TABLE INTERCHANGE_FORMAT = BINARY ROWS = 2048 COLUMNS = 7 ROW_BYTES = 24 ROW_SUFFIX_BYTES = 2048 ^LINE_PREFIX_STRUCTURE = "PREFIX2.FMT" END_OBJECT = LINE_PREFIX_TABLE OBJECT = IMAGE LINES = 2048 LINE_SAMPLES = 2048 SAMPLE_BITS = 16 SAMPLE_TYPE = SUN_INTEGER LINE_PREFIX_BYTES = 24 END_OBJECT = IMAGE END