CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 1995-04-18 NOTE = "Software Interface Specification for the Clementine bistatic radar raw data archive. Formatted for display or printing at 61 lines per page with up to 78 constant-width characters per line." END_OBJECT = TEXT END Stanford Center for Radar Astronomy Software Interface Specification CLEM1-L-RSS-1-BSR-V1.0 Bistatic Radar Raw Data Archive (BSR-RDA) prepared by Richard A. Simpson Center for Radar Astronomy Stanford University Stanford, CA 94305-4055 415-723-3525 Version 1.0 18 April 1995 PREFACE |================================================================| | | | DOCUMENT CHANGE LOG | | | |================================================================| |REVISION|REVISION| SECTION | REMARKS | | NUMBER | DATE | AFFECTED | | |--------+--------+------------+---------------------------------| | 1.0 |95/03/02| All |Adapted from SIS for Magellan | | | | | Radio Occultation Raw Data | | | | | Archive. | |================================================================| |================================================================| | | | ITEMS TO BE DETERMINED | | | |================================================================| | REVISION | SECTION | ITEM DESCRIPTION | RESOLUTION | | NUMBER | AFFECTED | | | |----------+----------+------------------------+-----------------| | | | | | |================================================================| Distribution PDS/JPL Y. Fletcher..........525/3610 yfletcher@jplpds.jpl.nasa.gov M. Martin............525/3610 mike_martin@isd.jpl.nasa.gov G. Woodward..........525/3610 gwoodward@jplpds.jpl.nasa.gov R. Monarrez..........525/3610 rmonarrez@jplpds.jpl.nasa.gov PDS/MIT P.G. Ford................37-601 pgf@space.mit.edu Stanford University R. Simpson.........Durand 232 rsimpson@nova.stanford.edu J. Twicken.........Durand 232 joe@nova.stanford.edu L. Tyler...........Durand 232 len@nova.stanford.edu Naval Research Laboratory C. Lichtenberg......Code 8131 lichtenberg@nrlvax.nrl.navy.mil RSST/JPL S.W. Asmar.............161-260 sami.w.asmar@ccmail.jpl.nasa.gov Contents Preface.........................................................ii Document Change Log.............................................ii Items to be Determined..........................................ii Distribution....................................................ii Contents.......................................................iii Acronyms and Abbreviations......................................vi 1 Introduction..................................................1 1.1 Overview....................................................1 1.2 Scope.......................................................1 1.3 Applicable Documents........................................1 1.4 System Siting...............................................1 1.4.1 Interface Location and Medium.............................1 1.4.2 Data Sources, Destinations, and Transfer Methods..........1 1.4.3 Generation Method and Frequency...........................2 1.5 Assumptions and Constraints.................................2 1.5.1 Usage Constraints.........................................2 1.5.2 Documentation Conventions.................................2 1.5.2.1 Data Format Descriptions................................2 1.5.2.2 Limits of This Document.................................3 1.5.2.3 Typographic Conventions.................................3 1.5.3 Time Standards............................................3 2 Interface Characteristics.....................................4 2.1 Hardware Characteristics and Limitations....................4 2.1.1 Special Equipment and Device Interfaces...................4 2.1.2 Special Set-Up Requirements...............................4 2.2 Volume and Size ............................................4 2.3 Labeling and Identification.................................4 2.3.1 External Labels...........................................4 2.3.2 Internal Labels...........................................5 2.4 Interface Medium Characteristics............................5 2.5 Backup and Duplicates.......................................5 3 Structure and Organization Overview...........................6 3.1 Disc Organization...........................................6 3.1.1 Root Directory............................................7 3.1.2 CALIB Directory...........................................7 3.1.3 CATALOG Directory.........................................7 3.1.4 DOCUMENT Directory........................................7 3.1.5 GEOMETRY Directory........................................8 3.1.6 INDEX Directory...........................................8 3.1.7 Directories for Raw Bistatic Radar Data...................8 3.2 Formats.....................................................8 3.3 File Naming Conventions.....................................9 3.3.1 PDS Labels................................................9 3.3.2 Text Files...............................................10 3.3.3 Tabular Files............................................10 3.3.4 Catalog Files............................................10 3.3.5 Data Files...............................................11 4 Detailed Interface Specifications............................12 4.1 Root Files.................................................12 4.1.1 AAREADME.TXT File........................................12 4.1.2 ERRATA.TXT File..........................................12 4.1.3 VOLDESC.CAT File.........................................12 4.2 Static Directories.........................................13 4.2.1 CALIB Directory..........................................13 4.2.1.1 CALINFO.TXT File.......................................13 4.2.1.2 High-Gain Antenna (HGA) Pattern Measurements...........13 4.2.1.3 Real-Time Note Files...................................13 4.2.1.4 Transponder Data Files.................................13 4.2.2 CATALOG Directory........................................14 4.2.2.1 CATINFO.TXT File.......................................14 4.2.2.2 MISSION.CAT File.......................................14 4.2.2.3 INSTHOST.CAT File......................................14 4.2.2.4 INST.CAT File..........................................14 4.2.2.5 REF.CAT File...........................................14 4.2.2.6 PERSON.CAT File........................................14 4.2.2.7 DATASET.CAT File.......................................14 4.2.3 DOCUMENT Directory.......................................15 4.2.3.1 DOCINFO.TXT File.......................................15 4.2.3.2 DESCRIPT.TXT File......................................15 4.2.3.3 ARC_SIS.TXT File.......................................15 4.2.3.4 RSC11_11.TXT File......................................15 4.2.3.5 TRK_2_25.TXT.File......................................15 4.2.3.6 LMC.TXT File...........................................15 4.2.3.7 TK_DESCR.TXT.File......................................16 4.2.3.8 TK_INSTL.TXT.File......................................16 4.2.3.9 TK_FTP.TXT File........................................16 4.2.4 GEOMETRY Directory.......................................16 4.2.4.1 GEOMINFO.TXT File......................................16 4.2.4.2 SPK Files..............................................16 4.2.4.3 CK Files...............................................17 4.2.4.4 SCLK Files.............................................17 4.2.5 INDEX Directory..........................................17 4.2.5.1 INDXINFO.TXT File......................................17 4.2.5.2 INDEX.LBL File.........................................18 4.2.5.3 INDEX.TAB File.........................................18 4.2.5.4 CUMINDEX.LBL File......................................18 4.2.5.5 CUMINDEX.TAB File......................................18 4.3 Data Directories...........................................18 5 Support Staff and Cognizant Personnel........................20 A Example Labels and Other Files...............................21 A.1 Example Files from BSR-RDA Root............................21 A.1.1 Example VOLDESC.CAT File.................................21 A.2 Example Files from CALIB Directory.........................21 A.2.1 Example CALINFO.TXT File.................................21 A.2.2 Example High-Gain Antenna Pattern Label File.............22 A.2.3 Example Transponder Data File............................25 A.3 Examples Files from CATALOG Directory......................27 A.3.1 Example CATINFO.TXT File.................................27 A.4 Example Files from DOCUMENT Directory......................28 A.4.1 Example DOCINFO.TXT File.................................28 A.5 Example Files from GEOMETRY Directory......................29 A.5.1 Example GEOMINFO.TXT FILE................................29 A.5.2 Example CK Label File....................................30 A.5.3 Example SCLK Label File..................................31 A.5.4 Example SPK Label File...................................31 A.6 Example Files from INDEX Directory.........................32 A.6.1 Example INDXINFO.TXT File................................32 A.6.2 Example INDEX.LBL File...................................32 A.7 Example LMC Label File.....................................34 A.8 Example ODR Label File.....................................34 A.9 Example TDF Label File.....................................35 Tables 2-2 Data Directories for BSR-RDA Volumes...................4 Figures 3-1 Example Top-Level BSR-RDA Directory Structure..........6 4-1-1 Example Label for BSR-RDA TXT Files...................12 Acronyms and Abbreviations ANSI American National Standards Institute ASCII American Standard Code for Information Interchange ATDF Archival Tracking Data File BMDO Ballistic Missile Defense Organization BSR Bistatic Radar CCSDS Consultative Committee for Space Data Systems CD Compact Disc CD-WO Compact Disc - Write Once CK Camera (Attitude) Kernel CLEM Clementine DOS Disk Operating System DSN Deep Space Network DSPSE Deep Space Program Science Experiment ftp File Transfer Protocol HGA High-Gain Antenna ISO International Standards Organization JPL Jet Propulsion Laboratory K Degrees Kelvin kB Kilobytes LGA Low-Gain Antenna LMC Link Monitor and Control MB Megabytes MGA Medium-Gain Antenna MGN Magellan MGS Mars Global Surveyor MO Mars Observer NAIF Navigation and Ancillary Information Facility NASA National Aeronautics and Space Administration NAV Navigation Subsystem/Team NRL Naval Research Laboratory ODR Original Data Record PDS Planetary Data System RDA Raw Data Archive ROM Read-Only Memory RS Radio Science RSST Radio Science Support Team RST Radio Science Team SFDU Standard Formatted Data Unit SIS Software Interface Specification SOPC Science Operations Planning Computer SPK Spacecraft Planet Kernel (NAIF file) TBD To Be Determined TDF (Archival) Tracking Data File 1 Introduction 1.1 Overview This Software Interface Specification (SIS) describes the format and content of the Clementine (CLEM) bistatic radar (BSR) raw data archive (RDA). The BSR-RDA consists of Compact Disc - Write Once (CD-WO) media containing files of raw bistatic radar data copied from magnetic tape and files created at Stanford University and elsewhere. Each CD-WO represents a "volume" of archival data. The BSR-RDA is a deliverable product to the Clementine Project, the Planetary Data System (PDS), and the scientific community that PDS supports. The formats of all files in the data set are based on PDS standards. 1.2 Scope The specifications in this document apply to all BSR-RDA volumes produced at Stanford University for delivery to PDS. This document provides a detailed description of the BSR-RDA 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, 3 August 1994. [3] Planetary Science Data Dictionary, JPL D-7116, Rev. C, 20 November 1992. [4] Planetary Data System, Data Preparation Workbook, JPL Publication D-7669, Part 1, Version 3.0, 21 April 1993. Clock (SCLK) File, MO SPICE CD-WO, 26 September 1993 [5] RSC-11-11, Radio Science System Original Data Record (ODR) and Original Data Stream (ODS), 1992. [6] TRK-2-25, DSN Tracking System Interfaces: Archival Tracking Data File Interface, Document 820-13 Rev A, 1986. 1.4 System Siting 1.4.1 Interface Location and Medium BSR-RDA volumes are created at Stanford University using the Mars Global Surveyor (MGS) Science Operations Planning Computer (SOPC) and the Young Minds CD-Studio compact disc authoring subsystem. All volumes intended for delivery to PDS will be on CD-WO media. 1.4.2 Data Sources, Destinations, and Transfer Methods Each BSR-RDA volume is a collection of products representing, derived from, or needed to analyze raw bistatic radar data. Each CD-WO is delivered using the most appropriate means to the Planetary Data System (PDS). 1.4.3 Generation Method and Frequency Each BSR-RDA volume is produced in several stages. First, an inventory of the data is completed and algorithms are developed to provide each file with a unique name having the format XXXXXXXX.ext where "XXXXXXXX" represents no more than eight upper case ASCII characters, digits, or the underscore character and "ext" is a three-character upper-case extension. In most cases file names are based on the year and day (or revolution number) during which the data were collected. The inventory also includes information on the start and stop times of the data in the file and the date on which the file was created. Second a PDS label is created for each file. The PDS label carries identifying information (such as the date and time at which the file was created). In most cases the PDS label is "detached" -- it exists as a file in its own right. But in certain cases the label may be prepended (or attached) to the beginning of the file, such as for text files. The PDS labels facilitate management of the data files. Third, the files are organized by data type. For BSR-RDA volumes no more than three primary data types are included in the archive: the Original Data Record (ODR), the (Archival) Tracking Data File (TDF), and the Link Monitor and Control (LMC) data types. Ancillary data, such as measurements of high-gain antenna patterns and spacecraft ephemerides are assigned to other directories (such as CALIB and GEOMETRY, in these cases). Fourth, limits on the experiment files to be included in each CD-WO volume are defined. The number of files is limited by the capacity of a single CD-WO disc (less than 650 MB). ODR, TDF, and LMC files are assigned chronologically to a volume until that capacity is approached. The assignments are adjusted so that corresponding ancillary data files can be included. Fifth, the designated files are moved to a special disk partition and the CD-WO is pre-mastered. After correction of errors, the final CD is produced. Ancillary files (SIS documents, information files, etc.) are created in parallel with the data manipulation. Each BSR-RDA volume is evaluated internally at Stanford and (to the extent that resources permit) by a representative of PDS, by a representative of the Clementine Project, and by the Radio Science Support Team (RSST) at JPL. 1.5 Assumptions and Constraints 1.5.1 Usage Constraints None. 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 64-bit floating point numbers and to 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 BSR-RDA volumes. 1.5.2.3 Typographic Conventions This document has been formatted for simple electronic file transfer and display. Line lengths are limited to 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 61 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 BSR-RDA files that follow PDS standards, times are expressed as a string of 23 ASCII characters YYYY-MM-DDThh:mm:ss.fff where "-", "T", ":", and "." are fixed delimiters; "YYYY" is the year "19nn" or "20nn"; "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) 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 BSR-RDA volumes conform to ISO 9660 standards for CD-ROM [1]. Users of the volumes must have access to systems which can read these media. 2.1.2 Special Set-Up Requirements None. 2.2 Volume and Size Each BSR-RDA volume contains an accumulation of bistatic radar data products. Each CD-WO contains at most 650 Mbytes of data. The file types and their directory assignments are shown in Table 2-2. When a file type is not included in a data set, the corresponding directory will be omitted. |==================================================== | | | Table 2-2 Data Directories for BSR-RDA Volumes | | | |===================================================| |Directory| Data Type | | Name | | |---------+-----------------------------------------| | LMC | Link Monitor and Control Log | | ODR | Original Data Record | | TDF | (Archival) Tracking Data File | |===================================================| 2.3 Labeling and Identification 2.3.1 External Labels Each BSR-RDA volume bears a label using the following format: ACRONYM_SEQUENCE;VERSION where ACRONYM = CL SEQUENCE = 20xx where xx is a two digit number indicating the order in which the CD-WO volumes were produced (starting from 01) VERSION = A single digit denoting version number of the CD-WO volume. "1" is the original version. For example, CL_2003;5 is the fifth version of the third BSR-RDA volume. 2.3.2 Internal Labels The contents of each BSR-RDA volume will be labeled in accordance with PDS standards. Labeling is described further in subsequent sections. 2.4 Interface Medium Characteristics Each BSR-RDA 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 BSR-RDA volume will be backed up onto 8-mm tapes and retained at Stanford. At least four copies of each final BSR-RDA volume will be created. One copy will be delivered to PDS, one copy will be delivered to the Clementine Project, one copy will be delivered to the Radio Science Support Team (RSST) at JPL, and one copy will be retained at Stanford. 3 Structure and Organization Overview 3.1 Disc Organization Each BSR-RDA volume contains a CALIB directory, a CATALOG directory, a DOCUMENT directory, a GEOMETRY directory, an INDEX directory, and one or more data directories (Figure 3-1). |================================================================| | | | Figure 3-1 Example Top-Level BSR-RDA Directory Structure | | | |================================================================| | | | root | | | | | |- AAREADME.TXT | | |- ERRATA.TXT | | |- VOLDESC.CAT | | | | | |- CALIB | | | | | | | |---------------------------------------- | | | |- CALINFO.TXT |- QHGA_L_Q.TAB |- QHGA_L_Q.LBL | | | |- NOTESddd.TXT |- QHGA_C_Q.TAB |- QHGA_C_Q.LBL | | | |- ... |- QHGA_C_2.TAB |- QHGA_C_2.LBL | | | |- XPNDRnnn.TAB |- XPNDRnnn.LBL | | |- CATALOG | | | | | | | |---------------------------------------- | | | |- CATINFO.TXT |- INSTHOST.CAT |- REF.CAT | | | |- MISSION.CAT |- INST.CAT |- PERSON.CAT | | | |- DATASET.CAT | | | | | |- DOCUMENT | | | | | | | |---------------------------------------- | | | |- DOCINFO.TXT |- LMC.TXT |- TK_DESCR.TXT | | | |- ARC_SIS.TXT |- RSC11_11.TXT |- TK_INSTL.TXT | | | |- DESCRIPT.TXT |- TRK_2_25.TXT |- TK_FTP.TXT | | | | | |- GEOMETRY | | | | | | | |---------------------------------------- | | | |- GEOMINFO.TXT |- CKyyddd.TCK |- CKyyddd.LBL | | | |- SPKyyddd.TSP |- SPKyyddd.LBL | | | |- DSPSE002.TSC |- DSPSE002.LBL | | |- INDEX | | | | | | | |- INDXINFO.TXT | | | |- INDEX.LBL | | | |- INDEX.TAB | | | |- CUMINDEX.LBL | | | |- CUMINDEX.TAB | | | | | |- LMC data | | |- ODR directories | | |- TDF | | | |================================================================| 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 the following files (detached PDS labels and format files are not listed): CALINFO.TXT text description of the directory contents [2] aHGA_p_r.TAB radiation pattern of high-gain antenna; "a" denotes antenna type (F for flight antenna, Q for qualification antenna), "p" denotes polarization (C for circular, L for linear), and "r" denotes cone angle resolution (2 for 2-degree resolution, Q for quarter-degree resolution). increments in circular polarization NOTESddd.TXT real-time notes for experiments starting on days-of-year ddd of 1994. XPNDRnnn.TAB engineering telemetry on oscillator temperature and transmitter power for revolution nnn. 3.1.3 CATALOG Directory The CATALOG directory contains the following files: CATINFO.TXT text description of the directory contents [2] 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] REF.CAT PDS data set catalog object for references [2] PERSON.CAT PDS data set catalog object for personnel [2] DATASET.CAT PDS data set catalog object for the data set [2] 3.1.4 DOCUMENT Directory The DOCUMENT directory contains the following files: DOCINFO.TXT text description of the directory contents [2] ARC_SIS.TXT this SIS document TK_DESCR.TXT Text description of NAIF Toolkit TK_INSTL.TXT Text description of NAIF Toolkit installation TK_FTP.TXT Text description of ftp procedure for obtaining NAIF Toolkit In addition the DOCUMENT directory may contain descriptive material on the experiment or Software Interface Specification documents for component files. For the Clementine BSR-RDA these additional files include: DESCRIPT.TXT Text description of experiment LMC.TXT Ad hoc software interface specification for Link Monitor and Control Log files RSC11_11.TXT DSN Interface for the DSN Radio Science System Original Data Record (ODR) and Original Data Stream (ODS) [5] TRK_2_25.TXT DSN Interface for the Archival Tracking Data File [6] 3.1.5 GEOMETRY Directory The GEOMETRY directory contains the following files (detached PDS labels and format files are not listed): GEOMINFO.TXT text description of the directory contents [2] SPKyyddd.TSP transfer version of the NAIF SPK (ephemeris) file beginning on year yy and day-of-year ddd CKyyddd.TCK transfer version of the NAIF CK (attitude) file beginning on year yy and day-of-year ddd DSPSE002.TSC ASCII NAIF SCLK file for the entire mission 3.1.6 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) [2] CUMINDEX.TAB index in tabular form for all volumes in the BSR-RDA [2] 3.1.7 Directories for Raw Bistatic Radar Data Each BSR-RDA volume contains directories for one or more data types (Figure 3-1; Table 2-2). When no data files of a given type are to be archived, the corresponding data directory will be omitted. 3.2 Formats BSR-RDA volumes conform 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 the BSR-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. 3.3.1 PDS Labels All files contained on BSR-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 file except for the suffix ".LBL". Detached label files will be located in the same directory as the primary file, or in one of a few default directories based on search rules specified in [2]. Collections of documents and associated figures may be represented by a single PDS detached label having a unique file name ending in ".LBL". 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 will have lengths that are multiples of 80 bytes, but individual records may have variable lengths. Each record will end 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.3.2 Text Files Text files (.TXT suffix) may exist in the root, CALIB, CATALOG, DOCUMENT, GEOMETRY, and INDEX directories. These are ASCII files with embedded PDS labels which employ the TEXT object. All records in text files are limited to 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.3.3 Tabular Files Tabular files (.TAB suffix) exist in the CALIB and INDEX directories. All tabular files are filled with ASCII characters. Tabular files 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 PDS labels, either prepended to the beginning of the file or detached. If detached, the PDS label has the same name as the data file it describes, with the extension .LBL; for example, the file INDEX.TAB is accompanied by the detached label file INDEX.LBL in the INDEX directory. 3.3.4 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 in the form of a completed PDS template. The files in the CATALOG directory provide a top-level understanding of the mission, the spacecraft, the ground system, and the data set. They are presented in the form of completed PDS templates [2]. 3.3.5 Data Files Files in data directories are generally binary files, described by Software Interface Specifications (SISs) in the DOCUMENT directory. Each data file is accompanied by a detached PDS minimal label. All detached labels have lengths that are multiples of 80 bytes, but individual records may have variable lengths. Each record will end with a carriage-return character (ASCII 13) in the next-to-last byte and a line-feed character (ASCII 10) in the last byte. Data files in the ODR directory have file names of the form ydddhhmm.ODR and labels have file names ydddhhmm.LBL, where y is the least significant digit in the year (4) ddd is the 3-digit day-of-year (099, 100, 113, or 114) hh is the 2-digit start hour (00-23) mm is the 2-digit start minute (00-59) The single TDF data file has a file name of the form yydddeee.TDF and a label file name yydddeee.LBL, where yy is the two-digit starting year number (94) ddd is the 3-digit start day-of-year (095) eee is the 3-digit stop day-of-year (114) Data files in the LMC directory have file names of the form sssaaddd.LMC and labels have file names sssaaddd.LBL, where sss is the 3-digit DSN spacecraft number (064) aa is the 2-digit antenna number (63) ddd is the 3-digit start day-of-year (100 or 113) 4 Detailed Interface Specifications 4.1 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 no longer than 72 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 BSR-RDA TXT Files | | | |================================================================| | | | CCSD3ZF0000100000001NJPL3IF0PDSX00000001 | | PDS_VERSION_ID = PDS3 | | RECORD_TYPE = STREAM | | OBJECT = TEXT | | PUBLICATION_DATE = 1994-01-25 | | NOTE = "Pre-launch description of science | | investigations, instruments, and | | experimental methods planned by | | the Mars Observer 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 all BSR-RDA volumes published to date. This is an ASCII file with record lengths no longer than 72 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 this volume in a PDS format readable by both humans and computers. This is an ASCII file with record lengths no longer than 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 Appendix A. Keywords are defined in [3]. 4.2 Static Directories Static directories are those which do not change (or change very little) from one volume to another. They appear on all volumes. 4.2.1 CALIB Directory The CALIB directory contains files used in calibrating the data. Included are files which give the radiation pattern of the spacecraft high-gain antenna and notes taken in near real-time during the experiments. 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 no longer than 72 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 High-Gain Antenna (HGA) Pattern Measurements Antenna Pattern files are tabular files of high-gain antenna pattern measurements made using either the Clementine qualification model antenna or the Clementine flight antenna. Record lengths are fixed and are no longer than 80 ASCII characters. The next to last and last characters in each record are a carriage-return (ASCII 13) line-feed (ASCII 10), respectively. Each tabular file is accompanied by a detached PDS label which describes both its content and format. Each line in the PDS label is no longer than 80 ASCII characters, and includes a final ASCII 13 (carriage-return) and ASCII 10 (new line) pair. An example PDS label is reproduced in Appendix A. 4.2.1.3 Real-Time Note Files Real-Time Note Files are text files of notes taken during execution of a Clementine bistatic radar experiment. Record lengths are no longer than 80 ASCII characters. The next to last and last characters in each record are a carriage-return (ASCII 13) line-feed (ASCII 10), respectively. The file has an attached PDS label of the form shown in Figure 4-1-1. 4.2.1.4 Transponder Data Files Transponder Data files are tabular files containing estimates of temperature in the vicinity of the auxiliary oscillator and transmitter output power for each on-board transponder. Record lengths are fixed at 64 bytes per record. The next to last and last characters in each record are a carriage-return (ASCII 13) line-feed (ASCII 10), respectively. Each tabular file is accompanied by a detached PDS label which describes both its content and format. Each line in the PDS label is no longer than 80 ASCII characters, and includes a final ASCII 13 (carriage-return) and ASCII 10 (new line) pair. An example Transponder Data File PDS label is reproduced in Appendix A. 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" template forms 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 no longer than 72 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 Clementine mission and spacecraft [2]. This is an ASCII file with record lengths no longer than 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 no longer than 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 no longer than 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 no longer than 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 BSR- RDA volume set [2]. This is an ASCII file with record lengths no longer than 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 no longer than 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 BSR-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 no longer than 72 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 DESCRIPT.TXT File The DESCRIPT.TXT file is a description of the experiment objectives and execution. This is an ASCII file with record lengths no longer than 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 ARC_SIS.TXT File The ARC_SIS.TXT file is the Clementine BSR-RDA Software Interface Specification (this document). This is an ASCII file with record lengths no longer than 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 RSC11_11.TXT File The RSC11_11.TXT file is the DSN Radio Science System Original Data Record (ODR) and Original Data Stream (ODS) Software Interface Specification. This is an ASCII file with record lengths no longer than 72 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 TRK_2_25.TXT File The TRK_2_25.TXT file is the DSN Archival Tracking Data File Interface. This is an ASCII file with record lengths no longer than 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 TDF data directory of the BSR-RDA volume. 4.2.3.6 LMC.TXT File The LMC.TXT file is a description of the content and format of Link Monitor and Control Log files. This is an ASCII file with record lengths no longer than 72 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 TK_DESCR.TXT File The TK_DESCR.TXT file is a description of the NAIF Toolkit, which is used to access and manipulate SPK (ephemeris) and CK (attitude) files. The version of the file included here is tailored for the Sun operating system, but the Toolkit is available for other platforms and the differences in the Toolkit description are minor. This is an ASCII file with record lengths no longer than 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.8 TK_INSTL.TXT File The TK_INSTL.TXT file is a set of installation instructions for the NAIF Toolkit, which is used to access and manipulate SPK (ephemeris) and CK (attitude) files. The version of the file included here is tailored for the Sun operating system, but the Toolkit is available for other platforms and the differences in the Toolkit installation are minor. This is an ASCII file with record lengths no longer than 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.9 TK_FTP.TXT File The TK_FTP.TXT file is a set of instructions for using ftp (File Transfer Protocol) to obtain the current version of the NAIF Toolkit via Internet. The Toolkit is used to access and manipulate SPK (ephemeris) and CK (attitude) files. This is an ASCII file with record lengths no longer than 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.4 GEOMETRY Directory 4.2.4.1 GEOMINFO.TXT File The GEOMINFO.TXT file contains a description of the contents of the GEOMETRY directory. This is an ASCII file with record lengths no longer than 72 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.4.2 SPK Files SPK Files contain data which, in conjunction with the NAIF Toolkit, allows calculation of spacecraft and planetary positions and velocities. The Toolkit is described in the file TK_DESCR.TXT in the DOCUMENT directory; its installation is described by the file TK_INSTL.TXT in the same location. Documentation within the Toolkit, which can be obtained following instructions in the file TK_FTP.TXT in the DOCUMENT directory, provides information on file structure and use of NAIF readers to manipulate the data. SPK files contain ASCII characters only; lines have variable lengths, and each line is terminated by a carriage-return (ASCII 13) line-feed (ASCII 10) pair. On some systems one or the other of these delimiters may have to be removed before the files can be used with NAIF software. File names have the form SPKyyddd.TSP, where 'yy' is the two-digit year and 'ddd' is the three-digit day- of-year of the first data in the file. Each SPK file is accompanied by a detached PDS label with name SPKyyddd.LBL. An example SPK label file is included in Appendix A. 4.2.4.3 CK Files CK Files contain data which, in conjunction with the NAIF Toolkit, allows calculation of spacecraft attitude. The Toolkit is described in the file TK_DESCR.TXT in the DOCUMENT directory; its installation is described by the file TK_INSTL.TXT in the same location on each BSR-RDA volume. Documentation within the Toolkit, which can be obtained following instructions in the file TK_FTP.TXT in the DOCUMENT directory, provides information on file structure and use of readers to manipulate the data. CK files contain ASCII characters only; lines have variable lengths, and each line is terminated by a carriage-return (ASCII 13) line-feed (ASCII 10) pair. On some systems one or the other of these delimiters may have to be removed before the files can be used with NAIF software. CK files have names of the form CKyyddd.TCK where yy is the year and ddd is the day-of-year when the file begins. Each CK file is accompanied by a detached PDS label; in the Clementine BSR-RDA the label accompanying the CK file has the name CKyyddd.LBL. An example CK label file is included in Appendix A. 4.2.4.4 SCLK Files SCLK Files contain data which, in conjunction with the NAIF Toolkit, allows interpretation of spacecraft clock values; an SCLK file is necessary for use of CK files. The Toolkit is described in the file TK_DESCR.TXT in the DOCUMENT directory; it's installation is described by the file TK_INSTL.TXT in the same location on each BSR-RDA volume. Documentation within the Toolkit, which can be obtained following instructions in the file TK_FTP.TXT in the DOCUMENT directory, provides information on file structure and use of readers to manipulate the data. SCLK files contain ASCII characters only; lines have variable lengths, and each line is terminated by a carriage-return (ASCII 13) line-feed (ASCII 10) pair. On some systems one or the other of these delimiters may have to be removed before the files can be used with NAIF software. The only SCLK file in the Clementine BSR-RDA has the name DSPSE002.TSC. Each SCLK file is accompanied by a detached PDS label; the label for the only SCLK file in the Clementine BSR-RDA has the name DSPSE002.LBL. An example SCLK label file is included in Appendix A. 4.2.5 INDEX Directory 4.2.5.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 no longer than 72 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.5.2 INDEX.LBL File INDEX.LBL is a detached label that completely describes INDEX.TAB. The length of the INDEX.LBL file is an integral multiple of 80 bytes. The SFDU label is followed immediately by a carriage-return (ASCII 13) line-feed (ASCII 10) pair, 36 ASCII blank characters, and a second ASCII carriage-return line-feed pair for a total of 80 bytes. All other records are padded to 78 bytes with ASCII blanks and are delimited by a carriage-return line-feed pair in bytes 79 and 80. Appendix A includes an example INDEX.LBL file for an BSR-RDA volume. Keywords are defined in [3]. 4.2.5.3 INDEX.TAB File INDEX.TAB is a table listing all BSR-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.2.5.4 CUMINDEX.LBL File CUMINDEX.LBL is a detached label that completely describes CUMINDEX.TAB. The length of the CUMINDEX.LBL file is an integral multiple of 80 bytes. The SFDU label is followed immediately by a carriage-return (ASCII 13) line-feed (ASCII 10) pair, 36 ASCII blank characters, and a second ASCII carriage-return line-feed pair for a total of 80 bytes. All other records are padded to 78 bytes with ASCII blanks and are delimited by a carriage-return line-feed pair in bytes 79 and 80. CUMINDEX.LBL differs from INDEX.LBL in only three ways: * ^TABLE points to CUMINDEX.TAB rather than to INDEX.TAB * INDEX_TYPE = CUMULATIVE rather than SINGLE * INDEXED_FILE_NAME refers to INDEX.TAB and CUMINDEX.TAB rather than to data files or labels 4.2.5.5 CUMINDEX.TAB File CUMINDEX.TAB is a table listing all BSR-RDA data files included in all volumes of the volume set to date. 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 CUMINDEX.LBL. 4.3 Data Directories BSR-RDAs include directories for each of the separate data types included in the BSR-RDA volume. Table 2-2 shows the range of data types that can be included; not all data types are necessarily included on each volume, however. Files in the ODR directory are binary files described by the SIS RSC11_11.TXT in the DOCUMENT directory. Files in the TDF directory are binary files described by the SIS TRK_2_25.TXT in the DOCUMENT directory. Files in the LMC directory are ASCII files described by LMC.TXT in the DOCUMENT directory. Each file is accompanied by a "minimal" PDS label. Example labels for LMC, ODR, and TDF data are included in Appendix A. Keywords are defined in [3]. 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-4055 Phone: 415-723-3525 FAX: 415-723-9251 Electronic Mail: rsimpson@magellan.stanford.edu Experiment Principal Investigator: Christopher L. Lichtenberg Code 8131 U.S. Naval Research Laboratory 4555 Overlook Ave., S.W. Washington, DC 20375-5000 Phone: 202-767-6622 FAX: N/A Electronic Mail: lichtenberg@nrlvax.nrl.navy.mil Radio Science Support Team: Sami W. Asmar MS 161-260 Jet Propulsion Laboratory 4800 Oak Grove Drive Pasadena, CA 91109 Phone: 818-3546288 FAX: 818-393-4643 Electronic Mail: sami.w.asmar@ccmail.jpl.nasa.gov Planetary Data System: PDS Operator MS 525/3610 Jet Propulsion Laboratory 4800 Oak Grove Drive Pasadena, CA 91109 Phone: 818-306-6130 Electronic mail: JPLPDS::PDS_OPERATOR pds_operator@jplpds.jpl.nasa.gov Appendix A Example Labels and Other Files A.1 Example Files from BSR-RDA Root A.1.1 Example VOLDESC.CAT File CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 OBJECT = VOLUME VOLUME_SERIES_NAME = "MISSION TO THE MOON" VOLUME_SET_NAME = "CLEMENTINE: RAW BISTATIC RADAR DATA ARCHIVE" VOLUME_SET_ID = USA_NASA_PDS_CL_20XX VOLUMES = UNK VOLUME_ID = CL_2001 VOLUME_VERSION_ID = "VERSION 1" VOLUME_NAME = "VOLUME 1: RAW BISTATIC RADAR DATA" PUBLICATION_DATE = 1995-04-18 DATA_SET_ID = "CLEM1-L-RSS-1-BSR-V1.0" MEDIUM_TYPE = "CD-WO" VOLUME_FORMAT = "ISO-9660" DESCRIPTION = "This volume contains raw data, partially processed data, and ancillary files from Clementine bistatic radar experiments." MISSION_NAME = "DEEP SPACE PROGRAM SCIENCE EXPERIMENT" SPACECRAFT_NAME = "CLEMENTINE 1" SPACECRAFT_ID = CLEM1 OBJECT = DATA_PRODUCER INSTITUTION_NAME = "STANFORD UNIVERSITY" FACILITY_NAME = "MGS RS REMOTE MISSION SUPPORT AREA" FULL_NAME = "MARS GLOBAL SURVEYOR RADIO SCIENCE TEAM" ADDRESS_TEXT = "DURAND BLDG - ROOM 232 STANFORD UNIVERSITY STANFORD, CA 94305-4055" 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 A.2 Example Files from CALIB Directory A.2.1 Example CALINFO.TXT File CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 1995-04-18 NOTE = "Description of contents of CALIB directory" END_OBJECT = TEXT END The CALIB directory holds calibration files for the Clementine bistatic radar experiment. The following files are in the CALIB directory. CALINFO.TXT (this file): Describes contents of the CALIB directory. NOTESddd.TXT: Text file of near real-time notes taken during the course of the experiment which began on day of year ddd (ddd = 099 or 113). File has an attached PDS label prepended to the text object. Line lengths in the file are limited to 80 characters with a carriage-return (ASCII 13) line-feed (ASCII 10) pair in the next-to-last and last positions. QHGA_L_Q.TAB: Qualification model high-gain antenna pattern measurements in linear polarization at 0.25 degree increments in angle from boresight. Format described by detached PDS label QHGA_L_Q.LBL. QHGA_C_Q.TAB: Qualification model high-gain antenna patterns in circular polarization at 0.25 degree increments in angle from boresight. Format described by detached PDS label QHGA_C_Q.LBL. Circular patterns are derived from linear measurements. QHGA_C_2.TAB: Same as QHGA_C_Q.TAB except that measurements are provided at two degree increments in angle from boresight. Format described by detached PDS label QHGA_C_2.LBL. XPNDRnnn.TAB: Telemetry data giving temperature of on-board auxiliary oscillators and output power from transponder transmitters for Clementine revolution nnn. Format described by detached PDS label XPNDRnnn.LBL. A.2.2 Example High-Gain Antenna Pattern Label File CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 76 FILE_RECORDS = 65160 ^TABLE = "QHGA_L_Q.TAB" DATA_SET_ID = "CLEM1-L-RSS-1-BSR-V1.0" PRODUCT_ID = "QHGA_L_Q.TAB" SPACECRAFT_NAME = CLEMENTINE_1 INSTRUMENT_ID = RSS TARGET_NAME = MOON PRODUCT_CREATION_TIME = 1995-04-06T22:43:00.000 MISSION_PHASE_NAME = {"PRE-LAUNCH","LAUNCH", "LOW EARTH ORBIT","EARTH PHASING LOOP A","LUNAR ORBIT INSERTION", "LUNAR MAPPING","LUNAR DEPARTURE","EARTH PHASING LOOP B"} START_TIME = 1994-01-01T00:00:00.000 STOP_TIME = 1994-05-31T23:59:59.999 OBJECT = TABLE INTERCHANGE_FORMAT = ASCII ROWS = 65160 COLUMNS = 6 ROW_BYTES = 76 DESCRIPTION = "This table provides antenna pattern data in linear polarizations for the Clementine qualification model high-gain antenna (HGA). This table was derived from measurements made in orthogonal linear polarizations at one-quarter degree increments in cone angle from boresight (THETA=180) to 45 degrees off boresight (THETA=135). The qualification model HGA was built identically to the flight antenna and is believed to have the same boresight gain to within 0.1 dB. No measurements of comparable detail are available for the flight antenna. A second table gives the circular polarization patterns, calculated from the linear measurements; it is in QHGA_C_Q.TAB. A third table gives circular patterns at two degree increments in cone angle from boresight to 100 degrees from boresight (table QHGA_C_2.TAB). Measurements were carried out on an antenna range at a distance of about 100 feet (30 meters) from the antenna; this is about twice what is usually taken to be the beginning of the 'far field' region for an antenna of this size. The measured values were not adjusted to an infinitely far field. The coordinate system for these measurements is defined as follows. The spacecraft positive x-axis is in the direction of the spacecraft main thruster. The HGA boresight is in the negative x-axis direction. The sensor panel faces in the direction of the positive z-axis. The positive y-axis makes a right-handed rectangular frame and points in the direction of the solar panel rotation axis (Y = Z x X; all unit vectors). Alignment of the HGA boresight was found to be within 0.1 degrees of the negative x-axis using laser instrumentation. The antenna pattern was measured by placing a probe at a point R. The vector to R from the center of the HGA made an angle THETA with respect to the positive X-axis. The projection of R onto the y-z plane made an angle PHI with respect to the negative z-axis; PHI was measured positive from the negative z-axis toward the negative y-axis. 'Vertical' is defined by the vector product of the vector to R and the positive x-axis (V = R x X/|R x X|). 'Horizontal' is defined by the vector product between the 'vertical' vector and the vector to R (H = V x R/|V x R|). Quantities in the table include cone and clock angles, magnitude and phase of the horizontally polarized component of the field, and magnitude and phase of the vertically polarized component of the field. All values are stored in fixed-length 11-digit fields in ASCII_REAL format. Fields in the table are separated by commas; each line in the table is delimited by an ASCII blank and an ASCII carriage-return line-feed pair. These data were provided by Fred Domer of the Clementine Project." OBJECT = COLUMN COLUMN_NUMBER = 1 NAME = "THETA" DATA_TYPE = ASCII_REAL START_BYTE = 1 BYTES = 11 FORMAT = "F11.6" UNIT = DEGREE DESCRIPTION = "The angle from the positive x-axis (arccos{R.X/|R|}, where R.X denotes the scalar product between R and X). Since the high-gain antenna boresight is along the negative x-axis, THETA is the supplement of the HGA cone angle. The angle from the HGA boresight is 180-THETA degrees." END_OBJECT = COLUMN OBJECT = COLUMN COLUMN_NUMBER = 2 NAME = "PHI" DATA_TYPE = ASCII_REAL START_BYTE = 13 BYTES = 11 FORMAT = "F11.6" UNIT = DEGREE DESCRIPTION = "The HGA clock (azimuthal) angle to probe position R, measured positive from the spacecraft negative z-axis direction toward the spacecraft negative y-axis direction. That is, PHI= 0 deg negative z-axis PHI= 90 deg negative y-axis PHI=180 deg positive z-axis PHI=270 deg positive y-axis" END_OBJECT = COLUMN OBJECT = COLUMN COLUMN_NUMBER = 3 NAME = "HORIZONTAL MAGNITUDE" DATA_TYPE = ASCII_REAL START_BYTE = 25 BYTES = 11 FORMAT = "F11.6" UNIT = "DECIBEL RELATIVE TO ISOTROPIC" DESCRIPTION = "The magnitude of the linear field component polarized in the horizontal (H) direction." END_OBJECT = COLUMN OBJECT = COLUMN COLUMN_NUMBER = 4 NAME = "HORIZONTAL PHASE" DATA_TYPE = ASCII_REAL START_BYTE = 37 BYTES = 11 FORMAT = "F11.6" UNIT = DEGREE DESCRIPTION = "The phase of the linear field component polarized in the horizontal (H) direction." END_OBJECT = COLUMN OBJECT = COLUMN COLUMN_NUMBER = 5 NAME = "VERTICAL MAGNITUDE" DATA_TYPE = ASCII_REAL START_BYTE = 49 BYTES = 11 FORMAT = "F11.6" UNIT = "DECIBEL RELATIVE TO ISOTROPIC" DESCRIPTION = "The magnitude of the linear field component polarized in the vertical (V) direction." END_OBJECT = COLUMN OBJECT = COLUMN COLUMN_NUMBER = 6 NAME = "VERTICAL PHASE" DATA_TYPE = ASCII_REAL START_BYTE = 61 BYTES = 11 FORMAT = "F11.6" UNIT = "DEGREE" DESCRIPTION = "The phase of the linear field component polarized in the vertical (V) direction." END_OBJECT = COLUMN END_OBJECT = TABLE END A.2.4 Example Transponder Data Label File CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 64 FILE_RECORDS = 5575 ^TABLE = "XPNDR233.TAB" DATA_SET_ID = "CLEM1-L-RSS-1-BSR-V1.0" PRODUCT_ID = "XPNDR233.TAB" SPACECRAFT_NAME = CLEMENTINE_1 INSTRUMENT_ID = RSS TARGET_NAME = MOON PRODUCT_CREATION_TIME = 1995-04-13T16:45:00.000 MISSION_PHASE_NAME = "LUNAR MAPPING" START_TIME = 1994-04-09T17:47:59.350 STOP_TIME = 1994-04-09T20:05:01.000 OBJECT = TABLE INTERCHANGE_FORMAT = ASCII ROWS = 5575 COLUMNS = 5 ROW_BYTES = 64 DESCRIPTION = "This table provides information on Clementine auxiliary oscillator temperature and transmitter output power during bistatic radar experiments. Values in the table are based on engineering data in the spacecraft telemetry stream; they have been checked for the APPEARANCE of correctness, but they have not been rigorously calibrated against pre-launch and other laboratory data. Quantities in the table include the date and time of the telemetered values, the oscillator temperature and output power from transponder unit A, and the oscillator temperature and output power from transponder B. These data were provided by Chris Lichtenberg of the Clementine Project." OBJECT = COLUMN COLUMN_NUMBER = 1 NAME = "TIME" DATA_TYPE = TIME START_BYTE = 1 BYTES = 23 DESCRIPTION = "The spacecraft event time at which the engineering values were obtained." END_OBJECT = COLUMN OBJECT = COLUMN COLUMN_NUMBER = 2 NAME = "TRANSPONDER A AUX OSC TEMPERATURE" DATA_TYPE = ASCII_REAL START_BYTE = 25 BYTES = 8 FORMAT = "F8.3" UNIT = KELVIN INVALID = "999.999" DESCRIPTION = "The temperature of the auxiliary oscillator in Transponder A. The oscillator frequency is temperature dependent, but the relationship is not known." END_OBJECT = COLUMN OBJECT = COLUMN COLUMN_NUMBER = 3 NAME = "TRANSPONDER A POWER OUTPUT" DATA_TYPE = ASCII_REAL START_BYTE = 34 BYTES = 8 FORMAT = "F8.3" UNIT = "WATT" INVALID = "999.999" DESCRIPTION = "The output power of Transponder A. The power radiated by the antenna is this value reduced by 1 dB to account for transmission line losses. Negative values are also invalid, and generally indicate that the other transponder was active." END_OBJECT = COLUMN OBJECT = COLUMN COLUMN_NUMBER = 4 NAME = "TRANSPONDER B AUX OSC TEMPERATURE" DATA_TYPE = ASCII_REAL START_BYTE = 43 BYTES = 8 FORMAT = "F8.3" UNIT = KELVIN INVALID = "999.999" DESCRIPTION = "The temperature of the auxiliary oscillator in Transponder B. The oscillator frequency is temperature dependent, but the relationship is not known." END_OBJECT = COLUMN OBJECT = COLUMN COLUMN_NUMBER = 5 NAME = "TRANSPONDER B POWER OUTPUT" DATA_TYPE = ASCII_REAL START_BYTE = 52 BYTES = 8 FORMAT = "F8.3" UNIT = "WATT" INVALID = "999.999" DESCRIPTION = "The output power of Transponder B. The power radiated by the antenna is this value reduced by 1 dB to account for transmission line losses. Negative values are also invalid, and generally indicate that the other transponder was active." END_OBJECT = COLUMN END_OBJECT = TABLE END A.3 Examples Files from CATALOG Directory A.3.1 Example CATINFO.TXT File CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 1995-04-18 NOTE = "Description of contents of CATALOG directory " END_OBJECT = TEXT END The CATALOG directory contains mission, host, instrument, reference, personnel, and data set PDS catalog objects for this archive volume. The files follow the 'streamlined' format adopted by the Planetary Data System (PDS) in late 1993 and documented in the Planetary Data System Standards Reference (Version 3.1, 3 August 1994; JPL D-7669, Part 2). Each catalog object is in ASCII, with a maximum of 80 characters per line. Each line is delimited with a carriage- return (ASCII 13) line-feed (ASCII 10) pair in positions 79-80. The templates are: MISSION.CAT A brief description of the mission. It includes a chronology of events, definition of mission phases, and science objectives. INSTHOST.CAT A description of the Clementine spacecraft and a very brief overview of the NASA Deep Space Network. INST.CAT An overview of the spacecraft radio system used for these experiments on Clementine, and a summary (albeit long) description of the Deep Space Network instrumentation which support radio science experiments. REF.CAT A listing of references used elsewhere in the streamlined templates and of references that might be generally useful in working with these data. PERSON.CAT A listing of key people involved in analyzing the radio data and in producing the archival data set. DATASET.CAT A description of the data set contained in the archival volumes. The file includes information on the two primary data types included in the archive collection -- the ODR and the TDF. Brief discussions of the quality of the data are included where a judgment can be made. The data types [and their directory names in the archive volume] are: Original Data Record (DSP tape) files [ODR] (Archival) Tracking Data Files [TDF] Link Monitor and Control log files [LMC] A.4 Example Files from DOCUMENT Directory A.4.1 Example DOCINFO.TXT File CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 1995-04-18 NOTE = "Description of contents of DOCUMENT directory" END_OBJECT = TEXT END The DOCUMENT directory holds PDS Documentation files. Documents are in plain unmarked ASCII text. All files in the DOCUMENT directory have attached PDS labels. The following files have a maximum of 72 ASCII characters per line. The next-to-last and last characters in each line are the carriage-return (ASCII 13) and line-feed (ASCII 10). The first two lines together contain 72 characters; all other lines are exactly 72 characters long. DOCINFO.TXT (this file): A description of the contents of the DOCUMENT directory. LMC.TXT: A description of the Link Monitor and Control log files. RSC11_11.TXT: Software Interface Specification for the DSN open-loop receiver Original Data Record. The following files have a maximum of 80 ASCII characters per line. The next-to-last and last characters in each line are the carriage-return (ASCII 13) and line-feed (ASCII 10). The first two lines together contain 80 characters; all other lines are exactly 80 characters long. ARC_SIS.TXT: Software Interface Specification for the Clementine bistatic radar raw data archive (this volume set of CD-WO media). DESCRIPT.TXT: A description of the Clementine bistatic radar experiment. TK_DESCR.TXT: A description of the contents and organization of the NAIF Toolkit. TK_FTP.TXT: Instructions on obtaining the NAIF Toolkit via Internet. This file also provides pointers to other documents which describe organization, installation, and installation of the Toolkit. TK_INSTL.TXT: A description of the installation of the NAIF Toolkit under a Sun operating system. The Sun description is representative; versions for other platforms are available from NAIF. TRK_2_25.TXT: Software Interface Specification for the DSN (Archival) Tracking Data File. A.5 Example Files from GEOMETRY Directory A.5.1 Example GEOMINFO.TXT FILE CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 1995-04-18 NOTE = "Description of contents of GEOMETRY directory" END_OBJECT = TEXT END The GEOMETRY directory holds NAIF SPK, SCLK, and CK files for Clementine bistatic radar experiments. Each file is a data module which can be read and interpreted using software provided by the PDS Navigation and Ancillary Information Facility (NAIF). That software is described briefly in TK_FTP.TXT, TK_DESCR.TXT, and TK_INSTL.TXT in the DOCUMENT directory. Each line in each SPK, SCLK, and CK file is delimited by an ASCII carriage-return line-feed pair. Users may need to remove one of these before using the file with the NAIF software. For example, most Unix users will need to convert the carriage-return line-feed pair to a single line-feed. After adaptation of the line delimiters for the local operating system, users will normally convert the file from its archival 'transfer' format to the local binary format using the NAIF utility SPACIT. SPK file names are of the form SPKyyddd.TSP. Detached PDS labels have names SPKyyddd.LBL. In each case yyddd represents the 2-digit year and 3-digit day-of-year on which the file starts. For the Clementine experiments yyddd = 94099, 94100, or 94113. CK file names are of the form CKyyddd.TCK. Detached PDS labels have names CKyyddd.LBL. In each case yyddd represents the 2-digit year and 3-digit day-of-year on which the file starts. For the Clementine experiments yyddd = 94099 or 94113. The SCLK file name is DSPSE002.TSC. It covers mission phases from Low Earth Orbit through Earth Phasing Loop B. A.5.2 Example CK Label File CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM DATA_RECORDS = 68488 SPACECRAFT_NAME = "CLEMENTINE 1" TARGET_NAME = MOON INSTRUMENT_ID = RSS DATA_SET_ID = "CLEM1-L-RSS-1-BSR-V1.0" PRODUCT_ID = "CK94099.TCK" FILE_NAME = "CK94099.TCK" PRODUCT_VERSION_ID = "1" PRODUCT_CREATION_TIME = 1995-04-04T09:06:56.000 MISSION_PHASE_NAME = "LUNAR MAPPING" SOFTWARE_NAME = "N/A" START_TIME = 1994-04-09T17:29:36.972 STOP_TIME = 1994-04-10T11:00:26.550 SPACECRAFT_CLOCK_START_COUNT = "N/A" SPACECRAFT_CLOCK_STOP_COUNT = "N/A" PRODUCER_ID = "NAIF" ^DESCRIPTION = "TK_FTP.TXT" NOTE = " (1) For archive, line delimiters were changed to ASCII carriage-return line-feed pairs. Most users will need to remove one or the other before using NAIF software with this file. (2) This file is stored on the archival volume in NAIF 'transfer' format. Users will normally want to convert it to local binary using the NAIF utility SPACIT before using it with Toolkit reader routines. (3) This file obtained in binary format (clemdef1-apr09.bck) from Mike Spencer of NAIF on 1995-04-04." END A.5.3 Example SCLK Label File (DSPSE002.LBL) CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM DATA_RECORDS = 73 SPACECRAFT_NAME = "CLEMENTINE 1" TARGET_NAME = MOON INSTRUMENT_ID = RSS DATA_SET_ID = "CLEM1-L-RSS-1-BSR-V1.0" PRODUCT_ID = "DSPSE002.TSC" FILE_NAME = "DSPSE002.TSC" PRODUCT_VERSION_ID = "1" PRODUCT_CREATION_TIME = 1994-01-18T00:00:00.000 MISSION_PHASE_NAME = {"LOW EARTH ORBIT", "EARTH PHASING LOOP A","LUNAR ORBIT INSERTION","LUNAR MAPPING", "LUNAR DEPARTURE","EARTH PHASING LOOP B"} SOFTWARE_NAME = "N/A" START_TIME = 1994-02-01T10:37:48.671 STOP_TIME = 1994-05-26T02:42:11.378 SPACECRAFT_CLOCK_START_COUNT = "N/A" SPACECRAFT_CLOCK_STOP_COUNT = "N/A" PRODUCER_ID = "NAIF" ^DESCRIPTION = "TK_FTP.TXT" NOTE = " (1) For archive, line delimiters were changed to ASCII carriage-return line-feed pairs. Most users will need to remove one or the other before using NAIF software with this file." END A.5.4 Example SPK Label File (SPK94099.LBL) CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM DATA_RECORDS = 26659 SPACECRAFT_NAME = "CLEMENTINE 1" TARGET_NAME = MOON INSTRUMENT_ID = RSS DATA_SET_ID = "CLEM1-L-RSS-1-BSR-V1.0" PRODUCT_ID = "SPK94099.TSP" FILE_NAME = "SPK94099.TSP" PRODUCT_VERSION_ID = "1" PRODUCT_CREATION_TIME = 1995-04-11T22:00:00.000 MISSION_PHASE_NAME = "LUNAR MAPPING" SOFTWARE_NAME = "N/A" START_TIME = 1994-04-09T07:10:40.000 STOP_TIME = 1994-04-10T07:23:20.000 SPACECRAFT_CLOCK_START_COUNT = "N/A" SPACECRAFT_CLOCK_STOP_COUNT = "N/A" PRODUCER_ID = "NAIF" ^DESCRIPTION = "TK_FTP.TXT" END A.6 Example Files from INDEX Directory A.6.1 Example INDXINFO.TXT File CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 1995-04-17 NOTE = "Description of contents of INDEX directory" END_OBJECT = TEXT END The INDEX directory contains an index for this CD-WO volume (INDEX.TAB) and a cumulative index for the volume set (CUMINDEX.TAB). Accompanying each *.TAB file is a PDS label (INDEX.LBL and CUMINDEX.LBL, respectively). The *.TAB files are ASCII files. Each line (or record) in the *.TAB file contains information about a single data file in the BSR-RDA volume. Each line is made up of nine comma-delimited fixed- length fields. Most fields contain character strings, which are enclosed by double quotes. Other fields contain integer data, which are NOT enclosed by quotes. The *.LBL label files describe the format and content of each of the respective *.TAB files at the byte level. Simply stated, the fields are: number of the CD-WO volume path name to the PDS detached label for each data file unique file name for the data file within this data set start date/time of the data in the file stop date/time of the data in the file creation date/time for the original file A.6.2 Example INDEX.LBL File CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 118 FILE_RECORDS = 7 ^INDEX_TABLE = "INDEX.TAB" OBJECT = INDEX_TABLE INTERCHANGE_FORMAT = ASCII ROWS = 7 ROW_BYTES = 118 COLUMNS = 6 INDEX_TYPE = SINGLE INDEXED_FILE_NAME = {"ODR/*.LBL", "TDF/*.LBL", "LMC/*.LBL"} SPACECRAFT_NAME = "CLEMENTINE 1" TARGET_NAME = "MOON" INSTRUMENT_NAME = "RADIO SCIENCE SUBSYSTEM" DATA_SET_ID = "CLEM1-L-RSS-1-BSR-V1.0" DESCRIPTION = "INDEX.TAB lists all data files in this volume. Rows in this table contain 115 bytes of table data followed by one byte of blank spare and the pair." OBJECT = COLUMN NAME = VOLUME_ID DATA_TYPE = "CHARACTER" START_BYTE = 2 BYTES = 7 COLUMN_NUMBER = 1 DESCRIPTION = "The volume containing this data file." END_OBJECT = COLUMN OBJECT = COLUMN NAME = FILE_SPECIFICATION_NAME DATA_TYPE = "CHARACTER" START_BYTE = 12 BYTES = 16 COLUMN_NUMBER = 2 DESCRIPTION = "Pathname to the detached label which identifies this data file." END_OBJECT = COLUMN OBJECT = COLUMN NAME = PRODUCT_ID DATA_TYPE = "CHARACTER" START_BYTE = 31 BYTES = 12 COLUMN_NUMBER = 3 DESCRIPTION = "The name of the data file, which is unique within this data set." END_OBJECT = COLUMN OBJECT = COLUMN NAME = START_TIME DATA_TYPE = "TIME" START_BYTE = 45 BYTES = 23 COLUMN_NUMBER = 4 DESCRIPTION = "Earliest valid time within the data file." END_OBJECT = COLUMN OBJECT = COLUMN NAME = STOP_TIME DATA_TYPE = "TIME" START_BYTE = 69 BYTES = 23 COLUMN_NUMBER = 5 DESCRIPTION = "Latest valid time within the data file." END_OBJECT = COLUMN OBJECT = COLUMN NAME = PRODUCT_CREATION_TIME DATA_TYPE = "TIME" START_BYTE = 93 BYTES = 23 COLUMN_NUMBER = 6 DESCRIPTION = "Time at which the data file was created." END_OBJECT = COLUMN END_OBJECT = INDEX_TABLE END A.7 Example LMC Label File CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM DATA_RECORDS = 1295 SPACECRAFT_NAME = CLEMENTINE_1 TARGET_NAME = MOON INSTRUMENT_ID = RSS DATA_SET_ID = "CLEM1-L-RSS-1-BSR-V1.0" PRODUCT_ID = "06463100.LMC" FILE_NAME = "06463100.LMC" PRODUCT_VERSION_ID = "1" PRODUCT_CREATION_TIME = 1994-04-10T10:58:00.000 MISSION_PHASE_NAME = "LUNAR MAPPING" START_TIME = 1994-04-10T08:29:56.000 STOP_TIME = 1994-04-10T10:58:00.000 SPACECRAFT_CLOCK_START_COUNT = "N/A" SPACECRAFT_CLOCK_STOP_COUNT = "N/A" PRODUCER_ID = "DSN" DSN_STATION_NUMBER = 63 ^DESCRIPTION = "LMC.TXT" NOTE = " " END A.8 Example ODR Label File CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 4166 FILE_RECORDS = 24000 SPACECRAFT_NAME = "CLEMENTINE 1" TARGET_NAME = "MOON" INSTRUMENT_ID = RSS DATA_SET_ID = "CLEM1-L-RSS-1-BSR-V1.0" PRODUCT_ID = "40991748.ODR" FILE_NAME = "40991748.ODR" PRODUCT_VERSION_ID = "1" PRODUCT_CREATION_TIME = 1994-04-09T18:04:44.000 MISSION_PHASE_NAME = "LUNAR MAPPING" SOFTWARE_NAME = "DSPR-5205-OP-F.0V9.9" START_TIME = 1994-04-09T17:48:45.000 STOP_TIME = 1994-04-09T18:04:44.000 SPACECRAFT_CLOCK_START_COUNT = "N/A" SPACECRAFT_CLOCK_STOP_COUNT = "N/A" PRODUCER_ID = "DSN" DSN_STATION_NUMBER = 14 ^DESCRIPTION = "RSC11_11.TXT" END A.9 Example TDF Label File CCSD3ZF0000100000001NJPL3IF0PDSX00000001 PDS_VERSION_ID = PDS3 RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 8064 FILE_RECORDS = 1220 SPACECRAFT_NAME = "CLEMENTINE 1" TARGET_NAME = MOON INSTRUMENT_ID = RSS DATA_SET_ID = "CLEM1-L-RSS-1-BSR-V1.0" PRODUCT_ID = "94095113.TDF" FILE_NAME = "94095113.TDF" PRODUCT_VERSION_ID = "1" PRODUCT_CREATION_TIME = 1994-05-18T00:00:00.000 MISSION_PHASE_NAME = "LUNAR MAPPING" START_TIME = 1994-04-05T17:03:00.000 STOP_TIME = 1994-04-24T00:00:00.000 SPACECRAFT_CLOCK_START_COUNT = "N/A" SPACECRAFT_CLOCK_STOP_COUNT = "N/A" PRODUCER_ID = "DSN" DSN_STATION_NUMBER = {12,14,16,42,43,46,61,63,66} ^DESCRIPTION = "TRK_2_25.TXT" NOTE = "The data file contains only Tracking Data Logical Records. The File Identification Record and Transponder Record are missing." END