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?