Below are the liens for the following NH Pluto Encounter data sets: NH-X-REX-2-LAUNCH-V2.0 NH-X-REX-3-LAUNCH-V1.0 NH-J-REX-2-JUPITER-V2.0 NH-J-REX-3-JUPITER-V1.0 NH-X-REX-2-PLUTOCRUISE-V2.0 NH-X-REX-3-PLUTOCRUISE-V1.0 NH-P-REX-2-PLUTO-V2.0 NH-P-REX-3-PLUTO-V1.0 - All index directories and files need to be checked for selection errors in the slim indices, and column labeling errors in all index files. - There are problems in solar geometric distance, which will affect the labels of the instrument. This need to be fixed. - REX Radiometer Calibration report is need to be thoroughly reviewed and corrected. It suffers from numerous issues such technical writing, different writing styles,development of many examples, spellings and punctuations. For details, please look at the file "nh_rex_radiometer_cal_4.2cm_v2.2.1_RS.pdf". - There seems to be either a discrepancy or an outright disagreement between the description of the detailed calibration method described in the ICD and dataset.cat, and the method as explained by the REX PI (Ivan Linscott). This needs to be investigated. - Radiometry values may differ by 10x from previous review. This need to be investigated. - 'nh-x-rex-2-plutocruise-v2.0/data/tnf/*.lbl' None of these are listed in index.tab - nh-x-rex-3-plutocruise-v1.0/data/tnf/*.lbl None of these are listed in index.tab - 'nh-p-rex-2-pluto-v2.0/catalog/dataset.cat nh-p-rex-3-pluto-v1.0/catalog/dataset.cat' This target is referred to here, but EN has no TARGET.CAT for it TARGET_NAME = "CYG A" - 'nh-p-rex-2-pluto-v2.0/data/tnf/*.lbl' None of these are listed in index.tab - 'nh-p-rex-3-pluto-v1.0/data/tnf/*.lbl' None of these are listed in index.tab file: 'catalog/dataset.cat' ---> For the raw data sets, there is no version history, only a general comment. What is different between V2.0 and V1.0? I expect to find it here as in the data sets provided for other instruments. ---> The "Confidence Level Overview" might need to be updated to reflect the disconnect between version numbers of raw vs calib. ---> Note that calib ds_id does not exist and that calib v1.0 is based on raw v2.0. ---> Why is the "Caveat about TARGET_NAME in PDS labels and observational intent" section different in REX than for all the other instruments? Should it be? ---> The ABSTRACT_DESC needs to be expanded as has been done for data sets for the other NH instruments. Note needs to be included for versioning as well. file: 'document/nh_rex_radiometer_calib.pdf' --> This document may need to be replaced with the calibration document found: 'nh-p-rex-3-pluto-v1.0/document/nh_rex_radiometer_cal_4.2cm_v2.2.1.pdf' file: 'nh-*-rex-2-*-v2.0/document/seq_rex_*.lbl' --> The DATA_SET_ID of for the calibrated data set, states "V2.0" which does not currently exist. file: 'index/index.lbl' ---> File breaks down after column 11 for accurately describing the index table. ICD 12.3.1.2 Calibrating the REX Radiometry: - dBm = Rbase + 10*log10(4.5e6 * RAW) + dBstep (AGC - AGCoffset) + Ro In the equation, dBm is total power not power density. The origins of 'Rbase' and 'Ro' not explained. - Rbase = -178, however, CR section 4 used -176 - In the tittle of third and fourth column of the table, Beside "Side A Value" and "Side B Value", “RCP” and “LCP” should be written in parenthesis. - In Ro entry, CR section 4 used -106.6 and -104.2 for RCP and LCP. This need to be checked - In Example ICD Calculations with CR Section 4 Values, the calculation of the values of RCP and LCP are surprisingly alike. This need to be investigated. - In Radiometer Integration Time and Effective Time Tag, every tenth radiometer sample has 10x integration time and an effective time tag in the previous ROF. Instead of 102.4 ms, Integration Time would be "1024.0 ms". Cal Radiometer time for 0th index would be 's0 -512.0 ms' and 10th index would be 's0 + 512.0 ms' - In Summary of Calibration Solutions, Most of the values are presented without derivation; there is no discussion about how to choose among them. Uncertainties tend to exclude other solutions. This need to be reviewed. - There is an issue with linearity and long term reciever stability. The observed step appears to be closer to 0.86 dB than the expected 0.96 dB. This need to be checked - When were calibration data collected? The abstract says calibration data were collected "during Integration and Test, … after launch in April 2006, and [during] an 'additional' Calibration Campaign in July 2016." But the next page refers to "four calibrations over the course of the mission" and expands the post-launch campaign to April-June 2006, while Figure 2.2.1 shows data from January 2013 and Section 2.1 says the "X-band receiver was measured … at every annual checkout". This is very confusing to the reader who is trying to understand what measurements were taken, when, and how they fit together to nail down the conversion of REX units to dBm (or antenna temperature) for both channels/polarizations. - Complete List of Power Measurements Is Needed: A summary table showing cold sky and radio source measurements (average and standard deviation) in each polarization over the length of the mission would be an important addition. Gain settings should be included in the table. There is no information in this report about amplitude stability of the receiving system over time scales of months to years; that is important because Pluto/Charon measurements are being calibrated using measurements made years earlier and later. - For additional reference, please look at the comments from Dick Simpson at‘Simpson_commnents.docs’ ================================================================= Error Unique for: *LAUNCH* file: 'catalog/dataset.cat' ---> Found a reference, "TYLERETAL2008", which is not defined in a REFERENCE_KEY_ID within the label. Please add it. ================================================================= Error unique for: *PLUTOCRUISE* file: 'catalog/dataset.cat' ---> All TARGET_NAMEs found in the 'data/' directory should be found within this file. Currently there appears to be a mix up with target_name values in the data labels. Please resolve and confirm this list. Also note that "N/A" should not be included in this list and never included when you have other valid targets listed. file: 'data/*/*.lbl' ---> There is a known TARGET_NAME issue where these labels are not the same as what is described in the FITS header, PDS index tables, and PDS data set catalog file. Please verify and fix the TARGET_NAME values. file: 'index/*ind*.tab' ---> File contains TARGET_NAME values that are not listed in the data label. ---> Note that PDS-SBN would prefer to use the name found in the index and FITS header over the generic ones currently present in the PDS data label. files: 'index/index.*' --> The 'data/tnf/' files are not indexed. files: 'index/slimindx.*' --> The 'data/tnf/' files are not indexed. ================================================================= Error unique for: *PLUTO*(Encounter) file: 'catalog/dataset.cat' ---> All TARGET_NAMEs found in the 'data/' directory should be found within this file. Currently there appears to be a mix up with target_name values in the data labels. Please resolve and confirm this list. Also note that "N/A" should not be included in this list and never included when you have other valid targets listed. ---> Note that if 'CYG A' is a valid value for TARGET_NAME, that we will need to add it to the PDSDD. ---> For the Calib data set, the ABSTRACT_DESC appears to be for P2 and not P3 (look at the data through dates). file: 'data/*/*.lbl' ---> Resolve things like "STAR" or "CALIBRATION" to the actual target name if known and provided. files: 'nh-p-rex-3-pluto-v1.0/document/nh_rex_radiometer_cal_4.2cm_v2.2.1.*' ---> The filename is not structured correctly. There should be only one period. Please rename. ---> Also note that this file may need to replace the existing 'nh_rex_radiometer_calib.pdf' file. file: 'nh-p-rex-2-pluto-v2.0/document/seq_rex_pluto.lbl' --> The DATA_SET_ID of "NH-P-REX-3-PLUTO-V2.0" does not exist. file: 'index/*ind*.tab' ---> File contains TARGET_NAME values that are not listed in the data label. ---> Note that PDS-SBN would prefer to use the name found in the index and FITS header over the generic ones currently present in the PDS data label. files: 'index/index.*' ---> The 'data/tnf/' files are not indexed. files: 'index/slimindx.*' ---> The 'data/tnf/' files are not indexed.