PDS_VERSION_ID = PDS3
RECORD_TYPE = STREAM
OBJECT = TEXT
PUBLICATION_DATE = 2009-02-04
NOTE = "AAREADME.TXT describes this archive product."
END_OBJECT = TEXT
END
2001 Mars Odyssey
Martian Radiation Environment Experiment (MARIE)
Planetary Plasma Interactions Discipline Node
of the
Planetary Data System
==============================================================================
Introduction
==============================================================================
This volume contains the reduced data from the Martian Radiation
Environment Experiment (MARIE) aboard the 2001 Mars Odyssey spacecraft,
submitted to the Planetary Data System (PDS).
Users are encouraged to provide comments back to the PPI Node of the PDS
if errors or omissions are found either in data or in documentation.
Please send comments by e-mail or U.S. mail to PDS Operator as defined
at the end of this document.
==============================================================================
Brief Volume Description
==============================================================================
This archive volume contains MARIE data from the Mars Odyssey
mission. All data files are stored in the "DATA" branch of the
directory tree.
Documentation for this volume is located in the CATALOG and DOCUMENT
directories. In CATALOG, the data set is documented as part of the
archive (*DATASET.CAT); so are the MARIE instrument (INST.CAT), the Mars
Odyssey mission (MISSION.CAT) and spacecraft (INSTHOST.CAT), the
MARIE team and other personnel (PERSON.CAT), and useful literature
references (REF.CAT). Among the documents in the DOCUMENT directory
is the Volume Software Interface Specification (VOLSIS.*), which
provides detailed information about the volume's nature, contents and
structure. (This document pertains to an earlier release of the
archive, but it still may be useful for users of the present archive.)
Some documents are presented in multiple formats, indicated
by filenames having the same name with different extensions.
All data files on this volume are described by detached PDS labels (.LBL)
and format files (.FMT). Metadata are stored as text files with the
data. Information on the particular form of metadata used in the PDS
catalog can be found in the CATALOG directory.
==============================================================================
Volume Contents and Structure
==============================================================================
This section describes the volume structure and naming conventions.
Below is a tree diagram of the volume, followed by a description of the
directory function and key files in each directory.
Root directory
|
|- AAREADME.TXT Describes volume contents, organization and
| use (this file).
|
|- ERRATA.TXT Describes known deficiencies or caveats in the data
| on this volume.
|
|- VOLDESC.CAT High-level description of volume contents.
|
|
|- [CATALOG] Information on data sets and how they are processed
| and produced. Also contains information regarding
| Mars Odyssey, the MARIE instrument, personnel
| involved, and relevant literature.
|
|- [DATA] Contains all data in a branching tree structure of
| subdirectories, arranged by year and month.
| Also contains a subdirectory of ancillary data
| (not part of the calibrated dataset).
|
|- [DOCUMENT] Contains documents describing the data on the
| volume. These include VOLSIS.*, which gives
| detailed information about the volume.
| (Documents are presented in multiple formats,
| identical in content except for features
| impractical to represent in ASCII versions.)
|
|- [EXTRAS] Contains files potentially useful, but not required,
| for the end user's understanding of the data.
| (May not be present on the final archive.)
|
|- [GEOMETRY] Contains a table of spacecraft trajectory data
| and SPICE kernel files.
|
|- [INDEX] Contains a table of contents for all files located
| on the volume and the volume series to date.
|
==============================================================================
File Formats
==============================================================================
The data files on this volume include both binary and ASCII text files.
All data files are described by detached PDS labels. A detached label
file has the same name as the data file that it describes, but with the
extension .LBL. For example, a file named 98097.STS would be accompanied
by the detached label file 98097.LBL in the same directory. File names
within this archive comply with the "8.3" convention to conform with the
ISO-9660 standard.
All ASCII documents, detached PDS labels, and text files are stream
format files, with a carriage return (ASCII 13) and a line feed
character (ASCII 10) at the end of the record. This allows the files
to be read by MacOS, DOS, Windows, UNIX, and VMS operating systems.
UNIX system users will see an unnecessary carriage return character
(^M) at the end of each line. Mac users will see an unnecessary line
feed character (^J) at the start of each line.
ASCII tabular data files (*.TAB) are formatted so that they may
be read directly into many database management systems (DBMS) or
spreadsheet programs on various computers. All fields are of fixed
length and are separated by white space (blank characters or commas).
Character fields are left justified, and numeric fields are
right justified. The "start byte" and "bytes" values listed in a PDS
label do not include the white space between fields. The records are
of 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 normal text file on other computers.
The document, PDS label, and ASCII table files on this volume can
be viewed with a Web browser. Note that to view these files, the
browser may need to be configured to recognize files with extensions
of .LBL and .TAB as text files.
PDS labels are object-oriented. The object to which the label
refers (e.g., SERIES, TABLE, etc.) is denoted by a statement of
the form:
^object = location
in which the caret character (^, also called a pointer in this
context) indicates that the object starts at the given location. For
an object in the same file as the label, the location is an integer
representing the starting record number or byte of the object (the first
record/byte in the file is 1). For an object located outside the
label file, the location denotes the name of the file containing the
object, along with the starting record or byte number. For example:
^SERIES = ("20903684.DAT", 3)
indicates that the SERIES object begins at record 3 of the file
20903684.DAT, in the same directory as the detached label file. Below
is a list of the possible formats that use the ^object keyword.
^object = n
^object = n❮BYTES❯
^object = ("filename.ext",n)
^object = ("[dirlist]filename.ext",n)
^object = ("filename.ext",n❮BYTES❯)
^object = ("[dirlist]filename.ext",n❮BYTES❯)
where n is the starting record or byte number of the object,
counting from the beginning of the file (record 1,
byte 1); default is record number.
❮BYTES❯ indicates that number given is in units of bytes.
filename upper-case file name.
ext upper-case file extension.
dirlist* period-delimited path-list of parent directories,
in upper case, that specifies the object file
directory (used only when the object is not in the
same directory as the label file).
* All PDS labels on this volume are located in the same directory as
the file they describe so this construct is not used here.
In cases where many files of the same format or structure are present,
the structure description component is detached from the primary label.
This minimizes repeating information which does not vary from file to
file. In these cases, a format file (.FMT) contains the file structure
information and the base label (.LBL) describes the parameters which
generally do vary from file to file (number of records, file name,
start/stop time, etc.). When a format file is used within the PDS
label, the syntax is:
^STRUCTURE = filename
Example:
^STRUCTURE = "EDRHDR.FMT"
Syntactically, the contents of the format file can be inserted directly
into the base label such that the entire file contents replace the single
line ^STRUCTURE = filename.
==============================================================================
Errata
==============================================================================
There is a file called ERRATA.TXT found at the root level of this volume
which contains a list of known deficiencies or caveats associated with
data on this volume at the time this volume was published.
If you find an error on this volume, please report the error to the PDS
Operator at the PPI Node of the PDS.
Email pds_operator@igpp.ucla.edu
Telephone (310) 206-6073
U.S. Mail PDS Operator
c/o Dr. Raymond Walker
UCLA - IGPP
Los Angeles, CA 90095-1567
Only through support and feedback of the users of these data can an
effective errata list be maintained.
==============================================================================
Contacts
==============================================================================
PPI personnel who may be aware of issues related to this volume
include Mr. Steven Joy, the PPI Node Data Administrator, and
Dr. Raymond Walker, the PDS/PPI Node manager. For questions or
problems regarding this dataset, please contact the PPI PDS operator:
Email pds_operator@igpp.ucla.edu
Telephone (310) 206-6073
U.S. Mail PDS Operator
c/o Dr. Raymond Walker
3845 Slichter Hall
UCLA - IGPP
Los Angeles, CA 90095-1567
For questions regarding PDS Standards or other data available from the
PDS, please contact PDS Operator at the PDS Engineering Node (at JPL):
Email pds_operator@jpl.nasa.gov
Telephone (818) 354-4321
U.S. Mail Planetary Data System, PDS Operator
Jet Propulsion Laboratory
Mail Stop 202-101
4800 Oak Grove Dr.
Pasadena, CA 91109-8099
The PDS, and the Planetary Plasma Interactions (PPI) Node in particular,
assume no legal liability for errors on this volume. All users are encouraged
to verify the "correctness" of the data prior to submitting any publications
or other work based on these data. Errors on this volume should be reported
back to the PPI Node of the PDS through the ERRATA reporting procedures
described above.
|