Raw Radio Science Data from the Voyager 2 Radio Occultation at Uranus, collected at Canberra Observatory

Background

This bundle contains open-loop radio science raw data collected using NASA Deep Space Network antennas near Canberra, Australia, on January 24-25, 1986. The 64-m antenna (DSS-43) and the 34-m antenna (DSS-42) both received S-Band (13.1 cm wavelength) and X-band (3.6 cm wavelength) transmissions in right circular polarization from Voyager 2 during its encounter with Uranus (and its satellite Miranda).

The data include samples from all four receivers during the flyby of Miranda and during the occultations by the Uranian rings, ionosphere, and neutral atmosphere. Also included are calibration measurements collected a few hours prior to the Miranda and Uranus observations.

55 original binary data tapes -- known as Original Data Records (ODRs) -- were delivered to the Voyager Radio Science Team in a format specified by the DSN RSC-11-9 Software Interface Specification (SIS) (version dated 1 March 1985).

Each original ODR tape forms the basis for a PDS4 product in the bundle. The binary file is the first part of the product; but the binary data are in an archaic binary format, so they have been converted to ASCII tables for easier reading. In addition there is one ASCII table with record header data and a separate ASCII file with header labels for the ASCII record header data. Together, they can be used to create a spreadsheet with record header data.

There is a separate ASCII table/file for samples from each receiver -- 43SR, 42SR, 43XR, and 42XR. Future users will likely prefer to work with the ASCII files rather than the original binary file. Each product also includes a detached PDS4 label file written in XML. For example, the following eight files constitute one PDS4 product (from original tape UC0475):

Each *.tab file has been processed to give a 'browse' product -- a figure in JPEG format providing a snapshot of tape content and data quality. Each figure contains a histogram of data sample values, a line drawing of average sample power versus time, a waterfall plot of time-averaged power spectra, and labeling information.

Data Bundle

The complete peer review bundle (voyager2_rss_uranus_40mr_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:

Instructions for Reviewers

Here are guidelines and some information to help you produce an effective review with a reasonable level of effort.

• 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).

• Compliance with PDS4 Standards.

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 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

• 10 warning.label.context_ref_mismatch
  Four of 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).
  Six of these refer to a context product that has a typo (a new version has been submitted but not yet posted for 'DSS-42 34-m Radio Telescope').
• 1 warning.integrity.pds4_version_mismatch
  The Canberra files were developed under IM v1.23.0.0 while the re-used Parkes files (secondary members in calib_freq, document, and geometry collections) were developed under IM v1.21.0.0.

Reviewers' Submitted Comments and Responses

Review Outcome