New Horizon PEPSSI Specific Liens for Pluto Encounter Data Sets
---------------------------------------------------------------

Certification Status: Certified with minor liens.


It is not clear from instrument descriptions and SIS whether the instrument was capable of recording high and low resolution data simultaneously (and the data set incomplete because data have not been received), or not (and there are gaps because of alternating between modes).  Larry B. explains the data taking is simultaneous, but getting the data down takes a long time.  So this needs to be added to the documentation in appropriate (and editable) places.

The description of the sequence table needs to be clearer on what it contains (planned observations as opposed to only those resulting in data), and it should indicate which sequences actually have observations in the data set.

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).

The rateboxdefinitionplanes.fit file is still in a different place than that referenced in the ICD.  See page 76 of ICD.  

Steve’s presentation notes an unexpected disconnect between low and high resolution data (see slide with "dataset.cat (2)" title and preceding graphs). Some sort of explanation should probably be added in something like the dataset.cat description.

Rudy notes that there seem to be data points recorded below the lower sensitivity limit of the instrument.  There should probably be an explanation somewhere of what is going on in this range.

Why does PEPSSI see the solar wind and SWAP does not?


For file: 'catalog/dataset.cat'
--> typo: "Pluto flyby on 14.July" ... remove period

For file: 'catalog/pepssi.cat'
--> typo: "In this initial delivery" ... 'this' => 'the'

For file: 'document/rateboxdefinitionplanes.lbl'
--> typo: "corresponds to one on nineteen rate" ... 'on' => 'of'
--> typo: "LINES positions 1 through 20148 corresponds" ... '20148' => '2048'