PDS_VERSION_ID = PDS3 RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 80 OBJECT = TEXT PUBLICATION_DATE = 1999-05-02 NOTE = "Software Interface Specification for the Mars Global Surveyor Radio Science Raw Data Archive. Formatted for display or printing with up to 78 constant width characters per line." END_OBJECT = TEXT END Stanford Center for Radar Astronomy Software Interface Specification Mars Global Surveyor Radio Science Raw Data Archive prepared by Richard A. Simpson Center for Radar Astronomy Stanford University Stanford, CA 94305-9515 650-723-3525 Version 1.0.8 5 May 1999 PREFACE |================================================================| | | | DOCUMENT CHANGE LOG | | | |================================================================| |REVISION|REVISION| SECTION | REMARKS | | NUMBER | DATE | AFFECTED | | |--------+--------+------------+---------------------------------| | 0.1 |96/07/13| All |Adapted from SIS for draft GLL | | | | | Radio Science Raw Data Archive | |--------+--------+------------+---------------------------------| | 0.2 |97/05/28| All |Revised to reflect practical | | | | | archive organization and actual | | | | | data types and labels | |--------+--------+------------+---------------------------------| | 0.3 |97/08/05| All |Fleshed out contents in terms of | | | | | actual directories and files to | | | | | be included. | |--------+--------+------------+---------------------------------| | 1.0 |97/09/12| All |Editorial improvements | |--------+--------+------------+---------------------------------| | 1.0.1 |97/09/24| 4.4.20 |Added data type SAK; renumbered | | | |Acr & Abbrev| subsequent sections. Minor | | | | Fig. 3-1 | rewording in existing section on| | | | Table 3-1-6| spacecraft CK files. | | | | 4.4.24 | | |--------+--------+------------+---------------------------------| | 1.0.2 |97/11/18|Distribution|Updated Yolanda Oliver address | |--------+--------+------------+---------------------------------| | 1.0.2 |97/11/18| 3.3 |Changed "Unix" to "UNIX" | |--------+--------+------------+---------------------------------| | 1.0.3 |97/12/30| 4.2.3.3 |Added OPTG_SIS.TXT document | |--------+--------+------------+---------------------------------| | 1.0.3 |97/12/30| All, esp. |Abandoned close control of | | | |T of Content| pagination | |--------+--------+------------+---------------------------------| | 1.0.3 |97/12/30| 4.4.15 |Added MPF data type | |--------+--------+------------+---------------------------------| | 1.0.4 |98/04/10| 4.4.6 |Added ECT and GDN data types; | | | | 4.4.10 | add GDN_SPK.TXT to DOCUMENT | | | | 3.1.4 | directory | | | | 4.2.3.2 | | | | | Figure 3-1 | | | | | Table 3-1-6| | |--------+--------+------------+---------------------------------| | 1.0.4 |98/04/10| Table 4-1-3|Update VOLUME_ID and dates to | | | | | reflect longer MOI phase and | | | | | delayed Mapping. | |--------+--------+------------+---------------------------------| | 1.0.4 |98/04/10| 5 |Updated PDS Operator information | |--------+--------+------------+---------------------------------| (continued) |================================================================| | | | DOCUMENT CHANGE LOG | | (continued) | | | |================================================================| |REVISION|REVISION| SECTION | REMARKS | | NUMBER | DATE | AFFECTED | | |--------+--------+------------+---------------------------------| | 1.0.5 |98/06/26| 3.1.4 |Added GDF data type and | | | | 4.4.10 | and GDF_SPK.TXT documentation | | | | 4.2.3.2 | file. | | | | Fig 3-1 | | | | | Table 3-1-6| | |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21|Distribution|Substitute Henderson for Sword; | | | | | updates for Oliver, Martin, | | | | | Springer, Lemoine. | |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21|Acro & Abbrv|Added BRO and MPF | | | | Figure 3-1 |Added BRO and MPF | | | |Table 3-1-6|Added BRO | |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21| 1.1 |Changed "over one hundred" to | | | | | "several hundred" CD WO volumes.| | | | 1.4.3 |Changed "likely to exceed 100" to| | | | | "likely to be 400-500." | |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21| 1.3 |Substituted ad hoc SIS written by| | | | | MGS Radio Science Team at [21] | | | | | for official DSN document, which| | | | | has not been updated since 1986.| |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21| 2.3.1 |Updated "P" for MOI, TMO, and | | | | | Mapping. | |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21| 2.5 |Changed number of copies from 3 | | | | | to 6 with explicit distribution | | | | | to PDS CN, NSSDC via PDS CN, PDS| | | | | GEO, PDS AMT, RSST, and RST. | |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21| 3.1.4 |Removed GDF_SPK.TXT, GDN_SPK.TXT,| | | | | and OPTG_SIS.TXT from list; | | | | | these are covered by the | | | | | paragraph which follows. | |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21|Figure 4-1-3|Corrected DATA_SET_ID to be | | | | | MGS-M-RSS-1-CRU-V1.0 | |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21|Table 4-1-3|Corrected Cruise DATA_SET_ID to | | | | | MGS-M-RSS-1-CRU-V1.0; updated | | | | | info for other phases. | |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21| 4.2.1.2.1 |Added text to over TSCnnnnn.SCK | | | | | naming, adopted in early 1999. | |--------+--------+------------+---------------------------------| (continued) |================================================================| | | | DOCUMENT CHANGE LOG | | (continued) | | | |================================================================| |REVISION|REVISION| SECTION | REMARKS | | NUMBER | DATE | AFFECTED | | |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21| 4.2.3.9 |Noted that document is an ad hoc | | | | | adaptation of an obsolete DSN | | | | | original. Corrected location of| | | | | files from CALIB to WEA. | |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21| 4.4.3 |Added section describing BRO | | | |4.4.4-4.4.32| files; renumbering following | | | | | sections. | |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21| 4.4.12 |Updated description of PostScript| | | |(now 4.4.13)| files accompanying Health Report| |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21| 4.4.25 |Added note that production of MGS| | | |(now 4.4.26)| SFO files was discontinued in | | | | | August 1998. | |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21| 4.4.26 |Added text describing new formats| | | |(now 4.4.27)| beginning in late August 1998. | |--------+--------+------------+---------------------------------| | 1.0.6 |99/03/21| 5 |Updated information for PDS | | | |(now 4.4.27)| Operator | |--------+--------+------------+---------------------------------| | 1.0.7 |99/03/22| 3.1.4 |Added paragraph allowing files of| | | | | opportunity to be included in | | | | | the final DOCUMENT directory of | | | | | a data set if they improve | | | | | understanding of the data. | | | | Figure 3-1 | Updated figure for consistency. | |--------+--------+------------+---------------------------------| | 1.0.7 |99/03/24|Acro & Abbrv|Added DCO, DCS, ENB, MCT; | | | | | updated USO | |--------+--------+------------+---------------------------------| | 1.0.7 |99/03/24| Figure 3-1 |Added ENB, MCT, USO; dropped TIM | |--------+--------+------------+---------------------------------| | 1.0.7 |99/03/24| Table 3-1-6|Added ENB, MCT, USO | |--------+--------+------------+---------------------------------| | 1.0.7 |99/03/24| 4.2.1.2.8 |Moved to Section 4.4; reworded. | |--------+--------+------------+---------------------------------| | 1.0.7 |99/03/24| 4.4.nn |Added language explicitly stating| | | | | that AGK, ECH-CSV, ECS, ECT, | | | | | FBR, MCH-CSV, and USO files have| | | | | fixed length records with | | | | | delimiters. | |--------+--------+------------+---------------------------------| | 1.0.7 |99/03/24| 4.4.nn |Added sections for ENB, MCT, USO | |--------+--------+------------+---------------------------------| (continued) |================================================================| | | | DOCUMENT CHANGE LOG | | (continued) | | | |================================================================| |REVISION|REVISION| SECTION | REMARKS | | NUMBER | DATE | AFFECTED | | |--------+--------+------------+---------------------------------| | 1.0.7 |99/03/24| 4.4.5 |CSV file names should have *.ECH | | | | 4.4.16 | or *.MCH suffix instead of *.TAB| |--------+--------+------------+---------------------------------| | 1.0.8 |99/05/02| 3.1.2 |Added "antenna description files"| | | | | to list of subjects covered in | | | | | CALIB directory. | |--------+--------+------------+---------------------------------| | 1.0.8 |99/05/02| 4.2.1.2.4- |Added sections describing ASP, | | | | 4.2.1.2.6 | HCK, and TFK files; renumbered | | | | Contents | following sections; added ASP, | | | | Acro & Abbr| HCK, TFK to acronym list | |--------+--------+------------+---------------------------------| | 1.0.8 |99/05/02| 4.2.3.2 |Added section on ANTFILES.TXT; | | | | Contents | renumbered following sections. | |--------+--------+------------+---------------------------------| | 1.0.8 |99/05/02| 4.4.1 |Minor updates to conform to AGK | | | | | file as actually produced. | |================================================================| |================================================================| | | | ITEMS TO BE DETERMINED | | | |================================================================| | REVISION | SECTION | ITEM DESCRIPTION | RESOLUTION | | NUMBER | AFFECTED | | | |----------+----------+------------------------+-----------------| | | | | | |================================================================| Distribution PDS/JPL Y. Oliver.............171-264 Yolanda.J.Oliver@jpl.nasa.gov V.L. Henderson..........171-264 Valerie.L.Henderson@jpl.nasa.gov M. Martin.............171-264 mike_martin@isd.jpl.nasa.gov PDS/Washington University E. Guinness......Dept E&P Sci guinness@wunder.wustl.edu R.E. Arvidson......Dept E&P Sci arvidson@wunder.wustl.edu PDS/NMSU R. Beebe......Dept. Astronomy rbeebe@nmsu.edu L. Huber......Dept. Astronomy lhuber@nmsu.edu Stanford University R. Simpson.........Durand 232 rsimpson@magellan.stanford.edu L. Tyler...........Durand 232 len@nova.stanford.edu D.P. Hinson..........Durand 232 hinson@nimbus.stanford.edu J.D. Twicken.........Durand 232 joe@neptune.stanford.edu Jet Propulsion Laboratory J.W. Armstrong.......MS 238-725 john@oberon.jpl.nasa.gov S.W. Asmar...........MS 161-260 sami_w_asmar@jpl.nasa.gov P. Priest..........MS 264-325 trish@qmail.jpl.nasa.gov W.L. Sjogren.........MS 301-150 wls@kamel.jpl.nasa.gov R. Springer........MS 264-214 richard.j.springer@jpl.nasa.gov R. Woo.............MS 238-725 richard@oberon.jpl.nasa.gov Goddard Space Flight Center D.E. Smith.............Code 920 dsmith@tharsis.gsfc.nasa.gov F. Lemoine...........Code 926 flemoine@olympus.gsfc.nasa.gov Centre Nationales d'Etudes Spatiales G. Balmino...............GRGS balmino@pontos.cnes.fr Contents Preface Document Change Log Items to be Determined Distribution Contents Acronyms and Abbreviations 1 Introduction 1.1 Overview 1.2 Scope 1.3 Applicable Documents 1.4 System Siting 1.4.1 Interface Location and Medium 1.4.2 Data Sources, Destinations, and Transfer Methods 1.4.3 Generation Method and Frequency 1.5 Assumptions and Constraints 1.5.1 Usage Constraints 1.5.2 Documentation Conventions 1.5.2.1 Data Format Descriptions 1.5.2.2 Limits of This Document 1.5.2.3 Typographic Conventions 1.5.3 Time Standards 2 Interface Characteristics 2.1 Hardware Characteristics and Limitations 2.1.1 Special Equipment and Device Interfaces 2.1.2 Special Set-Up Requirements 2.2 Volume and Size 2.3 Labeling and Identification 2.3.1 External Labels 2.3.2 Internal Labels 2.4 Interface Medium Characteristics 2.5 Backup and Duplicates 3 Structure and Organization Overview 3.1 Disc Organization 3.1.1 Root Directory 3.1.2 CALIB Directory 3.1.3 CATALOG Directory 3.1.4 DOCUMENT Directory 3.1.5 INDEX Directory 3.1.6 Data Directories 3.2 Formats 3.3 File Naming Conventions 3.4 PDS Labels 3.5 Generic File Types 3.5.1 Text Files 3.5.2 Tabular Files 3.5.3 Catalog files 4 Detailed Interface Specifications 4.1 Logical Root Files 4.1.1 AAREADME.TXT File 4.1.2 ERRATA.TXT File 4.1.3 VOLDESC.CAT File 4.2 Static Directories 4.2.1 CALIB Directory 4.2.1.1 CALINFO.TXT File 4.2.1.2 Calibration Files 4.2.1.2.1 NAIF SCET/SCLK Files (ydddeeeC.SCK file names) 4.2.1.2.2 NAIF Leapsecond Files (LSKydddC.TLS file names) 4.2.1.2.3 NAIF Planetary Constants Files (PCKydddC.TPC names) 4.2.1.2.4 Channel Conversion Language Files (CCLydddZ.ext names) 4.2.1.2.5 Channel Parameter Table Files (CPTydddZ.ext names) 4.2.1.2.6 Template Description Language Files (TDLydddZ.ext names) 4.2.1.2.7 Decommutation Map Files (DCZxxxxx.ext file names) 4.2.2 CATALOG Directory 4.2.2.1 CATINFO.TXT File 4.2.2.2 MISSION.CAT File 4.2.2.3 INSTHOST.CAT File 4.2.2.4 INST.CAT File 4.2.2.5 REF.CAT File 4.2.2.6 PERSON.CAT File 4.2.2.7 DATASET.CAT File 4.2.3 DOCUMENT Directory 4.2.3.1 DOCINFO.TXT File 4.2.3.2 GDF_SPK.TXT File 4.2.3.3 GDN_SPK.TXT File 4.2.3.4 MGSRSSIS.TXT File 4.2.3.5 OPTG_SIS.TXT File 4.2.3.6 TRK_2_18.TXT File 4.2.3.7 TRK_2_21.TXT File 4.2.3.8 TRK_2_23.TXT File 4.2.3.9 TRK_2_24.TXT File 4.2.3.10 TRK_2_25.TXT File 4.2.3.11 NAIF Toolkit Documentation 4.3 INDEX Directory 4.3.1 INDXINFO.TXT File 4.3.2 INDEX.LBL File 4.3.3 INDEX.TAB File 4.3.4 CUMINDEX.LBL File 4.3.5 CUMINDEX.TAB File 4.4 Data Directories 4.4.1 Antenna Gimbal Kernel Files (AGK Directory) 4.4.2 Angular Momentum Desaturation Files (AMD Directory) 4.4.3 Browse Files (BRO Directory) 4.4.4 DSN Keyword Files (DKF Directory) 4.4.5 Channelized Engineering Data (ECH Directory) 4.4.6 Engineering Channel Summary File (ECS Directory) 4.4.7 Engineering Channel Table files (ECT Directory) 4.4.8 Experimenters Notebook Files (ENB Directory) 4.4.9 Earth Orientation Parameter Files (EOP Directory) 4.4.10 Spacecraft Engineering Packet Data (EPK Directory) 4.4.11 Filtered Body Rate Files (FBR Directory) 4.4.12 GEODYN Final SPK Files (GDF Directory) 4.4.13 GEODYN Quick-Look SPK Files (GDN Directory) 4.4.14 Radio Science Team Daily Health Reports (HEA Directory) 4.4.15 Ionosphere Calibration Files (ION Directory) 4.4.16 Light Time Files (LIT Directory) 4.4.17 Channelized DSN Monitor Data (MCH Directory) 4.4.18 Monitor Channel Table files (MCT Directory) 4.4.19 Maneuver Implementation Files (MIF Directory) 4.4.20 Maneuver Performance Data Files (MPD Directory) 4.4.21 Maneuver Profile Files (MPF Directory) 4.4.22 DSN Monitor Packet Data (MPK Directory) 4.4.23 Orbit Data Files (ODF Directory) 4.4.24 Original Data Record Files (ODR Directory) 4.4.25 Orbit Number Files (ONF Directory) 4.4.26 Orbit Propagation and Timing Files (OPT Directory) 4.4.27 Solar Array Kernel Files (SAK directory) 4.4.28 Space Flight Operations Schedule Files (SFO Directory) 4.4.29 Sequence of Event Files (SOE Directory) 4.4.30 NAIF SPK Files (SPK Directory) 4.4.31 NAIF CK Files (TCK Directory) 4.4.32 Archival Tracking Data Files (TDF Directory) 4.4.33 Troposphere Calibration Files (TRO Directory) 4.4.34 UltraStable Oscillator Files (USO Directory) 4.4.35 DSN Weather Calibration Files (WEA Directory) 5 Support Staff and Cognizant Personnel Figures 3-1 MGS RS RDA Directory Structure 4-1-1 Example Label for MGS VRF-RDA TXT Files 4-1-3 Example VOLDESC.CAT File Tables 3-1-6 Data Directories for MGS RS RDA 4-1-3 DATA_SET_ID Values Acronyms and Abbreviations AGK Antenna Gimbal Kernel File AMD Angular Momentum Desaturation (file or directory) ASCII American Standard Code for Information Interchange ASP Antenna SPK file (or data type) ATDF Archival Tracking Data File BRO Browse data type and directory CCL Channel Conversion Language CD Compact Disc CK Camera Kernel (as in CK file) CPT Channel Parameter Table DCO Decommutation Object (file) DCS Decommutation Source (file) DKF DSN Keyword File DOS Disk Operating System DSN Deep Space Network ECH Channelized Engineering Data (file or directory) ECS Engineering Channel Summary File ECT Engineering Channel Table (file or directory) ENB Experimenters Notebook (file or directory) ENG Engineering EOP Earth Orientation Parameters file (or directory) EPK Engineering Packet data (file or directory) FBR Filtered Body Rates GDF GEODYN Final SPK (file or directory) GDN GEODYN Quick-Look SPK (file or directory) GLL Galileo HCK Hinge CK file (or data type) HEA Health ION Ionosphere Calibration File (or directory) ISO International Standards Organization JPL Jet Propulsion Laboratory K Degrees Kelvin kB Kilobytes LIT Light Time File (or directory) LSK Leap Seconds Kernel (file or directory) MB Megabytes MCH DSN Monitor Channelized data (file or directory) MCT Monitor Channel Table (file or directory) MGS Mars Global Surveyor MGSO Multimission Ground Support Organization MIF Maneuver Implementation File (or directory) MOLA Mars Orbiter Laser Altimeter MPD Maneuver Performance Data (file or directory) MPF Maneuver Profile File MPK DSN Monitor Packet data (file or directory) NAIF Navigation and Ancillary Information Facility NASA National Aeronautics and Space Administration NAV Navigation Subsystem/Team NERT Near Real-Time (as in NERT Cache) NMSU New Mexico State University NSSDC National Space Science Data Center ODF Orbit Data File ODR Original Data Record (file or directory) ODS Original Data Stream ONF Orbit Number File OPT OPTG (file or directory) OPTG Orbit Propagation and Timing Geometry (file) PCK Planetary Constants Kernel (file or directory) PDS Planetary Data System RDA Raw Data Archive ROM Read-Only Memory RS Radio Science RSST Radio Science Support Team RST Radio Science Team SAK Solar Array Kernel (file or directory) SCLK Spacecraft Clock SCET Spacecraft Event Time SCK SCLK/SCET Conversion File (or directory) SFO Space Flight Operations Schedule (file or directory) SFOC Space Flight Operations Center SIS Software Interface Specification SOE Sequence of Events (file of directory) SP Spacecraft/Planetary (as in SPK file) SPK Spacecraft Planet Kernel (file or directory) TBD To Be Determined TCK (SPICE) Attitude (camera) Kernel File (or directory) TDF Tracking Data File (same as ATDF; file or directory) TDL Template Definition Language TFK Text Frame Kernel file (or data type) TLS Leap Second file (or directory) TRO Troposphere Calibration Data (file or directory) TXT Text USO Ultra-Stable Oscillator (device, file, or directory) UTC Coordinated Universal Time WEA DSN Weather data (file or directory) WO Write Once 1 Introduction 1.1 Overview This Software Interface Specification (SIS) describes the format and content of the Mars Global Surveyor (MGS) Radio Science (RS) Raw Data Archive (RDA). The MGS RS RDA represents the complete archive of raw data from investigations conducted using the radio link between the Mars Global Surveyor spacecraft and stations of the NASA Deep Space Network (DSN). It includes several hundred Compact Disc (CD) Write Once (WO) volumes. The MGS RS RDA is a product of the MGS Radio Science Team (RST), in conjunction with the MGS Radio Science Support Team (RSST) and the NASA Planetary Data System (PDS). It is the deliverable raw data archive from the MGS Project radio science investigations to PDS. The MGS Mission is managed by the NASA Jet Propulsion Laboratory (JPL). 1.2 Scope The specifications in this document apply only to the MGS RS RDA. This document provides a detailed description of the interface, including data flow information and a definition of all data objects that flow across the interface. 1.3 Applicable Documents [1] ISO 9660-1988. Information Processing - Volume and File Structure on CD-ROM for Information Exchange, 15 April 1988. [2] Planetary Data System Standards Reference, JPL D-7669, part 2, 24 July 1995. [3] Planetary Science Data Dictionary, JPL D-7116, Rev. D, 15 July 1996. [4] Planetary Data System, Data Preparation Workbook, JPL Publication D-7669, Part 1, Version 3.1, 17 February 1995. [5] Mars Observer Interface DACE004, ATDF, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 1, 1991. [6] TRK-2-25, DSN Tracking System Interfaces: Archival Tracking Data File Interface, Document 820-13 Rev A, 1986. [7] Mars Global Surveyor Interface DACE004, ATDF, in Mars Global Surveyor Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specification, 542-409, Vol. 5, Part 1, 26 January 1996. [8] SFOC-NAV-TRK-2-25, MGSO Tracking System Interfaces: Archival Tracking Data File Interface, 31 July 1996. [9] Mars Observer Interface DACE005, ODF, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 1, 1991. [10] TRK-2-18, DSN Tracking System Interfaces: Orbit Data File Interface, Document 820-13, 15 August 1996. [11] Mars Global Surveyor Interface DACE005, ODF, in Mars Global Surveyor Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specification, 542-409, Vol. 5, Part 1, 26 January 1996. [12] SFOC-NAV-TRK-2-18, MGSO Tracking System Interfaces: Orbit Data File Interface, 15 August 1996. [13] Mars Observer Interface DACE006, Media Calibration Data File, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 1, 1991. [14] TRK-2-23, DSN Tracking System Interfaces: Media Calibration Data Interface, Document 820-13 Rev A, 1985. [15] Mars Global Surveyor Interface DACE007, Timing and Polar Motion, in Mars Global Surveyor Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specification, 542-409, Vol. 5, Part 1, 26 January 1996. [16] TRK-2-21, DSN Tracking System Interfaces: Earth Orientation Parameter Data Interface, Document 820-13 Rev A. [17] Mars Observer Interface DACE011, Raw DSN Monitor Blocks, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 1, 1991. [18] Mars Observer Interface DACE012, S/C Channelized ENG Data, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 1, 1991. [19] Mars Observer Interface DACE013, Channelized Monitor Data, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 1, 1991. [20] Mars Observer Interface DACE022, Meteorological Weather Data, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 1, 1991. [21] MGS Radio Science Team, ad hoc adaptation of "TRK-2-24, DSN Tracking System Interfaces: Weather Data Interface, Document 820-13 Rev A, 1986" to MGS, 10 March 1999. [22] Mars Observer Interface DACE040, S/C ENG Telemetry Packet Data Record, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 2, 1991. [23] Mars Observer Interface DACE046, Radio Science Open Loop Data, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 2, 1991. [24] RSC-11-11 DSN Radio Science System, Original Data Record (ODR) and Original Data Stream (ODS), Document 820-13 Rev A, 1992. [25] Mars Global Surveyor Interface EAE003, Angular Momentum Desaturation File, in Mars Global Surveyor Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specification, 542-409, Vol. 5, Part 1, 26 January 1996. [26] Mars Observer Interface EAE007, C-KERNEL (reconstructed), in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 3, 1991. [27] Mars Observer Interface EAE008, Maneuver Performance Data File, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 3, 1991. [28] Mars Observer Interface EAE014, Maneuver Implementation/Reconstruction File, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 3, 1991. [29] Mars Global Surveyor Interface EAE022, ENG Channel Parameter Table, in Mars Global Surveyor Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, 26 January 1996. [30] Mars Global Surveyor Interface EAE023, Channel Conversion Language (CCL), File, in Mars Global Surveyor Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, 26 January 1996. [31] Mars Global Surveyor Interface EAE025, Decom Map, in Mars Global Surveyor Mission Operations Specification, Vol. 5: Interfaces, Part 1: Software Interface Specification, 542-409, Vol. 5, Part 1, 26 January 1996. [32] Mars Observer Interface NAE002, Light Time File, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 3, 1991. [33] Mars Observer Interface NAE003, Orbit Propagation and Timing Geometry File, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 3, 1991. [34] Mars Observer Interface NAE007, Planetary Constants Kernel File (PcK), in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 3, 1991. [35] Mars Observer Interface NAE011, SP KERNEL, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 3, 1991. [36] Mars Global Surveyor Interface NAE016, Orbit Number File, in Mars Global Surveyor Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specification, 542-409, Vol. 5, Part 1, 26 January 1996. [37] Mars Observer Interface PSE002, Sequence of Events File, in Mars Observer Mission Operations Specification, Vol. 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 4, 1991. [38] Mars Observer Interface PSE003, Space Flight Operations Schedule File, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 4, 1991. [39] Mars Observer Interface PSE005, DSN Keyword File, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 4, 1991. [40] Mars Observer Interface NAE006, Maneuver Profile File, in Mars Observer Mission Operations Specification, Volume 5: Interfaces, Part 1: Software Interface Specifications, 642-315, Vol. 5, Part 1, Book 4, 1991. 1.4 System Siting 1.4.1 Interface Location and Medium The MGS RS RDA is a set of CD-WO volumes compiled by the MGS RST and RSST and delivered to the PDS. The CD-WO volumes conform to ISO 9660 standards [1]. 1.4.2 Data Sources, Destinations, and Transfer Methods The MGS RS RDA is a collection of products generated by various elements of the DSN, the MGS Project, the RSST, the RST, and others; it is delivered to the PDS for archive. The files are organized as close to chronologically as is possible given delivery schedules, then written to CD-WO volumes within each data set. Access to the MGS RS RDA is determined by PDS. 1.4.3 Generation Method and Frequency The MGS RS RDA is organized around three primary data types: Archival Tracking Data Files (ATDFs or TDFs, so-called closed loop or radio tracking data), Orbit Data Files (ODFs, a derivative of ATDFs), and Original Data Records (ODRs, or open loop data). ODRs are derived from the Original Data Stream (ODS, an ODR variation suitable for packet delivery over electronic lines). Data sets are defined according to MGS Mission phase boundaries and radio science activity periods. ATDFs, ODFs, and ODRs are organized chronologically, except where late receipt at Stanford precludes proper ordering; they are accompanied by ancillary files likely to be used during analysis or interpretation. The time covered by each CD-WO volume varies, depending on the types of radio science activity and sampling rates chosen for each data type. The total number of CD-WO volumes in the MGS RS RDA cannot be predicted in advance but is likely to be 400-500. MGS RS RDA volumes are produced, reviewed and delivered to PDS as data become available, are validated, and organized for archiving. Production occurs in several stages. As data are received at Stanford, they are given file names of the form XXXXXXXX.ext and PDS labels. They are then staged in a disk partition until sufficient volume has accumulated nearly to fill a CD-WO volume. Documentation files are added, index files generated, and minor formatting changes carried out to make the files consistent with PDS standards for archiving. Primary data are stored in directories TDF, ODF, and ODR, as appropriate. Secondary files are stored in directories AMD, SPK, etc. A few files which are infrequently modified (decommutation files, leapsecond files, etc.) are assigned to the CALIB directory. Documentation files are in the DOCUMENT directory. The table of contents for the CD-WO volume is placed in the INDEX directory. The CD is pre-mastered; after correction of errors, the final version is produced and distributed. Each MGS RS RDA volume is evaluated internally by the MGS RST/RSST and (to the extent that resources permit) by a representative of PDS, and by one of the MGS radio science investigators familiar with the data. 1.5 Assumptions and Constraints 1.5.1 Usage Constraints Access to MGS RS RDA volumes is determined by PDS. 1.5.2 Documentation Conventions 1.5.2.1 Data Format Descriptions Data are stored in fields of various sizes and formats ranging from single-bit flags to 96-bit integers, floating point numbers, and character strings. The formats vary widely among file types; users should consult the appropriate SIS for details (See Section 1.3). If a field is described as containing n bytes of ASCII character string data, this implies that the leftmost (lowest numbered) byte contains the first character, the next lowest byte contains the next character, and so forth. Character strings are written to CD-WO with lower numbered bytes preceding higher numbered bytes. 1.5.2.2 Limits of This Document This document applies only to MGS RS RDA volumes. As the MGS mission progresses, the document may be amended. The version stored on any CD volume should be correct for the accompanying data; the most recent CD should have the latest version of the document. 1.5.2.3 Typographic Conventions This document has been formatted for simple electronic file transfer and display. Line lengths are fixed at 80 ASCII characters, including line delimiters. The last two characters on each line are the carriage-return (ASCII 13) and the line-feed (ASCII 10). No special fonts or structures are included within the file. Constant width characters are assumed for display. Hard copy pagination at the rate of 58 lines per page is assumed. For page numbers consistent with those shown in the Table of Contents, breaks in page numbering immediately before "PREFACE" and immediately before "1. Introduction" will be required. 1.5.3 Time Standards Within MGS RS RDA files that follow PDS standards, times are expressed as a string of up to 24 ASCII characters YYYY-MM-DDThh:mm:ss[.fff][Z] where "-", "T", ":", and "." are fixed delimiters; "YYYY" is the year "19nn"; "MM" is a two-digit month of year; "DD" is a two-digit day of month; "T" separates the date and time segments of the string; "hh" is hour of day; "mm" is the minutes of hour (00-59); "ss" is the seconds of minute (00-59); and "fff" is milliseconds (000-999). The data type "TIME" is assigned to this format. The TIME may be optionally truncated to 19 characters by omitting the last four characters (".fff"). It is also permissible to substitute "YYYY-DDD" for "YYYY-MM-DD", where "DDD" is the day-of-year (001-366). The suffix "Z" may be appended to any time format to indicate explicitly that time is given in UTC. When only the date is required, the 10-character string YYYY-MM-DD may be substituted. The data type "DATE" is assigned to this format. Alternatively, the form "YYYY-DDD" may be substituted, where "DDD" is day-of-year. 2 Interface Characteristics 2.1 Hardware Characteristics and Limitations 2.1.1 Special Equipment and Device Interfaces The MGS RS RDA is distributed on CD-WO volumes which conform to ISO 9660 standards for CD-ROM [1]. Users of the volume must have access to systems which can read these media. 2.1.2 Special Set-Up Requirements None. 2.2 Volume and Size The physical volumes on which the MGS RS RDA resides contain a maximum of 650 megabytes (MB) of data. 2.3 Labeling and Identification 2.3.1 External Labels The physical CD-WO volume bears a label using the following format: ACRONYM_SEQUENCE;VERSION where ACRONYM = MORS SEQUENCE = 0Pnn where P is a one-digit number denoting mission phase 0 is Mars Observer Cruise 1 is MGS Cruise 2,3 is MGS Orbit Insertion (MOI) and Transition to Mapping Orbit (TMO) 4 is MGS Mapping nn is a two digit number indicating the order in which the CD-WO volumes were produced (starting from 01) VERSION = A single digit indicating the version number of the CD-WO volume. "1" is the original version. For example, MORS_0112;5 is the fifth version of the twelfth CD-WO volume from the Mars Global Surveyor Cruise Phase. 2.3.2 Internal Labels The contents of the MGS RS RDA volumes will be labeled in accordance with PDS standards. Labeling is described further in subsequent sections. 2.4 Interface Medium Characteristics Each CD-WO volume conforms to ISO 9660 standards [1]. The quantity of data stored is no more than 650 MB per disc. 2.5 Backup and Duplicates The entire contents of each MGS RS RDA volume will be backed up to 8-mm tape, which will be retained by the RST. Six copies of each CD-WO volume will be created. Two copies will be delivered to PDS Central Node (one of which will be forwarded to NSSDC upon completion of peer review), one each will be delivered to the PDS Geoscience and Atmospheres Nodes, one will be delivered to the MGS Radio Science Support Team at JPL, and one copy will be retained by the RST at Stanford. 3 Structure and Organization Overview 3.1 Disc Organization Each MGS RS RDA volume contains one or more directories for primary data (TDF, ODF, and ODS), a CALIB directory, a CATALOG directory, a DOCUMENT directory, and an INDEX directory. Special directories for specific ancillary file types will be defined when those are available (Figure 3-1). |================================================================| | | | Figure 3-1 MGS RS RDA Directory Structure | | | |================================================================| | | | root | | | | | |- AAREADME.TXT | | |- ERRATA.TXT | | |- VOLDESC.CAT | | | | | |- [CALIB] | | | | | | | |- CALINFO.TXT | | | `- ... | | | | | |- [CATALOG] | | | | | | | |---------------------------------------- | | | |- CATINFO.TXT |- INSTHOST.CAT |- REF.CAT | | | `- MISSION.CAT `- INST.CAT |- PERSON.CAT | | | `- DATASET.CAT | | |- [DOCUMENT] | | | | | | | |---------------------------------------- | | | |- DOCINFO.TXT |- TK_DESCR.TXT |- GDF_SPK.TXT | | | |- MGSRSSIS.TXT |- TK_FTP.TXT |- GDN_SPK.TXT | | | `- ... `- TK_INSTL.TXT `- ... | | | | | |- [INDEX] | | | | | | | |---------------------------------------- | | | |- INDXINFO.TXT |- INDEX.LBL |- CUMINDEX.LBL | | | |- INDEX.TAB |- CUMINDEX.TAB | | | | | |----------------------------------- | | |- [AGK] |- [EPK] |- [MPD] |- [SPK] | | |- [AMD] |- [FBR] |- [MPF] |- [TCK] | | |- [BRO] |- [GDF] |- [MPK] |- [TDF] | | |- [DKF] |- [GDN] |- [ODF] |- [TRO] | | |- [ECH] |- [HEA] |- [ODR] |- [USO] | | |- [ECS] |- [ION] |- [ONF] |- [WEA] | | |- [ECT] |- [LIT] |- [OPT] |- nnnnnnnn.LBL | | |- [ENB] |- [MCH] |- [SAK] |- nnnnnnnn.WEA | | `- [EOP] |- [MCT] |- [SFO] `- ... | | `- [MIF] `- [SOE] data directories | |================================================================| 3.1.1 Root Directory The root directory contains the following files: AAREADME.TXT terse description of volume contents [2] ERRATA.TXT overview of anomalies and errors [2] VOLDESC.CAT volume object definition [2] 3.1.2 CALIB Directory The CALIB directory contains decommutation files, files for converting and displaying data, leapsecond files, planetary constant files, antenna description files, and files which give calibrations for the radio science "instrument." Each of these files will be accompanied by a detached PDS label. Also in this directory will be the file CALINFO.TXT which is a text description of the directory contents [2]. 3.1.3 CATALOG Directory The CATALOG directory contains a CATINFO.TXT file which describes the contents of the directory. The CATALOG directory also contains the following files: MISSION.CAT PDS data set catalog object for mission [2] INSTHOST.CAT PDS data set catalog object for instrument host [2] INST.CAT PDS data set catalog object for instrument [2] DATASET.CAT PDS data set catalog object for the data set [2] REF.CAT PDS data set catalog object for references [2] PERSON.CAT PDS data set catalog object for personnel [2] Because the schedule for composing *.CAT files trails generation of CD-WO volumes, early volumes may be missing one or more of these files. Also, because the content of some files -- especially MISSION.CAT and DATASET.CAT -- evolves during the mission, users should refer to the latest CD-WO volume for the most up-to-date version of the files. 3.1.4 DOCUMENT Directory The DOCUMENT directory contains the following files. DOCINFO.TXT text description of the directory contents [2] MGSRSSIS.TXT this SIS document TK_DESCR.TXT Description of NAIF software TK_FTP.TXT Access information for NAIF software TK_INSTL.TXT Installation instructions for NAIF software The DOCUMENT directory will also contain SIS documents describing individual data product types when those are available in electronic form. Because some product formats change during the course of the mission, the user should refer to the documents accompanying the data files being used. The last volume in a data set (e.g., MORS_0156 for MGS Cruise data) may contain other documentation files useful in understanding the data. These will be listed in DOCINFO.TXT and will generally be files that were compiled before the final version of the last volume was cut. Such files will be completely described by their attached or detached PDS labels. |============================================================================| | | | Table 3-1-6 Data Directories for MGS RS RDA | | | |============================================================================| |Directory| File Type | SIS | | Name | | | |---------+----------------------------------------+-------------------------| | AGK |Antenna Gimbal Kernel | self documenting label | | AMD |Angular Momentum Desaturation | [25] | | BRO |Browse Directory (PostScript plot files)| self documenting label | | DKF |DSN Keywords | [39] | | ECH |Engineering Channelized Data | [18] | | ECS |Engineering Channel Summary | self documenting label | | ECT |Engineering Channel Table | self documenting label | | ENB |Experimenters Notebook | self documenting text | | EOP |Earth Orientation Parameters | [15-16] | | EPK |Engineering Packet | [22] | | FBR |Filtered Body Rates | self documenting label | | GDF |GEODYN Final SPK | [35] | | GDN |GEODYN Quick-Look SPK | [35] | | HEA |RS Daily Health Reports | self documenting label | | ION |Ionosphere Calibration | [13-14] | | LIT |Light Time | [32] | | MCH |Monitor Channelized Data | [19] | | MCT |Monitor Channel Table | self documenting label | | MIF |Maneuver Implementation | [28] | | MPD |Maneuver Performance | [27] | | MPF |Maneuver Profile | [40] | | MPK |Monitor Packet Data | [17] | | ODF |Orbit Data File |[9-10] before 1997-04-15 | | | | [11-12] from 1997-04-15 | | ODR |Original Data Record | [23-24] | | ONF |Orbit Number File | [36] | | OPT |Orbit Propagation and Timing | [33] | | SAK |Solar Array Kernel File | [26] | | SFO |Space Flight Operations Schedule | [38] | | SOE |Sequence of Events | [37] | | SPK |SPK File (ephemerides) (SPICE) | [35] | | TCK |CK File (attitude) (SPICE) | [26] | | TDF |Tracking Data File | [5-6] before 1997-04-15 | | | | [7-8] from 1997-04-15 | | TRO |Troposphere Calibration | [13-14] | | USO |UltraStable Oscillator File | self documenting label | | WEA |Weather (DSN) | [20-21] | |============================================================================| 3.1.5 INDEX Directory The INDEX directory contains the following files: INDXINFO.TXT text description of the directory contents [2] INDEX.LBL PDS label for the volume index (INDEX.TAB); identifies the volume index and describes structure of the index table [2] INDEX.TAB volume index in tabular form [2] CUMINDEX.LBL PDS label for the cumulative volume index (CUMINDEX.TAB); identifies the cumulative volume index and describes structure of the cumulative index table [2] CUMINDEX.TAB cumulative volume index in tabular form [2] 3.1.6 Data Directories Each MGS RS RDA volume contains one or more data directories. Table 3-1-6 lists Directory names and file types. 3.2 Formats Each CD-WO conforms to the ISO 9660 level 1 Interchange Standard CD-WO format [1], which is compatible with common computer systems including MS-DOS, Macintosh, SunOS, and VMS. Data that comprise MGS RS RDA volumes are formatted in accordance with Planetary Data System specifications [2-4]. 3.3 File Naming Conventions In this document and on the discs themselves, file and directory names are in upper case characters. This ensures compatibility with operating systems in which these names are case insensitive (e.g., VMS and DOS) and operating systems in which names are automatically translated into one case or the other (e.g., UNIX and MacOS). Within disc directories the characters ";1" are appended to all file names. VMS excepted, most operating systems will hide these suffixes from users. File names are of the form XXXXXXXX.ext were XXXXXXXX is up to eight digits, upper case letters, or the underscore and ext is up to three upper case letters. The period is required in file names. Directory names are of the form XXXXXXXX where XXXXXXXX is as defined above. 3.4 PDS Labels All files contained on MGS RS RDA volumes are accompanied by PDS labels [2-4]. The label can either be prepended to the associated primary file or "detached", in which case the label becomes a file in its own right with the same name as the primary except for the suffix ".LBL". Detached label files are located in the same directory as the primary file. PDS labels, whether prepended to or detached from their primary file provide descriptive information about the associated file. The PDS label is an object-oriented structure consisting of sets of "keyword=value" declarations. The object to which the label refers (e.g. IMAGE, TABLE, etc.) is denoted by a statement of the form: ^object = location in which the carat character (^, also called a pointer in this context) indicates where to find the object. In a prepended label, the location is an integer representing the starting record or byte number of the object, where counting starts from record or byte number 1. In a detached label, the location denotes the name of the file containing the object, along with the starting record or byte number if there is more than one object. For example: ^HEADER = ("F01.IMG",1) ^IMAGE = ("F01.IMG",1025 ) indicates that the IMAGE object begins at byte 1025 of the file F01.IMG, in the same directory as the detached label file. Below is a list of the possible formats for the ^object definition. ^object = n ^object = n ^object = "filename.ext" ^object = ("filename.ext",n) ^object = ("filename.ext",n) where n is the starting record or byte number of the object, counting from the beginning of the file (record 1 or byte 1), indicates that the number given is in units of bytes; default is RECORDS filename is the (up to) 8 character, alphanumeric upper-case file name, ext is the 3 character upper-case file extension, All detached labels have record lengths of 80 bytes. Each record ends with a carriage return character (ASCII 13) in the next-to-last byte and a line feed character (ASCII 10) in the last byte. 3.5 Generic File Types 3.5.1 Text Files Text files (.TXT suffix) may exist in any directory. These are ASCII files with attached PDS labels which employ the TEXT object. All records in text files have 80-bytes, with a carriage return character (ASCII 13) in the next-to-last byte and a line feed character (ASCII 10) in the last byte. 3.5.2 Tabular Files Tabular files (.TAB suffix) exist in the INDEX directory and may be present in the other directories. All tabular files are filled with ASCII characters. Some are formatted for direct reading into database management systems; they consist of data "fields" separated by commas. Character fields are also enclosed in double quotation marks (") and are padded with spaces to keep quotation marks in the same columns of successive records. Character fields are left justified, and numeric fields are right justified. The "start byte" and "bytes" values listed in the labels do not include the commas between fields or the quotation marks surrounding character fields. The records in tabular files have fixed length, and the last two bytes of each record contain the ASCII carriage return and line feed characters. This allows a table to be treated as a fixed length record file on computers that support this file type and as a text file with embedded line delimiters on those that do not. All tabular files are accompanied by descriptive detached PDS labels. The PDS label has the same name as the data file it describes, except for the extension which is .LBL. For example, the file INDEX.TAB is accompanied by the detached label file INDEX.LBL in the INDEX directory. 3.5.3 Catalog files Catalog files (suffix .CAT) exist in the root and CATALOG directories. They are formatted in an object-oriented structure consisting of sets of "keyword=value" declarations. VOLDESC.CAT provides an overview of the contents of the volume. The files in the CATALOG directory provide a top-level understanding of the mission, the spacecraft, the ground system, and the data set [2]. 4 Detailed Interface Specifications 4.1 Logical Root Files 4.1.1 AAREADME.TXT File The AAREADME.TXT file contains terse volume content and format information. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. |================================================================| | | | Figure 4-1-1 Example Label for MGS RS RDA TXT Files | | | |================================================================| | | | PDS_VERSION_ID = PDS3 | | RECORD_TYPE = FIXED_LENGTH | | RECORD_BYTES = 80 | | OBJECT = TEXT | | PUBLICATION_DATE = 1994-01-25 | | NOTE = "Pre-launch description of science | | investigations, instruments, and | | experimental methods planned by | | the Galileo Radio Science Team." | | END_OBJECT = TEXT | |================================================================| Labeling requirements applicable to Figure 4-1-1 are described in [2]; keywords are defined in [3]. For this application, the only keywords that change are PUBLICATION_DATE the date in YYYY-MM-DD format on which the document was published or released (see Section 1.5.3). NOTE a brief description of the document, including a title if available. 4.1.2 ERRATA.TXT File ERRATA.TXT contains a cumulative listing of comments and updates concerning the CD-WO volumes in the data set as of the publication date. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. 4.1.3 VOLDESC.CAT File VOLDESC.CAT contains a description of the contents of the logical volume in a PDS format readable by both humans and computers. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage- return (ASCII 13) line-feed (ASCII 10) pair. An example VOLDESC.CAT file is shown in Figure 4-1-3. Keywords are defined below. |============================================================================| | | | Figure 4-1-3 Example VOLDESC.CAT File | | | |============================================================================| |PDS_VERSION_ID = PDS3 | |RECORD_TYPE = FIXED_LENGTH | |RECORD_BYTES = 80 | |OBJECT = VOLUME | | VOLUME_SERIES_NAME = "MISSION TO MARS" | | VOLUME_SET_NAME = "MARS GLOBAL SURVEYOR: RADIO SCIENCE DATA" | | VOLUME_SET_ID = USA_NASA_JPL_MORS_0xxx | | VOLUMES = "UNK" | | MEDIUM_TYPE = "CD-WO" | | VOLUME_FORMAT = "ISO-9660" | | VOLUME_NAME = "RAW DATA: NOVEMBER-DECEMBER 1996" | | VOLUME_ID = MORS_0101 | | VOLUME_VERSION_ID = "VERSION 1" | | PUBLICATION_DATE = 1997-01-31 | | DATA_SET_ID = "MGS-M-RSS-1-CRU-V1.0" | | DESCRIPTION = "This volume contains MGS raw radio science | | data and ancillary files from November and | | December 1996. Included are the MGS Launch, | | insertion into an Earth-Mars trajectory, and | | early Cruise tests." | | OBJECT = DATA_PRODUCER | | INSTITUTION_NAME = "STANFORD UNIVERSITY" | | FACILITY_NAME = "MGS RS REMOTE MISSION SUPPORT AREA" | | FULL_NAME = "RICHARD A. SIMPSON" | | ADDRESS_TEXT = "ELECTRICAL ENGINEERING (STARLAB) | | STANFORD UNIVERSITY | | STANFORD, CA 94305-9515 | | END_OBJECT = DATA_PRODUCER | | OBJECT = CATALOG | | ^MISSION_CATALOG = "MISSION.CAT" | | ^INSTRUMENT_HOST_CATALOG = "INSTHOST.CAT" | | ^INSTRUMENT_CATALOG = "INST.CAT" | | ^REFERENCE_CATALOG = "REF.CAT" | | ^PERSONNEL_CATALOG = "PERSON.CAT" | | ^DATA_SET_CATALOG = "DATASET.CAT" | | END_OBJECT = CATALOG | |END_OBJECT = VOLUME | |END | |============================================================================| Keywords in the VOLDESC.CAT file are defined as follows. Where standard values have been assigned, those are indicated. PDS_VERSION_ID The version of PDS standards to which this volume adheres; set to "PDS3". RECORD_TYPE The record format of the file; set to "FIXED_LENGTH". RECORD_BYTES The number of bytes in each record; set to "80". VOLUME_SERIES_NAME The formal name that describes a broad categorization of data products; set to "MISSION TO MARS". VOLUME_SET_NAME The formal name describing one or more volumes containing a single data set or a collection of related data sets. Acceptable values include: "MARS GLOBAL SURVEYOR: RADIO SCIENCE DATA" VOLUME_SET_ID Identification of a data volume or a set of archival data volumes (see also VOLUME_ID below); set to: "USA_NASA_JPL_MORS_0xxx" VOLUMES The number of physical volumes in a volume set; set to "UNK" because the total number of volumes is not known in advance. MEDIUM_TYPE Identifies the physical storage medium; set to "CD-WO". VOLUME_FORMAT Identifies the logical format used in writing the data volume; set to "ISO-9660". VOLUME_NAME The formal name of the individual volume; a more specific identification than VOLUME_SET_NAME. Acceptable values include: "RAW DATA: NOVEMBER-DECEMBER 1996" VOLUME_ID A unique identifier for the volume; the last two components of the VOLUME_SET_ID, with place- holders filled in (see also Section 2.3.1). VOLUME_VERSION_ID The version of the data volume, starting with "1" for original versions and incrementing by 1 for each subsequent version. PUBLICATION_DATE The date in YYYY-MM-DD format on which the volume was published or released (see Section 1.5.3). DATA_SET_ID A unique alphanumeric identifier for the data set. Acceptable values are listed in Table 4-1-3. DESCRIPTION A brief text description of the contents of the volume. INSTITUTION_NAME The name of the institution under which this volume was produced; set to "STANFORD UNIVERSITY". FACILITY_NAME The name of the department, laboratory, or under which the volume was produced; set to "MGS RS REMOTE MISSION SUPPORT AREA". |============================================================================| | | | Table 4-1-3 DATA_SET_ID Values | | | |============================================================================| | DATA_SET_ID |VOLUME_ID| Data Set Description | |---------------------------+---------+--------------------------------------| |MGS-M-RSS-1-CRU-V1.0 |MORS_01xx|Raw Radio Science and other data from | | | | Launch to beginning of Mars Orbit | | | | Insertion (November 1996 to | | | | approximately 2 September 1997). | |---------------------------+---------+--------------------------------------| |MGS-M-RSS-1-MOI-V1.0 |MORS_02xx|Raw Radio Science and other data | | |MORS_03xx| during Mars Orbit Insertion | | | | (approximately 2 Sept 1997 through | | | | 8 March 1999). | |---------------------------+---------+--------------------------------------| |MGS-M-RSS-1-MAP-V1.0 |MORS_04xx|Raw Radio Science and other data | | |MORS_05xx| during the Mars Global Surveyor | | | | Mapping Phase Wave (approximately | | | | 9 March 1999 to 31 January 2001) | |---------------------------+---------+--------------------------------------| |MGS-M-RSS-1-REL-V1.0 |MORS_06xx|Raw Radio Science and other data | | | | during the Mars Global Surveyor | | | | Relay Phase (after approximately | | | | 1 February 2001). | |============================================================================| FULL_NAME The name of the individual or organization responsible for producing this volume; set to "RICHARD A. SIMPSON". ADDRESS_TEXT Mailing address for the individual or organization responsible for producing this volume; set to: "ELECTRICAL ENGINEERING (STARLAB) STANFORD UNIVERSITY STANFORD, CA 94305-9515." ^MISSION_CATALOG File name in the CATALOG directory under which the PDS streamlined mission catalog file is stored; set to "MISSION.CAT". ^INSTRUMENT_HOST_CATALOG File name in the CATALOG directory under which the PDS streamlined instrument host catalog file is stored; set to "INSTHOST.CAT". ^INSTRUMENT_CATALOG File name in the CATALOG directory under which the PDS streamlined instrument catalog file is stored; set to "INST.CAT". ^REFERENCE_CATALOG File name in the CATALOG directory under which the PDS streamlined reference catalog file is stored; set to "REF.CAT". ^PERSONNEL_CATALOG File name in the CATALOG directory under which the PDS streamlined personnel catalog file is stored; set to "PERSON.CAT". ^DATA_SET_CATALOG File name in the CATALOG directory under which the PDS streamlined data set catalog file is stored; set to "DATASET.CAT". 4.2 Static Directories Static directories are those which do not change (or change very little) from one volume to another. Keywords are defined in [3]. 4.2.1 CALIB Directory The CALIB directory contains files used in parsing or calibrating the data. Included are decommutation and decalibration files, files useful in data display, files of constants, and files which characterize ground or spacecraft systems. 4.2.1.1 CALINFO.TXT File The CALINFO.TXT file contains a description of the contents of the CALIB directory. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. 4.2.1.2 Calibration Files Calibration files which may be included in each CD-WO volume are described in the following sections. If a calibration file is not needed for the data on the CD-WO volume, it will not be included in the CALIB directory. For example, decommutation maps will not be included if the data on the CD have already been decommutated. Each has a file name of the form XXXXXXXX.ext where "XXXXXXXX" is a combination of eight digits and/or upper case letters and "ext" is a three character extension, also drawn from digits and upper case letters. Each file is accompanied by a PDS label with the name XXXXXXXX.LBL. All PDS labels have 80 characters per line with the last two characters being the ASCII carriage-return and line-feed. Except were noted, the labels are PDS minimal labels. 4.2.1.2.1 NAIF SCET/SCLK Files (ydddeeeC.SCK file names) Until early 1999 NAIF SCET/SCLK Files had names of the form ydddeeeC.SCK where ydddeee denotes the time interval covered by the file and C is an upper case letter denoting the order when there is more than one file with the same ydddeee. "y" is the least significant digit of the year on which the file starts (typically "6"), "ddd" is the day-of-year when the file starts, and "eee" is the day-of-year when the file ends (not necessarily in the same year as "ddd". The sequence character starts with "A" for the first ydddeee, increments to "B" for the next, etc. Starting in early 1999 the naming was changed to TSCnnnnn.SCK, where nnnnn is the sequence number assigned by the data producer. For example, MGS_SCLKSCET.00023.tsc became TSC00023.SCK in the RDA. This change removed the ambiguity in year associated with eee in the previous system. NAIF SCET/SCLK Files are ASCII files with variable record lengths. Each record has been delimited by an ASCII carriage-return line-feed pair. On some systems it may be necessary to convert this to the default record delimiter before using the file. NAIF software and files are described elsewhere. The file TK_FTP.TXT in the DOCUMENT directory provides additional information. 4.2.1.2.2 NAIF Leapsecond Files (LSKydddC.TLS file names) NAIF Leapsecond Files have names of the form LSKydddC.TLS where yddd denotes the year and day when the file was created and C is an upper case letter denoting the version when there is more than one file with the same yddd. "y" is the least significant digit of the year and "ddd" is the day-of-year when the file was created. The sequence character starts with "A" for the first version, increments to "B" for the second, etc. NAIF Leapsecond Files are ASCII files with variable record lengths. Each record has been delimited by an ASCII carriage-return line-feed pair. On some systems it may be necessary to convert this to the default record delimiter before using the file. NAIF software and files are described elsewhere. The file TK_FTP.TXT in the DOCUMENT directory provides additional information. 4.2.1.2.3 NAIF Planetary Constants Files (PCKydddC.TPC file names) NAIF Planetary Constants Files have names of the form PCKydddC.TPC where yddd denotes the year and day when the file was created and C is an upper case letter denoting the version when there is more than one file with the same yddd. "y" is the least significant digit of the year and "ddd" is the day-of-year when the file was created. The sequence character starts with "A" for the first version, increments to "B" for the second, etc. NAIF Planetary Constants Files are ASCII files with variable record lengths. Each record has been delimited by an ASCII carriage-return line-feed pair. On some systems it may be necessary to convert this to the default record delimiter before using the file. NAIF software and files are described elsewhere. The file TK_FTP.TXT in the DOCUMENT directory provides additional information. See also [34]. 4.2.1.2.4 Antenna SPK Files (HGAnnnnn.ASP file names) Antenna SPK (ASP) files contain the locations of low-gain antennas in the spacecraft coordinate frame and information on constant offsets (e.g., boom lengths) for the high-gain antenna. ASP files have names of the form HGAnnnnn.ASP where nnnnn is a sequence number indicating the order in which ASP files were created. ASP files are ASCII files in NAIF transfer format with variable record lengths. Each record has been delimited by an ASCII carriage-return line-feed pair. On some systems it may be necessary to convert this to the default record delimiter before using the file. File HGA00011.ASP was created shortly after deployment of the high-gain antenna; it was expected to be valid for the entire mission. NAIF software and files are described elsewhere. The files TK_FTP.TXT and ANTFILES.TXT in the DOCUMENT directory provide additional information. See also [34]. 4.2.1.2.5 Hinge CK Files (HINGEnnn.HCK file names) Hinge CK (HCK) files contain angles for the deployed high-gain antenna boom. HCK files have names of the form HINGEnnn.HCK where nnn is a sequence number indicating the order in which HCK files were created. HCK files are ASCII files in NAIF transfer format with variable record lengths. Each record has been delimited by an ASCII carriage-return line-feed pair. On some systems it may be necessary to convert this to the default record delimiter before using the file. File HINGE001.HCK was created shortly after deployment of the high-gain antenna; it was expected to be valid for the remainder of the mission. Before deployment, the HGA was fixed to the +X side of the spacecraft body. NAIF software and files are described elsewhere. The files TK_FTP.TXT and ANTFILES.TXT in the DOCUMENT directory provide additional information. See also [34]. 4.2.1.2.6 Text Frame Kernel Files (HGAnnnnn.TFK file names) Text Frame Kernel (TFK) files contain information on coordinate frame definitions for translating between the spacecraft frame and the frame of the high-gain antenna. TFK files have names of the form HGAnnnnn.TFK where nnnnn is a sequence number indicating the order in which TFK files were created. TFK files are ASCII files with variable record lengths. Each record has been delimited by an ASCII carriage-return line-feed pair. On some systems it may be necessary to convert this to the default record delimiter before using the file. File HGA00001.TFK was created shortly after deployment of the high-gain antenna; it was expected to be valid for the remainder of the mission. NAIF software and files are described elsewhere. The files TK_FTP.TXT and ANTFILES.TXT in the DOCUMENT directory provide additional information. See also [34]. 4.2.1.2.7 Channel Conversion Language Files (CCLydddZ.ext file names) Channel Conversion Language (CCL) Files have names of the form CCLydddZ.ext where "y" is the least significant digit of the year and "ddd" is the day-of-year on which the file was created, respectively. The character "Z" denotes the version of the CCL file -- "S" for source, "B" for binary, and "D" for dependency. The extension "ext" is "SRC" for source files and "BIN" for the other two types. CCL source files have ASCII carriage-return line-feed pairs at the end of each line; these may need to be converted to the local default line delimiter on some machines before the file can be used. CCL files are described by the Mars Global Surveyor SIS EAE023 [30]. 4.2.1.2.8 Channel Parameter Table Files (CPTydddZ.ext file names) Channel Parameter Table (CPT) Files have names of the form CPTydddZ.ext where "y" is the least significant digit of the year and "ddd" is the day-of-year on which the file was created, respectively. The character "Z" denotes the version of the CPT file -- "S" for source and "B" for binary. The extension "ext" is "SRC" for source files and "BIN" for binary. CPT source files have ASCII carriage-return line-feed pairs at the end of each line; these may need to be converted to the local default line delimiter on some machines before the file can be used. CPT files are described by the Mars Global Surveyor SIS EAE022 [29]. 4.2.1.2.9 Template Description Language Files (TDLydddZ.ext file names) Template Description Language (TDL) Files have names of the form TDLydddZ.ext where "y" is the least significant digit of the year and "ddd" is the day-of-year on which the file was created, respectively. The character "Z" denotes the version of the TDL file -- "S" for source and "B" for binary. The extension "ext" is "SRC" for source files and "BIN" for binary. TDL source files have ASCII carriage-return line-feed pairs at the end of each line; these may need to be converted to the local default line delimiter on some machines before the file can be used. TDL files are described by the Mars Global Surveyor SIS EAE023 [30]. 4.2.1.2.10 Decommutation Map Files (DCZxxxxx.ext file names) Decommutation Map Files have names of the form DCZxxxxx.ext where "Z" denotes the version of the file -- "S" for source and "O" for object (binary), and "xxxxx" indicates the type of data that may be decommutated. The extension "ext" is "SRC" for source files and "BIN" for object files. Decommutation Map source files have ASCII carriage-return line-feed pairs at the end of each line; these may need to be converted to the local default line delimiter on some machines before the file can be used. Decommutation Map Files are described by the Mars Global Surveyor SIS EAE025 [31]. 4.2.2 CATALOG Directory The CATALOG directory contains files used in cataloging the data, including files which provide high-level descriptions of the planetary mission, spacecraft, instrument, and data set. PDS "streamlined" formats are used [2]. 4.2.2.1 CATINFO.TXT File The CATINFO.TXT file contains a description of the contents of the CATALOG directory. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. 4.2.2.2 MISSION.CAT File The MISSION.CAT file contains a PDS high-level description and catalog information about the MGS mission and spacecraft [2]. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. 4.2.2.3 INSTHOST.CAT File The INSTHOST.CAT file contains a PDS high-level description and catalog information about the spacecraft and ground system [2]. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. 4.2.2.4 INST.CAT File The INST.CAT file contains a PDS high-level description and catalog information about the spacecraft and ground elements of the radio system [2]. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. 4.2.2.5 REF.CAT File The REF.CAT file contains a PDS high-level list and catalog information about references describing the mission, spacecraft, and radio system [2]. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. 4.2.2.6 PERSON.CAT File The PERSON.CAT file contains a PDS high-level list and catalog information about personnel involved in creating the logical volume [2]. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. 4.2.2.7 DATASET.CAT File The DATASET.CAT file contains a PDS high-level description and catalog information about the data set on this archive volume. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. 4.2.3 DOCUMENT Directory The DOCUMENT directory contains files which describe the data included in the MGS RS RDA volume. 4.2.3.1 DOCINFO.TXT File The DOCINFO.TXT file contains a description of the contents of this directory. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. 4.2.3.2. ANTFILES.TXT File The ANTFILES.TXT file contains brief descriptions of the AGK, ASP, HCK, and TFK file types and their use in reconstructing antenna location and orientation with respect to the spacecraft coordinate frame. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. 4.2.3.3 GDF_SPK.TXT File The GDF_SPK.TXT file contains a description of the GEODYN Final SPK files. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. 4.2.3.4 GDN_SPK.TXT File The GDN_SPK.TXT file contains a description of the GEODYN Quick-Look SPK files. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. 4.2.3.5 MGSRSSIS.TXT File The MGSRSSIS.TXT file is the MGS Radio Science Raw Data Archive Software Interface Specification (this document). This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. 4.2.3.6 OPTG_SIS.TXT File The OPTG_SIS.TXT file is the Software Interface Specification for the Orbit Propagation and Timing Geometry (OPTG) File. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage- return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. 4.2.3.7 TRK_2_18.TXT File The TRK_2_18.TXT file is the DSN Orbit Data File interface description. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. This file documents the structure and content of data files archived in the ODF directory of the MGS RS RDA volume. TRK_2_18.TXT is valid only for ODFs generated before 15 April 1997; for files generated after that date, the full PDS label accompanying the file provides comparable documentation. 4.2.3.8 TRK_2_21.TXT File The TRK_2_21.TXT file is the Earth Orientation Parameters (EOP) interface description. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. This file documents the structure and content of EOP Files archived in the EOP directory of the MGS RS RDA logical volume. For early volumes of the MGS RDA, this file was being updated and may not be included on some volumes. 4.2.3.9 TRK_2_23.TXT File The TRK_2_23.TXT file is the DSN Media Calibration File interface description. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. This file documents the structure and content of Ionosphere and Troposphere Media Calibration Files archived in the CALIB directory of the MGS RS RDA volume. 4.2.3.10 TRK_2_24.TXT File The TRK_2_24.TXT file is the DSN Weather Data File Interface description. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. This file documents the structure and content of DSN Weather Data Files archived in the WEA directory of the MGS RS RDA volume. This document was written by the MGS Radio Science Team; it is an ad hoc update of a DSN document issued in 1986 but now obsolete. 4.2.3.11 TRK_2_25.TXT File The TRK_2_25.TXT file is the DSN Archival Tracking Data File interface description. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. This file documents the structure and content of Archival Tracking Data Files stored in the TDF directory of the MGS RS RDA volume. This document describes only ATDFs generated before 15 April 1997; for files generated later, the full PDS label is sufficient documentation and this document is not included with the archival volume. 4.2.3.12 NAIF Toolkit Documentation TK_FTP.TXT is an explanation for obtaining NAIF Toolkit software and documentation from on-line servers; TK_DESCR.TXT and TK_INSTL.TXT describe the Toolkit and explain its installation, respectively. Each of these three files is an ASCII file with line lengths of 80 characters. Each line is terminated by a carriage return (ASCII 13) character in the next-to-last position and a line-feed (ASCII 10) character in the last position. 4.3 INDEX Directory 4.3.1 INDXINFO.TXT File The INDXINFO.TXT file contains a description of the contents of the INDEX directory. This is an ASCII file with record lengths of 80 bytes. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. 4.3.2 INDEX.LBL File INDEX.LBL is a detached label that completely describes INDEX.TAB. Each record in INDEX.LBL contains 80 bytes. Each record ends with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. 4.3.3 INDEX.TAB File INDEX.TAB is a table listing all MGS RS RDA data files included in this volume. It is an ASCII file with fixed-length records. Each record is delimited by a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The detailed format and content are described by INDEX.LBL. 4.3.4 CUMINDEX.LBL File CUMINDEX.LBL is a detached label that completely describes CUMINDEX.TAB. Each record in CUMINDEX.LBL contains 80 bytes. Each record ends with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. 4.3.5 CUMINDEX.TAB File CUMINDEX.TAB is a table listing all MGS RS RDA data files included in this volume. It is an ASCII file with fixed-length records. Each record is delimited by a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The detailed format and content are described by INDEX.LBL. 4.4 Data Directories Each MGS RS RDA volume has one or more data directories. The directory types are listed in Table 3-1-6. 4.4.1 Antenna Gimbal Kernel Files (AGK Directory) The AGK directory contains Antenna Gimbal Kernel (AGK) Files. Each AGK File has a name of the form ydddeeeZ.AGK where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee" in the data set. Z is "A" for the first file, "B" for the second, etc. Each AGK File is described by an accompanying minimal PDS label with the file name ydddeeeZ.LBL. The label file has 80-byte fixed-length records, the last two bytes in each line being occupied by an ASCII carriage-return line-feed pair. AGK files are ASCII files in NAIF transfer format with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 4.4.2 Angular Momentum Desaturation Files (AMD Directory) The AMD directory contains Angular Momentum Desaturation Files. These are files with names of the form ydddeeeC.AMD where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "C" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". C is "A" for the first file, "B" for the second, etc. Each AMD file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. AMD files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 4.4.3 Browse Files (BRO Directory) The BRO directory contains PDS DOCUMENT objects--PostScript plot files accompanied by a detached PDS label. These are four-panel single-page files containing summary results from quick-look processing of ODR files. File names have the form ydddhhmm.PSn where ydddhhmm is explained below (see section on ODR data) and n is the DSN channel or receiver number (usually set to "1") from which the data were obtained. The PostScript files comprise ASCII records of variable lengths. Each record is delimited by an ASCII carriage-return line-feed pair. On some systems, this pair of delimiters may have to be replaced with the local default delimiter before the file can be printed or displayed. Each BRO file is accompanied by a PDS label having file name ydddhhmm.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. 4.4.4 DSN Keyword Files (DKF Directory) The DKF directory contains DSN Keyword Files. These are files with names of the form ydddeeeC.DKF where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "C" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". C is "A" for the first file, "B" for the second, etc. Each DKF file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. DKF files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 4.4.5 Channelized Engineering Data (ECH Directory) The ECH directory contains Channelized Spacecraft Engineering Data Files and Channelized Summary Vector Files for Spacecraft Engineering Data. Channelized Spacecraft Engineering Data Files are files with names of the form ydddeeeZ.ECH where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". Z is "A" for the first file, "B" for the second, etc. Each Channelized Spacecraft Engineering Data file is accompanied by a PDS minimal label having file name ydddeeeZ.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. Channelized Spacecraft Engineering Data files are binary files created when MGS Project-provided software is used to decommutate Spacecraft Engineering Packet Data. More details on the content and format of Channelized Spacecraft Engineering Data Files can be found in MGS SIS DACE012. Channelized Summary Vector (CSV) files for Spacecraft Engineering Data contain extracts of ECH data in formats more readily ingested by user written software. CSV files derived from ECH data have names of the form CSVydddZ.ECH where "y", "ddd", and "Z" are as explained above. Each Channelized Summary Vector file for Spacecraft Engineering Data is an ASCII PDS TABLE object with fixed length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. Each CSV file derived from ECH data is completely described by an accompanying full PDS label with the file name CSVydddZ.LBL. The label file has fixed-length records of 80 bytes each, the last two being occupied by an ASCII carriage-return line-feed pair. 4.4.6 Engineering Channel Summary File (ECS Directory) The ECS directory contains one Engineering Channel Summary File. The Engineering Channel Summary File has a name of the form ydddeeeZ.ECS where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee" in the data set. Z is "A" for the first file, "B" for the second, etc. Each Engineering Channel Summary File is a PDS TABLE object with fixed length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. The content and format of each ECS file is completely described by an accompanying full PDS label with the file name ydddeeeZ.LBL. The label file has fixed-length records of 80 bytes each, the last two bytes in each line being occupied by an ASCII carriage-return line-feed pair. 4.4.7 Engineering Channel Table File (ECT Directory) The ECT directory contains one or more Engineering Channel Table Files. Each Engineering Channel Table File has a name of the form CCCydddZ.ECT where "CCC" denotes the quantity saved in the file, "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "CCCyddd" in the data set. Z is "A" for the first file, "B" for the second, etc. Each Engineering Channel Table File is a PDS TABLE object with fixed length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. The content and format of each ECT file is completely described by an accompanying full PDS label with the file name CCCydddZ.LBL. The label file has fixed-length records of 80 bytes each, the last two bytes in each line being occupied by an ASCII carriage-return line-feed pair. The first Engineering Channel Table File defined was for the MGS UltraStable Oscillator temperature -- engineering channel T-0315 -- for which "CCC" was set to "TUS". 4.4.8 Experimenters Notebook File (ENB Directory) The ENB directory contains one or more Experimenters Notebook files. Each file is a collection of electronic mail and other messages relating to MGS radio science activities on or about a single day. ENB files have names of the form ENByyddd.TXT where "yy" is the two-digit year and "ddd" is the three-digit day-of-year mentioned in the messages. ENB files have variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. Each ENB file includes an attached PDS label similar to the one shown in Figure 4-1-1. For ENB files RECORD_TYPE is set to STREAM and the RECORD_BYTES keyword-value pair is omitted. 4.4.9 Earth Orientation Parameter Files (EOP Directory) The EOP directory contains Earth Orientation Parameter Files. These are files with names of the form ydddeeeC.EOP where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "C" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". C is "A" for the first file, "B" for the second, etc. Each EOP file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. EOP files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 4.4.10 Spacecraft Engineering Packet Data (EPK Directory) The EPK directory contains Spacecraft Engineering Packet Data Files. Spacecraft Engineering Packet Data Files are files with names of the form ydddeeeZ.EPK where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". Z is "A" for the first file, "B" for the second, etc. Each Spacecraft Engineering Packet Data File is accompanied by a PDS minimal label having file name ydddeeeZ.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. Spacecraft Engineering Packet Data Files are binary files created through queries to the MGS Near-Real-Time (NERT) Cache. More details on the content and format of Spacecraft Engineering Packet data can be found in MGS SIS DACE040. 4.4.11 Filtered Body Rate Files (FBR Directory) The FBR directory contains Filtered Body Rate Files. Each FBR file has a name of the form ydddeeeZ.FBR where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee" in the data set. Z is "A" for the first file, "B" for the second, etc. Each Filtered Body Rate File is a PDS TABLE object with fixed length records. Each record is delimited by an ASCII carriage-return line-feed pair On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. The content and format of each FBR file are completely described by an accompanying full PDS label with the file name ydddeeeZ.LBL. The label file has fixed-length records of 80 bytes each, the last two bytes in each line being occupied by an ASCII carriage-return line-feed pair. 4.4.12 GEODYN Final SPK Files (GDF Directory) The GDF directory contains SPK Files in NAIF "transfer" format (see below). These are files with names of the form ydddeeeZ.GDF where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". Z is "A" for the first file, "B" for the second, etc. Each GDK file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. GDF files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. GDF files are "final" orbit solutions, provided by the MGS MOLA Precise Orbit Determination Team. The analysis program is GEODYN. Files are in formats compatible with the NAIF Toolkit Software (see below). 4.4.13 GEODYN Quick-Look SPK Files (GDN Directory) The GDN directory contains SPK Files in NAIF "transfer" format (see below). These are files with names of the form ydddeeeZ.GDN where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". Z is "A" for the first file, "B" for the second, etc. Each GDN file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. GDN files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. GDN files are "quick-look" orbit solutions, provided by the MGS MOLA Precise Orbit Determination Team. The analysis program is GEODYN. Files are in formats compatible with the NAIF Toolkit Software (see below). 4.4.14 Radio Science Team Daily Health Reports (HEA Directory) The HEA directory contains Daily Health Reports from the MGS Radio Science Team. Each Health Report has a file name of the form HEAydddZ.TXT where "y" is the least significant digit of the year in which the Health Report was generated, "ddd" is the day-of-year when the Health Report was generated, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee" in the data set. Z is "A" for the first file, "B" for the second, etc. Multiple files could result from revision or augmentation to an earlier report. Each Health Report is an ASCII file with variable length records. Each line is terminated with a carriage-return (ASCII 13) line-feed (ASCII 10) pair. The file has an attached PDS label of the form shown in Figure 4-1-1. Accompanying some Health Reports may be a PostScript file containing graphics information. Each file has a name of the form HEAydddZ.PSn where the first eight characters are identical to the first eight characters in the name of the Health Report file. The number "n" identifies the figure number, generally set to "1" since there is no way to label and index more than one figure per Health Report. The PostScript file comprises ASCII records of variable lengths. Each record is delimited by an ASCII carriage-return line-feed pair. On some systems, this pair of delimiters may have to be replaced with the local default delimiter before the file can be used. 4.4.15 Ionosphere Calibration Files (ION Directory) The ION directory contains Ionosphere (Media) Calibration Files. These are files with names of the form ydddeeeC.ION where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "C" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". C is "A" for the first file, "B" for the second, etc. Each ION file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. ION files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 4.4.16 Light Time Files (LIT Directory) The LIT directory contains Light Time Files. These are files with names of the form ydddeeeC.LIT where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "C" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". C is "A" for the first file, "B" for the second, etc. Each LIT file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. LIT files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 4.4.17 Channelized DSN Monitor Data (MCH Directory) The MCH directory contains Channelized DSN Monitor Data Files and Channelized Summary Vector Files for DSN Monitor Data. Channelized DSN Monitor Data Files are files with names of the form ydddeeeZ.MCH where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". Z is "A" for the first file, "B" for the second, etc. Each Channelized DSN Monitor Data File is accompanied by a PDS minimal label having file name ydddeeeZ.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. Channelized DSN Monitor Data files are binary files created when MGS Project-provided software is used to decommutate DSN Monitor Packet Data. More details on the content and format of Channelized DSN Monitor Data Files can be found in MGS SIS DACE013. Channelized Summary Vector (CSV) files for DSN Monitor Data contain extracts of MCH data in formats more readily ingested by user written software. CSV files derived from MCH data have names of the form CSVydddZ.MCH where "y", "ddd", and "Z" are as explained above. Each Channelized Summary Vector file for Spacecraft DSN Monitor Data is an ASCII PDS TABLE object with fixed length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. Each CSV file derived from MCH data is completely described by an accompanying full PDS label with the file name CSVydddZ.LBL. The label file has fixed-length records of 80 bytes each, the last two being occupied by an ASCII carriage-return line-feed pair. 4.4.18 Monitor Channel Table File (MCT Directory) The MCT directory contains one or more DSN Monitor Channel Table Files. Each Monitor Channel Table File has a name of the form CCCydddZ.MCT where "CCC" denotes the quantity saved in the file, "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "CCCyddd" in the data set. Z is "A" for the first file, "B" for the second, etc. Each Monitor Channel Table File is a PDS TABLE object with fixed length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. The content and format of each MCT file is completely described by an accompanying full PDS label with the file name CCCydddZ.LBL. The label file has fixed-length records of 80 bytes each, the last two bytes in each line being occupied by an ASCII carriage-return line-feed pair. 4.4.19 Maneuver Implementation Files (MIF Directory) The MIF directory contains Maneuver Implementation Files. These are files with names of the form ydddeeeC.MIF where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "C" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". C is "A" for the first file, "B" for the second, etc. Each MIF file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. MIF files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 4.4.20 Maneuver Performance Data Files (MPD Directory) The MPD directory contains Maneuver Performance Data Files. These are files with names of the form ydddeeeC.MPD where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "C" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". C is "A" for the first file, "B" for the second, etc. Each MPD file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. MPD files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 4.4.21 Maneuver Profile Files (MPF directory) The MPF directory contains Maneuver Profile Files. There are two types of Maneuver Profile Files. Files with names ending in .MPF are Maneuver Profile Files generated by the MGS Navigation Team (NAV). Files with names ending in .TAB are PDS TABLE objects and contain summary information for use with one or more NAV MPFs; they are generated by the MGS Radio Science Team at Stanford. NAV MPFs generated during the MGS Orbit Insertion phase were intended for multiple use during aerobraking. They have dummy values for maneuver execution times and velocity changes; those should be obtained from the corresponding .TAB file. NAV MPFs for Orbit Insertion have file names of the form InnnnddCC.MPF where "I" identifies the Insertion phase, "nnn" gives the argument of periapsis for the generic maneuver, "dd" indicates whether the aerobraking maneuver was intended to raise ("UP") or lower ("DN") periapsis, and "CC" allows for multiple versions of files having the same first six characters -- starting from "AA". Each NAV MPF is accompanied by a PDS minimal label having the same file name except for an .LBL extension. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. NAV MPFs are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. Stanford MPFs (.TAB suffix) contain maneuver execution times, velocity changes, and NAV MPF file names to be used to reconstruct maneuvers. Stanford MPFs have file names of the form MPFydddC.TAB where "y" is the least significant digit of the year marking the end of data in the file, "ddd" is the three-digit day-of-year for the (nominal) last entry in the file, "C" is a letter starting from "A" which allows for multiple files with identical characters in the first seven positions. Each Stanford MPF is accompanied by a full PDS label having the same file name except for an .LBL extension. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. Each Stanford MPF is an ASCII file with fixed-length records. Each record is delimited by an ASCII carriage-return line-feed pair. The format and content of each Stanford MPF is described completely by the accompanying label file. 4.4.22 DSN Monitor Packet Data (MPK Directory) The MPK directory contains DSN Monitor Packet Data Files. DSN Monitor Packet Data Files are files with names of the form ydddeeeZ.MPK where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". Z is "A" for the first file, "B" for the second, etc. Each DSN Monitor Packet Data File is accompanied by a PDS minimal label having file name ydddeeeZ.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. DSN Monitor Packet Data Files are binary files created through queries to the MGS Near-Real-Time (NERT) Cache. More details on the content and format of Spacecraft Engineering Packet data can be found in MGS SIS DACE011. 4.4.23 Orbit Data Files (ODF Directory) Orbit Data Files are files with names of the form ydddeeeZ.ODF where "y" is the least significant digit of the year, "ddd" is the three-digit day of year for start of data, "eee" is the three-digit day of year for end of data, and "Z" is a single character (starting from "A") that is used to distinguish among two or more ODFs with the same first 7 characters. Each Orbit Data File is accompanied by a full PDS label having file name ydddeeeZ.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. Each label completely describes the format and content of its corresponding ODF. 4.4.24 Original Data Record Files (ODR Directory) Original Data Record Files are files with names of the form ydddhhmm.ODR where "y" is the least significant digit of the year, "ddd" is the three-digit day of year for start of data, "hh" is the two-digit hour for start of data, and "mm" is the two-digit minute for start of data. In cases where two or three ODRs begin at the same time, the "mm" in the second (and third) will be modified as follows: If the less significant Then the less significant The less significant digit in "mm" is digit in the second file digit in the third file will be replaced by will be replaced by ----------------------- ------------------------- ----------------------- 0 A K 1 B L 2 C M 3 D N 4 E O 5 F P 6 G Q 7 H R 8 I S 9 J T Each Original Data Record File is accompanied by a full PDS label having file name ydddhhmm.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. Each label completely describes the format and content of its corresponding ODR. 4.4.25 Orbit Number Files (ONF Directory) The ONF directory contains Orbit Number Files. These are files with names of the form ydddeeeC.ONF where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "C" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". C is "A" for the first file, "B" for the second, etc. Each ONF file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. ONF files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 4.4.26 Orbit Propagation and Timing Files (OPT Directory) The OPT directory contains Orbit Propagation and Timing Files. These are files with names of the form ydddeeeC.OPT where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "C" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". C is "A" for the first file, "B" for the second, etc. Each OPT file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. OPT files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 4.4.27 Solar Array Kernel Files (SAK Directory) The SAK directory contains CK Files in NAIF "transfer" format for the solar array panels. These are files with names of the form ydddeeeZ.SAK where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". Z is "A" for the first file, "B" for the second, etc. Each SAK file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. SAK files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 4.4.28 Space Flight Operations Schedule Files (SFO Directory) The SFO directory contains Space Flight Operation Schedule Files. These are files with names of the form ydddeeeZ.SFO where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". Z is "A" for the first file, "B" for the second, etc. During the first part of MGS Cruise, some SFO files were given names based on the Mission Phase and planning cycle. These were names of the form CaabbccZ.SFO were "aa", "bb", and "cc" were two-digit numbers and "Z" is a single upper case letter indicating order of files when there is more than one with the same "aabbcc". Z is "A" for the first file, "B" for the second, etc. Each SFO file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. SFO files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. The MGS Project discontinued production of SFO files in late August 1998. 4.4.29 Sequence of Events Files (SOE Directory) The SOE directory contains Sequence of Events Files. These are files with names of the form ydddeeeZ.SOE where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". Z is "A" for the first file, "B" for the second, etc. During the first part of MGS Cruise, some SOE files were given names based on the Mission Phase and planning cycle. These were names of the form CaabbccZ.SOE were "aa", "bb", and "cc" were two-digit numbers and "Z" is a single upper case letter indicating order of files when there is more than one with the same "aabbcc". Z is "A" for the first file, "B" for the second, etc. Each SOE file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. SOE files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. The format of SOE files produced by the MGS Project changed in late August 1998. Prior to that date, files were in a somewhat cryptic format most easily displayed using the MGS-provided soeedt utility. The format after August 1998 was straight ASCII text. 4.4.30 NAIF SPK Files (SPK Directory) The SPK directory contains SPK Files in NAIF "transfer" format. These are files with names of the form ydddeeeZ.SPK where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". Z is "A" for the first file, "B" for the second, etc. Each SPK file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. SPK files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 4.4.31 NAIF CK Files (TCK Directory) The TCK directory contains CK Files in NAIF "transfer" format for the spacecraft attitude. These are files with names of the form ydddeeeZ.TCK where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "Z" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". Z is "A" for the first file, "B" for the second, etc. Each TCK file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. TCK files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 4.4.32 Archival Tracking Data Files (TDF Directory) Archival Tracking Data Files are files with names of the form ydddeeeZ.TDF where "y" is the least significant digit of the year, "ddd" is the three-digit day of year for start of data, "eee" is the three-digit day of year for end of data, and "Z" is a single character (starting from "A") that is used to distinguish among two or more ODFs with the same first 7 characters. Each Archival Tracking Data File is accompanied by a full PDS label having file name ydddeeeZ.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. Each label completely describes the format and content of its corresponding TDF. 4.4.33 Troposphere Calibration Files (TRO Directory) The TRO directory contains Troposphere (Media) Calibration Files. These are files with names of the form ydddeeeC.TRO where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "C" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". C is "A" for the first file, "B" for the second, etc. Each TRO file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. TRO files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 4.4.34 UltraStable Oscillator Files (USO Directory) The USO directory contains tables of USO calibration data. These include Allan Deviation and models of USO frequency as a function of time. USO calibration files have names of the form USOCyddd.TAB where "C" identifies the type of USO calibration data included in the file, "y" is the least significant digit of the year on which the file was created, and "ddd" is the day-of-year on which the file was created. Each USO Calibration File is a PDS TABLE object with fixed length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. Each USO file is accompanied by a full PDS label having the same file name (except for the suffix *.LBL) and completely describing both the format and the content of the file. 4.4.35 DSN Weather Calibration Files (WEA Directory) The WEA directory contains DSN Weather Calibration Files. These are files with names of the form ydddeeeC.WEA where "y" is the least significant digit of the year in which data in the file begin, "ddd" is the day-of-year when data begin, "eee" is the day-of-year when data end, and "C" is a single upper case letter indicating order of files when there is more than one with the same "ydddeee". C is "A" for the first file, "B" for the second, etc. Each WEA file is accompanied by a PDS minimal label having file name ydddeeeC.LBL. Each label file has fixed length records of 80 ASCII characters each, with an ASCII carriage-return line-feed pair in the last two positions. WEA files are ASCII files with variable length records. Each record is delimited by an ASCII carriage-return line-feed pair. On some machines it may be necessary to convert the carriage-return line-feed pair to the local default delimiter before using the file. 5 Support Staff and Cognizant Personnel The following persons may be contacted for information. Planetary Data System Radio Science Advisor: Richard A. Simpson Durand Building - Room 232 Center for Radar Astronomy Stanford University Stanford, CA 94305-9515 Phone: 650-723-3525 FAX: 650-723-9251 Electronic mail: rsimpson@magellan.stanford.edu Planetary Data System operator: PDS Operator MS 171-264 Jet Propulsion Laboratory 4800 Oak Grove Drive Pasadena, CA 91109 Phone: 626-744-5414 Electronic mail: pds_operator@jpl.nasa.gov