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