PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 2000-03-17 NOTE = "AAREADME.TXT describes this volume." END_OBJECT = TEXT END Volume GOMW_5001 Galileo Orbiter Magnetospheric Working Group (MWG) Io/J0 Collection Planetary Plasma Interactions Discipline Node of the Planetary Data System ============================================================================ Brief Disk Description ============================================================================ This disk contains the Jupiter Approach and 0 Orbit data (includes Io flyby) from the Galileo Orbiter Magnetospheric Working Group (MWG) submitted to the Planetary Data System (PDS). The Magnetospheric Working Group consists of the Energetic Particle Detector (EPD), Magnetometer (MAG), Plasma Analyzer (PLS), Plasma Wave Subsystem (PWS), Dust Detector (DDS), and Heavy Ion Counter (HIC) instrument teams. In addition, the Ultraviolet Spectrometer (UVS) is considered to be an MWG instrument when auroral images are being acquired. There are no UVS or other auroral images on this CD-ROM. The Galileo spacecraft and some science instruments were reprogrammed after arrival at Jupiter so that data acquisition and downlink could be achieved at the low bit rates associated with mission after the high gain antenna (HGA) anomaly (see INSTHOST.CAT file in the CATALOG directory). New software was telemetered to the spacecraft in early May 1996 in a period known as the "Inflight Load" or IFL. The mission prior to the IFL is known as the Phase 1 mission. After the IFL the mission is referred to as the Phase 2 mission. In Phase 1 raw data were provided to the instrument teams in Experiment Data Record (EDR) format. In Phase 2, the whole telemetry stream and ground data system were changed. The raw data were "packetized" and delivered electronically as packet files or instrument packet files (IPF). The difference between a packet file and an IPF is a single 44 byte header called an SFDU. The Io data stored on this volume were acquired during Phase 1 and downlinked after the IFL by using the new capabilities of the Phase 2 flight software. As such, they are a hybrid form of data that were acquired by using flight software that may differ from other files of the same raw data format. This is primarily of concern when instrument reprogramming has resulted in a change in the contents of the raw data (i.e. MAG). This volume contains data from the Jupiter Approach (MAG and DDS only) mission phase (Nov 6, 1995 through Dec 6, 1995), the Io 0 Encounter phase (Dec 7-8, 1995), and the remainder of the Jupiter 0 Orbit (Dec 9, 1995 through June 22, 1996). The Jupiter 0 Orbit data set are primarily real-time science (RTS) data acquired shortly after the in-flight load, however, some MAG data acquired earlier are also included. The time interval in Jupiter 0 Orbit where all MWG instruments (except HIC) acquired RTS data was May 23 - June 1, 1996. The spacecraft software to create HIC RTS data was not included in the initial in-flight load delivery. There were no remote sensing observations during the Io flyby in J0. All data files are stored in the "DATA" branch of the directory tree. Each instrument is given a subdirectory and each data set is located in a subdirectory beneath that. Most data are stored in ASCII tables although some binary data are also included. All files give time values in Spacecraft Event Time (SCET). Some files may give an additional time column that contains the Earth Receive Time (ERT) in addition the the SCET. All data files on this CD-ROM are described by detached PDS labels (.LBL). When there are multiple data files with the same structure in a single directory, the format portion of the PDS label is further detached into a format file (.FMT). In general, there is a brief description of each data set collocated with the data files in a file called INFO.TXT. Documentation formatted for inclusion in the PDS catalog can be found in the CATALOG directory. Additional documentation is generally located in the DOCUMENT directory. In particular, all of the Space Science Reviews (SSR) instrument papers can be found in subdirectories of the DOCUMENT directory. The documents are reprinted by permission of Kluwer Academic Publishers, Dordrecht, Boston, London. Users of these data are encouraged to acknowledge both the PDS and the principal investigators of the instruments whose data is used in analysis in all publications. ============================================================================ Volume Set Information ============================================================================ This CD-ROM is the first volume of the GOMW_50xx set. This volume set is designed to facilitate the correlative analysis of the fields and particles data sets acquired during Jupiter orbital operations. Data from all of the primary MWG instruments are included on each volume. The first volume of this set is being produced on CDROM. Subsequent volumes will be created on DVDROM or DVD-R media. Data volumes are organized chronologically. Each DVD volume will contain several orbits of data. ============================================================================ Mission Facts ============================================================================ The Galileo orbits were named by concatenating the first letter of the name of the primary target in each orbit with the orbit number. Thus, the fourth Jupiter orbit, in which Europa is the primary target, is called E4. The project defined orbits according to spacecraft command load boundaries rather than the normal convention of apoapsis to apoapsis. The navigation team did not always adhere to this convention, causing some confusion. The PDS has organized the data and data delivery schedules around the project defined orbit boundaries. The following tables contain information about the orbital tour and satellite encounters: ____________________________________________________________________________ Galileo Prime Mission Orbit Information ____________________________________________________________________________ Orbit Orbit Periapsis Orbit Start End Range** Periapsis Date/Time* Date/Time* (Rj)*** Date/Time* ____________________________________________________________________________ J0 1995-12-03T00:00:00 1996-06-23T00:00:00 4.00 1995-12-07T21:53:44 G1 1996-06-23T00:00:00 1996-09-01T00:00:00 11.03 1996-06-28T00:31:26 G2 1996-09-01T00:00:00 1996-11-02T00:00:00 10.65 1996-09-07T13:37:54 C3 1996-11-02T00:00:00 1996-12-15T00:00:00 9.21 1996-11-06T13:31:07 E4 1996-12-15T00:00:00 1997-02-16T00:00:00 9.16 1996-12-19T03:21:58 J5**** N/A N/A 9.05 1997-01-20T00:26:57 E6 1997-02-16T00:00:00 1997-03-30T00:00:00 9.12 1997-02-20T20:54:15 G7 1997-03-30T00:00:00 1997-05-04T00:00:00 9.12 1997-04-04T11:03:38 G8 1997-05-04T00:00:00 1997-06-22T00:00:00 9.27 1997-05-08T11:41:46 C9 1997-06-22T00:00:00 1997-09-14T00:00:00 10.77 1997-06-27T11:52:22 C10 1997-09-14T00:00:00 1997-11-02T00:00:00 9.17 1997-09-18T23:10:00 E11 1997-11-02T00:00:00 1997-12-15T00:00:00 8.97 1997-11-07T00:42:01 * Spacecraft event time (UTC) provided. ** Range is measured from the center of mass. *** Rj = 71492 km. **** There was no targeted encounter in orbit 5, thus the primary target is Jupiter. There is little or no data available from this orbit because of a superior conjunction. ___________________________________________________________________________ Prime Mission Satellite Flyby Geometry at Closest Approach ___________________________________________________________________________ Moon-centric* Sys III Local Date/Time Altitude** Lat E.Long W.Long Time Flyby Orbit (UTC) (km) (deg) (deg) (deg) (hh:mm) Descr ___________________________________________________________________________ Io 1995-12-07T17:45:58 896 -9.6 258.9 273.3 11:50 wake xing G1 1996-06-27T06:29:07 838 30.4 246.7 174.9 11:15 wake xing G2 1996-09-06T18:59:34 264 79.3 236.4 158.0 10:46 polar C3 1996-11-04T13:34:28 1138 13.2 282.3 242.9 07:48 wake xing E4 1996-12-19T06:52:58 688 -1.7 322.4 156.8 16:42 wake xing*** J5 N/A N/A N/A N/A N/A N/A E6 1997-02-20T17:06:10 582 -17.0 34.7 341.7 12:59 wake xing G7 1997-04-05T07:09:58 3104 55.8 270.4 19.8 19:44 wake xing G8 1997-05-07T15:56:10 1606 28.3 84.8 286.7 08:06 upstream C9 1997-06-25T13:47:50 421 2.0 101.0 59.9 05:32 upstream C10 1997-09-17T00:18:55 538 4.6 281.3 335.9 05:02 wake xing E11 1997-11-06T20:31:44 2039 18.1 172.3 217.6 10:53 wake xing*** * J2000 reference, body fixed spherical coordinates. ** Altitude assumes a spherical body where the following body radii have been assumed: Io = 1818 km Europa = 1560 km Ganymede = 2634 km Callisto = 2409 km *** Highly oblique crossing angle. ============================================================================ Volume Format Information ============================================================================ The disk is organized into a hierarchical directory structure. The disk is formatted according to both ISO 9660 and POSIX (UNIX) standards in order to accommodate users on a wide variety of platforms. This volume does not contain any Extended Attribute Records (XAR). Thus, VAX/VMS users may have some problems accessing files on this volume. ============================================================================ File Formats ============================================================================ The data files on this volume are a mix of ASCII text and binary 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, the file ATTITUDE.TAB is accompanied by the detached label file ATTITUDE.LBL in the same directory. File names within this archive comply with the "8.3" convention to conform with the ISO-9660 standard. All document, detached PDS labels, and HTML 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 and Macintosh users will see the unnecessary carriage return character (^M) at the end of each line. Mac users will see an unnecessary line feed (^J) character 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., TIME_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: ^TIME_SERIES = ("20903684.DAT", 3) indicates that the TIME_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 ^object = ("filename.ext",n) ^object = ("[dirlist]filename.ext",n) ^object = ("filename.ext",n) ^object = ("[dirlist]filename.ext",n) where n is the starting record or byte number of the object, counting from beginning of the file (record 1, byte 1); default is record number. 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 is not varying 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 (# 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 ============================================================================ Every effort has been made to assure that the data and documentation are of the best possible quality. However, mistakes are inevitable. The PPI Node of the PDS will maintain an online list of ERRATA where errors and updates are documented. Should any user of this product find an error on this volume, please report the error to the PPI Node so that the finding can be made public. All users are encouraged to verify the "correctness" of the data prior to submitting any publications or other work based on these data. 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 CD was published. Any changes or errors that are found on this or any GOMW_50xx CD-ROM after the production of this volume can be found via anonymous-ftp at ftp.igpp.ucla.edu. The account name is "anonymous" and the password should be your e-mail address (it's polite to leave an audit trail). Locate yourself in the PDS errata directory (cd pds/ERRATA/GOMW_50xx), and transfer the file ERRATA.TXT (get ERRATA.TXT). If you find an error on this disk, please report the error to the PDS Operator at the PPI Node of the PDS. Internet 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. ============================================================================ Software ============================================================================ The Planetary Plasma Interactions (PPI) Node of NASA's Planetary Data System (PDS) provides software to facilitate the location of the data of interest on CD-ROM data products, as well as software to convert data between architecture specific data formats. In addition, the PPI Node provides software which has been made available by individual projects which may be useful when working with PPI data. Non-PDS software is provided "as is" and is distributed by the PPI Node as a service to the community. The PWS team has provided software which can be found in the EXTRAS/SOFTWARE/USERSOFT directory of this disk. The PWS software (PWSLIST) will read the uncalibrated, binary data set and the calibration tables and will output calibrated data in ASCII table form. To obtain the most recent release of any PPI distributed software use anonymous FTP to connect to the PPI FTP server located at "ftp.igpp.ucla.edu". (Complete instructions on using FTP can be found in the EXTRAS/SOFTWARE directory in the file "FTP.TXT"). ============================================================================ Volume Contents and Structure ============================================================================ This section describes the volume structure and naming conventions. Below is a tree diagram of the CD-ROM, followed by a description of the directory function and key files in each directory. GOMW_5001 (root directory) | |- AAREADME.TXT Describes volume contents, organization and CD-ROM use | (this file) | |- ERRATA.TXT Describes known deficiencies or caveats in the data or | on this CD-ROM. | |- VOLDESC.CAT High level description of CD-ROM contents. | | |- [BROWSE] Contains browse plots depicting the data. | | | |- [MAG] Magnetometer data browse plots. | | | | | |- [APPROACH] Plots pertaining to approach. | | | | | |- [IO] Plots pertaining to Io. | | | | | |- [ORBIT_0] Plots pertaining to orbit 0. | | | |- [TRAJECT] Trajectory browse plots. | | | |- [IO] Plots pertaining to Io. | | | |- [JUPITER] Plots pertaining to Jupiter. | | |- [CALIB] Contains calibration information for the data sets. | | | |- [MAG] Calibration information for the MAG instrument. | | | |- [PLS] Calibration tables for the PLS instrument. | | | |- [PWS] Calibration tables for the PWS instrument. | | |- [CATALOG] Information on data sets and how they are processed and | produced. Also contains information regarding Galileo | orbiter, the instruments covered by this volume, personnel | involved, and references from various documents | including those contained in the /CATALOG and /DOCUMENT | directories. | |- [DATA] Contains all data in a branching tree structure of | | sub-directories. | | | |- [DDS] Contains the dust data submissions which are the complete | | table of impacts from 1989 - 1995, a table of high | | confidence impacts from 1996, raw impact data, calibration | | data, etc. | | | |- [EPD] Data sets from the Energetic Particle Detector (EPD) | | | | | |- [LRS] Low-Rate science data taken during the Io encounter | | | | | |- [RTS] Rate data taken during May to June, 1996 | | (Jupiter 0 Orbit) | | | |- [HIC] Data sets from the Heavy Ion Counter (HIC) | | | |- [MAG] Data sets from the Magnetometer (MAG) | | | | | |- [BROWSE] MAG browse data all have identical file structures | | | | but come from different mission phases and instrument | | | | configurations. Data are organized by mission phase. | | | | | | | |- [APPROACH] MAG browse data from the Jupiter Approach | | | | phase covering 11/6/95 - 12/6/95 which | | | | is well outside the first bow shock crossing | | | | to well inside the last magnetopause | | | | crossing. These data were all acquired in | | | | the optimal averager mode and returned by | | | | memory readout (MRO). | | | | | | | |- [IO] MAG browse data from the Io flyby which have | | | | been resampled from the high time resolution | | | | data. | | | | | | | |- [J0_ORBIT] MAG browse data from Jupiter Orbit 0 which | | | were acquired by either the optimal averager | | | or through the RTS procedure (special | | | application of Opt/Avg) after the IFL. | | | | | |- [HIGH_RES] MAG high time resolution data recorded | | | during the Io flyby. | | | | | |- [IO_MRO] MAG MRO data returned shortly after the Io | | | flyby. | | | | | |- [RAW_DATA] MAG Raw data products | | | | | |- [EDR] MAG EDR (phase 1) raw data files | | | | | |- [PKT] MAG packetized (phase 2) raw data files | | | |- [PLS] Data sets from the Plasma Instrument (PLS) | | | | | |- J0_EVNT.TXT A listing of various spacecraft and instrument | | | related events that affect the PLS data sets. | | | | | |- [BROWSE] PLS Browse spectra from selected detector | | | positions (look directions) from the Ion and | | | Electron detectors. | | | | | |- [RDR] PLS raw data reformatted into ASCII tables | | | with calibration tables provided. | | | | | |- [RAW] PLS raw data (phase 2) in packetized format. | | | |- [PWS] Data sets from the Plasma Wave Subsystem (PWS) | | | | | |- [IO_BRWSE] PWS browse data (E and B field) resampled | | | from data (ASCII) recorded during the Io | | | flyby and near Jupiter Orbit Insertion | | | (JOI). | | | | | |- [IO_LPW] PWS low rate science resolution data | | | recorded during the Io flyby and near | | | JOI. These data are in an uncalibrated, | | | compact binary form. Software is provided | | | that will apply calibration and output data | | | in ASCII tables. | | | | | |- [J0_RTS] PWS real time science (RTS) data acquired | | | during Jupiter orbit 0 after the IFL. These | | | data are in an uncalibrated, compact binary | | | form. Software is provided that will apply | | | calibration and output data in ASCII tables. | | | | | |- [WAVEFORM] PWS waveform (high rate) data | | | | | |- [10KHZ] Waveform data acquired at sampling frequency | | | | sufficient to resolve 10 kHz waves. Data are | | | | organized into a directory structure based | | | | on the spacecraft clock 6 most significant | | | | digits. The file naming convention in the | | | | subdirectories uses the 6 least significant | | | | digits of the S/C clock major frame (RIM) and | | | | and the 2 digits of the minor frame (mod 91) | | | | count. | | | | | | | |- [C032090] Data from 03209000:00 to 03209099:00 | | | | | | | |- [C032091] Data from 03209100:00 to 03209199:00 | | | | | | | |- [C032095] Data from 03209500:00 to 03209599:00 | | | | | |- [01KHZ] Waveform data acquired at sampling frequency | | | | sufficient to resolve 1 kHz waves. | | | | | | | |- [C032090] Data from 03209000:00 to 03209099:00 | | | | | | | |- [C032091] Data from 03209100:00 to 03209199:00 | | | | | | | |- [C032092] Data from 03209200:00 to 03209299:00 | | | | | | | |- [C032095] Data from 03209500:00 to 03209599:00 | | | | | | | | | |- [80KHZ] Waveform data acquired at sampling frequency | | | sufficient to resolve 80 kHz waves. | | | | | |- [C032090] Data from 03209000:00 to 03209099:00 | | | | | |- [C032091] Data from 03209100:00 to 03209199:00 | | | | | |- [C032092] Data from 03209200:00 to 03209299:00 | | | | | |- [C032095] Data from 03209500:00 to 03209599:00 | | | | | |- [C032096] Data from 03209600:00 to 03209699:00 | | | |- [TRAJECT] Spacecraft trajectory (ephemeris) data sets. | | | |- [IO_CRDS] Spacecraft trajectory data in 2 different | | coordinate systems: Io planetocentric and | | Io Phi-Omega. | | | |- [JUP_CRDS] Spacecraft trajectory data in 3 different | coordinate systems: System III, Jupiter Solar | Magnetospheric, and Jupiter Solar Equatorial. | |- [DOCUMENT] Contains instrument papers and other documents that will | | be useful when analyzing data. All SSR instrument | | description papers are copyrighted material reproduced | | here with permission of Kluwer Academic Publishers. | | | |- [DDS] | | | | | |- [SSR] Contains EPD instrument paper published in Space | | | Science Reviews in ASCII and HTML (with GIF images | | | of figures) formats | | | | | |- [GDDS] Contains updated descriptions relating to the | | data set contained on this volume in HTML format. | | | |- [EPD] Contains EPD instrument paper published in Space Science | | Reviews in ASCII and HTML (with GIF images of figures) | | formats | | | |- [HIC] | | | | | |- [SSR] Contains HIC instrument paper published in Space Science | | | Reviews in ASCII and HTML (with GIF images of figures) | | | formats | | | | | |- [TECH_DOC] Contains a technical document published at CalTech | | which describes the HIC data formats and | | processing. Available in ASCII and HTML | | (with GIF images of figures) formats | | | |- [MAG] Contains MAG instrument paper published in Space Science | | Reviews in ASCII and HTML (with GIF images of figures) | | formats | | | |- [PLS] Contains PLS instrument paper published in Space Science | | Reviews in ASCII and HTML (with GIF images of figures) | | formats | | | |- [PROJECT] Galileo project documentation describing raw telemetry | | | data files, formats, etc. | | | | | |- [ARSEF] As-Run Spacecraft event files (SEF) for Jupiter | | | Approach and Jupiter 0 Orbit mission phases. | | | | | |- [GLL3_280] Text, Postscript, and PDF format versions of the | | | Galileo Phase 1 and 2 documents describing EDR | | | data formats | | | | | |- [GLL3_310] Text (useless), Postscript, and PDF format | | | versions of Galileo ground system processing | | | and packet file creation and formats. | | | | | |- [GLL3_640] Text and HTML (with GIF images of figures) format | | | versions of the pages from the document that | | | describes the headers in the Phase 1 EDR raw data | | | files. | | | | | |- [SEF_SIS] Text, Postscript, and PDF format versions of the | | | SIS describing the SEF command files. | | | | | |- [SFDU_DOC] Text, Postscript, and PDF format versions of a | | particularly useful document put together by | | Betsy Wilson describing the various SFDU headers | | and packet types possible in the Phase 2 raw | | packetized data files. | | | |- [PWS] | | | | | |- [FRD] PWS Functional Requirements Document (ASCII and PDF) | | | | | |- [SSR] Contains PWS instrument paper published in Space Science | | Reviews in ASCII and HTML (with GIF images of figures) | | formats | | | |- [SPICE] Descriptions of the SPICE kernels related to this portion | of the Galileo Mission. |- [EXTRAS] | | | |- [HTML] HTML files that contain brief descriptions and links for | | most files on this volume. These files are designed to | | make navigation and browsing of this volume easier. | | | |- [SOFTWARE] | | | | | |- [PDS_SOFT] Software provided by PDS and PPI for use on | | | Windows95 (tm) platforms. | | | | | |- [USERSOFT] Software provided by the PWS team, executable | | is created for Sun Solaris 2.5 (source code | | provided) | | | |- [SPICE] | | | |- [ASCII] SPICE kernels in transfer form for PC, VAX, and | | other platforms that use the Carriage Return, | | Linefeed ASCII line termination | | characters. | | | |- [BINARY] SPICE kernels in the forms usable by software on | Unix or other platforms that use IEEE (MSB) | floating point and ASCII with the linefeed line | termination character. | |- [GEOMETRY] Contains information on Galileo Orbiter orientation and | trajectory. Also contains information on SPICE kernels | relating to this mission. | |- [INDEX] Contains a table of contents for all files located on the CD-ROM and the volume set to date. ============================================================================ Driver and Hardware Information ============================================================================ This disk has been formatted according to the ISO standard for CD-ROM production (9660) with level 1 compliance. Any system which complies with this standard (all of them should) should be able to access this disk. ============================================================================ Contacts ============================================================================ The person most directly responsible for the construction and release of this CD-ROM is Mr. Steven Joy. He was the PPI Node Data Administrator at the time this disk was created and understands as much about the disk structure and data organization as anyone. Other PPI personnel who may be aware of about issues related to this CD-ROM include Mr. Bill Harris, and Dr. Raymond Walker, the PDS/PPI Node manager. For questions or problems regarding this CD-ROM, please contact the PDS/PPI PDS operator: Internet 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 CD-ROM's available from the PDS, please contact PDS Operator at the PDS Central Node (at JPL): Internet 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 disk. 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 disk should be reported back to the PPI Node of the PDS through the ERRATA reporting procedures described above.