New Horizon ALICE Specific Liens for Pluto Encounter Data Sets -------------------------------------------------------------- Certification Status: Certified for release. aareadme (both Levels 2 & 3) ======================== >In the Suggested FITS & PDS Software section, there is an incomplete thought and a sentence fragment that needs to be fixed: "The following URLs were current as of 2007 when the early New occasionally, and given the availability of search engines, no attempt will be made to update this information throughout the mission. " voldesc.cat (Level 2) ================== > The Level 2 data set includes the calib directory and same supporting files as in the Level 3 data, so should "-calibration information" be added to the "DESCRIPTION = … This volume also contains - mission documentation - spacecraft documentation - instrument documentation - data set documentation - index tables of the data" alice.cat (both Levels 2 & 3) ======================= >Typo in Operational Modes, Histogram Imaging Mode section, 2nd paragraph, "equivalentof" should be "equivalent of" >Typo in Measured Parameters, Histogram Imaging Mode section , 1st paragraph, "threshhold" should be "threshold" dataset.cat (both Levels 2 & 3) ========================= >Typo in Alice_Func_080 section , #3 and #4, "succesful" should be "successful" >Typos in Data section, Notes #1, "be sretored" should be "are stored", "capabilty" should be "capability", and "Historgram" should be "Histogram" >Data coverage and quality section, the description of the lollipop fuzz is a bit misleading. Qualitatively it is fine. Quantitatively, it is off. It appears that the central ~70 Angstrom band of uncoated photocathodes is described properly and apparent in the data, and especially along the slit portion of the aperture is fine. However, in the 2x2 degree box of the aperture, the description of the spread of the signal is not quite right. It states that the HI Ly-alpha spreads out beyond the 70 Angstrom (35 Ang on each side of 1215 Ang) over another ~110 Ang on either side. That would lead a reader to think that the spread goes out to 35 Ang + 110 Ang = 145 Ang beyond 1215 Ang. This is not the case. In the data, it appears that the spread goes out an additional 110 Ang total, so 55 Ang on each side beyond the 35 Ang uncoated band on each side. So, the lollipop fuzz appears to extend ~90 Ang (35 Ang + 55 Ang) on either side of 1215 Ang rather than 145 Ang. Consider a non-misleading description so that the user can avoid/interpret the lollipop fuzz as intended. calinfo.txt (both Levels 2 & 3) ======================== >pa_aeff_* in the directory structure listing has all of the pa_eff files, no matter the running number in the filename, as calibration version "005". Should the description version number match what appears to be a version number in the directory tree filenames? In .fit header: SOCVER = 6.3 / SOC pipeline software version and MIKE_VER= '13 [2016 Mar 15]' / Version of Mike pipeline code. Neither of these are 005. Please address. >Typo "Superceded by PA_ARFF_007" should be "Superseded by PA_AEFF_007" >Typo, there should be a semicolon or period after "… version 004" and before "Superseded by …" in the directory tree listing for pa_aeff_004.tab >Typo, in listing for pa_aeff_socc_001.tab, Solar Occultation Channel >There are two dark calibration files, pa_dark_*, in the directory structure listing but they do not state when they are applicable, unlike their counterpart for aeff. It appears that in the *.fit data headers themselves, DARKFILE= 'pa_dark_002.fit' is the only one used for this data set. Is pa_dark_001.fit superseded? Please fix. >There is a listing for "pa_wave_000.fit" in this file, but there is no file by that name. The only wavelength calibration file in the directory is "pa_wave_002.fit" and this is the file that is listed in the *.fit file headers as being used in the Mike pipeline for all of the data files. Please fix. >Is there a file for the per pixel solid angle along the 32 rows of the slit and box aperture? It is not evident. various files (both Levels 2 & 3) ========================= >Reviewer’s terminology nit: spectrograph vs. spectrometer Alice is actually a spectrograph (see the SSR paper and other documentation in the data sets) but the word spectrometer is used in 5 occurrences in document/nh_alice_v200_ti.txt, 1 occurrence in catalog/alice.cat, 2 occurrences in catalog/nhsc.cat, and 1 occurrence in catalog/ref.cat. Does the team want this to be fixed/consistent? General Liens for all New Horizon Pluto Encounter Data Sets ----------------------------------------------------------- Some very brief, high-level description of when the actual encounter happened, and maybe where in the directory structure those data are, would be very helpful to users. [This should probably be in some permanent part of the data set description that users are likely to see – like the abstract.] The dataset.cat needs to reflect the state of the Pluto data now, as delivered (with little Pluto data at very low resolution). The boilerplate, all-encompassing descriptions that worked reasonably well for early mission and cruise data are not addressing the needs of users now, who are looking for the more interesting encounter data, and need to be able to find the most interesting data easily. AAREADME should be pared down to only relevant sections that actually address volume layout and otherwise refer users to documents. Please update the references that refer to JPL internal documents, which are not generally accessible to anyone outside JPL, to indicate that the referenced documents are not generally available (in the reference.cat file). For file: 'aareadme.txt' --> typo: "The filename prefix may provides additional infomation about the instrument detector." => "The filename prefix may provide additional information about the instrument detector." --> typo: Missing content "The following URLs were current as of 2007 when the early New occasionally, and ..." between the words "New" and "occasionally". For file: 'catalog/nh.cat' --> Add subphase table to the mission.cat description. It is referenced in SWAP data set catalog file for example. For file: 'catalog/nhsc.cat' --> Check statement "more than 4 billion miles from Earth" -> 4.9 billion km from Sun. Change unit to km. --> Section on propulsion mentions a "Figure 5" but there is no such figure in the catalog file. It should say "as shown in Figure 5 of [FOUNTAINETAL2008]." --> Some of the mission descriptions are still written in future tense, with predicted distances, etc. These could be updated with more meaningful information. Emphasis given using asterisks ('*'). --> --> "Pluto and Charon *will first appear* as unresolved bright dots, but the planet and its moon *appear larger* as the encounter date *approaches*. About three months from the closest approach … the cameras on the spacecraft *can make* the first maps." --> --> "the spacecraft *comes as close as* … when the spacecraft *is closest* to Pluto … it *will take* close-up pictures ..." --> Is his statement still true: "as of early 2016, no extension to the mission has been approved." --> Include reference in text: Control rates for each of the spacecraft axes are *shown below in Table II.* ==> "shown in [FOUNTAINETAL2008] Table 2." --> Spacecraft sketches do not show position of SDC nor is its position described in the document. For file: 'catalog/ref.cat' --> ROSENBERGETAL1994: Abbreviate the authors' names appropriately. Also, the DOI is given in two formats; I suggest dropping the URL one. For file: 'document/codmac_level_definitions.pdf' --> Describes the NASA Level 1B (Resampled L4) as irreversibly transformed measured values. I assume these are derived from the calibrated L3? Please note the source. For file: 'document/docinfo.txt' --> In several places throughout the text, the SSR papers are referenced to 2007 though they should be for 2008. Also please make reference to the REF_ID used in the reference catalog file when a copy of the paper is present in this directory. For file: 'document/nh_mission_trajectory.tab' --> This file ends before the start date of the data sets. This file only goes through 2014-12-31. For file: 'document/nh_trajectory.tab' --> This file is only relevant for Jupiter fly-by. Why include it here? For file: 'document/soc_inst_icd.pdf' --> page 18, 8.1: Note that the type in the spectral range ("1.225-2.5" should be "1.25-2.5"). --> page 54, table 10-2, 10-3: Data format not consistent with the specifications in these two tables --> page 66, 10.3.4: The unit for resolved and unresolved sources are reversed --> page 67, 10.3.6: Information outdated, and conflict with 10.3.13 --> page 54, table 10-2, 10-3: Data format not consistent with the specifications in these two tables --> --> For example: '028769/mc0_0287692247_0x536_eng.fit': HOUSEKEEPING table 75 columns and WINDOW_MISMATCHES table 10 columns --> page 66, 10.3.4: The unit for resolved and unresolved sources are reversed --> page 67, 10.3.6: Information outdated, and conflict with 10.3.13 --> page 115, 13.2.1, 2) the unused channel should be 10 not 11 (which on higher level data products becomes 11) --> page 121, 13.4.4, 1) Calibrated Data - Only 9 columns are defined but there are 10 columns. "j. Impact Velocity" should be added --> page ???, 14. : The ICD refers to the RPA as a "low-pass filter". It is, in fact, a high-pass filter. --> page 132: It refers to "section 135" which does not exist. This is probably Section 14.5.10. --> page 133: It refers to "section 13" which does not exist. This is probably Section 14.5.10. --> page 141: typo: "4 time" => "4 times"