PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 2000-08-17 NOTE = "A lookup table that provides the value for the OBSERVATION_CLASSIFICATION keyword in the obs*.tab files." END_OBJECT = TEXT END 1. Overview This document describes the bit contents of the OBSERVATION_CLASSIFICATION keyword, including an explanation for each bit and the code definitions for the bit values. The information in this keyword is primarily based on the data collection command sequences uploaded to TES, and the instrument self-reported activity that is returned with the collected data. For more details of uploaded command sequences per orbit, see the summarized Experimenter's Notebook entries in data/enb.txt. The OBSERVATION_CLASSIFICATION keyword is located in the obs*.tab files and is intended to be used as an index of observation criteria in a "vanilla" data selection command. Table 1 lists the vanilla field names and outlines the organizational structure of the keyword. The remainder of this document provides details for each bit group in the order they appear in the keyword, with the exception of the Numerical Details group which is discussed with the TES Target Type and Command Sequence groups on which it depends. Table 1 - Classification Bit Structure BIT NO. CLASSIFICATION VANILLA FIELD NAME 1-3 MGS Mission Phase Identity MISSION_PHASE 4-7 TES Target Type INTENDED_TARGET 8-11 Command Sequence (Target dependent) TES_SEQUENCE 12,13 Neon Lamp Status NEON_LAMP_STATUS 14 Timing Accuracy TIMING_ACCURACY 15,16 (Reserved for future use) SPARE 17-32 Numerical Details (Sequence dependent) CLASSIFICATION_VALUE 2. MGS Mission Phase Identity The Mission Phase is defined in the MGS Mission Plan (see catalog/mission.cat) and included here in bits 1-3. Note that bit values of 0 or greater than 5 indicate an error has occurred, and the OBSERVATION_CLASSIFICATION keyword should not be used for this observation. BIT CODE DEFINITION 0 = Error 1 = Aerobraking Phase 1 (AB-1) 2 = Science Phasing Orbit 1 (SPO-1) 3 = Science Phasing Orbit 2 (SPO-2) 4 = Aerobraking Phase 2 (AB-2) 5 = Mapping Phase >5 = Error 3. TES Target Type, Command Sequence, and Numerical Details The bits for Target Type (bits 4-7), Command Sequence (bits 8-11), and the Numerical Details (bits 17-32) are organized in a pseudo-tiered structure, with each successive bit group dependent on the information in the previous bit group. There are 9 exclusive Target Groups including "no target", various physical targets, and observational tests for instrument health and data quality related issues. For each Target Group there are 1 to 8 Command Sequences specific to that Target Group (see below). The Numerical Details are signed (+/-) values related to the Command Sequence for selected entries; these values include latitude, timing before or after periapsis, or ANS roll number relative to periapsis. (For more information on spacecraft configuration or ANS motion modes see catalog/host.cat.) In order to access the information stored in these bits, the vanilla command must contain a selection on both the Target Type and Command Sequence, (Numerical Details optional). The following are two examples of a vanilla call selection criteria and their respective results: -select "OBSERVATION_CLASSIFICATION:INTENDED_TARGET 1 1 \ OBSERVATION_CLASSIFICATION:TES_SEQUENCE 3 3" returns surface periapsis nadir observations conducted in the mapping spacecraft configuration -select "OBSERVATION_CLASSIFICATION:INTENDED_TARGET 6 6 \ OBSERVATION_CLASSIFICATION:TES_SEQUENCE 2 2 \ OBSERVATION_CLASSIFICATION:CLASSIFICATION_VALUE +1 +1" returns ANS roll, Mars and space observations collected in mapping mode during the first outbound roll. BIT CODE DEFINITION FORMAT # = TES Target Type # = Command Sequence (Target dependent) Numerical Details included in bits 17-32 BIT CODE DEFINITION 0 = No Target 1 = Surface Target 1 = periapsis nadir looks, aerobrake spacecraft configuration -x down 2 = periapsis nadir looks, aerobrake spacecraft configuration +x down 3 = periapsis nadir looks, mapping spacecraft configuration +z down 4 = surface mosaic (during mapping phase) Latitude or Code in bits 17-32 (Appendix A.1) 5 = MOC coincident looks (rollout), SPO1 targets: Viking 1, Viking 2, Pathfinder, Cydonia Region 6 = Emission Phase Function (airmass set) Latitude in bits 17-32 (Appendix A.2) 2 = Atmospheric Target 1 = limb set, fore Seconds before/after periapsis in bits 17-32 2 = limb set, aft Seconds before/after periapsis in bits 17-32 3 = halo observation (see data/enb.txt) Seconds before/after periapsis in bits 17-32 3 = Phobos Target 1 = Phobos Data 4 = Deimos Target 1 = Deimos Data 5 = Reference Target 1 = reference look of internal black body 2 = reference look of albedo lamp one 3 = reference look of space 6 = Space and Global Mars Targets 1 = ANS roll contains Mars, sample mode In/outbound roll number relative to periapsis in bits 17-32 2 = ANS roll contains Mars, map mode In/outbound roll number relative to periapsis in bits 17-32 3 = ANS roll contains Mars, contingency mask In/outbound roll number relative to periapsis in bits 17-32 4 = ANS roll contains Mars, pseudo-idle In/outbound roll number relative to periapsis in bits 17-32 5 = ANS roll contains space only, sample mode In/outbound roll number relative to periapsis in bits 17-32 6 = ANS roll contains space only, map mode In/outbound roll number relative to periapsis in bits 17-32 7 = ANS roll contains space only, contingency mask In/outbound roll number relative to periapsis in bits 17-32 8 = ANS roll contains space only, pseudo-idle In/outbound roll number relative to periapsis in bits 17-32 7 = Test Data 1 = Image Motion Compensation (IMC) Test 2 = Background Noise Test 3 = Albedo Calibration Test 4 = Interferogram Test 5 = "Ringing-Data" Test 6 = High Gain Antenna/Solar Panels Noise Test 8 = Less Than Ick 15 1 = Instrument setup period at beginning of each orbit 9 = PROM Data 1 = PROM 4. Neon Lamp Status Bits 12 and 13 describe the status of the neon lamp which affects the ability of the instrument to collect spectral data. Albedo and thermal bolometer observations are not affected by the neon lamp status. BIT CODE DEFINITION 0 = Neon lamp on, spectra collected 1 = Neon lamp off, spectra not collected 5. Timing Accuracy Bit 14 describes observation timing accuracy which is related to the equator crossing broadcast. During all pre-mapping phases (AB-1, SPO-1, SPO-2, AB-2), the equator crossing is supplied by ground command. Any orbits executed between uplinks of the equator crossing contain timing accuracy drifts, which increase in severity with each passing orbit. In mapping, the MGS-PDS supplies the equator crossing broadcast; however, missed broadcasts still occur, resulting in a timing accuracy drift. BIT CODE DEFINITION 0 = most accurate timing, MGS-PDS equator crossing broadcast received 1 = timing drifts present, MGS-PDS equator crossing broadcast not received A. Appendicies A.1. Numerical Details: Surface Mosaic Latitudes and Codes Individual surface mosaic locations can be identified using either their latitude location, for "latitude band" mosaics, or an assigned code value, for targeted mosaics. The appropriate value is stored in the OBSERVATION_CLASSIFICATION:CLASSIFICATION_VALUE field. Latitude and code values which can be used in a vanilla selection command are listed below. MOSAIC LATITUDES Scan Day/Night Ock Range Length Side Latitude Values ------------------------------------------------------------------------ 3356:4814 1 day -12 -9 -6 -3 0 3 5426:avail 2 day -25 -22 -19 -16 -13 -9 5756:7422 1 night -60 -57 -54 -51 -48 -45 -42 -39 -36 -33 -30 -27 -21 -18 -15 -12 -9 -6 -3 0 3 6 9 12 15 18 21 24 27 30 7788:avail 1 night -58.5 -55.5 -52.5 -49.5 -46.5 -43.5 -40.5 -37.5 -34.5 -31.5 -28.5 -25.5 -22.5 -19.5 -16.5 -13.5 -10.5 -7.5 -4.5 -1.5 1.5 4.5 7.5 10.5 13.5 16.5 19.5 22.5 25.5 28.5 31.5 TARGET MOSAIC CODES Code Target Name Day/Night Side Latitude* Longitude ---------------------------------------------------------------------- 100 White Rock day -8 335 101 W. Hematite day -1:-5 3:8 102 W. Hematite night -1:-5 3:8 103 Aram Chaos day 2:4 20:23 105 Isidis Rim day -1:3 270:280 106 Hematite2 day -4.3 73 107 Hematite2 night -4.3 73 108 Hebes Chasm day -0.5 76.5 109 Viking2 day 47.9 225.9 110 Herschel day -13.8 229.1 111 Dao Vallis1 day -34.1 266.9 112 Olympus Mons day 18.4 131 113 Olympus Mons night 18.4 131 114 Adamas Laby. day 35 255 115 Proctor Cr. day -47.5 329.5 116 ML1 day 30 67 117 Hematite5 day -10.6 70.4 118 Hematite5 night -10.6 70.4 119 Nili day 8.5 292 120 Hematite3 day -8.9 73.6 121 Hematite3 night -8.9 73.6 122 Arsia Mons day -9.4 118 123 Arsia Mons night -9.4 118 124 Gusev Cr. day -15.5 184.5 125 Hematite4 day -6.9 70.9 126 Hematite4 night -6.9 70.9 127 Elysium Mons day 24.8 210.5 128 Elysium Mons night 24.8 210.5 129 Korolev Cr. day 73 195 130 Viking1 day 22.5 48 131 crap-shoot day -21 8 132 W. Candor day -5.5 76.5 133 Ma'adim night -20 182.6 134 Hebes night -1 77 135 Viking2 night 47.9 225.6 136 Ophir night -4 74 137 Hesp. Windstreak night -20.5 247.6 138 Gusev Cr. night -15.4 185 139 Isidis - double day 21.5 282 140 Viking1 night 22.46 48 141 "dusty" night 4.5 6.3 142 "sandy" night -19.8 136.1 143 Dao Vallis2 day -34.4 265.7 144 Lobate Cr. day 43.6 254.7 145 Huygens Cr. day -13.2 303.8 146 Hesp. paleolake day -2.35 249.2 147 Acidalea Crater day 31.4 31.4 148 ML2 day -9.5 34.7 149 Becquerel Crater day 22 8 150 Pathfinder day 19.33 33.55 151 Nili night -34 266 152 Crommelin Cr2 day 2.5 9 153 Kasei-cloud day 23 68 154 Kasei-cloud night 23 68 155 Debris4 night -44.5 251 156 W. Olympus Mons day 23 134:144 157 W. Olympus Mons night 23 134:144 158 W. Elysium Mons day 23 212:222 159 W. Elysium Mons night 23 212:222 160 Chryse-control day 23 40:50 161 Chryse-control night 23 40:50 162 Elysium-control day 23 250:260 163 Elysium-control night 23 250:260 164 W. Acidalea night 36 50 165 S. Isidis night 10 262 166 Kaiser Cr day -47 340 *Note: latitude information is included here to assist in identifying the targeted mosaics, but it is NOT a searchable characteristic. A.2. Numerical Details: Emission Phase Function Latitudes Emission Phase Function (EPF) groups can be identified by the latitude where they were collected; this value is stored in the OBSERVATION_CLASSIFICATION:CLASSIFICATION_VALUE field. Latitudes values which can be used in a vanilla selection command are listed below. EPF LATITUDES Day/Night Ock Range Side Latitude Values ----------------------------------------------------------------- 2146:avail day -90 -75 -60 -45 -30 -15 0 15 30 45 60 75 90 2146:avail night 20 8044:avail day -90 -67 -53 -38 -23 -8 7 22 37 52 67 82 90 8044:avail night 27