for the mars science laboratory, nasa / jpl...

ROVER ENVIRONMENTAL MONITORING STATION

REMS

for the Mars Science Laboratory, NASA / JPL 2011

Reduced Data Record (RDR) Software Interface Spec. (SIS)

CAB-REMS-SPC-0006 JPL D-38125

SIS-SCI022-MSL Issue 3

Copyright 2013. All rights reserved.

Pag. 2 Ed./Iss. : Issue 3

Doc: CAB-REMS-SPC-0006 JPL-D38125 SIS-SCI022-MSL

ROVER ENVIRONMENTAL MONITORING STATION (REMS)

Título Title

Reduced Data Record (RDR)

Software Interface Specification (SIS) Doc. núm. Doc. no.

CAB-REMS-SPC-0006

Edición Issue

Issue 3

Fecha Date

May, 2013

Preparado por Prepared by

Luis Mora Sotomayor (CAB) Fecha

Date:

Revisado por Revised by

Jose A Rodriguez-Manfredi, Instrument GDS Manager (CAB) Roser Urqui (INSA)

Fecha Date :

Autorizado por Authorized by

Javier Gómez-Elvira Instrument PI (CAB)

Fecha Date :

Aprobado por Approved by

Reta Beebe PDS Atmosphere Node Manager Ed Grayzeck PDS Program Manager

Fecha Date :

Fecha Date :

CENTRO DE ASTROBIOLOGIA (CSIC-INTA)

Carretera de Ajalvir Km. 4 28850 Torrejón de Ardoz

Madrid SPAIN



This document is property of the Centro de Astrobiología (CSIC-INTA).

TODOS LOS DERECHOS RESERVADOS

CENTRO DE ASTROBIOLOGIA

CAB posee en propiedad el original de este documento. Las copias que de este documento se suministren no podrán ser utilizadas para fines diferentes a aquellos para los cuales son solicitadas.




DOCUMENT CHANGE RECORD

Ed.

Issue Fecha Date

Sección –Párrafo afectado

Section – Paragraph Affected

Descripción del cambio Reason of change - Remarks

Draft 1 All sections Initiating Document.

Draft 2 26/8/2011 Section 3 Appendix A

Specification updates.

Draft 3 10/9/2012 Sections 1.3, 2.1, 2.2, 2.3.1, 2.3.3, 2.3.4, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.3, 4.2 All appendices

Incorporated comments from the peer review. Included new RDR type, the ADR. Changes in Wind Sensor Data. Data processing appendix moved to an external document.

Issue 1 03/27/2013 All sections Post-landing updates Issue 2 05/20/2013 Section 3.1.4

Section 3.1.5 Appendix A

Updates reflecting changes in FMT files: Corrections and confidence level updates

Issue 3 08/30/2013 Section 3.1.3 Section 3.1.5 Appendix A

New ATS data in MODRDR. Updates to confidence levels.




CONTENTS

1 Introduction 9

1.1 Purpose and Scope 9

1.2 Contents 9

1.3 Applicable Documents and Constraints 9

1.4 Reference Documents and Publications 10

1.5 Relationships with Other Interfaces 10

2 Data Products Characteristics and Environment 11

2.1 Instrument Overview 11

2.2 Data Product Overview 13

2.3 Data Processing 15

2.3.1 Data Processing Level 15

2.3.2 Data Product Generation 16

2.3.3 Data Flow 16

2.3.4 Labeling and Identification 18

2.4 Standards Used in Generating Data Products 23

2.4.1 PDS Standards 23

2.4.2 Time Standards 23

2.4.3 Coordinate Systems 24

2.4.4 Data Storage Conventions 24

2.5 Data Validation 24

3 Detailed Data Products Specifications 25

3.1 Data Products Structure and Organization 25

3.1.1 TELRDR 25

3.1.2 ENVRDR 26

3.1.3 MODRDR 27

3.1.4 ADR 28

3.1.5 Confidence levels codes 28

3.2 Data Format Description 30

3.3 Label and Header Descriptions 30

4 Applicable Software 31

4.1 Utility Programs 31

4.2 Applicable PDS Software Tools 31




5 Acronyms and Abbreviations 31




LIST OF FIGURES

Figure 1 Sketch of the boom locations on a section of the rover mast, and the booms themselves. On the right is Boom 1 with wind and ground temperature sensor and on the left is Boom2 with wind and humidity sensors. On both booms the conditioning electronics are located on the back, close to the attachment point ........................................................... 11

Figure 2 The REMS RDRs consist of two files ................................................. 25




LIST OF TABLES

Table 1 Product and Software Interfaces to this SIS ........................................ 10

Table 2 Processing Levels for Science Data Sets ............................................ 16

Table 3 RDR data sizes, 3 hours/sol ................................................................ 18




1 Introduction

1.1 Purpose and Scope

The purpose of this data product Software Interface Specification (SIS) is to provide users of the Rover Environmental Monitoring Station (REMS) Reduced Data Record (RDR) with a detailed description of the product and a description of how it was generated, including data sources and destinations. This SIS is intended to provide enough information to enable users to understand the REMS RDR data product. The users for whom this SIS is intended are software developers of the programs used in generating the RDR products and scientists who will analyze the data, including those associated with the Mars Science Laboratory (MSL) Project and those in the general planetary science community.

1.2 Contents

This data product SIS describes how the REMS RDR products are generated, formatted, labeled, and uniquely identified. The document discusses standards used in generating the products and software that may be used to access the products. The products are described in sufficient detail to enable a user to read the products. Finally, examples of the PDS labels are provided, along with definitions for label keywords.

1.3 Applicable Documents and Constraints

This Data Product SIS is responsive to the following MSL documents:

1. Mars Science Laboratory Project Archive Generation, Validation and Transfer Plan, Joy Crisp, JPL D-35281, November 13, 2006.

2. MSL REMS EDR SIS, JPL D-64995.

This SIS is also consistent with the following Planetary Data System documents:

1. Planetary Data System Archive Preparation Guide (AGP), Version 1.4, JPL D-31224, April 1, 2010.

2. Planetary Data System Data Standards Reference, Version 3.8, JPL D-7669, Part 2, February 27, 2009.

3. Planetary Science Data Dictionary Document, JPL D-7116, October 20, 2008.

Finally, this SIS is meant to be consistent with the contract negotiated between the MSL Project and the Instrument Principal Investigator (PI) in which reduced data records and documentation are explicitly defined as deliverable products.




1.4 Reference Documents and Publications

4. REMS: The Environmental Sensor Suite for the Mars Science Laboratory Rover, Space Sci Rev (2012) 170:583-640, DOI 10.1007/s 11214-012-9921-1

1.5 Relationships with Other Interfaces

Changes to this REMS SIS document will affect the following products, software, and/or documents.

Table 1 Product and Software Interfaces to this SIS

Name

Type P-product S-software D-document

Owner

REMS RDRs P PDS / REMS

REMS QRS S REMS

PDS database schema P PDS

Other REMS Programs/Products/Documents

P/S/D REMS Science Team

In addition, changes to the processing tools used to generate the REMS RDR data products could affect both the data products and this SIS document.



2 Data Products Characteristics and Environment

2.1 Instrument Overview

REMS has been designed to record six atmospheric parameters: wind speed/direction, pressure, relative humidity, air temperature, ground temperature, and ultraviolet radiation. All sensors are located around three elements: two booms attached to the rover Remote Sensing Mast (RSM), the Ultraviolet Sensor (UVS) assembly located on the rover top deck, and the Instrument Control Unit (ICU) inside the rover body. The booms are approximately 1.5 m above ground level. Boom length is similar to the RSM diameter, and therefore the wind flow perturbation by the RSM may reach the boom tip where the wind sensor is located. The two booms are

separated in azimuth by 120 to help insure that at least one of them will record clean wind data for any given wind direction. Figure 1 shows the booms relative position. There is a 50 mm height difference to minimize mutual wind perturbation. Boom 2, which points in the driving direction of the rover, has wind sensors and the relative humidity sensor. Boom 1, which looks to the side and slightly to the rear of the rover, hosts another set of wind sensors and the ground temperature sensor. Both booms have an air temperature sensor.

Figure 1On the right, Boom 1 and 2 located in the Remote Sensing Mast, and on the left, Boom 1 with wind and Ground Temperature Sensors.




Wind speed and direction will be derived based on information provided by three two-dimensional wind sensors on each of the booms. The three sensors are located 120° apart around the boom axis. Each of them will record local speed and direction in the plane of the sensor. The convolution of the 12 data points will be enough to determine wind speed as well as pitch and yaw angle of each boom relative to the flow direction. As mentioned previously, the wind field at the booms will be perturbed by the RSM and by the rover itself. Calibration will be done via a variety of wind tunnel tests under Mars conditions as well as numerical analysis. Simulations will be used to obtain results where test conditions cannot be reproduced on Earth. Ground temperature will be recorded with three thermopiles placed on Boom 1 that view the Martian surface to the side of the rover (see Figure 1). The three thermopiles view the surface through filters with pass bands of 8-14, 14.5-15.5, and 16-20μm, respectively. These bands were selected to allow separation of the emissions from the atmospheric CO2 absorption band and the surface. Air temperature will be recorded at both booms with two PT1000-type sensors placed on a small rod long enough to be outside the mast and boom thermal boundary layers. Sensors are bonded to the tip and at intermediate position of the rod. The information provided by these two sensors alongside knowledge of the temperature at the base of the rod (boom temperature) shall be used to estimate the temperature of the fluid around it, despite the thermal contamination due to the boom and radiative forcing. The measurement range is 150 to 300 K. Boom 2 houses the humidity sensor, which is located inside a protective cylinder. A dust filter protects it from dust deposition. Two of the main constraints on the REMS instrument design are the need for the booms to survive and operate in a broad range of temperatures, and for the entire instrument to have a mass less than 1.3 kg. Both conditions have required the development of an ASIC for data conditioning, which must survive

a -130 C to +70 C temperature ranges and minimize power consumption for operation. The UV sensor will be located on the rover deck and is composed of six photodiodes in the following ranges: 315-370 nm (UVA), 280-320 nm (UVB), 220-280 nm (UVC), 200-370 nm (total dose), 230-290 nm (UVD), and 300-350 nm (UVE). The photodiodes face the zenith direction and have a field of view of 60°. The sensor will be placed on the rover deck without any dust protection. To mitigate dust degradation, a magnetic ring has been placed around each photodiode with the aim of maximizing their operational time. Nevertheless, to evaluate dust deposition degradation, images of the sensor will be recorded periodically. Comparison of these images with laboratory measurements will permit evaluation of the level of dust absorption.




The pressure sensor will be located inside the rover body and connected to the external atmosphere via a tube. The tube exits the rover body through a small opening with protection against dust deposition. Its measurement range goes from 1 to 1150 Pa. As this component will be in contact with the atmosphere, a HEPA filter will be placed on the tube inlet to avoid contaminating the Mars environment. Systematic measurement is the main driver for REMS operation. Each hour, every sol, REMS will record 5 minutes of data at 1 Hz for all sensors. This strategy will be implemented based on a high degree of autonomy in REMS operations. The instrument will wake itself up each hour and after recording and storing data, will go to sleep independently of rover operations. REMS will record data whether the rover is awake or not, and both day and night. It is expected that under certain conditions, the ground temperature and humidity sensor measurements will require the integration of multiple measurement samples within the 5-minute interval in order to meet their science requirements. REMS operation is designed assuming an integrated total of three hours of operation each day, primarily constrained by power availability. Nevertheless, the REMS science team will have the capability to define additional prescheduled observation periods with durations longer than 5 minutes and located at any time during the day. Since the hourly observations will use a total of two hours of operational time, the third hour can be scheduled as a continuous block, for example. Another option that has been implemented in REMS flight software is a simple algorithm to lengthen some of the regular observations autonomously when an atmospheric event is detected. The main science objectives that the science team will focus on are:

Signature of the Martian general circulation and mesoscale phenomena near the surface (e.g., fronts, jets)

Microscale weather systems (e.g., boundary layer turbulence, heat fluxes, dust devils)

Local hydrological cycle (e.g., spatial and temporal variability, diffusive transport from regolith)

Destructive potential of UV radiation, dust UV optical properties, photolysis rates, and oxidant production

Subsurface habitability based on ground-atmosphere interaction

2.2 Data Product Overview

REMS RDRs are ASCII formatted tables that contain instrument’s processed data. Each RDR file contains data of every sensor.




There are several RDRs for various reduction levels. The most processed RDRs contain physical magnitudes measured by REMS with necessary corrections applied: wind speed and direction, air temperature, ground temperature, ultraviolet radiation, humidity and pressure. In addition to the highest level data product, two intermediate processing levels are also provided. An effort has been made to integrate results from all sensors in each RDR, in order to facilitate data analysis. However, the complexity of data processing is not the same for all sensors, so there are a greater number of transformations between RDR types for some sensors compared to others. The RDRs provided are:

TELRDR (Thermal and Electrical RDR) This is the result of the first processing step. It contains data where counts recorded by the instrument have been converted to thermal and electrical values using calibration information. Temperatures for PT1000 sensors are given instead of resistances since the conversion between them is straightforward and temperatures are more helpful.

ENVRDR (Environmental Magnitudes RDR) ENVRDRs are the second processing step. At this level, data has been converted from electrical to environmental magnitudes provided by each engineering sensor (e.g. data for each air temperature PT1000 sensor instead of a unique air temperature, or data for each ground temperature sensor thermophile instead of a unique ground temperature). Minimal corrections exist for some sensors to compensate their degradation due to exposure to Martian conditions.

MODRDR (Models RDR) This level is the third and final processing level. It contains data where ENVRDRs are corrected and modeled to provide a best estimate of the environmental magnitudes. Numerous tests and data analysis have been done to ensure that their value is as accurate as possible within the project constrains.

ADR (Ancillary Data Record) The Ancillary Data Record provides the additional data required for producing the highest level RDRs, such as rover location data (from NAIF) and the signal attenuation caused by dust deposited over the ultraviolet sensor. The sources of these data are external to REMS.




2.3 Data Processing

2.3.1 Data Processing Level

This SIS uses the Committee on Data Management and Computation (CODMAC) data level numbering system to describe the processing level of the RDR data product. REMS RDR data products are considered CODMAC “Level 3” or “Calibrated Data” (equivalent to NASA level 1-A), CODMAC “Level 4” or “Resampled Data” (equivalent to NASA level 1-B) and CODMAC “Level 5” or “Derived Data” (equivalent to NASA level 2) products. The RDR data files are obtained from “Level 2” or “Edited Data”, which are the Experiment Data Records (EDR) generated from telemetry packets within the project-specific Standard Formatted Data Unit (SFDU) record. Details about the REMS EDR products are defined in the REMS EDR SIS. Refer to Table 2 for a breakdown of the CODMAC and NASA data processing levels and their equivalence to the REMS data products.




Table 2 Processing Levels for Science Data Sets

NASA CODMAC Description REMS Data Product

Packet 0data

Raw - Level 1

Telemetry data stream as received at the ground station, with science and engineering data embedded.

Level-0 Edited - Level 2

Instrument science data (e.g., raw voltages, counts) at full resolution, time ordered, with duplicates and transmission errors removed.

EDR

Level 1-A

Calibrated - Level 3

Level 0 data that have been located in space and may have been transformed (e.g., calibrated, rearranged) in a reversible manner and packaged with needed ancillary and auxiliary data (e.g., radiances with the calibration equations applied).

TELRDR

Level 1-B

Resampled - Level 4

Irreversibly transformed (e.g., resampled, remapped, calibrated) values of the instrument measurements (e.g., radiances, magnetic field strength).

ENVRDR

Level 1-C

Derived - Level 5

Level 1A or 1B data that have been resampled and mapped onto uniform space-time grids. The data are calibrated (i.e., radiometrically corrected) and may have additional corrections applied (e.g., terrain correction).

MODRDR

Level 2 Derived - Level 5

Geophysical parameters, generally derived from Level 1 data, and located in space and time commensurate with instrument location, pointing, and sampling.

Level 3 Derived - Level 5

Geophysical parameters mapped onto uniform space-time grids.

Level 4 Ancillary – Level 6

Ancillary data. ADR

2.3.2 Data Product Generation

RDR data products will be generated by the REMS team from EDR products provided by MIPL using a custom software program named QRS (Quick Response System). Although there are still some manual steps in the processing, almost all of the process is automatic and it will be improved in a near future. Every process step relies on previous steps and ancillary data. All ancillary data required is included either in the ADR data products or in calibration files in the RDR archive volume.

2.3.3 Data Flow

The REMS EDR data products are first generated by the MIPL (Multimission Image Processing Laboratory) at JPL, under the OPGS, using the telemetry




processing software called MSLEdrGen. This software will convert the binary data received from telemetry to ASCII. REMS EDR data products are then retrieved by the REMS team using the File Exchange Interface (FEI), by means of a secure subscription protocol, as soon as they are available. In parallel, NAIF will provide rover location data required to generate ADR data products. Ultraviolet Sensor images used in the calculation of the Ultraviolet Sensor signal attenuation will be retrieved as they are available. EDR data products have a first process using calibration data. The result of this is the TELRDR data set. Afterwards EDRs, TELRDRs, ADRs, and calibration data are processed together to obtain the ENVRDRs. Finally, by applying models and corrections developed by the REMS team, MODRDRs are generated. Once RDRs are created, they will be transferred back to FEI to make them available to the rest of the mission team. After the data validation period, the REMS RDR data will be delivered to the Planetary Data System for archiving. This is expected to occur every three months, with the first delivery 6 months after landing, as described in the MSL Archive Generation, Validation and Transfer Plan (AD1). Each data product will comprise one sol of data, and will be generated once per day. Additional versions may be produced as better models for estimating the higher level data products are developed. REMS has a baseline operation of three hours of measurements per sol, consisting of a minimum of two hours (working 5 minutes at 1Hz every hour) plus an extra hour of extended observations that will be allocated at the science team discretion. Additional observation time for opportunistic science beyond the three hours may be allowed depending on the mission resources. Table 3 shows the estimated data sizes for the baseline operation. Real data sizes will be higher depending on the amount of time allocated to REMS during the mission.




Table 3 RDR data sizes, 3 hours/sol

Data product Product Size Volume size (90 sols)

TELRDR 7.88 MB 709,13 MB

ENVRDR 4.5 MB 404.16 MB

MODRDR 2.35 MB 211.35 MB

ADR 1.33 MB 119.58 MB

Total 14.73 MB 1324.64 MB

2.3.4 Labeling and Identification

There is a file-naming scheme adopted for the MSL image and non-image data products. The scheme applies to the EDR and several RDR data products. The file naming schemes adhere to the Level II 36.3 filename convention approved by PDS in 2009. This is a change from the 27.3 convention that MER and PHX were constrained to using.

The primary attributes of the filename nomenclature are:

a) Uniqueness - It must be unique unto itself without the filesystem’s directory path. This protects against product overwrite as files are copied/moved within the file system and external to the file system, if managed correctly.

b) Metadata - It should be comprised of metadata fields that keep file bookkeeping and sorting intuitive to the human user. Even though autonomous file processing will be managed via databases, there will always be human-in-the-loop that puts a premium on filename intuition. Secondly, the metadata fields should be smartly selected based on their value to ground processing tools, as it is less CPU-intensive to extract information from the filename than from the label.

NOTE: The metadata information in the filename also resides in the product label. The metadata fields have been selected based on MER and PHX lessons learned. In general, the metadata fields are arranged to achieve:

a) Sortability - At the beginning of the filename resides a primary time oriented field such as Spacecraft Clock Start Count (SCLK). This allows




for sorting of files on the MSL file system by spacecraft data acquisition time as events occurred on Mars.

b) Readability - An effort is made to alternate Integer fields with ASCII character fields to optimize differentiation of field boundaries for the human user.

Each REMS RDR has a detached PDS label associated with the REMS data file. The file-naming scheme for the REMS RDR data products is:

where, instr = (2 alpha character) Instrument ID, denoting the source MSL

science or engineering instrument that acquired the data. Valid values for Instrument ID’s are: ”RM” - REMS

config = (1 alphanumeric) Valid values: “E” - Environmental

spec

= (1 character) Special Processing flag, applicable to RDRs on a case-by-case basis.

Special Processing EDR Value RDR Value

None “_” “_”

Special method types A - Z

n/a “A” - “Z”

sclk = (9 alphanumeric) Spacecraft Clock Start Count, in units of

seconds. The first SCLK for the corresponding SOL of the data (EDR) is used.

The valid values, in their progression, are as follows (non-Hex): Range 000000000 thru 999999999 -




“000000000”,“000000001”, … “999999999” Range 1000000000 thru 1099999999 -“A00000000”, “A00000001”, … “A99999999” Range 1100000000 thru 1199999999 -“B00000000”, “B00000001”, … “B99999999”

Range 3500000000 thru 3599999999 - “Z00000000”,“Z00000’001”, … “Z99999999”

prod = (3 char) Product Type identifier.

This field has the following rule-of-thumb: Beginning “E” - Type of EDR, which is the first order product with no processing applied. Beginning “R” – Type of RDR, except for ADRs.

Valid values for Product identifiers are listed below for RDRs:

Product Type Description Value

TELRDR RTL ENVRDR RNV

MODRDR RMD

ADR ADR

sol = (4 alphanumeric) Sol, or Mars Solar Day. It is converted from the SCLK using LMST (Local Mean Solar Time). NOTE: If the first character is an underscore (“_”) then the remaining 3 characters denote the day of year (DOY). This format will be used during cruise.

The valid values, in their progression, are as follows (non-Hex): Range 0000 thru 9999 -“0000”,“0001”, … “9999” Range 10000 thru 10999 -“A000”, “A001”, … “A999” Range 11000 thru 11999 -“B000”, “B001”, … “B999”

Range 35000 thru 35999 - “Z000”,“Z001”, … “Z999”

site = (3 alphanumeric) Site location count, from the RMC. This field has the following rules-of-thumb: If value is any 3 alphanumeric characters, or 3 underscores (denoting value is out-of-range), then content represents Site index extracted from RMC.

The valid Site values, in their progression, are as follows (non-




Hex): Range 000 thru 999 -“000”,“001”, … “999” Range 1000 thru 1099 -“A00”, “A01”, … “A99” Range 1100 thru 1199 -“B00”, “B01”, … “B99”

Range 3500 thru 3599 - “Z00”,“Z01”, … “Z99”

drive = (4 alphanumeric) Drive (position-within-Site) location count, from the RMC. This field has the following rules-of-thumb: If value is any 4 alphanumeric characters, or 4 underscores (denoting value is out-of-range), then content represents Drive index extracted from RMC.

The valid Drive values, in their progression, are as follows (non-Hex): Range 0000 thru 9999 -“0000”,“0001”, … “9999” Range 10000 thru 10999 -“A000”, “A001”, … “A999” Range 11000 thru 11999 -“B000”, “B001”, … “B999”

Range 35000 thru 35999 - “Z000”,“Z001”, … “Z999” Range 36000 thru 36099 - “AA00”,“AA01”, … “AA99” Range 36100 thru 36199 - “AB00”,“AB01”, … “AB99”

Range 38500 thru 38599 - “AZ00”,“AZ01”, … “AZ99” Range 38600 thru 38699 - “BA00”,“BA01”, … “BA99” Range 38700 thru 38799 - “BB00”,“BB01”, … “BB99”

Range 41100 thru 41199 - “BZ00”,“BZ01”, … “BZ99” Range 41200 thru 41299 - “CA00”,“CA01”, … “CA99”

Range 65400 thru 65499 - “LI00”,“LI01”, … “LI99” Range 65500 thru 65535 - “LJ00”,“LJ01”, … “LJ35”

req id = (7 alphanumeric) - Request ID. For REMS, this field indicates the specific type of REMS EDR. For RDRs it stays as “underscores” (“_______”).

Who =

(1 alpha character) Product Producer ID identifies the institution that generated the product.




This field has the following rules-of-thumb: Producer - If value is “P” (for Flight) or “Y” (for Engineering), the provider of the product is the Principal Investigator. Except for MIPL as the provider (“M” for Flight or “Z” for Engineering), the remaining characters are assigned to Co-investigator providers at the discretion of the P.I. and will be identified in due time. Within the instrument of the P.I., characters are unique. Across instruments, characters are reusable. Valid values: “P” – Principal Investigator (REMS)

ver = (1 alphanumeric) Version identifier. The valid values, in their progression, are as follows (non-Hex):

Range 1 thru 10 -“1”, “2”, … “9”,“0” Range 11 thru 36 -“A”,“B”, … “Z” Range 37 and higher -“_” (underscore) The Version number increments by one whenever an otherwise-identical filename would be produced. Note that not every version need exist, e.g. versions 1, 2 and 4 may exist but not 3. In general, the highest-numbered Version represents the “best” version of that product. NOTE: To be clear, this field increments independently of all fields, including the Special Processing field.

ext = (2 to 3 alpha characters) Product type extension. Valid values for nominal operations data products: “LBL”

“TAB” - -

Detached label in PDS format Table data

Example #1: RME_351797691RTE00550000000_______P1.TAB Where, Instr config spec sclk prod sol site drive reqid who ver ext

= = = = = = = = = = = =

“RM” “E” “_” “_” “RTL” “0055” “000” “0000” “_______” “P” “1” “TAB”

= = = = = = = = = = = =

REMS Environmental Unused Spacecraft Clock Start Count of 351797691 sec. “R”-RDR Sol 55 Site 0 Position (Drive) 0 Unused for RDRs Produced by Principal Investigator at CAB Version 1 Indicates this file contains data, and not label info (LBL).




2.4 Standards Used in Generating Data Products

2.4.1 PDS Standards

The REMS RDRs comply with Planetary Data System standards for file formats and labels, as specified in the PDS Standards Reference version 3.8 and the Planetary Science Data Dictionary Document.

2.4.2 Time Standards

The following time standards and conventions are used throughout this document, as well as the MSL project for planning activities and identification of events.

Time Format Definition

SCET Spacecraft event time. This is the time when an event occurred on-board the spacecraft, in UTC. It is usually derived from SCLK.

SCLK Spacecraft Clock. This is an on-board 64-bit counter, in units of nano-seconds and increments once every 100 milliseconds. Time zero corresponds to midnight on 1-Jan-2000.

ERT Earth Received Time. This is the time when the first bit of the packet containing the current data was received at the Deep Space (DSN) station. Recorded in UTC format.

Local Solar Time Local Solar Time (LST). This is the local solar time defined by the local solar days (sols) from the landing date using a 24 “hour” clock within the current local solar day (HR:MN:SC). Since the Mars day is 24h 37m 22s long, each unit of LST is slightly longer than the corresponding Earth unit. LST is computed using positions of the Sun and the landing site from SPICE kernels. If a landing date is unknown to the program (e.g. for calibration data acquired on Earth) then no sol number will be provided on output LST examples: SOL 12 12:00:01 SOL 132 01:22:32.498 SOL 29

RCT Record Creation Time. This is the time when the first telemetry packet, containing a given data set was created on the ground. Recorded in UTC format.

Local True Solar Time

This is related to LST, which is also known as the mean solar time. It is the time of day based on the position of the Sun, rather than the measure of time based on midnight to midnight “day”. LTST is used in all MIPL/OPGS generated products.

SOL Solar Day Number, also known as PLANET DAY NUMBER in PDS label. This is the number of complete solar days on Mars since landing. The landing day therefore is SOL zero.

The PDS label for an REMS RDR uses keywords containing time values, such as start time, stop time, start spacecraft clock count, and stop spacecraft clock count. Each time value standard is defined according to the keyword definition. See Appendix C.




2.4.3 Coordinate Systems

The following coordinate systems are used within the project to refer to the position of the Lander and its instruments. Coordinate System Origin Orientation

Local Level Same as payload frame, and it moves with the Lander

+X North +Z down along gravity vector +Y East

Payload Frame At the shoulder of the Robotic Arm. Attached and moves with the Lander

+X along Lander –X ( point out into the work space) +Z down along Lander (vertical axis) +Y along Lander -Y

Site Frame Same as payload frame when first defined and never moves relative to Mars. Possible to define multiple site frames in case the Lander moves/slips.

Same as local level

Rover Frame Attached to Rover Aligned with Rover

2.4.4 Data Storage Conventions

The REMS RDR data files contain comma separated value data. The detached PDS labels for REMS RDRs are stored as ASCII text, with each keyword definition terminated by ASCII carriage-return and line-feed characters. The RDR products are described/defined as PDS table objects. All REMS RDR data files will contain fixed length records, although the size of the records in each file could differ between RDRs. Label keywords will provide necessary information to determine the size and organization of the records.

2.5 Data Validation

The REMS RDRs, as with all other MSL RDRs, are subject to PDS peer review. Review will take place well before the start of operations, to allow sufficient time to correct problems. Validation of REMS RDR products during production will be performed according to specifications in the MSL Archive Plan and the REMS science team. The REMS Team will validate the science content of the data products, by ensuring that it contains the expected measurements and associated required information, such as calibration data. The PDS Atmospheres Node will validate the products for compliance with PDS standards and for conformance with the design specified in this SIS.




3 Detailed Data Products Specifications

3.1 Data Products Structure and Organization

The structure of all REMS RDR consists of a detached ASCII PDS label and a data file in ASCII format as shown in Figure 2.

Detached ASCII PDS Label

REMS Data File (ASCII)

Figure 2 The REMS RDRs consist of two files

The PDS label describes the content of the data file, while the data file contains the scientific data itself. Data files are ASCII tables containing a time-ordered succession of records. Each record includes information from all the sensors for the defined moment of time, in addition to some ancillary data needed to generate higher level data products. A time correspondence with EDR is maintained. There are three types of RDR, as introduced in section 2.2, for each one of the three processing level REMS has. Each RDR type is in its own separate data set. The second and third RDR levels include data quality codes (called confidence levels) to give an indication of how reliable the information of a record is. They are explained in section 3.1.5.

3.1.1 TELRDR

TELRDR products are generated by processing raw telemetry data included in the REMS EDRs using calibration information. These raw data are counts dispatched by the Analog/Digital converters and the TELRDR are electrical magnitudes. Pt1000 electrical values are transformed to temperature with a straightforward conversion. There are several types of EDRs (as described in the REMS EDR SIS), but only part of the Science and Engineering EDRs are used, like ACQ, ENG, GTS_GAIN and SP_PARMS. The rest of EDRs are used for monitoring and reporting purposes and not for RDR processing. The TELRDR contains the following information:




- Wind Sensor: convective powers and hot temperatures from the 12 transducers for each boom. Cold temperatures from the 3 boards in each boom where the transducers are allocated.

- Ground Temperature Sensor: temperatures and voltages from the 3 thermopiles. Calibration plate temperature.

- Air Temperature Sensor: temperatures measured by each one of the PT1000 sensors along the rods at each boom, making a total of six temperatures (three for each boom). There is no sensor at the base of the rod at boom 1, so for that boom the third temperature is the mean of the three thermopiles temperatures.

- Ultraviolet Sensor: photodiodes output currents and sensor operating temperature.

- Humidity Sensor: sensor capacities for each of the 8 channels.

- Pressure Sensor: sensor capacities for each of the 8 channels.

3.1.2 ENVRDR

ENVRDR products are produced from TELRDRs. They contain environmental magnitudes for each physical sensor. The only corrections at this level are mainly to compensate the degradation of the sensors like in the case of the one caused by dust deposition over the Ground Temperature Sensor and over the Ultraviolet Sensor. There are also additional adjustments like the one done to the Ultraviolet Sensor data by modifying the responsivity depending on the Solar Zenith Angle (SZA). This is the information included in these data products:

- Wind sensor: longitudinal and transversal differential thermal conductance for each of the 3 boards in each boom.

- Ground Temperature Sensor: brightness temperature of the 3 thermopiles and their estimated systematic uncertainties.

- Air Temperature Sensor: temperatures measured by each one of the PT1000 sensors on each boom (unmodified from the TELRDRs), and their estimated uncertainties.

- Ultraviolet Sensor: ultraviolet radiation for each band and their estimated uncertainties.

- Humidity Sensor: relative humidity from each of the 3 channels and the Humidity Sensor operating temperature.




- Pressure Sensor: pressure from each of the 2 barocaps, 2 thermocaps temperatures and their estimated accuracy. Pressure Sensor configuration (oscillator and low/high resolution mode).

- Confidence level codes for each of the sensors, estimating the quality of the data. They are gathered for each sensor and for each boom.

3.1.3 MODRDR

The MODRDR contains the highest processed data. At this level unique environmental magnitudes are given regardless the number of data sources for each sensor. Models and corrections have been applied to compensate for some factors influencing the sensors measurements such as rover temperatures, position, shadows, dust or noise. In some cases data not considered useful is removed. Data at this level is:

- Wind Sensor: horizontal and vertical wind speed, wind direction. An inverse model (based on calibration tests on a wind tunnel) has been applied to get these from differential thermal conductance.

- Ground Temperature Sensor: brightness temperature of the thermopile A

(band 8-14 m) and its estimated uncertainty. The other thermopiles are discarded due to invalid data. Also data not in calibration sequence or acquired when ASIC temperature was unstable is removed.

- Air Temperature Sensor: local air temperature around each boom (with the assumption of an equilibrium state) and an estimated ambient temperature around the rover, calculated after a filtering of both local air temperatures.

- Ultraviolet Sensor: ultraviolet radiation for each band and their estimated uncertainties. Data which may cause internal reflections inside the photodiodes is removed, leaving only data measured SZA (Solar Zenith Angle) is inside the Field of View, or when there is diffuse radiation. Data is also removed if acquired when the rover or the arm were moving.

- Humidity Sensor: relative humidity and temperature.

- Pressure Sensor: pressure after application of a drift correction and its uncertainty. Pressure Sensor configuration (oscillator and low/high resolution mode).

- Confidence level codes.




3.1.4 ADR

The ADR contains ancillary data needed in the processing of some sensors, obtained from sources external to the REMS instrument. In particular:

- Geometry information: solar longitude angle, solar zenithal angle, rover position, rover velocity, rover pitch, rover yaw, rover roll, masthead location and arm status (still and/or stowed). These data are provided by NAIF in SPICE kernels.

- Magnitude of the signal attenuation produced by dust deposited over the Ultraviolet Sensor. This data is evaluated by taking images of the sensor by the rover’s cameras and by applying an algorithm developed at CAB.

3.1.5 Confidence levels codes

Confidence levels codes are strings containing sequences of ones and zeroes representing different factors that affect the quality of a sensor measurement. For each factor, a ‘1’ means that it was optimal (and hence it made the data more reliable) and a ‘0’ that it was not. Confidence in the measured data will be bigger the higher the number of ‘1’ in the code. The character 'X' may be present in some codes for factors whose value is not known at the moment of the data generation. Confidence level codes are present in the second and the third data processing steps. The following list specifies the optimal conditions regarding the factors considered in ENVRDRs. The detailed explanation of the confidence level codes can be found in the descriptions of the FMT files (Appendix A)

Wind Sensor

- ASIC temperature more than -50C.

- ASIC power supply within the range [4.83 - 5.03].

- No ASIC noise present.

- Wind Sensor Gain set to 0x30.

- Rover not moving.

- The Wind Sensor was correctly configured for the measured air temperature.

Ground Temperature Sensor

- ASIC power supply within the range [4.87 - 4.97].

- GTS in-flight recalibration quality high.




- Rover moving.

- The GTS field of view is not in shadow.

Air Temperature Sensor

- ASIC temperature more than -50C.

- Wind Sensor ON.

- ASIC power supply within one of the following ranges: [4.71 - 4.79], [4.82 - 4.98], [5.11 - 5.19].

- Low wind speed.

- Wind direction with respect to each boom free from rover perturbation.

- Sensor in total shadow or at night.

Ultraviolet Sensor

- Solar Zenith Angle (SZA) in FOV range [0,20] or pure diffuse irradiance [55,inf).

- Global irradiance (SZA in (0,30)).

- Diffuse irradiance (SZA in (30,inf)).

- Rover not moving.

- Rover arm not moving and stowed.

- No shadow over the sensor.

- Attenuation by dust known below 10%.

Pressure Sensor

- Oscillator 2 used.

- No warm up effect (data is not reliable on barocap1 at the beginning of the measurement).

- No shadow effect (this effect is caused when there is a change from shadow to not shadow or the opposite).

In MODRDRs, the codes are the same with the following exceptions:

- For the Ultraviolet Sensor, the “Solar Zenith Angle (SZA) in FOV range”, the “Rover not moving” and the “Arm not moving” factors are not considered, because data not matching these conditions are removed.




- For the Pressure Sensor, the “No warm up effect” is not considered (since it only affects barocap 1, which is not used at this level).

3.2 Data Format Description

REMS RDRs consist of ASCII data organized as tables of N-columns by M-rows. The columns are separated by commas and are of fixed sizes. They are defined in external files that carry the name of the RDR type, in addition to a version number, and have extension .FMT. The number of rows in the RDR is equivalent to the number of records contained in the RDR. Each row is separated by a carriage return/line feed (<CR><LF>). Data may be set to UNK if their value is not known and it will never be (such as saturation, or a specific sensor switched off during acquisition). They may also be set to NULL if their value is not known at the moment of a release of the data, but it is expected to be known in a future release. The detached PDS label (.LBL) will contain a reference to a “TABLE” object and a reference to the corresponding .FMT file, according to the RDR’s type. Appendix A contains the FMT files for each of the three RDR types, describing names, sizes and data types.

3.3 Label and Header Descriptions

REMS RDR data products have detached PDS labels stored as ASCII. A PDS label is object-oriented and describes the objects in the data file. The PDS label contains keywords for product identification and for table object definitions. The label also contains descriptive information needed to interpret or process the data objects in the file. PDS labels are written in Object Description Language (ODL). PDS label statements have the form of “KEYWORD = VALUE". Each label statement is terminated with a carriage return character (ASCII 13) and a line feed character (ASCII 10) sequence to allow the label to be read by many operating systems. Pointer statements with the following format are used to indicate the location of data objects in the file:

^OBJECT = LOCATION

Where the caret character (^, also called a pointer) is followed by the name of the specific data object. The location is the starting record number for the data object within the file. Each PDS keyword defined for the REMS label will always be included in the PDS label. If a keyword does not have a value, a value of N/A will be given as the keyword value. Appendix B below contains an example of a detached PDS label for a REMS RDR.




4 Applicable Software

4.1 Utility Programs

Since the tables are in ASCII format and the columns separated by commas, REMS RDR data products can be loaded into any software that can read the CSV (Comma Separated Value) format, such as spreadsheet programs or MATLAB, and use them to display plots or any other kind of data analysis.

4.2 Applicable PDS Software Tools

PDS-labeled images and tables can be viewed with the program NASAView, developed by the PDS and available for a variety of computer platforms from the PDS web site http://pdsproto.jpl.nasa.gov/Distribution/license.html. There is no charge for NASAView. 5 Acronyms and Abbreviations

ASCII American Standard Code for Information Interchange

ASIC Application-Specific Integrated Circuit

CODMAC Committee on Data Management and Computation

EDR Experiment Data Record

FEI File Exchange Interface

GDS Ground Data System

HEPA High Efficiency Particulate air

JPL Jet Propulsion Laboratory

MIPL Multi-mission image Processing Laboratory

MPCS Multi-mission Data Processing and Control System

MSL Mars Science Laboratory

NASA National Aeronautics and Space Administration

ODL Object Description Language

OPGS Operations Products Generation Sub-system

PDS Planetary Data System

RDR Reduced Data Record

REMS Rover Environmental Monitoring Station

RTO Real Time Operations (MSL terminology)

SIS Software Interface Specification

TBD To Be Determined

VICAR Video image Communications and Retrieval system

http://pdsproto.jpl.nasa.gov/Distribution/license.html




ODS MSL’s Operations Data Store

SZA Solar Zenith Angle



APPENDIX A – FORMAT FILES

Each RDR is organized as a table and comes with a FMT file describing the contents of such table: the name of each column, their types, their size and their description. Following there are the FMT files for each REMS RDR type. TELRDR.FMT OBJECT = COLUMN

COLUMN_NUMBER = 1

NAME = "TIMESTAMP"

UNIT = "SECOND"

DESCRIPTION = "Number of seconds since noon 1-Jan-2000"

DATA_TYPE = ASCII_INTEGER

START_BYTE = 1

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 2

NAME = "LMST"

DESCRIPTION = "Local Mean Solar Time. It is in the format

SSSSSMHH:MM:SS.sss where:

SS - Sol number (00000-99999)

M - sol/time separator

HH - hour (0-23)

MM - minute (0-59)

SS - second (0-59)

sss - fractions of second (000-999)"

DATA_TYPE = CHARACTER

START_BYTE = 13

BYTES = 18

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 3

NAME = "BOOM1_PCONV_1"

UNIT = "MILLIWATT"

FORMAT = "F7.2"

DESCRIPTION = "Boom 1 wind sensor convective power 1"

DATA_TYPE = ASCII_REAL

START_BYTE = 33

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 4


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 41

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 5


UNIT = "MILLIWATT"

FORMAT = "F7.2"






START_BYTE = 49

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 6


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 57

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 7


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 65

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 8


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 73

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 9


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 81

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 10


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 89

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 11


UNIT = "MILLIWATT"

FORMAT = "F7.2"






START_BYTE = 97

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 12


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 105

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 13


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 113

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 14


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 121

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 15


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 129

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 16


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 137

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 17


UNIT = "MILLIWATT"

FORMAT = "F7.2"






START_BYTE = 145

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 18


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 153

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 19


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 161

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 20


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 169

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 21


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 177

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 22


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 185

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 23


UNIT = "MILLIWATT"




FORMAT = "F7.2"



START_BYTE = 193

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 24


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 201

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 25


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 209

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 26


UNIT = "MILLIWATT"

FORMAT = "F7.2"



START_BYTE = 217

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 27

NAME = "BOOM1_THOT_1"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Boom 1 wind sensor hot temperature 1"


START_BYTE = 225

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 28


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 233

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 29





UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 241

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 30


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 249

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 31


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 257

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 32


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 265

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 33


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 273

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 34


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 281

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 35





UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 289

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 36


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 297

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 37


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 305

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 38


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 313

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 39


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 321

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 40


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 329

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN




COLUMN_NUMBER = 41


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 337

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 42


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 345

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 43


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 353

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 44


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 361

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 45


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 369

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 46


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 377

BYTES = 7

END_OBJECT = COLUMN




OBJECT = COLUMN

COLUMN_NUMBER = 47


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 385

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 48


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 393

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 49


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 401

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 50


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 409

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 51

NAME = "BOOM1_TCOLD_1"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Boom 1 wind sensor cold temperature 1"


START_BYTE = 417

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 52


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 425

BYTES = 7

END_OBJECT = COLUMN




OBJECT = COLUMN

COLUMN_NUMBER = 53


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 433

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 54


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 441

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 55


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 449

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 56


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 457

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 57

NAME = "THERMOPILE_A_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "GTS thermopile A temperature (band 8-14 um)"


START_BYTE = 465

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 58

NAME = "THERMOPILE_B_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "GTS thermopile B temperature (band 16-20 um)"


START_BYTE = 473

BYTES = 7




END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 59

NAME = "THERMOPILE_C_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "GTS thermopile C temperature (band 14-15 um)"


START_BYTE = 481

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 60

NAME = "CALIBRATION_PLATE_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "GTS calibration plate temperature"


START_BYTE = 489

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 61

NAME = "THERMOPILE_A_VOLTAGE"

UNIT = "MICROVOLT"

FORMAT = "F8.2"

DESCRIPTION = "GTS thermopile A voltage"


START_BYTE = 497

BYTES = 8

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 62

NAME = "THERMOPILE_B_VOLTAGE"

UNIT = "MICROVOLT"

FORMAT = "F8.2"

DESCRIPTION = "GTS thermopile B voltage"


START_BYTE = 506

BYTES = 8

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 63

NAME = "THERMOPILE_C_VOLTAGE"

UNIT = "MICROVOLT"

FORMAT = "F8.2"

DESCRIPTION = "GTS thermopile C voltage"


START_BYTE = 515

BYTES = 8

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 64

NAME = "THERMOPILE_A_BETA"

FORMAT = "F4.2"

DESCRIPTION = "GTS thermopile A degradation correction factor"


START_BYTE = 524

BYTES = 4




END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 65

NAME = "THERMOPILE_B_BETA"

FORMAT = "F4.2"

DESCRIPTION = "GTS thermopile B degradation correction factor"


START_BYTE = 529

BYTES = 4

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 66

NAME = "THERMOPILE_C_BETA"

FORMAT = "F4.2"

DESCRIPTION = "GTS thermopile C degradation correction factor"


START_BYTE = 534

BYTES = 4

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 67

NAME = "BOOM1_AIR_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Boom 1 ATS boom internal temperature (mean of the

three thermopile temperatures)"


START_BYTE = 539

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 68

NAME = "BOOM1_INTERMEDIATE_AIR_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Boom 1 ATS intermediate temperature"


START_BYTE = 547

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 69

NAME = "BOOM1_TIP_AIR_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Boom 1 ATS tip temperature"


START_BYTE = 555

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 70


UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Boom 2 ATS boom internal temperature "


START_BYTE = 563

BYTES = 7




END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 71


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 571

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 72


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 579

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 73

NAME = "UV_A"

UNIT = "NANOAMPERE"

FORMAT = "F7.2"

DESCRIPTION = "Band A ultraviolet photodiode output current"


START_BYTE = 587

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 74

NAME = "UV_B"

UNIT = "NANOAMPERE"

FORMAT = "F7.2"

DESCRIPTION = "Band B ultraviolet photodiode output current"


START_BYTE = 595

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 75

NAME = "UV_C"

UNIT = "NANOAMPERE"

FORMAT = "F7.2"

DESCRIPTION = "Band C ultraviolet photodiode output current"


START_BYTE = 603

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 76

NAME = "UV_ABC"

UNIT = "NANOAMPERE"

FORMAT = "F7.2"

DESCRIPTION = "Band A+B+C ultraviolet photodiode output current"


START_BYTE = 611




BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 77

NAME = "UV_D"

UNIT = "NANOAMPERE"

FORMAT = "F7.2"

DESCRIPTION = "Band D ultraviolet photodiode output current"


START_BYTE = 619

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 78

NAME = "UV_E"

UNIT = "NANOAMPERE"

FORMAT = "F7.2"

DESCRIPTION = "Band E ultraviolet photodiode output current"


START_BYTE = 627

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 79

NAME = "UV_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Ultraviolet sensor temperature"


START_BYTE = 635

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 80

NAME = "H_CHANNEL1_CAPACITANCE"

UNIT = "PICOFARAD"

FORMAT = "F9.4"

DESCRIPTION = "Humidity channel 1 capacitance"


START_BYTE = 643

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 81


UNIT = "PICOFARAD"

FORMAT = "F9.4"



START_BYTE = 653

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 82


UNIT = "PICOFARAD"

FORMAT = "F9.4"






START_BYTE = 663

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 83


UNIT = "PICOFARAD"

FORMAT = "F9.4"



START_BYTE = 673

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 84


UNIT = "PICOFARAD"

FORMAT = "F9.4"



START_BYTE = 683

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 85


UNIT = "PICOFARAD"

FORMAT = "F9.4"



START_BYTE = 693

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 86


UNIT = "PICOFARAD"

FORMAT = "F9.4"



START_BYTE = 703

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 87


UNIT = "PICOFARAD"

FORMAT = "F9.4"



START_BYTE = 713

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 88

NAME = "P_CHANNEL1_CAPACITANCE"

UNIT = "PICOFARAD"

FORMAT = "F9.4"

DESCRIPTION = "Pressure sensor channel 1 capacitance"





START_BYTE = 723

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 89


UNIT = "PICOFARAD"

FORMAT = "F9.4"



START_BYTE = 733

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 90


UNIT = "PICOFARAD"

FORMAT = "F9.4"



START_BYTE = 743

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 91


UNIT = "PICOFARAD"

FORMAT = "F9.4"



START_BYTE = 753

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 92


UNIT = "PICOFARAD"

FORMAT = "F9.4"



START_BYTE = 763

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 93


UNIT = "PICOFARAD"

FORMAT = "F9.4"



START_BYTE = 773

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 94


UNIT = "PICOFARAD"

FORMAT = "F9.4"






START_BYTE = 783

BYTES = 9

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 95


UNIT = "PICOFARAD"

FORMAT = "F9.4"



START_BYTE = 793

BYTES = 9

END_OBJECT = COLUMN

ENVRDR.FMT OBJECT = COLUMN

COLUMN_NUMBER = 1

NAME = "TIMESTAMP"

UNIT = "SECOND"



START_BYTE = 1

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 2

NAME = "LMST"



SS - Sol number (00000-99999)


HH - hour (0-23)

MM - minute (0-59)

SS - second (0-59)



START_BYTE = 13

BYTES = 18

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 3

NAME = "BOOM1_BOARD1_B_LONG"

FORMAT = "E10.3"

DESCRIPTION = "Wind sensor longitudinal differential thermal

conductance for Boom 1 Board 1"


START_BYTE = 33

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 4

NAME = "BOOM1_BOARD1_B_TRANS"

FORMAT = "E10.3"

DESCRIPTION = "Wind sensor transversal differential thermal



START_BYTE = 44




BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 5


FORMAT = "E10.3"




START_BYTE = 55

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 6


FORMAT = "E10.3"




START_BYTE = 66

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 7


FORMAT = "E10.3"




START_BYTE = 77

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 8


FORMAT = "E10.3"




START_BYTE = 88

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 9

NAME = "WS_BOOM1_CONFIDENCE_LEVEL"

DESCRIPTION = "String representing the confidence level for

the wind sensor; 0 = bad; 1 = good; X = unknown;

(byte 0 is on the left end)

- Byte 0: ASIC temperature;

0 = less than -50C;

1 = more than -50C;

- Byte 1: ASIC power supply range;

0 = out of range;

1 = in range (V = [4.83 - 5.03]);

- Bytes 2-3: ASIC noise;

00 = electronic noise (no valid data);

01 = frequent electronic noise (warning);

10 = electronic noise (warning);

11 = No electronic noise;

- Byte 4: Wind sensor gain;




0 = other than 0x30;

1 = gain 0x30;

- Byte 5: Rover movement;

0 = moving;

1 = still;

- Byte 6: Wind Sensor correctly configured based

on air temperature;

0 = wrong configuration;

1 = good configuration;"


START_BYTE = 100

BYTES = 8

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 10


FORMAT = "E10.3"




START_BYTE = 110

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 11


FORMAT = "E10.3"




START_BYTE = 121

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 12


FORMAT = "E10.3"




START_BYTE = 132

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 13


FORMAT = "E10.3"




START_BYTE = 143

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 14


FORMAT = "E10.3"







START_BYTE = 154

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 15


FORMAT = "E10.3"




START_BYTE = 165

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 16

NAME = "WS_BOOM2_CONFIDENCE_LEVEL"





0 = less than -50C;

1 = more than -50C;


0 = out of range;

1 = in range (V = [4.83 - 5.03]);





11 = no electronic noise;



1 = gain 0x30;


0 = moving;

1 = still;

- Byte 6: Wind Sensor correctly configured based

on air temperature;

0 = wrong configuration;

1 = good configuration;"


START_BYTE = 177

BYTES = 8

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 17

NAME = "BRIGHTNESS_TEMP_A"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Brightness temperature of the GTS Thermopile A

(band 8-14 um)"


START_BYTE = 187

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 18

NAME = "BRIGHTNESS_TEMP_B"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Brightness temperature of the GTS Thermopile B




(band 16-20 um)"


START_BYTE = 195

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 19

NAME = "BRIGHTNESS_TEMP_C"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Brightness temperature of the GTS Thermopile C

(band 14-15 um)"


START_BYTE = 203

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 20

NAME = "BRIGHTNESS_TEMP_A_UNCERTAINTY"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Systematic uncertainty of the brightness

temperature provided by the GTS Thermopile A

(band 8-14 um)"


START_BYTE = 211

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 21

NAME = "BRIGHTNESS_TEMP_B_UNCERTAINTY"

UNIT = "KELVIN"

FORMAT = "F7.2"


temperature provided by the GTS Thermopile B

(band 16-20 um)"


START_BYTE = 219

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 22

NAME = "BRIGHTNESS_TEMP_C_UNCERTAINTY"

UNIT = "KELVIN"

FORMAT = "F7.2"


temperature provided by the GTS Thermopile C

(band 14-15 um)"


START_BYTE = 227

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 23

NAME = "GTS_CONFIDENCE_LEVEL"

DESCRIPTION = "String representing the GTS confidence level;

0 = bad; 1 = good; X = unknown; (byte 0 is on the

left end)

- Byte 0: GTS temperature in calibration

sequence;




0 = in sequence;

1 = not in sequence;


0 = out of range;

1 = in range (V = [4.87 - 4.97]);


0 = unstable;

1 = stable;

- Byte 3: GTS recalibration quality;

0 = low quality;

1 = high quality;


0 = still;

1 = moving;

- Byte 5: Shadow in GTS Field of View

0 = full or partial shadow;

1 = no shadow;"


START_BYTE = 236

BYTES = 8

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 24


UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Boom 1 ATS boom internal temperature. This

value is the mean of the three GTS thermopiles

temperatures since there is no physical sensor"


START_BYTE = 246

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 25


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 254

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 26


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 262

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 27

NAME = "BOOM1_INTERMEDIATE_AIR_TEMP_UNCERTAINTY"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Boom 1 ATS intermediate temperature uncertainty"


START_BYTE = 270




BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 28

NAME = "BOOM1_TIP_AIR_TEMP_UNCERTAINTY"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Boom 1 ATS tip temperature uncertainty"


START_BYTE = 278

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 29

NAME = "ATS_BOOM1_CONFIDENCE_LEVEL"

DESCRIPTION = "String representing the boom 1 ATS confidence

level; 0 = bad; 1 = good; X = unknown; (byte 0 is

on the left end)


0 = less than -50C;

1 = more than -50C;

- Byte 1: Wind Sensor status;

0 = WS off;

1 = WS on;


0 = out of range;

1 = in range (valid ranges:

[4.71 - 4.79], [4.82 - 4.98], [5.11 - 5.19]);

- Byte 3: Wind speed;

0 = Wind Speed > TBD;

1 = Wind Speed < TBD;

- Byte 4: Wind direction with respect to

each boom;

0 = from RTG or rover deck;

1 = free to rover perturbation;

- Byte 5: Shadow in tip sensor;

0 = no shadow or partial shadow;

1 = total shadow or at night;

- Byte 6: Shadow in intermediate sensor;


1 = total shadow or at night;"


START_BYTE = 287

BYTES = 8

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 30


UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Boom 2 ATS boom internal temperature"


START_BYTE = 297

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 31


UNIT = "KELVIN"

FORMAT = "F7.2"






START_BYTE = 305

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 32


UNIT = "KELVIN"

FORMAT = "F7.2"



START_BYTE = 313

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 33

NAME = "BOOM2_AIR_TEMP_UNCERTAINTY"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Boom 2 ATS internal temperature uncertainty"


START_BYTE = 321

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 34

NAME = "BOOM2_INTERMEDIATE_AIR_TEMP_UNCERTAINTY"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Boom 2 ATS intermediate temperature uncertainty"


START_BYTE = 329

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 35

NAME = "BOOM2_TIP_AIR_TEMP_UNCERTAINTY"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Boom 2 ATS tip temperature uncertainty"


START_BYTE = 337

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 36




on the left end)


0 = less than -50C;

1 = more than -50C;


0 = WS off;

1 = WS on;


0 = out of range;


[4.71 - 4.79], [4.82 - 4.98], [5.11 - 5.19]);








each boom;

0 = from RTG or rover deck;


- Byte 5: Shadow in tip sensor;



- Byte 6: Shadow in intermediate sensor;




START_BYTE = 346

BYTES = 8

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 37

NAME = "UV_A"

UNIT = "W/m**2"

FORMAT = "F7.2"

DESCRIPTION = "Ultraviolet radiation in band A"


START_BYTE = 356

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 38

NAME = "UV_B"

UNIT = "W/m**2"

FORMAT = "F7.2"

DESCRIPTION = "Ultraviolet radiation in band B"


START_BYTE = 364

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 39

NAME = "UV_C"

UNIT = "W/m**2"

FORMAT = "F7.2"

DESCRIPTION = "Ultraviolet radiation in band C"


START_BYTE = 372

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 40

NAME = "UV_ABC"

UNIT = "W/m**2"

FORMAT = "F7.2"

DESCRIPTION = "Ultraviolet radiation in band ABC"


START_BYTE = 380

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 41

NAME = "UV_D"




UNIT = "W/m**2"

FORMAT = "F7.2"

DESCRIPTION = "Ultraviolet radiation in band D"


START_BYTE = 388

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 42

NAME = "UV_E"

UNIT = "W/m**2"

FORMAT = "F7.2"

DESCRIPTION = "Ultraviolet radiation in band E"


START_BYTE = 396

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 43

NAME = "UV_A_UNCERTAINTY"

UNIT = "%"

FORMAT = "F7.2"

DESCRIPTION = "Systematic uncertainty in the ultraviolet

radiation band A"


START_BYTE = 404

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 44

NAME = "UV_B_UNCERTAINTY"

UNIT = "%"

FORMAT = "F7.2"


radiation band B"


START_BYTE = 412

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 45

NAME = "UV_C_UNCERTAINTY"

UNIT = "%"

FORMAT = "F7.2"


radiation band C"


START_BYTE = 420

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 46

NAME = "UV_ABC_UNCERTAINTY"

UNIT = "%"

FORMAT = "F7.2"


radiation band ABC"


START_BYTE = 428

BYTES = 7




END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 47

NAME = "UV_D_UNCERTAINTY"

UNIT = "%"

FORMAT = "F7.2"


radiation band D"


START_BYTE = 436

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 48

NAME = "UV_E_UNCERTAINTY"

UNIT = "%"

FORMAT = "F7.2"


radiation band E"


START_BYTE = 444

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 49

NAME = "UVS_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "UVS operating temperature at the time of data

collection"


START_BYTE = 452

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 50

NAME = "UVS_CONFIDENCE_LEVEL"


the ultraviolet sensor; 0 = bad; 1 = good; X =

unknown; (byte 0 is on the left end)

- Byte 0: Solar Zenith Angle (SZA);

0 = SZA unknown or SZA out of FOV (20,55);

1 = SZA in FOV range [0,20] or pure diffuse

irradiance [55,inf);

- Byte 1: Global irradiance;

0 = no global irradiance;

1 = global irradiance (SZA in (0,30));

- Byte 2: Diffuse irradiance;

0 = no diffuse irradiance;

1 = diffuse irradiance (SZA in (30,inf));

- Byte 3: Rover motion;

0 = rover motion;

1 = rover still;

- Byte 4: Arm motion;

0 = arm motion;

1 = arm still;

- Byte 5: Arm position;

0 = unstowed;

1 = stowed;

- Byte 6: Shadow;

0 = partial or total shadow;




1 = no shadow;

- Byte 7: Dust sensor degradation;

0 = attenuation by dust unknown or attenuation

above 10%;

1 = attenuation by dust below 10%"


START_BYTE = 461

BYTES = 8

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 51

NAME = "HUMIDITY_CHANNEL_A"

UNIT = "%"

FORMAT = "F7.2"

DESCRIPTION = "Relative humidity from HS channel A"


START_BYTE = 471

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 52

NAME = "HUMIDITY_CHANNEL_B"

UNIT = "%"

FORMAT = "F7.2"

DESCRIPTION = "Relative humidity from HS channel B"


START_BYTE = 479

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 53

NAME = "HUMIDITY_CHANNEL_C"

UNIT = "%"

FORMAT = "F7.2"

DESCRIPTION = "Relative humidity from HS channel C"


START_BYTE = 487

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 54

NAME = "HS_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Humidity sensor operating temperature at the

time of data collection"


START_BYTE = 495

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 55

NAME = "HS_CONFIDENCE_LEVEL"


the humidity sensor; 0 = bad; 1 = good; X =

unknown; (byte 0 is on the left end). TBD"


START_BYTE = 504

BYTES = 8

END_OBJECT = COLUMN




OBJECT = COLUMN

COLUMN_NUMBER = 56

NAME = "PS_CONFIGURATION"

DESCRIPTION = "Pressure sensor configuration.

First character: '1' = oscillator 1 on

'2' = oscillator 2 on

Second character: 'L' = low resolution

'H' = high resolution"


START_BYTE = 515

BYTES = 2

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 57

NAME = "THERMOCAP_1_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "PS temperature from thermocap 1"


START_BYTE = 519

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 58

NAME = "THERMOCAP_2_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "PS temperature from thermocap 2"


START_BYTE = 527

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 59

NAME = "BAROCAP_PRESSURE_1"

UNIT = "PASCAL"

FORMAT = "F7.2"

DESCRIPTION = "Pressure for barocap 1"


START_BYTE = 535

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 60

NAME = "BAROCAP_PRESSURE_2"

UNIT = "PASCAL"

FORMAT = "F7.2"

DESCRIPTION = "Pressure for barocap 2"


START_BYTE = 543

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 61

NAME = "BAROCAP_PRESSURE_1_UNCERTAINTY"

UNIT = "PASCAL"

FORMAT = "F7.2"

DESCRIPTION = "Barocap 1 absolute accuracy"





START_BYTE = 551

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 62

NAME = "BAROCAP_PRESSURE_2_UNCERTAINTY"

UNIT = "PASCAL"

FORMAT = "F7.2"

DESCRIPTION = "Barocap 2 absolute accuracy"


START_BYTE = 559

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 63

NAME = "PS_CONFIDENCE_LEVEL"

DESCRIPTION = "String representing the confidence level for the

pressure sensor; 0 = bad; 1 = good; X = unknown;


- Byte 0: Oscillator;

0 = oscillator 1;

1 = oscillator 2;

- Byte 1: Warm up effect (only for oscillator 2

and barocap 1)

0 = warm up effect;

1 = no warm up effect;

- Byte 2: Shadow effect;

0 = shadow effect;

1 = no shadow effect;"


START_BYTE = 568

BYTES = 8

END_OBJECT = COLUMN

MODRDR.FMT OBJECT = COLUMN

COLUMN_NUMBER = 1

NAME = "TIMESTAMP"

UNIT = "SECOND"



START_BYTE = 1

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 2

NAME = "LMST"



SS - Sol number (00000-99999)


HH - hour (0-23)

MM - minute (0-59)

SS - second (0-59)



START_BYTE = 13

BYTES = 18

END_OBJECT = COLUMN

OBJECT = COLUMN




COLUMN_NUMBER = 3

NAME = "HORIZONTAL_WIND_SPEED"

UNIT = "METERS/SECOND"

FORMAT = "F7.2"

DESCRIPTION = "The horizontal wind direction refers to the

local incoming direction of wind and it is

defined clockwise w.r.t. North"


START_BYTE = 33

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 4

NAME = "VERTICAL_WIND_SPEED"

UNIT = "METERS/SECOND"

FORMAT = "F7.2"

DESCRIPTION = "The vertical wind speed, is the wind speed along

the vector defined by the local gravity"


START_BYTE = 41

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 5

NAME = "WIND_DIRECTION"

UNIT = "DEGREE"

FORMAT = "F7.2"

DESCRIPTION = "The wind direction refers to the local incoming

direction of wind and it is defined clockwise

w.r.t. North"


START_BYTE = 49

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 6

NAME = "WS_CONFIDENCE_LEVEL"





0 = less than -50C;

1 = more than -50C;


0 = out of range;

1 = in range (V = [4.83 - 5.03]);





11 = No electronic noise;



1 = gain 0x30;


0 = moving;

1 = still;"


START_BYTE = 58

BYTES = 8

END_OBJECT = COLUMN




OBJECT = COLUMN

COLUMN_NUMBER = 7

NAME = "BRIGHTNESS_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Brightness temperature"


START_BYTE = 68

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 8

NAME = "BRIGHTNESS_TEMP_UNCERTAINTY"

UNIT = "KELVIN"

FORMAT = "F7.2"


temperature"


START_BYTE = 76

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 9

NAME = "GTS_CONFIDENCE_LEVEL"

DESCRIPTION = "String representing the GTS confidence level;

0 = bad; 1 = good; X = unknown; (byte 0 is on the

left end)


0 = out of range;

1 = in range (V = [4.87 - 4.97]);

- Byte 1: GTS recalibration quality;

0 = low quality;

1 = high quality;


0 = still;

1 = moving;

- Byte 3: Shadow in GTS Field of View

0 = full or partial shadow;

1 = no shadow;"


START_BYTE = 85

BYTES = 8

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 10

NAME = "BOOM1_LOCAL_AIR_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Local temperature for boom 1"


START_BYTE = 95

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 11




on the left end)


0 = less than -50C;




1 = more than -50C;


0 = WS off;

1 = WS on;


0 = out of range;


[4.71 - 4.79], [4.82 - 4.98], [5.11 - 5.19]);





each boom;

0 = from RTG or rover desk;


- Byte 5: Shadow;




START_BYTE = 104

BYTES = 8

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 12

NAME = "BOOM2_LOCAL_AIR_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Local temperature for boom 2"


START_BYTE = 114

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 13




on the left end)


0 = less than -50C;

1 = more than -50C;


0 = WS off;

1 = WS on;


0 = out of range;


[4.71 - 4.79], [4.82 - 4.98], [5.11 - 5.19]);





each boom;



- Byte 5: Shadow;




START_BYTE = 123

BYTES = 8

END_OBJECT = COLUMN




OBJECT = COLUMN

COLUMN_NUMBER = 14

NAME = "AMBIENT_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Estimated ambient air temperature"


START_BYTE = 133

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 15

NAME = "AMBIENT_TEMP_CONFIDENCE_LEVEL"



on the left end)


0 = less than -50C;

1 = more than -50C;


0 = WS off;

1 = WS on;


0 = out of range;


[4.71 - 4.79], [4.82 - 4.98], [5.11 - 5.19]);





each boom;



- Byte 5: Shadow;



- Byte 6: Operational range (error < 5 kelvin);

0 = Error higher than operational range;

1 = Error in operational range;"


START_BYTE = 142

BYTES = 8

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 16

NAME = "UV_A"

UNIT = "W/m**2"

FORMAT = "F7.2"

DESCRIPTION = "Ultraviolet radiation in band A"


START_BYTE = 152

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 17

NAME = "UV_B"

UNIT = "W/m**2"

FORMAT = "F7.2"

DESCRIPTION = "Ultraviolet radiation in band B"


START_BYTE = 160

BYTES = 7




END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 18

NAME = "UV_C"

UNIT = "W/m**2"

FORMAT = "F7.2"

DESCRIPTION = "Ultraviolet radiation in band C"


START_BYTE = 168

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 19

NAME = "UV_ABC"

UNIT = "W/m**2"

FORMAT = "F7.2"

DESCRIPTION = "Ultraviolet radiation in band ABC"


START_BYTE = 176

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 20

NAME = "UV_D"

UNIT = "W/m**2"

FORMAT = "F7.2"

DESCRIPTION = "Ultraviolet radiation in band D"


START_BYTE = 184

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 21

NAME = "UV_E"

UNIT = "W/m**2"

FORMAT = "F7.2"

DESCRIPTION = "Ultraviolet radiation in band E"


START_BYTE = 192

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 22

NAME = "UV_A_UNCERTAINTY"

UNIT = "%"

FORMAT = "F7.2"


radiation band A"


START_BYTE = 200

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 23

NAME = "UV_B_UNCERTAINTY"

UNIT = "%"

FORMAT = "F7.2"


radiation band B"





START_BYTE = 208

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 24

NAME = "UV_C_UNCERTAINTY"

UNIT = "%"

FORMAT = "F7.2"


radiation band C"


START_BYTE = 216

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 25

NAME = "UV_ABC_UNCERTAINTY"

UNIT = "%"

FORMAT = "F7.2"


radiation band ABC"


START_BYTE = 224

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 26

NAME = "UV_D_UNCERTAINTY"

UNIT = "%"

FORMAT = "F7.2"


radiation band D"


START_BYTE = 232

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 27

NAME = "UV_E_UNCERTAINTY"

UNIT = "%"

FORMAT = "F7.2"


radiation band E"


START_BYTE = 240

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 28

NAME = "UVS_CONFIDENCE_LEVEL"


the ultraviolet sensor; 0 = bad; 1 = good; X =

unknown; (byte 0 is on the left end)

- Byte 0: Global irradiance;

0 = no global irradiance;

1 = global irradiance (SZA in (0,30));

- Byte 1: Diffuse irradiance;

0 = no diffuse irradiance;

1 = diffuse irradiance (SZA in (30,inf));




- Byte 2: Arm position;

0 = unstowed;

1 = stowed;

- Byte 3: Shadow;

0 = partial or total shadow;

1 = no shadow;

- Byte 4: Dust sensor degradation;

0 = attenuation by dust unknown or attenuation

above 10%;

1 = attenuation by dust below 10%"


START_BYTE = 249

BYTES = 8

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 29

NAME = "RELATIVE_HUMIDITY"

UNIT = "%"

FORMAT = "F7.2"

DESCRIPTION = "Relative humidity"


START_BYTE = 259

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 30

NAME = "HS_TEMP"

UNIT = "KELVIN"

FORMAT = "F7.2"

DESCRIPTION = "Humidity sensor operating temperature at the

time of data collection"


START_BYTE = 267

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 31

NAME = "HS_CONFIDENCE_LEVEL"


humidity sensor; 0 = bad; 1 = good; X = unknown;

(byte 0 is on the left end). TBD"


START_BYTE = 276

BYTES = 8

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 32

NAME = "PS_CONFIGURATION"

DESCRIPTION = "Pressure sensor configuration.

First character: '1' = oscillator 1 on

'2' = oscillator 2 on

Second character: 'L' = low resolution

'H' = high resolution"


START_BYTE = 287

BYTES = 2

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 33

NAME = "PRESSURE"




UNIT = "PASCAL"

FORMAT = "F7.2"

DESCRIPTION = "Pressure"


START_BYTE = 291

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 34

NAME = "PRESSURE_UNCERTAINTY"

UNIT = "PASCAL"

FORMAT = "F7.2"

DESCRIPTION = "Pressure absolute accuracy"


START_BYTE = 299

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 35

NAME = "PS_CONFIDENCE_LEVEL"


pressure sensor; 0 = bad; 1 = good; X = unknown;


- Byte 0: Oscillator;

0 = oscillator 1;

1 = oscillator 2;

- Byte 1: Shadow effect;

0 = shadow effect;

1 = no shadow effect;"


START_BYTE = 308

BYTES = 8

END_OBJECT = COLUMN ADR_GEOM.FMT

OBJECT = COLUMN

COLUMN_NUMBER = 1

NAME = "TIMESTAMP"

UNIT = "SECOND"



START_BYTE = 1

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 2

NAME = "LMST"



SS - Sol number (00000-99999)


HH - hour (0-23)

MM - minute (0-59)

SS - second (0-59)



START_BYTE = 13

BYTES = 18

END_OBJECT = COLUMN

OBJECT = COLUMN




COLUMN_NUMBER = 3

NAME = "SOLAR_LONGITUDE_ANGLE"

UNIT = "DEGREE"

FORMAT = "F7.2"

DESCRIPTION = "Solar azimuth angle relative to REMS rover

frame (+X points to the front of the rover;

+Z points up; +Y completes the right handed

frame; the origin is on the rover deck,

between the rover middle wheels) It is the

angle between the positive X-axis and the

orthogonal projection of the Sun onto the

XY plane. It increases in the

counterclockwise sense about the positive

Z-axis. Range of -180 to 180 degrees."


START_BYTE = 33

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 4

NAME = "SOLAR_ZENITHAL_ANGLE"

UNIT = "DEGREE"

FORMAT = "F7.2"

DESCRIPTION = "Solar elevation angle relative to REMS rover

frame (+X points to the front of the rover;

+Z points up; +Y completes the right handed

frame; the origin is on the rover deck,

between the rover middle wheels) It is the

angle between the direction of the Sun and

the positive Z-axis. A value of 0 degrees

represents Sun at frame's zenith, while a

value of 180 degrees represents Sun at

frame's nadir. Range of 0 to 180 degrees."


START_BYTE = 41

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 5

NAME = "ROVER_POSITION_X"

UNIT = "METER"

FORMAT = "F7.2"

DESCRIPTION = "Rover position relative to landing site. It is

the x-component of the rover's position

relative to landing site, expressed with

respect to MSL_TOPO frame (+X is along the

local north direction; +Z is along the

outward normal at the landing site; +Y

completes the right hand frame; the origin

of this frame is located at the landing

site)"


START_BYTE = 49

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 6

NAME = "ROVER_POSITION_Y"

UNIT = "METER"

FORMAT = "F7.2"


the y-component of the rover's position










site)"


START_BYTE = 57

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 7

NAME = "ROVER_POSITION_Z"

UNIT = "METER"

FORMAT = "F7.2"


the z-component of the rover's position







site)"


START_BYTE = 65

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 8

NAME = "ROVER_VELOCITY"

UNIT = "METERS/HOUR"

FORMAT = "F7.2"

DESCRIPTION = "Rover velocity"


START_BYTE = 73

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 9

NAME = "ROVER_PITCH"

UNIT = "DEGREE"

FORMAT = "F7.2"

DESCRIPTION = "Rover pitch. It is given relative to

MSL_LOCAL_LEVEL frame (+X is along the


downward normal at the landing site; +Y


of this frame is located between the

rover's middle wheels and moves with the

rover)"


START_BYTE = 81

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 10

NAME = "ROVER_YAW"

UNIT = "DEGREE"

FORMAT = "F7.2"




DESCRIPTION = "Rover yaw. It is given relative to



downward normal at the landing site; +Y


of this frame is located between the

rover's middle wheels and moves with the

rover)"


START_BYTE = 89

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 11

NAME = "ROVER_ROLL"

UNIT = "DEGREE"

FORMAT = "F7.2"

DESCRIPTION = "Rover roll. It is given relative to



downward normal at the landing site;

+Y completes the right hand frame;

the origin of this frame is located between

the rover's middle wheels and moves with the

rover)"


START_BYTE = 97

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 12

NAME = "MASTHEAD_AZIMUTH"

UNIT = "DEGREE"

FORMAT = "F7.2"

DESCRIPTION = "Masthead azimuth angle. Range of -180 to 180

degrees. An azimuth angle of 1 degree

represents rover looking backward, an

azimuth angle of 91 degrees represents

rover looking to the left, an azimuth angle

of -179 degrees represents rover looking

forward, and an azimuth angle of -89

degrees represents rover looking to the

right."


START_BYTE = 105

BYTES = 7

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 13

NAME = "MASTHEAD_ELEVATION"

UNIT = "DEGREE"

FORMAT = "F7.2"

DESCRIPTION = "Masthead elevation angle. Range of 0 to 360

degrees. An elevation angle of 1 degree

represents rover looking down, an elevation

angle of 91 degrees represents rover

looking forward and an elevation angle of

181 degrees represents rover looking at the

zenith."


START_BYTE = 113

BYTES = 7




END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 14

NAME = "ARM_STILL"

DESCRIPTION = "Flag to indicate whether the arm is still;

1 = still; 0 = in motion."


START_BYTE = 122

BYTES = 1

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 15

NAME = "ARM_STOWED"

DESCRIPTION = "Flag to indicate whether the arm is stowed;

1 = stowed; 0 = unstowed."


START_BYTE = 126

BYTES = 1

END_OBJECT = COLUMN

ADR_CORRECTIONS.FMT OBJECT = COLUMN

COLUMN_NUMBER = 1

NAME = "TIMESTAMP"

UNIT = "SECOND"



START_BYTE = 1

BYTES = 10

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 2

NAME = "LMST"



SS - Sol number (00000-99999)


HH - hour (0-23)

MM - minute (0-59)

SS - second (0-59)



START_BYTE = 13

BYTES = 18

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 3

NAME = "UV_DUST_ATTENUATION"

FORMAT = "F7.2"

DESCRIPTION = "Magnitude of the attenuation produced by dust

deposited over the UV sensor"


START_BYTE = 33

BYTES = 7

END_OBJECT = COLUMN




APPENDIX B – SAMPLE RDR LABEL

This appendix includes an example label for an ENVRDR type product.

PDS_VERSION_ID = PDS3

/* FILE DATA ELEMENTS */

RECORD_TYPE = FIXED_LENGTH

RECORD_BYTES = 578

FILE_RECORDS = 22200

/* POINTERS TO DATA OBJECTS */

^REMS_SCIENCE_TABLE = "RME_400997446RNV00400000000_______P1.TAB"

/* IDENTIFICATION DATA ELEMENTS */

DATA_SET_ID = "MSL-M-REMS-4-ENVRDR-V1.0"

DATA_SET_NAME = "MSL MARS ROVER ENV MONITORING STATION 4

ENVRDR V1.0"

INSTRUMENT_HOST_ID = MSL

INSTRUMENT_HOST_NAME = "MARS SCIENCE LABORATORY"

INSTRUMENT_ID = REMS

INSTRUMENT_NAME = "ROVER ENVIRONMENTAL MONITORING STATION"

INSTRUMENT_TYPE = ENVIRONMENTAL_STATION

PLANET_DAY_NUMBER = 40

MISSION_NAME = "MARS SCIENCE LABORATORY"

MISSION_PHASE_NAME = "PRIMARY SURFACE MISSION"

OBSERVATION_ID = UNK

PRODUCER_INSTITUTION_NAME = "CENTRO DE ASTROBIOLOGIA"

PRODUCT_CREATION_TIME = 2013-02-27T12:24:44.713

PRODUCT_ID = "RME_400997446RNV00400000000_______P1"

PRODUCT_VERSION_ID = "V1.0 D-38125"

SOURCE_PRODUCT_ID = {"RME_400997446ESE00400000000ACQ____M1",

"RME_400997446ESE00400000000ENG____M1",

"RME_400997446ESE00400000000GTSGAINM1"}

CALIBRATION_SOURCE_ID = {"ATS_CAL_20120804.TXT",

"GTS_CAL_20120804.TXT",

"HS_CAL_20130220.TXT",

"PS_CAL_20130220.TXT",

"UVS_CAL_20120804.TXT",

"WS_CAL_20130220.TXT"}

RELEASE_ID = "0001"

PRODUCT_TYPE = REMS_RDR

SPACECRAFT_CLOCK_START_COUNT = "400997495"

SPACECRAFT_CLOCK_STOP_COUNT = "401082892"

START_TIME = 2012-09-15T16:14:18.195

STOP_TIME = 2012-09-16T15:57:35.987

TARGET_NAME = MARS

TARGET_TYPE = PLANET

/* SOURCE DATA ELEMENTS */

SOFTWARE_NAME = "REMS_QRS"

SOFTWARE_VERSION_ID = "2.1.0"

SPICE_FILE_NAME = "chronos.msl"

OBJECT = REMS_SCIENCE_TABLE

INTERCHANGE_FORMAT = ASCII

ROWS = 22200

COLUMNS = 63

ROW_BYTES = 578




DESCRIPTION = "Table with physical magnitudes with

minimal corrections obtained from TEL_RDR

and calibration parameters"

^STRUCTURE = "ENVRDR1.FMT"

END_OBJECT = REMS_SCIENCE_TABLE

END



APPENDIX C – REMS LABEL KEYWORD DEFINITIONS

Keyword Name Definition Type Units Valid Values Location & Source

PDS_VERSION_ID Specifies the version number of the

PDS standards document that is valid

when a data product label is created.

Values for the PDS_version_id are

formed by appending the integer for

the latest version number to the letters

'PDS'.

String PDS3

/* FILE DATA ELEMENTS */ Comment

RECORD_TYPE A Specifies the record format of a

file.

Note: In the PDS, when

RECORD_TYPE is used in a

detached label file, it always describes

its corresponding detached data file

and not the label file itself. The use of

RECORD_TYPE along with other

file-related data elements is fully

described in the PDS Standards

Reference.

String FIXED_LENGTH Constant

RECORD_BYTES B Specifies the number of bytes in a

physical file record, including

record terminators and separators.

Note: In the PDS, the use of

record_bytes, along with other file-

related data elements is fully

described in the Standards Reference.

integer 2048 Product specific

FILE_RECORDS Specifies the number of physical file integer 1038 Calculated





records, including both label records

and data records. Note: In the PDS the

use of FILE_RECORDS along with

other file-related data elements is fully

described in the Standards Reference.

/* IDENTIFICATION DATA ELEMENTS */ Comment

DATA_SET_ID A unique alphanumeric identifier for a

data set or a data product. The

DATA_SET_ID value for a given data

set or product is constructed according

to flight project naming conventions.

In most cases the DATA_SET_ID is

an abbreviation of the

DATA_SET_NAME.

Note: In the PDS, the values for both

DATA_SET_ID and

DATA_SET_NAME are constructed

according to standards outlined in the

Standards Reference.

string(4

0)

See example labels for

actual values used in

each product type

Constant for each

instrument.

DATA_SET_NAME Specifies the full name given to a data

set or a data product.

The DATA_SET_NAME typically

identifies the instrument that acquired

the data, the target of that instrument,

and the processing level of the data.

In the PDS, values for

DATA_SET_NAME are constructed

according to standards outlined in the

String PDS Table lookup





Standards Reference.

INSTRUMENT_HOST_ID Specifies a unique identifier for the

host where an instrument is located.

This host can be either a spacecraft or

an earth base (e.g., and observatory or

laboratory on the earth). Thus,

INSTRUMENT_HOST_ID can

contain values, which are either

SPACECRAFT_ID values or

EARTH_BASE_ID values.

String “MSL” Scid

INSTRUMENT_HOST_NAME The full name of the host on which

this instrument is based

String “MARS SCIENCE

LABORATORY”

Scid

INSTRUMENT_ID Specifies an abbreviated name or

acronym which identifies an

instrument

String “REMS”

“DAN”

“SAM”

INSTRUMENT_NAME Name of the instrument, free format,

enclosed in double quotes. See

example labels for various names used

for MECA non-imaging products

String “ROVER

ENVIRONMENTAL

MONITORING

STATION”

EMD:

ProductName

INSTRUMENT_TYPE Specifies the type of an instrument. String “SPECTROMETER”

PLANET_DAY_NUMBER Specifies the number of sidereal days

(rotation of 360 degrees) elapsed since

a reference day (e.g., the day on which

a landing vehicle set down). Days are

measured in rotations of the planet in

question from the reference day.

For MSL, the reference day is “1”, as

Landing day is Sol 1. If before

Landing day, then value will be less

than “1” and can be negative.

Integer Calculation

- SCLK kernel

MISSION_NAME Specifies a major planetary mission or

project. A given planetary mission

String “MARS SCIENCE

LABORATORY”

Static Value





may be associated with one or more

spacecraft.

MISSION_PHASE_NAME Specifies the commonly-used

identifier of a mission phase.

String “DEVELOPMENT",

"LAUNCH",

"CRUISE AND

APPROACH",

"ENTRY,

DESCENT, AND

LANDING",

"PRIMARY

SURFACE

MISSION",

"EXTENDED

SURFACE MISSION"

User specified

parameter.

PRODUCER_INSTITUTION_NAME Specifies the identity of a university,

research center, NASA center or other

institution associated with the

production of a data set. This would

generally be an institution associated

with the element

PRODUCER_FULL_NAME.

String “MULTIMISSION

INSTRUMENT

PROCESSING

LABORATORY, JET

PROPULSION LAB”

Static Value.

PRODUCT_CREATION_TIME Defines the UTC system format time

when a product was created.

String YYYY-MM-

DDThh:mm:ss.fff

Calculated

PRODUCT_ID Represents a permanent, unique

identifier assigned to a data product by

its producer. See also:

source_product_id.

Note: In the PDS, the value assigned

to product_id must be unique within

its data set.

Additional note: The product_id can

String(4

0)

File name, less the

extension.

Filename minus the

extension





describe the lowest-level data object

that has a PDS label.

PRODUCT_VERSION_ID Specifies the version of an individual

product within a data set.

PRODUCT_VERSION_ID is

intended for use within AMMOS to

identify separate iterations of a given

product, which will also have a unique

FILE_NAME.

String “V<vernum> D-

38107”

User specified

parameter

SOURCE_PRODUCT_ID The source_product_id data element

identifies a product used

as input to create a new product. The

source_product_id may

be based on a file name. See also:

product_id.

Note: For Mars Pathfinder, this refers

to the filenames of the

SPICE kernels used to produce the

product and its ancillary data.

CALIBRATION_SOURCE_ID The CALIBRATION_SOURCE_ID

element is a unique identifier (within a

data

set) indicating the source of the

calibration data used in generating the

entity described by the enclosing

group (often, a camera model). The

construction of this identifier is

mission-specific, but should indicate

which specific calibration data set was

used (via date or other means) and

may also indicate the calibration

method.





RELEASE_ID Specifies the unique identifier

associated with the release to the

public of all or part of a data set. The

release number is associated with the

data set, not the mission.

When a data set is released

incrementally, such as every three

months during a mission, the

RELEASE_ID is updated each time

part of the data set is released. The

first release of a data set in the mission

should have a value of "0001".

For example, on MSL the first release

of the SSI EDR data set on MSL will

have RELEASE_ID = "0001". The

next SSI EDR release will have

RELEASE_ID = "0002".

String User parameter input.

SPACECRAFT_CLOCK_START_COUNT Starting SCLK, smallest, value of all

the records contained in the EDR.

string(3

0)

Format is

dddddddddd.ddd,

measured in units of

seconds stored

internally as a floating

point number.

- EMD:

DvtCourse/Dv

tFine or

- Sclk or

- Pulled from

instrument

data

SPACECRAFT_CLOCK_STOP_COUNT The spacecraft_clock_stop_count

element provides the value

of the spacecraft clock at the end of a

time period of

interest.

START_TIME SPACECRAFT_CLOCK_START_C

OUNT converted and represented in

string Formation rule:

YYYY-MM-

OnBoardCreationTime

– the coarse SCLK in





UTC DDThh:mm:ss.fff 1-second presentation

STOP_TIME The stop_time element provides the

date and time of the end

of an observation or event (whether it

be a spacecraft,

ground-based, or system event) in

UTC.

Formation rule: YYYY-MM-

DDThh:mm:ss[.fff].

TARGET_NAME Identifies a target. The target may be a

planet, satellite, ring, region, feature,

asteroid or comet. See

TARGET_TYPE. This is based on

mission phase.

string(3

0)

“MARS”,

“CALIBRATION”

Calculated by

algorithm to determine

if looking at the

calibration target, if

not, then MARS.

TARGET_TYPE Specifies the type of a named target. string CALIBRATION,

DUST, N/A, SUN,

PLANET

Static value

/* SOURCE DATA ELEMENTS */ Comment

SOFTWARE_NAME The software_name element identifies

data processing software such as a

program or a program library.

SOFTWARE_VERSION_ID The software_version_id element

indicates theversion (development

level) of a program or a program

library.

SPICE_FILE_NAME Specifies the names of the SPICE files

used in processing the data. For

Galileo, the SPICE files are used to

determine navigation and lighting

information.

String User parameter input