Below are the liens for the following NH ALICE data sets: NH-X-ALICE-2-PLUTOCRUISE-V1.0 NH-X-ALICE-3-PLUTOCRUISE-V1.0 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. file: 'calib/pa_flat_000.fit' --> The flat-field is a placeholder with all values set to 1.0. The RMS pixel variation is quoted as 15% in the SOC_ICD, so this seem like a big issue for trying to use the data to accurately measure emission strengths for lines that aren't spread over many pixels (e.g. for the solar occultation experiment and for calibration measurements on stars). --> --> This missing flat field file is a known issue that has not been resolved. It seems to be sufficiently well documented, so there is no need for further action on this for these data. file: 'catalog/alice.cat' --> In the Data Acquisition Modes section there are two references to P-Alice, but no information of how (or whether) P-Alice is distinct from Alice. The dataset.cat file says something about PERSI-Alice, but again no info is given about why it is being referred to as P-Alice or PERSI-Alice. I suspect this may have been a way to distinguish this instrument as being the one on New Horizons (i.e. not on Rosetta). Anyway, better to either give a very brief background about why it's sometimes called P- or PERSI-Alice, or just drop those and refer to it consistently as Alice. --> The entries in 'document/seq_alice_plutocruise.tab' typically include a frequency in Hz. I wasn't able to find anything in the alice.cat, dataset.cat, or seq_alice_plutocruise.lbl files stating what frequency is referred to or why it might matter to a scientist. Saying something brief, maybe in alice.cat, would be good. --> line ~91: In the Scientific Objectives section there is a sentence: "Temperature and vertical temperature gradient should be measured to ~10% at a vertical resolution of ~100 km for atmospheric densities greater than ~109 cm-3." Just want to check that "109 cm^-3" is correct (that's a very hard vacuum...), and whether a specific molecular species is relevant to this measurement capability. --> line ~129: The Operational Considerations section discusses tests to be performed in 2006/7. The discussion should be updated to reflect the outcome of those tests, if relevant. --> line ~139: The Detectors section notes that a ~250 x 32 pixels in the array are inactive. Might note here that the spectral grasp stated earlier in the document excludes wavelengths that would be covered by the inactive pixels. file: 'catalog/dataset.cat' --> In the Filename/Product IDs section the various ApIDs are described and associated with either CDH 1 or CDH 2. Might quickly state what CDH means and whether it refers to the Alice CDH or a computer associated with the spacecraft. I'm guessing that essentially all data were taken using one or the other CDH, with perhaps only aliveness data taken on the other. If so, it might be worth noting that nearly all of the data of interest to scientists is associated with a subset of the listed ApIDs. --> The ApID description notes that data comes in "lossless" and "packetized" flavors. There is no further detail offered in this file about those modes, nor is there anything I can see in the alice.cat file. It would be good to provide a little information about the two modes, when they are employed, any differences in the quality of the data from them, and what mission phases they are used in. --> Please add a brief note to the "Calibration" section of the data set catalog DESCRIPTION to explain the Lyman-alpha lollipop fuzz visible in the calibrated spectra. directory: 'data/' --> The .lbl files don't describe the image data contained in the fits files (in contrast to the labels describing the fits table extensions, EDUs 3-4). Examples: --> --> The PDU description is just boilerplate about the FITS standard (see quoted example below). The PDU in the Alice level-3 files contains the count-rate spectral image, so it seems like the label should say so, and include a statement of the units, the calibration steps applied, ...? --> --> The labels for EDUs 2-3 (error and wavelength images) are even worse. --> The raw IMAGE objects do not have UNITs. They should (it's "DN"). This may also need to be chased down in the samples/ directory labels. --> Useability of the spectra: --> --> The level-3 data appear to have significant background contamination in certain regions. I was expecting images where such artifacts had been corrected, such that an extracted spectrum would contain only signal from the target and be in (or easily converted to) physical units (see image below). --> --> The units of the spectral image (first extension) are given in the fits header, but not in the PDS label file. Since the PDS label is the gold standard for defining the data set, the label should be updated to include information about what data are in the PDU and what the units are. PDS labels for the 2nd and 3rd extensions should also be updated to state what data is present and give units. --> Lori reports that some level 3 files contain NaN values rather than data. This needs to be investigated and corrected as appropriate. --> --> Examples: ali_0235930840_0x4b1_eng_1, ali_0235930840_0x4b1_sci_1, ali_0140158550_0x4b1_eng_1, ali_0140158550_0x4b1_sci_1, ali_0140158552_0x4b1_sci_1, ali_0140158549_0x4b1_sci_1 --> Also, there are multiple dark files but no indication of when each is applicable. Seems like there should be. --> Emily notes that there is a 77-file discrepancy between the number of raw and calibrated files. This is not necessarily an issue, but in light of the NaN issue mentioned reviously, it's worth a little investigation. --> --> 20090726_011095/ali_0110954326_0x4b1_eng_1.* to 20130712_023594/ali_0235945705_0x4b2_eng_1.* file: 'document/seq_alice_plutocruise.tab' --> The entry for "07267:A1AL705_02_StdUV2FFScan" the exposure duration is given as "1.5 hr sec" (typo of some sort). That's the only entry w/ that typo. 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