Raw Radio Science Data from the Voyager 1 Radio Occultation at Titan
Review facilitated by the Ring-Moon Systems Node of NASA PDS: Mia Mace, Matt Tiscareno
May, 2025
The data provider is Richard A. Simpson.
Background
This bundle contains open-loop radio receiver data collected at the
Madrid (Spain) 64-m antenna of the NASA Deep Space Network (DSS-63)
during the Voyager 1 encounter with Titan on day 1980/317. The data
include samples from receiver outputs at S-band (13 cm wavelength)
and X-band (3.6 cm) in right-circular polarization. Also included
are calibration measurements collected within a few hours of the
Titan observations.
123 original data tapes (known as Original Data Records, or ODRs)
were delivered to the Voyager Radio Science Team in the RSC-11-6
binary format. Each original tape forms the basis for a PDS4 product
here. Each PDS4 product includes the original binary file, ASCII
versions of the binary file, and a PDS4 detached label file written
in XML. There is one ASCII file with record header data and a
separate ASCII file with the receiver samples.
Record 1429 on original tape VJ6363 could not be read. A replacement
record has been created and substituted. All 5000 data samples in
that record have been set to 127 (approximately the mean sample
value). The Replacement Record Flag in that record header has been
set to 257. VJ6363 contains Recorder B SR data starting at 07:35:00.
Each ODR has been processed to give a 'browse' product with a
histogram of data sample values, a plot of average sample power, and
a plot of time-averaged power spectra. There are 123 browse products,
each in PDF/A-1b format.
Also included in the bundle are reconstructions of the spacecraft
trajectory and spacecraft high-gain antenna pointing, which was offset
during the Titan occultation to compensate for atmospheric refraction.
A receiver tuning file allows calculation of the exact received
frequency at the ground station. A document collection includes
a description of the Voyager mission, the radio science operations
plan for the Saturn/Titan encounter, documentation of the high-gain
antenna pointing reconstruction, and a Software Interface
Specification (SIS) for the archive bundle. Documentation of the
binary formats in the ODR and receiver tuning binary files, which
has been archived elsewhere in PDS, has been included by reference.
Note: This information is provided in the bundle's readme.txt
Data Bundle
The complete peer review bundle (voyager1_rss_titan_raw.tar.gz) is online here. Also provided are the checksum manifest and validation report; these latter two files are primarily for reviewers concerned with PDS4-compliance (see instructions below).
Reviewers should begin by reading the readme.txt file (top level of the bundle). The Software Interface Specification (SIS) is included in the document collection and provides detailed descriptions of the archive bundle.
The directory structure of the PDS4 bundle is illustrated below:
- voyager1_rss_titan_raw/
- readme.txt High-level overview of data set
- bundle_voyager1_rss_titan_raw.xmlLabel for bundle, describing members of the bundle and references etc
- browse/Directory containing browse products (images)
- collection_browse.csv List of browse product LIDVIDs (logical identifier with version ID), with first column designating whether it is a primary (P) or secondary (S) member
- collection_browse.xml Label for the associated collection file
- vg1t_*.pdf Quick look plots from radio science observations during the Voyager 1 Titan encounter
- vg1t_*.xml Labels for associated browse products
- calib_freq/Directory containing receiver tuning data and estimates of USO frequency for Vgr 1 & 2
- collection_calib_freq.csvList of calibration frequency LIDVIDs, with first column designating whether it is a primary or secondary member
- collection_calib_freq.xmlLabel for the associated collection file
- vg*.dat/vg*.tab/vg*.txtReceiver tuning data during the Vgr 1 Titan encounter and USO frequency estimates for Vgr 1, 2
- vg*.xmlLabels for associated files
- context/Directory containing context information related to the archive; such as spacecraft, instruments, targets etc.
- collection_context.csvList of context product LIDs, with first column designating whether it is a primary or secondary member
- collection_context.xmlLabel for the associated collection file
- data/Directory containing open loop receiver raw data for radio science observations during the Voyager 1 Titan encounter
- collection_data.csvList of data product LIDs, with first column designating whether it is a primary or secondary member
- collection_data.xmlLabel for the associated collection file
- vg1t_63*.datRaw Radio Science RSC-11-6 binary data
- vg1t_63*.tabRSC-11-6 ASCII Raw Data
- vg1t_63*.hdrRSC-11-6 Headers in ASCII
- vg1t_63*.xmlLabels for the associated data files
- document/Directory containing mission description, radio science operations plan, and the archive SIS
- collection_document.csvList of members of the document collection, with first column designating whether it is a primary or secondary member
- collection_document.xmlLabel for the associated collection file
- *.docx/*.pdf/*.txt Documents
- *.xml Labels for the associated documents
- geometry/Directory containing (non-SPICE) geometry data for radio science observations during the Vgr 1 Titan encounter
- collection_geometry.csv List of members of the geometry collection, with first column designating whether it is a primary or secondary member
- collection_geometry.xmlLabel for the associated collection file
- *.dat/*.tabCelestial Reference Set, High-Gain Antenna Pointing files
- *.xmlLabels for the associated geometry file
- software/Directory containing software files for documentation purposes
- collection_software.csv List of members of the software collection, with first column designating whether it is a primary or secondary member
- collection_software.xmlLabel for the associated collection file
- *.fFORTRAN 77 software written to manipulate data from radio science observations during Vgr 1 Titan encounter
- aareadme.txtASCII text file describing the contents of the software collection
- software.xmlLabel for the software files
- spice/Directory containing SPICE files
- collection_spice.csv List of members of the SPICE collection, with first column designating whether it is a primary or secondary member
- collection_spice.xmlLabel for the associated collection file
- vg1_titan.bspS- and P-kernel binary file, the SPICE component that contains ephemeris data for spacecraft and target bodies
- vg1_titan.xmlLabel for the SPICE kernel
Instructions for Reviewers
Here are guidelines and some information to help you produce an effective review with a reasonable level of effort.
All reviewers must address two general areas:
- Scientific merit of data (are these the proper data to be archived?),
- Usability of the data (appropriate formats; completeness of data set, including ancillary data; comprehensive documentation).
Furthermore, if you are one of the panel members with a direct affiliation with the PDS, please also address a third general area:
- Compliance with PDS4 Standards.
If you are not one of the panel members with a direct affiliation with the PDS, then you do not need to address compliance with PDS4 standards. Rather, you should focus on the data (including ancillary data) and documentation.
While it is not realistic for you to analyze every data file, please check enough to convince yourself of the quality and consistency of the data and of any errors that you encounter.
Please also evaluate the documentation provided in individual table labels, and referenced journal articles. Much of the information contained in the referenced articles is not duplicated in the data sets.
Questions for reviewers to address are:
- Documentation:
- Does the documentation explain the data and how they were produced?
- Does the documentation explain how to use the data?
- Is the documentation (including referenced journal articles) sufficient to ensure the data will be intelligible to a scientist 10, 20, or 50 years in the future?
- Data:
- Are you able to manipulate and plot the data, interpret columns into tables, and understand the context and relationships of the data products?
- Are there any concerns about the creation/generation, calibration (if appropriate), or general usability of the data?
- Is the archive design suitable (is the directory tree structured in a reasonable way)?
The review panel submits written reviews by email and then, if the RMS Node thinks it is necessary, participates in a teleconference (date TBD) to discuss the reviews, including strengths and weaknesses of the data set. Specific shortcomings and errors will be identified as "liens" – questions about or requests for change – which will need to be corrected. The review panel is responsible for making a recommendation on whether:
- The bundle/s passed peer review and can be archived, once a set of panel identified liens have been resolved.
- The material did not pass peer review, and must undergo an incremental (delta) review in certain specified areas.
- The material did not pass peer review, and must undergo another full peer review.
- The material did not pass peer review, and does not merit a second peer review.
In addition to an overall recommendation, the RMS Node will compile a list of liens in the archive design or sample products/bundle. The liens must be resolved before the associated data set can be archived.
Known Issues
RMS has run Validate v3.7.0 on the bundle, full report available here.
Summary:
268 product(s)
0 error(s)
6 warning(s)
Product Validation Summary:
268 product(s) passed
0 product(s) failed
0 product(s) skipped
268 product(s) total
Referential Integrity Check Summary:
268 check(s) passed
0 check(s) failed
0 check(s) skipped
268 check(s) total
Message Types:
6 warning.label.context_ref_mismatch
- 6
warning.label.context_ref_mismatch
Value: 'Equipment' Expected one of: '[Spacecraft]'
These refer to Voyager 1 being described as 'Equipment' rather than 'Spacecraft'. This is because Voyager 1 is the 'target' of spacecraft engineering 'observations'. That is, the onboard engineering system is monitoring the status of the spacecraft. So, even though Voyager 1 is participating in observations of Saturn, the engineering system doesn't know that; its target is the spacecraft itself.
RMS is submitting an SCR to discuss dual use context products for discussion within DDWG and CCB (in-prep).
These known issues will be resolved during lien resolution, along with any other issues raised by the reviewers and deemed reasonable/necessary.
Reviewers' Submitted Comments and Responses
Review Outcome
Ring-Moon Systems Node Home