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

Background

The bundle contains raw radio science data from the Voyager 2 radio occultation at Uranus, collected at Parkes Observatory (Australia). Data include sampled output from an X-band receiver connected to a right-circularly polarized antenna feed on the 64-m antenna. Also included are receiver tuning data, files containing reconstructed pointing of the spacecraft high-gain antenna, a trajectory reconstruction, and documentation.

The data provider is Richard A. Simpson.

Data Bundle

The complete peer review bundle (voyager2_rss_uranus_49xr_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 bundle_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

• 64476 warning.table.field_value_format_specifier_mismatch
  This affects two files: geometry/uh0003a.xml, geometry/uk0015a.xml.
  Seems to be because many fields in the table described by Table_Character have an incorrect specifier, for instance <field_format>%18.6d</field_format> instead of <field_format>%18.6f</field_format> for a floating point number such as "1138128900.000000". Refer to section 4B.1.2 Field Formats in the PDS4 Standards Reference for details of specifiers.
• 145 warning.label.context_ref_mismatch
 Value: ‘Voyager Mission’ Expected one of: ‘[VOYAGER]’
 Value: ‘NASA Deep Space Network’ Expected one of: ‘[Deep Space Network]’
 Value: ‘DSN Radio Science Instrumentation’ Expected one of: ‘[NASA Deep Space Network Radio Science]’
 Value: ‘DSN Instrumentation’ Expected one of: ‘[NASA Deep Space Network Radio Science]’
 Value: ‘Voyager 2 Radio Science Instrumentation’ Expected one of: ‘[RADIO SCIENCE SUBSYSTEM]’
 Value: ‘Voyager 2 Spacecraft Sensors’ Expected one of: ‘[Voyager 2 Engineering]’
These are due to discrepancies between what the <name> attribute in the <Investigation_Area>/<Observing_System_Component>s of the labels and what the corresponding context products have for their <Instrument>/<name> , <Facility>/<name> or <Instrument_Host>/<name>. PDS Engineering Node have said that they only match the <Instrument_Host>/<name> value in order to encourage the highest level of consistency across the archive (this applies to Instruments and Facilities etc too). For example, the NASA Deep Space Network context product with LID urn:nasa:pds:context:facility:observatory.dsn states <Facility>/<name>= "Deep Space Network" (not "NASA Deep Space Network", which is the <Identification_Area>/<title>).
• 9 warning.integrity.unreferenced_member
   The following product flags a warning due to an incorrect <Bundle_Member_Entry> in the bundle label, erroneously stating "urn:nasa:pds:voyager2_rss_uranus_49xr_raw:data" (no suffix "_podr"):
    urn:nasa:pds:voyager2_rss_uranus_49xr_raw:data_podr::1.0
  The following warnings appear to be due to errors in the collection_document.csv , which references "urn:nasa:pds:voyager2_rss_uranus_raw:document" instead of "urn:nasa:pds:voyager2_rss_uranus_49xr_raw:document"; and the crs_notes LID has "_1" suffix;
    urn:nasa:pds:voyager2_rss_uranus_raw:document:mission::1.0
  urn:nasa:pds:voyager2_rss_uranus_49xr_raw:document:hga_doc::1.0
  urn:nasa:pds:voyager2_rss_uranus_49xr_raw:document:ops_plan::1.0
  urn:nasa:pds:voyager2_rss_uranus_49xr_raw:document:crs_notes_1.0::1.0
  The following warnings appear due to the <logical_identifier>s for the products in the collection_geometry erroneously stating "voyager1_…." instead of "voyager2_…":
    urn:nasa:pds:voyager1_rss_uranus_49xr_raw:geometry:uh0003b::1.0
  urn:nasa:pds:voyager1_rss_uranus_49xr_raw:geometry:uh0003a::1.0
  urn:nasa:pds:voyager1_rss_uranus_49xr_raw:geometry:uk0015b::1.0
  urn:nasa:pds:voyager1_rss_uranus_49xr_raw:geometry:uk0015a::1.0
  
• 10 warning.integrity.member_not_found
  Likewise, the following warning appears to be due to an incorrect <Bundle_Member_Entry> missing suffix "_podr" for the data_podr collection:
    urn:nasa:pds:voyager2_rss_uranus_49xr_raw:data
  And the following warnings appear to be due to errors in the collection_document.csv – it should reference "urn:nasa:pds:voyager2_rss_uranus_49xr_raw" and the crs_notes file has a "_1" suffix:
    urn:nasa:pds:voyager2_rss_uranus_raw:document:mission::1.0
  urn:nasa:pds:voyager2_rss_uranus_raw:document:ops_plan::1.0
  urn:nasa:pds:voyager2_rss_uranus_raw:document:sis_vgr_rs::1.0
  urn:nasa:pds:voyager2_rss_uranus_raw:document:hga_doc::1.0
  urn:nasa:pds:voyager2_rss_uranus_raw:document:crs_notes::1.0
  And the following warnings appear to be due to the <logical_identifier>s for the products in the geometry collection erroneously stating "voyager1_…." instead of "voyager2_…":
    urn:nasa:pds:voyager2_rss_uranus_49xr_raw:geometry:uk0015a::1.0
  urn:nasa:pds:voyager2_rss_uranus_49xr_raw:geometry:uk0015b::1.0
  urn:nasa:pds:voyager2_rss_uranus_49xr_raw:geometry:uh0003a::1.0
  urn:nasa:pds:voyager2_rss_uranus_49xr_raw:geometry:uh0003b::1.0
  NOTE: The SIS files (docx, pdf, xml) were initially missing from the document collection. RMS requested the files and transferred them for the data provider, and verified checksums.
• 62 error.label.context_ref_not_found
  All of these errors refer to "Context product not found: urn:nasa:pds:context:telescope:parkes.dss49_64m". However, that context product *does* exist. PDS Engineering Node are in the process of fixing the bug: https://github.com/NASA-PDS/validate/issues/1066. This should now be fixed in the updated version of Validate.

Reviewers' Submitted Comments and Responses

Review Outcome