Below are the liens for the following NH SDC data sets: NH-J-SDC-2-JUPITER-V3.0 NH-J-SDC-3-JUPITER-V3.0 NH-X-SDC-2-LAUNCH-V3.0 NH-X-SDC-2-PLUTOCRUISE-V1.0 NH-X-SDC-3-LAUNCH-V3.0 NH-X-SDC-3-PLUTOCRUISE-V1.0 o In the various documents we see SDC, VSDC, and VB-SDC all to refer to the same instrument - pick one. I prefer SDC, which is used most of the time (including the literature paper), none of the variants occur on the acronym list. o Emily has found one raw file that does not have a calibrated equivalent. She will supply the name and this will be investigated. This is in the Pluto cruise data. nh-x-sdc-2-plutocruise-v1.0/data/20100723_017143/sdc_0171435128_0x700_eng_1.* file: 'catalog/sdc.cat' --> In sdc.cat, in Operational Considerations Item 4) regarding the lack of observation of "large particles", please replace "large" with an actual threshhold number. file: 'document/soc_inst_icd*.pdf' --> On page 118 under Section 13.1.1 it says that Channel 11 failed before launch. On Page 119 under Section 13.2.1 it says that Channel 10 has an electrical issue. Other documentation makes it clear it is Channel 11 that has the issue. --> The first paragraph in section 13.3.1.1 repeats the previous paragraph. --> The last paragraph in section 13.3.1.1. cites a 2007 paper as being "in pub". We should have the updated citation here. --> Section 13.4.2 shows the Dataflow Block Diagram. The lower green rectangle should say "Conversion of Charge to Mass" instead of repeating the upper green rectangle. file: 'errata.txt' --> The statement in the errata.txt file should be in the dataset.cat CONFIDENCE_LEVEL_NOTE and in the sdc.cat "Operational Considerations" list. The errata.txt file should die. Last updated: 2015-01-08, SBN:T.Barnes ======================================= Liens general to all New Horizons data sets are listed below: file: 'aareadme.txt' --> typo: " to to " in "Refer to to DOCUMENT/DOCINFO.TXT" --> typo: " by the by " in "and used by the by NH instrument teams." --> typo: In the 'Generic PDS label details' section, par 1, the text "mission- specific" has an extra space and should read "mission-specific". --> --> For screen print, see 'frahm_extras/PEPSSI_README.pdf'. --> Utility of the raw vs. calibrated data products: I was unable to find any description of when a user might benefit from using the raw data products (contained in the nh-x-alice-2... nh-x-leisa-2... directories) rather than using the reduced and calibrated products (contained in the nh-alice-3... and nh-x-leisa-3... directories). My guess is that such instances are likely to be very rare, and users would probably have to work with NH project personnel to do much with the raw products. If that's correct, it would be useful to have a brief statement in the raw data archives saying that for most applications users would be better off using the reduced and calibrated data. It would also be useful to have a brief statement describing when starting with the raw data might be called for (if a summary of those conditions is difficult to compile, perhaps a couple of examples could be given). --> Filenames and Product IDs section: It would be worth noting that the filename used is an example relevant to Alice. The same filename is used in this file in the Liesa data archive, and perhaps all (?) the others. It would be helpful to enumerate the instrument IDs, perhaps in another note, or to tailor the example filename used to the instrument that produced the data in the archive being examined (i.e. in a Liesa archive, use a filename like "lsb_0052459065_0x53c_sci_1.fit" rather than an Alice file). --> Processing Level: Here the Raw and Calibrated data products are associated with something called "CODMAC Level 2" and "CODMAC Level 3", respectively. I have no idea what CODMAC is or why it's relevant here. Maybe explain or delete these associations. --> Contact information: Alan Stern's address is given as NASA HQ. I think that's incorrect, in which case an updated address and/or an alternative contact should be provided. file: 'catalog/dataset.cat' --> typo line 3: capitalize 'H' in "horizons" --> The Review section in the CONFIDENCE_LEVEL_NOTE should have the TBD date updated after the review. --> The CITATION_DESC has the data set name in all caps except for only one word (either "Raw" or "Calibrated"). Probably should make it uniform. file: 'catalog/nh.cat' --> typo line 90: Should the "11 to 12 Earth days" actually be "12 to 13"? file: 'catalog/nhsc.cat' --> In nhsc.cat, the second ASCII art image doesn't seem to be rendering correctly in fixed-space font. --> typo: line 27. There is a double space in between two words that should a single space, "requiring maximum". --> --> For screen print, see 'frahm_extras/PEnhsc.pdf'. --> typo line 42: change "PEPPSI" to "PEPSSI". --> line ~76: The RALPH/LEISA section presents the same erroneous information about the etalon bending the light that I note under comments on the leisa.cat file, and should be fixed. --> --> leisa.cat lien: The Description section states, incorrectly I think, that "... its etalon acts like a prism to bend different wavelengths of light by different amounts..." Etalons are interference filters that pass particular wavelengths through wile reflecting others. It might be more accurate to say something like, "...its etalon (a filter with a narrow spectral bandpass that varies linearly in one dimension) is bonded to the illuminated side of the IR detector. As a result, each row of detector pixels receives only light of a particular wavelength. Spectral maps are produced by sweeping the FOV of the instrument across a scene, sequentially sampling each point in the scene at each wavelength." --> typo line 125: The "Long" in "short for Long Range" should be "LOng" with a capital 'O'. --> typo line 144: The word "Science" is missing from the instrument name "Pluto Energetic Particle Spectrometer Science Investigation (PEPSSI)" --> line 315: Unable to locate Figure 5. --> line 323: Unable to locate Table II. file: 'catalog/ref.cat' --> Incorrect Reference Year for BELTONETAL2002. Can not find a 2002 reference which has more than 100 pages. There is a 2003 reference which exceeds 145 pages. --> Incomplete Journal Specification for ANDREWSETAL1998. Should site 'Proceedings SPIE' as the journal. --> Note that inaccessible JPL documents pose ongoing problems especially when their old references are included in new data by habit or cut & paste. The REX reviewers should consider whether there is any point in referencing DSN design documents not available to the great majority of end users. --> Change all occurrences of "PEPPSI" to "PEPSSI". files: 'data/*/*.fit' --> Remove ITEMS keywords from any COLUMN that is not actually a vector. --> Labels missing units of measure should be present wherever they are applicable. directory: 'document/' --> The following PDF files are not PDF/A compliant: --> --> asmar_and_renzetti_1993.pdf --> --> c2_qe.pdf --> --> c3_qe.pdf --> --> flat_field_from_ot2_data.pdf --> --> morgan_spie.pdf --> --> pepssi_ssr.pdf --> --> ralph_align_wrietup03.pdf --> --> rex_ssr.pdf --> --> sdc_ssr.pdf --> --> tnfsis.pdf files: 'document/soc_inst_icd*.pdf' --> A test was conducted on the ICD intro pdf to determine if an acronym was included within the ICD acroabbr pdf file. The acronym chosen was "CM" and occurs on page 6, section 6.6, line 3 of the ICD intro pdf. This acronym was not found in the acroabbr pdf file. file: 'document/soc_inst_acroabbr.pdf' --> Within the database acronyms should have a unique meaning to minimize confusion. In these cases we should pick a single acronym for a single phrase and do a find/replace to get rid of the rest. Please note that these are found in many documents. --> --> "ApID" and "APID" --> --> "G&C", "GN&C", and "GNC" --> --> "MOPs" and "MOPS" --> --> Bigger problem for SOC and SOCC - let's not use the same acronym for both "Science Operations Center" and "Solar Occultation Channel". --> --> In the various documents we see SDC, VSDC, and VB-SDC all to refer to the same instrument - pick one. I prefer SDC, which is used most of the time (including the literature paper), none of the variants occur on the acronym list. file: 'errata.txt' --> The errata.txt files tend to be empty or contain irrelevant notes that are not an errata. Ideally this file should not have to exist at all the time of archiving. It certainly should not contain anything that is not an actual erratum. Other General liens: o URLs and references to the peccadilloes of specific contemporary software packages do not belong in PDS archive labels. Please expunge them with all speed. Last updated: 2015-01-08, SBN:T.Barnes