Cassini ISS Derived Spoke Images Data Peer Review
Mia Mace, Matt Tiscareno, and Mitch Gordon
November, 2024
Background
This bundle contains maps of Saturn's B ring derived from images obtained with
the Wide-Angle Camera of the Cassini Imaging Science Subsystem (ISS) that can
be used to more easily quantify signals from spokes, by M.M. Hedman et al.
Reviewers should begin by reading the readme.txt file (top level of the bundles).
Data Bundle
The directory structure of the PDS4 bundle is illustrated below:
- cassini_iss_spokes_hedman-hamilton-2024/
- readme.txt High-level overview of data set
- bundle.lblx Label for bundle, describing members of the bundle and references etc
- browse_derived/ Directory containing browse products (images)
- collection_browse_derived.csv List of browse product LIDs, with first column designating whether it is a primary (P) or secondary (S) member
- collection_browse_derived.lblx Label for the associated collection file
- *_rprj_browse.png Images showing the maps of ring brightness derived from each data product
- *_rprj_browse.lblx Labels for associated browse product
- context/ Directory containing context information related to the archive; such as spacecraft, instruments, targets etc.
- collection_context.csv List of context product LIDs, with first column designating whether it is a primary (P) or secondary (S) member
- collection_context.lblx Label for the associated collection file
- data_derived/ Directory containing the derived maps
- collection_data_derived.csv List of derived data product LIDs, with first column designating whether it is a primary (P) or secondary (S) member
- collection_data_derived.lblx Label for the associated collection file
- *_rprj.fits FITS files containing the brightness maps derived from each image
- *_rprj.suppl ASCII supplementary file providing information about c-kernels used to navigate each image
- *_rprj.lblx Labels for the associated data files
- document/ Directory containing documentation
- collection_document.csv List of members of the document collection, with first column designating whether it is a primary (P) or secondary (S) member
- collection_document.lblx Label for the associated collection file
- *.pdf/*.txt Documents
- *.lblx/*.xml Labels for the associated documents
- spice kernels/ Directory containing information about SPICE kernels used in this study
- collection_spice_kernels.csv List of SPICE product LIDs, with first column designating whether it is a primary (P) or secondary (S) member
- collection_spice_kernels.lblx Label for the associated collection file
- kernels.ker ASCII file specifying the kernels used
- kernels.lblx Label for the associated kernel file
- xml_schema/ Directory identifying the XML schema products associated with this bundle
- collection_xml_schema.csv List of members of the XML schema collection, with first column designating whether it is a primary (P) or secondary (S) member
- collection_xml_schema.lblx Label for the associated collection file
The complete peer review bundle (cassini_iss_spokes_hedman-hamilton-2024.tar.gz) and accompanying journal article are 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).
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
The following warnings/errors appear in the bundle:
9882 product(s)
408 error(s)
5 warning(s)
Product Validation Summary:
9656 product(s) passed
226 product(s) failed
0 product(s) skipped
9882 product(s) total
Referential Integrity Check Summary:
9887 check(s) passed
0 check(s) failed
0 check(s) skipped
9887 check(s) total
Message Types:
46 error.label.checksum_mismatch
362 error.label.schema
5 warning.file.not_referenced_in_label
- The 362
error.label.schema reported refer to 181 (=362/2) labels that contain a negative value for the <rings:minimum_inertial_ring_longitude>. The negative longitude value triggers a second error in each case:
Element 'rings:minimum_inertial_ring_longitude' must have no element [children], and the value must be valid.
This affects approximately 4% of the data labels, and is because of the ring longitude range convention used by the data provider: [-180deg, 180deg] instead of the PDS4-compliant [0deg, 360deg]. During lien resolution, these negative longitude values will be corrected by having 360 added to them.
-
The 46
error.label.checksum_mismatch are as it sounds, a mismatch between the actual data file's checksum and that reported in the data label. These will be corrected during lien resolution.
-
The 5
warning.file.not_referenced_in_label refer to documents that need to be referenced by the data labels, which will be corrected by including Internal_References/External_References in each of the data_derived labels, and bundle.lblx.
-
The
readme.txt states "List for the associated collection file" beside collection_browse_derived.lblx in the directory tree diagram. This should say "Label for the associated collection file."
Reviewers' Submitted Comments and Responses
Review Outcome
Ring-Moon Systems Node Home