Mars Exploration Rover (MER) Project

MB Reduced Data Record (RDR) Software Interface Specification (SIS)

Version 1.0

Prepared by: Edward A. Guinness

SIS Custodian

Paper copies of this document may not be current and should not be relied on for official purposes. The current version is in the MER Project Library at http://mars03-lib.jpl.nasa.gov, in the Controlled Documents and Records folder.

JPL D-29708

September 26, 2005

Jet Propulsion Laboratory

California Institute of Technology

CHANGE LOG

TBD ITEMS

SECTION	DESCRIPTION
Appendix A	E. Guinness to design label for MIN product based on data file descriptions from team.

CONTENTS

CHANGE LOG.............................................................................................................................. iii

TBD ITEMS................................................................................................................................... iv

CONTENTS................................................................................................................................... v

LIST OF TABLES........................................................................................................................ vi

ACRONYMS................................................................................................................................ vii

1. INTRODUCTION....................................................................................................................... 1

1.1 Purpose and Scope........................................................................................................... 1

1.2 Contents............................................................................................................................... 1

1.3 Applicable Documents and Constraints........................................................................... 1

1.4 Relationships with Other Interfaces................................................................................... 2

2. Data Product Characteristics and Environment........................................ 2

2.1 Data Product Overview...................................................................................................... 2

2.2 Data Processing................................................................................................................. 2

2.2.1 Data Processing Level............................................................................................... 2

2.2.2 Data Product Generation............................................................................................ 3

2.2.3 Data Flow..................................................................................................................... 3

2.2.4 Labeling and Identification.......................................................................................... 4

2.3 Standards Used in Generating Data Products................................................................ 7

2.3.1 PDS Standards........................................................................................................... 7

2.3.2 Time Standards........................................................................................................... 7

2.3.3 Data Storage Conventions......................................................................................... 7

2.4 Data Validation................................................................................................................... 7

3. Detailed Data Product Specifications............................................................... 7

3.1 Data Format Description................................................................................................... 7

3.2 PDS Label Description.................................................................................................... 12

APPENDIX A - Sample MB RDR Label............................................................................ 13

MGC......................................................................................................................................... 13

MXC......................................................................................................................................... 18

RSC.......................................................................................................................................... 24

ESC.......................................................................................................................................... 29

DSC.......................................................................................................................................... 33

ESE.......................................................................................................................................... 37

MIN............................................................................................................................................ 41

aPPENDIX B - LABEL KEYWORD DEFINITIONS............................................................... 43

LIST OF TABLES

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

Table 2. MB RDR data product types......................................................................... 7

Table 3. 14.4 keV MB spectra as a function of channel number (MGC).. 8

Table 4. 6.4 keV MB spectra as a function of channel number (MXC)..... 9

Table 5. 14.4 keV MB reference spectra as a function of channel number (RSC). 9

Table 6. Differential signal as a function of channel number (DSC).. 10

Table 7. Energy spectra as a function of channel number (ESC)......... 10

Table 8. Energy spectra as a function of energy (ESE).............................. 11

Table 9. Results of mineralogical MB analysis (MIN)..................................... 11

ACRONYMS

ASCII	American Standard Code for Information Interchange
MB	Mössbauer
CODMAC	Committee on Data Management and Computation
EDR	Experiment Data Record
ISO	International Standards Organization
JPL	Jet Propulsion Laboratory
MER	Mars Exploration Rover
NASA	National Aeronautics and Space Administration
ODL	Object Description Language
OSS	Operations Storage Server
PDS	Planetary Data System
RDR	Reduced Data Record
SIS	Software Interface Specification
SOWG	Science Operations Working Group
STG	Science Theme Group
TBD	To Be Determined

1. INTRODUCTION

1.1 Purpose and Scope

The purpose of this data product SIS is to provide users of the MER Mössbauer (MB) Reduced Data Record (RDR) products with detailed descriptions of the products and descriptions of how they were generated, including data sources and destinations. The products are ASCII tables of data derived from MER MB Experiment Data Record (EDR) products. The RDR products include summed spectra in counts as a function of channel number, energy spectra in counts as a function of energy, and tables of Fe-mineral and Fe-state components within a sample. There are seven different types of MB RDR products that are divided into two separate data sets: Summed Spectra, and Mineral Abundances.

This SIS is intended to provide enough information to enable users to read and understand these data products. The users for whom this SIS is intended are the scientists who will analyze the data, including those associated with the MER Project and those in the general planetary science community.

1.2 Contents

This data product SIS describes how the MB 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 MER documents:

1. Mars Exploration Program Data Management Plan, R. E. Arvidson, S. Slavney, and S. Nelson, Rev. 3, March 20, 2002.

2. Mars Exploration Rover Project Archive Generation, Validation and Transfer Plan, R. E. Arvidson and S. Slavney, JPL D-19658, March 22, 2002.

3. MER Project MB EDR SIS, E. Guinness, JPL D-22849, Version 2.0, June 13, 2003.

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

4. Planetary Data System Data Preparation Workbook, Version 3.1, JPL D-7669, Part 1, February 1, 1995.

5. Planetary Data System Data Standards Reference, Version 3.5, JPL D-7669, Part 2, October, 15, 2002

6. Planetary Science Data Dictionary Document, JPL D-7116, August 28, 2002.

The reader is referred to the following documents for additional information:

7. Athena MIMOS II Mössbauer spectrometer investigation, G. Klingelhöfer, R. V. Morris, B. Bernhardt, D. Rodionov, P. A. de Souza Jr., S. W. Squyres, J. Foh, E. Kankeleit, U. Bonnes, R. Gellert, C. Schröder, S. Linkin, E. Evlanov, B. Zubkov, and O. Prilutski, JGR, Vol. 108, NO: E12, 8067, doi:10.1029/2003JE002138, 2003.

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

1.4 Relationships with Other Interfaces

Changes to the MB EDR data product and the SIS that describes the EDR product [3] could affect the MB RDR data products and/or this SIS. In addition, changes to the processing tools used to generate the MB RDR data products could affect both the data products and this SIS.

2. Data Product Characteristics and Environment

2.1 Data Product Overview

The MB RDR data products are ASCII formatted tables. Each ASCII table has an associated detached PDS label, also formatted as ASCII. There are seven MB RDR data products from intermediate data reduction to more highly derived ones. The product types include summed spectra in counts as a function of channel number, energy spectra in counts as a function of energy, and tables of Fe-mineral and Fe-state components within a sample.

2.2 Data Processing

2.2.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 MB RDR data products. These data products are considered CODMAC "Level 4" ["Resampled Data" equivalent to NASA Level 1-B] or "Level 5" ["Derived Data" equivalent to NASA Level 2]. Refer to Table 1 for a summary of the CODMAC and NASA data processing levels.

Table 1. Processing Levels for Science Data Sets

2.2.2 Data Product Generation

The MB RDR data products are produced by MB instrument team members from the Johannes Gutenberg University (Mainz, Germany) using software tools developed by the MB team. The first set of RDR data products - summed spectra in counts as a function of channel number - is generated after each sol in which MB data were acquired. This step comprises an extraction of the MB spectra from the EDR products and subsequent conversion into ASCII formatted tables. Further sets of RDR data products are added in a non-specified timeframe according to the progress in analysis of the data by the MB team.

The MB instrument has four counters to store eight measurements from the MB detectors (4 detectors with 2 energies each) [7]. As a result the measurements from pairs of detectors are added together and stored in one counter. These four co-added spectra are included in the MB EDR data products. In generating the RDR products, the two 6.4 keV spectra from each EDR are summed, as are the two 14.4 keV spectra. These summed spectra exist, and are labeled as separate products in the RDR data set (i.e., MGC and MXC products).

The interpretation of MB spectra requires precise knowledge at any given time of the drive velocity, which has a temperature dependence. There is documentation in the CALIB directory of the MB RDR data set that explains how the velocity calibration can be done. The CALIB directory also contains data files with velocity scales that take the temperature dependence into account. Each column in these velocity files corresponds to a preset temperature window that matches the columns in the MGC and the MXC data files.

Integration times for each MB measurement are listed in the observation table provided in the DOCUMENT directory of the RDR data set.

2.2.3 Data Flow

MB RDR data products are generated from binary EDR files that are extracted from the OSS to the MB team workstations. Once RDR data products are generated, they are transferred back to the OSS for access by other MER science and operations team members. After a science validation period, the MB RDR data products are transferred to the PDS for final validation and archiving in accordance with the MER archive plan [2].

2.2.4 Labeling and Identification

2.2.4.1 Data Sets Identification

The MB RDR data products are divided into two separate data sets. The groupings are based on the level of data processing and calibration that was applied to the EDR data. The two data sets with the PDS data set id's listed are:

MERn-M-MB-4-SUMSPEC-SCI-V1.0 - Spectra in counts as a function of channel number with data from all detectors summed together.

MERn-M-MB-5-MINERAL-SCI-V1.0 - Iron state and minerals present within a sample as derived from analysis by the MB team on the calibrated spectra.

Note the 'n' in the data set id is used to indicate the rover with 1 for Opportunity (MERB) and 2 for Spirit (MERA).

2.2.4.2 File Naming

A file naming scheme has been adapted for the MER image and non-image data products. The file naming scheme adheres to the ISO Level II 27.3 filename convention to be compliant with PDS standards.

Each MER EDR or RDR data product can be uniquely identified by incorporating into the product filename the Rover Mission identifier, the Instrument identifier, the Starting Spacecraft Clock count (SCLK) of the observation, the data Product Type, the Site location, the rover Position within the site, the Sequence number, the camera "Eye", the spectral Filter, the product Creator identifier and a Version number. For non-camera data, several fields do not apply.

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

<rover><inst>< sclk><prod><site>< pos><seq><eye>< filt><who><ver> .<ext>

2.3 Standards Used in Generating Data Products

2.3.1 PDS Standards

The MB RDR data products comply with Planetary Data System standards for file formats and labels, as specified in the PDS Standards Reference [5] and the Planetary Science Data Dictionary Document [6].

2.3.2 Time Standards

PDS labels for MB RDR data products use keywords containing time values, such as start time and stop time. Each time value standard is defined according to the keyword definition. See Appendix B.

2.3.3 Data Storage Conventions

MB RDR data products and detached PDS label files are stored as ASCII text. Each line or record in the files is terminated with a two-character sequence of carriage return (<CR>, ASCII 13) and line feed (<LF>, ASCII 10) to comply with PDS standards [5]. This line terminator sequence will allow the data files and labels to be easily read on most computers, which recognize either the carriage return, the line feed, or the <CR>/<LF> sequence as an ASCII record terminator.

2.4 Data Validation

Validation of MB RDR data product labels includes checking for correct PDS syntax, for accepted standard values of keywords, and for internal consistency of label items.

3. Detailed Data Product Specifications

3.1 Data Format Description

Each MB RDR data file is a comma delimited ASCII text table with variable length columns. The number of columns and rows in each table is dependent on the type of RDR. Each row is terminated with a carriage return and line feed character. Table 2 is a summary of the MB RDR product types and tables 3-9 contains the column definitions for each of the data products.

Table 2. MB RDR data product types

Table 3. 14.4 keV MB spectra as a function of channel number (MGC).

Column Number	Name	Data Type	Description
1	Temperature bin m1	Integer	The number is the sum of 14.4 keV photons counted by all four detectors within a temperature range from 0 to 180 K.
2	Temperature bin m2	Integer	The number is the sum of 14.4 keV photons counted by all four detectors within a temperature range from 180 to 190 K.
3	Temperature bin m3	Integer	The number is the sum of 14.4 keV photons counted by all four detectors within a temperature range from 190 to 200 K.
4	Temperature bin m4	Integer	The number is the sum of 14.4 keV photons counted by all four detectors within a temperature range from 200 to 210 K.
5	Temperature bin m5	Integer	The number is the sum of 14.4 keV photons counted by all four detectors within a temperature range from 210 to 220 K.
6	Temperature bin m6	Integer	The number is the sum of 14.4 keV photons counted by all four detectors within a temperature range from 220 to 230 K.
7	Temperature bin m7	Integer	The number is the sum of 14.4 keV photons counted by all four detectors within a temperature range from 230 to 240 K.
8	Temperature bin m8	Integer	The number is the sum of 14.4 keV photons counted by all four detectors within a temperature range from 240 to 250 K.
9	Temperature bin m9	Integer	The number is the sum of 14.4 keV photons counted by all four detectors within a temperature range from 250 to 260 K.
10	Temperature bin m10	Integer	The number is the sum of 14.4 keV photons counted by all four detectors within a temperature range from 260 to 270 K.
11	Temperature bin m11	Integer	The number is the sum of 14.4 keV photons counted by all four detectors within a temperature range from 270 to 280 K.
12	Temperature bin m12	Integer	The number is the sum of 14.4 keV photons counted by all four detectors within a temperature range from 280 to 290 K.
13	Temperature bin m13	Integer	The number is the sum of 14.4 keV photons counted by all four detectors at temperatures higher than 290 K.
Rows counted from the top correspond to channel number.

Table 4. 6.4 keV MB spectra as a function of channel number (MXC).

Column Number	Name	Data Type	Description
1	Temperature bin m1	Integer	The number is the sum of 6.4 keV photons counted by all four detectors within a temperature range from 0 to 180 K.
2	Temperature bin m2	Integer	The number is the sum of 6.4 keV photons counted by all four detectors within a temperature range from 180 to 190 K.
3	Temperature bin m3	Integer	The number is the sum of 6.4 keV photons counted by all four detectors within a temperature range from 190 to 200 K.
4	Temperature bin m4	Integer	The number is the sum of 6.4 keV photons counted by all four detectors within a temperature range from 200 to 210 K.
5	Temperature bin m5	Integer	The number is the sum of 6.4 keV photons counted by all four detectors within a temperature range from 210 to 220 K.
6	Temperature bin m6	Integer	The number is the sum of 6.4 keV photons counted by all four detectors within a temperature range from 220 to 230 K.
7	Temperature bin m7	Integer	The number is the sum of 6.4 keV photons counted by all four detectors within a temperature range from 230 to 240 K.
8	Temperature bin m8	Integer	The number is the sum of 6.4 keV photons counted by all four detectors within a temperature range from 240 to 250 K.
9	Temperature bin m9	Integer	The number is the sum of 6.4 keV photons counted by all four detectors within a temperature range from 250 to 260 K.
10	Temperature bin m10	Integer	The number is the sum of 6.4 keV photons counted by all four detectors within a temperature range from 260 to 270 K.
11	Temperature bin m11	Integer	The number is the sum of 6.4 keV photons counted by all four detectors within a temperature range from 270 to 280 K.
12	Temperature bin m12	Integer	The number is the sum of 6.4 keV photons counted by all four detectors within a temperature range from 280 to 290 K.
13	Temperature bin m13	Integer	The number is the sum of 6.4 keV photons counted by all four detectors at temperatures higher than 290 K.
Rows counted from the top correspond to channel number.

Table 5. 14.4 keV MB reference spectra as a function of channel number (RSC).

Column Number	Name	Data Type	Description
1	Temperature bin m1	Integer	14.4 keV photons counted by the reference detector within a temperature range from 0 to 180 K.
2	Temperature bin m2	Integer	14.4 keV photons counted by the reference detector within a temperature range from 180 to 190 K.
3	Temperature bin m3	Integer	14.4 keV photons counted by the reference detector within a temperature range from 190 to 200 K.
4	Temperature bin m4	Integer	14.4 keV photons counted by the reference detector within a temperature range from 200 to 210 K.
5	Temperature bin m5	Integer	14.4 keV photons counted by the reference detector within a temperature range from 210 to 220 K.
6	Temperature bin m6	Integer	14.4 keV photons counted by the reference detector within a temperature range from 220 to 230 K.
7	Temperature bin m7	Integer	14.4 keV photons counted by the reference detector within a temperature range from 230 to 240 K.
8	Temperature bin m8	Integer	14.4 keV photons counted by the reference detector within a temperature range from 240 to 250 K.
9	Temperature bin m9	Integer	14.4 keV photons counted by the reference detector within a temperature range from 250 to 260 K.
10	Temperature bin m10	Integer	14.4 keV photons counted by the reference detector within a temperature range from 260 to 270 K.
11	Temperature bin m11	Integer	14.4 keV photons counted by the reference detector within a temperature range from 270 to 280 K.
12	Temperature bin m12	Integer	14.4 keV photons counted by the reference detector within a temperature range from 280 to 290 K.
13	Temperature bin m13	Integer	14.4 keV photons counted by the reference detector at temperatures higher than 290 K.
Rows counted from the top correspond to channel number.

Table 6. Differential signal as a function of channel number (DSC).

Column Number	Name	Data Type	Description
1	Differential signal	Integer	The number is proportional to the velocity difference between actual drive velocity and the triangular nominal velocity signal.
Rows counted from the top correspond to channel number.

Table 7. Energy spectra as a function of channel number (ESC).

Column Number	Name	Data Type	Description
1	Detector 1	Integer	Energy spectrum.
2	Detector 2	Integer	Energy spectrum.
3	Detector 3	Integer	Energy spectrum.
4	Detector 4	Integer	Energy spectrum.
5	Reference detector	Integer	Energy spectrum.
Rows counted from the top correspond to channel number.

Table 8. Energy spectra as a function of energy (ESE).

Column Number	Name	Data Type	Description
1	Energy for detector 1	Real	Energy in keV.
2	Detector 1	Integer	Energy spectrum in counts.
3	Energy for detector 2	Real	Energy in keV.
4	Detector 2	Integer	Energy spectrum in counts.
5	Energy for detector 3	Real	Energy in keV.
6	Detector 3	Integer	Energy spectrum in counts.
7	Energy for detector 4	Real	Energy in keV.
8	Detector 4	Integer	Energy spectrum in counts.
9	Energy for reference detector	Real	Energy in keV.
10	Reference detector	Integer	Energy spectrum in counts.

Table 9. Results of mineralogical MB analysis (MIN).

Column Number	Name	Data Type	Description
1	Mineral name	Text	Mineral components identified in MB spectrum
2	Isomer shift	Real	Value of Isomer shift in mm/s.
3	Quadrupole splitting	Real	Value of quadrupole splitting n mm/s.
4	Internal magnetic field	Real	Value of the internal magnetic field in mm/s.
5	Temperature	Real	Value of the temperature /temperature range during measurement
6	Area %	Real	Relative peak area of component in MB spectrum (1.0 = 100 %).
7	Fe2+/Fe_Total	Real	Fe2+/Fe_Total number for overall sample.

3.2 PDS Label Description

Each MB RDR data product has a detached PDS label, which is stored as ASCII text. The PDS label is object-oriented with keywords for product identification, along with the data object definition. The data object definition within the label contains descriptive information needed to interpret or process the data.

PDS labels are written in Object Description Language (ODL) [5]. 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 data product:

^object = location

where the carat character (^, also called a pointer) is followed by the name of the specific data object. For detached PDS labels, location is the name of the file that contains data object and optionally the starting record number of the data object within the file or byte offset from the start of the file.

MB RDR data products are described using the PDS spreadsheet object. Appendix A lists example PDS labels for the each MB RDR type.

APPENDIX A - Sample MB RDR Label

MGC

PDS_VERSION_ID = PDS3

/* FILE DATA ELEMENTS */

RECORD_TYPE = STREAM

FILE_RECORDS = 512

^SPREADSHEET = "2B127615581MGC0309N1940N0J1.CSV"

/* IDENTIFICATION DATA ELEMENTS */

DATA_SET_ID = "MER2-M-MB-4-SUMSPEC-SCI-V1.0"

PRODUCT_ID = "2B127615581MGC0309N1940N0J1"

PRODUCT_TYPE = MB_MGC

SOURCE_PRODUCT_ID = "2B127615581EDR0309N1940N0M1"

RELEASE_ID = "0001"

ROVER_MOTION_COUNTER = (3, 9, 28, 983, 166)

ROVER_MOTION_COUNTER_NAME = (SITE, DRIVE, IDD, PMA, HGA)

COMMAND_SEQUENCE_NUMBER = 6

INSTRUMENT_HOST_ID = MER2

INSTRUMENT_HOST_NAME = "MARS EXPLORATION ROVER 2"

INSTRUMENT_ID = MB

INSTRUMENT_TYPE = SPECTROMETER

INSTRUMENT_VERSION_ID = FM3

LOCAL_TRUE_SOLAR_TIME = "14:00:44"

MAGNET_ID = "NULL"

MISSION_NAME = "MARS EXPLORATION ROVER"

MISSION_PHASE_NAME = "PRIMARY MISSION"

OBSERVATION_ID = "0"

PLANET_DAY_NUMBER = 14

PRODUCER_INSTITUTION_NAME = "JOHANNES GUTENBERG UNIVERSITY"

PRODUCT_CREATION_TIME = 2004-07-15T17:30:00

SEQUENCE_ID = n1940

SEQUENCE_VERSION_ID = "0"

SPACECRAFT_CLOCK_CNT_PARTITION = 1

SPACECRAFT_CLOCK_START_COUNT = "127615519.910"

SPACECRAFT_CLOCK_STOP_COUNT = "127615581.921"

START_TIME = 2004-01-17T12:43:54.397

STOP_TIME = 2004-01-17T12:44:56.409

TARGET_NAME = MARS

TARGET_TYPE = PLANET

/* TELEMETRY DATA ELEMENTS */

APPLICATION_PROCESS_ID = 33

APPLICATION_PROCESS_NAME = MB

APPLICATION_PROCESS_SUBTYPE_ID = 0

EARTH_RECEIVED_START_TIME = 2004-01-1