Mission-Specific Information:

The reference interface document was written to cover a set of missions that preceded the Mars Reconnaissance Orbiter (MRO) mission. The format information in this reference document also applies for MRO, but some mission-specific information is missing. Following is MRO-specific information that supplements the prior-mission information in the reference document:

MRO:

Mission Name = MARS_RECONNAISSANCE_ORBITER

Mission ID (decimal) = 28

Spacecraft Name Real (MRO) = MARS_ RECONNAISSANCE_ORBITER

Spacecraft Name Sim (MRO_SIM) = MARS_ RECONNAISSANCE_ORBITER _SIM

Spacecraft ID / DSN Spacecraft Number (MRO; decimal) = 74

Spacecraft ID / DSN Spacecraft Number (MRO_SIM; decimal) = 208

Mars Reconnaissance Orbiter (MRO)

RSDSGravity Experiment Products
Software Interface Specification (SIS)

Version 1.0

Prepared by:

Julia Henricks

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

October 11, 2005

Jet Propulsion Laboratory

California Institute of Technology

CHANGE LOG

TBD ITEMS

SECTION	DESCRIPTION	RESPONSIBILITY
	None

CONTENTS

CHANGE LOG.............................................................................................................................. v

TBD ITEMS................................................................................................................................... vi

CONTENTS.................................................................................................................................. vii

ACRONYMS............................................................................................................................... viii

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...................................................................................... 1

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

2.1 Instrument Overview............................................................................................................ 2

2.2 Data Product Overview........................................................................................................ 2

2.3 Data Processing..................................................................................................................... 2

2.3.1 Data Flow....................................................................................................................... 3

2.3.2 File Naming Conventions............................................................................................... 3

3. Detailed Data Product Specifications......................................................................................... 6

3.1 Data Product Structure, Organization, and Format.............................................................. 6

ACRONYMS

ASCII	American Standard Code for Information Interchange
CODMAC	Committee on Data Management and Computation
FEI	File Exchange Interface
ICD	Interface Control Document
JPL	Jet Propulsion Laboratory
MIPL	Multi-mission Image Processing Laboratory
MRO	Mars Reconnaissance Orbiter
NASA	National Aeronautics and Space Administration
ODL	Object Description Language
PDS	Planetary Data System
RAM	Random Access Memory
SFDU	Standard Formatted Data Unit
SIS	Software Interface Specification
TBD	To Be Determined

1. INTRODUCTION

1.1 Purpose and Scope

The purpose of this Gravity Experiment Products SIS is to provide users of the Gravity Experiment Team with a description of the products to be delivered by the Mars Reconnaissance Orbiter (MRO) Raw Science Data Server (RSDS), including data sources and destinations.

The files to be delivered to the Gravity Experiment Team and referenced by this SIS are:

1. NAV003, Light Time File

2. NAV011, Maneuver Performance Data File

3. NAV023, Orbit Data File

4. DSN006, DSN Media Calibration Data

5. DSN007, DSN Weather Data

This SIS is intended to provide enough information to enable users to understand the files to be delivered and the method and frequency of delivery to the Gravity Experiment Team. The users for whom this SIS is intended are the scientists and investigators who will process and analyze the data, including those associated with the MRO Project.

1.2 Contents

This SIS describes the files to be delivered to the Gravity Experiment Team via the MRO Raw Science Data Server (RSDS). The method of delivery to the Gravity Experiment Team is via File Exchange Interface (FEI) subscription.

1.3 Applicable Documents and Constraints

None

1.4 Relationships with Other Interfaces

RSDS will be used to provide a single delivery source for the above named files to the Gravity Team. As files are delivered by the originating teams to the DOM or OSCARX, the files are transferred into a corresponding file type on the MRO_DIST server. Notification of the availability of the files to the RSDS processes is via the DOM File Notification Service (FNS) for Light Time Files, Maneuver Performance Data Files, and Orbit Data Files. File lists on OSCARX for DSN Media Calibration Data Files and DSN Weather Data Files are queried daily and files received since the last received file are transferred via FEI to the MRO_DIST server.

2. Data Product Characteristics and Environment

2.1 Instrument Overview

The Gravity Experiment Team will track the orbiter during the Primary Science Phase to better map the gravity field of Mars, including characterization of mass changes due to the seasonal condensation and sublimation of CO₂.

2.2 Data Product Overview

The data are stored as files. The Light Time Files, Maneuver Performance Data Files, DSN Media Calibration Files, and DSN Weather Data Files are ASCII format of variable-length. Orbit Data Files are binary format of standard 1200-bit or 4800-bit data blocks. The following table defines the file type, estimated file size, frequency of delivery, source of files, and FEI file type for each file.

File	File Type	Estimated File Size	Frequency of Delivery	Source of Files	FEI File Type
SIS-NAV003-MRO Light Time File	ASCII	Less than 2 Mbytes	Every 14 - 30 days during cruise and weekly during PSP (ref OIA NAV-01)	MRO Project DOM	ops_ltf
SIS-NAV011-MRO Maneuver Performance Data File	ASCII	4300 bytes	An MPDF will be delivered pre-launch and before each propulsive maneuver. (ref OIA SCT-05)	MRO Project DOM	ops_mpdf
SIS-NAV023-MRO Orbit Data File	BINARY	Less than 2 Mbytes	Daily, after end of tracking pass (ref OIA NTDS-10)	OSCARX	ops_dsn_radio
SIS-DSN006-MRO DSN Media Calibration Data	ASCII	Less than 150 Kbytes	Weekly (ref OIA NTDS-05)	OSCARX	ops_dsn_media
SIS-DSN007-MRO DSN Weather Data	ASCII	1 Mbytes	Daily updates; which overwrite latest file (ref OIA NTDS-xx)	OSCARX	ops_dsn_weather

2.3 Data Processing

No additional data processing by RSDS is performed.

2.3.1 Data Flow

The Gravity Experiment data files are stored on the MRO Raw Science Data Server (RSDS) and then deposited into MIPL's File Exchange Interface (FEI) server for electronic distribution to remote sites via a secure subscription protocol.

The size of data files ranges from 4300 bytes to 2 Mbytes. The total estimated volume of the Gravity Experiment data files over the course of the MRO mission is 1 - 2 Gbytes. The data repositories (DOM and OSCARX) are checked once a day, and any files received since the last retrieved file are transferred to RSDS and made available to the Gravity Experiment Team via FEI.

2.3.2 File Naming Conventions

The file naming convention used by the originating teams and repositories are preserved in RSDS. The file naming conventions are defined in the referenced SISs and repeated here for convenience:

Light Time File:

Light Time Files are created by the Navigation Team and are stored on the MRO Project DOM. The size of the file depends on the length of the trajectory and upon the data interval for which Light Time records are desired.

File Naming Convention: <file_type>_<msn_phase>_<sp_id>_<epoch>_<end>_<version>.<ext>

<file_type>: ltf (light time file)

<msn_phase>: c - cruise/approach, moi - mars orbit insertion, ab -aerobraking/transition, psp -

primary science phase, rly - relay

<sp_id>:

-Test/traning: svt, test, ort#

-Operations:

»Cruise/moi/aerobraking/transition: sol/traj-id (OD solution/traj id)

» PSP/relay: lng (long term), sh (short term)

<epoch>/<end>: yymmdd (e.g. 050901)

<version>: geo-v# (geocentric light time version, e.g. geo-v1), top-v# (topocentric light time version,)

<ext>: txt (text) or none (no extension for sfdu wrapped file)

Example: ltf_psp_lng_070801-080801_geo-v1.txt

Maneuver Performance Data File:

An Maneuver Performance Data File is created pre-launch and before each propulsive maneuver by the Spacecraft Team (SCT). This excludes daily or periodic attitude control maneuvers and certain pre-planned maneuvers. The files are stored on the MRO Project DOM.

File Naming Convention:

<file_type>.<mission_id>_<tcm_id> or <msn_phase>_<version>.<ext>

<file_type> and <ext>: "mpdf"

<mission_id>: "mro"

<tcm_id>: "tcm"# (e.g., tcm1)

<msn_phase>: c - cruise/approach, moi - mars orbit insertion, ab -aerobraking/transition, psp -

primary science phase, rly - relay

Examples: mpdf.mro_tcm1, moi_prelim.mpdf

DSN Media Calibration Data File:

The DSN Media Calibration Files are created by the Tracking Systems Analytic Calibration (TSAC) Operations Unit and stored on OSCARX. A separate calibration file is provided for each medium (ionosphere, troposphere, or solar plasma) desired. Ionosphere and solar plasma calibration files provide one calibration per tracking pass, or other time period of interest, at each Deep Space Communications Complex (DSCC) or Deep Space Station (DSS). Troposphere calibration files provide two calibrations for each pass: a "dry" delay calibration and a "wet" delay calibration. Each calibration occupies approximately 160 to 320 bytes of storage.

A separate calibration file is provided for each medium (ionosphere, troposphere, or

solar plasma) desired. Ionosphere and solar plasma calibration files provide one calibration per tracking pass, or other time period of interest, at each Deep Space Communications Complex (DSCC) or Deep Space Station (DSS). Troposphere calibration files provide two calibrations for each pass: a "dry" delay calibration and a "wet" delay calibration. Each calibration occupies approximately 160 to 320 bytes of storage.

Media calibrations refer to one of four media: ionospheric charged particles (media model MODEL(CHPART)), tropospheric wet delay (MODEL(WET NUPART)), tropospheric dry delay (MODEL(DRY NUPART)), and solar plasma (MODEL(DRVID)).

File Naming Convention:

Media calibration file names are constructed to indicate the applicable transmission medium, spacecraft, dates, and tracking data type(s). The specific naming conventions are subject to change and should be confirmed with TSAC Operations. The following describes the conventions that are used currently.

Media calibration file names have the form medium_sc_datespan_datatype.CSP; e.g.,

TROPCAL_82_0002_DOPRNG.CSP. medium is either IONCAL, TROPCAL, or PLSMCAL; sc is the spacecraft id number; datespan indicates the range of UTC dates covered by the calibrations; and datatype is one of the data type limiters listed belowin section 3.1.2, usually DOPRNG.

datespan refers to the start dates of the calibrations. It takes one of three forms:

1. yymmdd_MMDD is used for TROPCAL and PLSMCAL files that contain less than a full calendar month of calibrations; e.g., 000201_0214 for the first two weeks of February, 2000. These files are typically created for daily-to-weekly deliveries and are replaced by files of type 2 below shortly after the end of the month.

2. yymm is used for files that contain one full calendar month of calibrations; e.g., 0002 for February of 2000. These files are typically created shortly after the end of the month. The same form is used for daily-to-weekly delivery IONCAL files, which contain calibrations for the first part of the month and predictions for the rest of it.

3. yymm_YYMM is used for IONCAL files that contain calibrations and predictions for month yymm plus predictions for the next month YYMM. These files are typically created for the last scheduled delivery of month yymm.

datatype, or data type limiters indicate the specific radio metric data type(s) to be adjusted or deleted; e.g., ADJUST(DOPRNG). The data type limiters used in the media calibrations are: DOPPLER

(Doppler data), RANGE (range data), DOPRNG (Doppler and range data), VLBI (VLBI data), and

DVLBI (Delta-VLBI data). Most media calibrations refer to data type DOPRNG since Doppler/Range

tracking is by far the most common.

DSN Weather Data File:

The DSN Weather Data files contain the the following data for each DSS complex (10, 60, 40):

· A header containing the current date , day of year (doy) and complex number

· Each data record comprises a time tag and four right-justified data fields, as shown in the following list.

· Time (HHMM), columns 2-5.

· Dew point (STT.T, degrees Celsius), columns 11-15.

The sign, S, may be either - or blank according to the data.

· Ambient temperature (STT.T, degrees Celsius), columns 20-24.

· Pressure (PPPP.P, millibars), columns 29=34.

· Water vapor partial pressure (PPPP.P, millibars), columns 40-45.

File Naming Convention:
weather_<STA_ID>_latest.txt or weather_<STA_ID>_<YYYY>.txt

<STA_ID>: DSS complex identifier (i.e., 10, 40, 60)

"latest": - file containing the latest DSN weather data collected to date. (This data represents the data collected for the current year to date.)

<YYYY>: year in which data was collected (The year is substituted for "latest" in the file name after the last data for that year has been collected. These files are typically created for the last scheduled delivery of year YYYY and contain the entire year's worth of weather data for the given station complex.).

Examples: weather_60_latest.txt, weather_60_2003.txt

Orbit Data File:

The Orbit Data File (ODF) contain radio metric data from the Deep Space Network (DSN). The contents and formats of the ODF data blocks/records generated by the DSN Multimission Navigation (MMNAV) Radio Metric Data Conditioning Team (RMDCT) are defined in the referenced SIS.

File Naming Convention:

<yydddhhmm>SC<sc_id>DSS<dss_id>.218

<yydddhhmm>: date and time data was collected (e.g. "052230640" represents year 2005, day of year 223, time 06:40 (UTC))

<sc_id>: MRO spacecraft id (decimal) (e.g., 74)

<dss_id>: DSS antenna ID (e.g., 16 representing Goldstone antenna)

Example: 052230640SC74DSS16.218

3. Detailed Data Product Specifications

3.1 Data Product Structure, Organization, and Format

The structure of Gravity Experiment Products are defined by the individual SISs for each of the five file types delivered. The structure and content of those files are defined by the relevant Software Interface Specifications referenced by this SIS document.