New Horizons Pluto Energetic Particle Spectrometer Science Investigation (PEPSSI) PRINCIPAL INVESTIGATOR: Ralph McNutt, APL DESCRIPTION: Medium Energy Particle Spectrometer ENERGY RANGE: 25-1000 keV (protons) 60-1000 keV (atomic ions) 25-500 keV (electrons) FIELD OF VIEW: 160 deg x 12 deg ANGULAR RESOLUTION: 25 deg x 12 deg ENERGY RESOLUTION: 0.25 keV SENSOR SIZE: 7.6 cm dia. x 2.5 cm thick POWER: 1.4 watt MASS: 1.5 kg

New Horizons PEPSSI Data Sets RAW -> nh-p-pepssi-2-pluto-v2.0 nh-x-pepssi-2-plutocruise-v2.0 CALIBRATED -> nh-p-pepssi-3-pluto-v2.0 nh-x-pepssi-3-plutocruise-v2.0

New Horizons PEPSSI Data Set Evaluation Tools All Data Processing and Evaluation - Machine: Dell Precision M4800 Operating System: Windows 10

May 2016 Peer Review Lien Resolution Status

Liens and Resolution (1) Add documentation to discuss incomplete data Text added to dataset.cat Overview addresses this lien - RESOLVED Sequence table unclear as to planned vs. executed activities Text added to dataset.cat (Confidence Note) now states that these are planned - RESOLVED Update ref.cat to indicate that JPL internal documents are not generally accessible to anyone outside JPL UNRESOLVED – maybe add to CATINFO.TXT discussion of REF>CAT? rateboxdefinitionplanes.fit file is in a different directory than specified in the SIS File now located in the CALIB directory as stated in the SIS - RESOLVED The reason for the disconnect between in energies between the low and high resolution data should be discussed/described somewhere Text added to dataset.cat and pepssi.cat to explain this behavior - RESOLVED Typo in dataset.cat “flyby on 14.July, 2015” line 88  “14 July” - UNRESOLVED Typo in pepssi.cat "In this initial delivery“ line “In the initial” ” - UNRESOLVED Typos in rateboxdefinitionplanes.lbl “to one on nineteen”  “one of nineteen” - UNRESOLVED “positions 1 through 20148”  “positions 1 through 2048” - UNRESOLVED

Liens and Resolution (2) nhsc.cat: as shown in Figure 5  Figure 5 of [FOUNTAINETAL2008] - RESOLVED nhsc.cat: shown below in Table II  shown in [FOUNTAINETAL2008] Table 2 - RESOLVED

Documentation Evaluation

nh-p-pepssi-2-pluto-v2. 0/catalog nh-p-pepssi-3-pluto-v2 nh-p-pepssi-2-pluto-v2.0/catalog nh-p-pepssi-3-pluto-v2.0/catalog nh-x-pepssi-2-plutocruise-v2.0/catalog nh-x-pepssi-3-plutocruise-v2.0/catalog Root Level Files AAREADME: lines marked “skel_DELETE_BETWEEN_IF_INSTRUMENT_IS_rex” should be removed Pluto files only: AAREADME (line 65): …subphase on the day of Pluto flyby: the first period… Add Pluto flyby date (i.e. Pluto flyby (14 July 2015): …) VOLDESC – No changes

nh-p-pepssi-2-pluto-v2. 0/catalog nh-p-pepssi-3-pluto-v2 nh-p-pepssi-2-pluto-v2.0/catalog nh-p-pepssi-3-pluto-v2.0/catalog nh-x-pepssi-2-plutocruise-v2.0/catalog nh-x-pepssi-3-plutocruise-v2.0/catalog dataset.cat (1) Filename/Product IDs: PEP_0123456789_0X691_ENG.FIT | Application ID (ApID) of the telemetry data packet from which the data come N.B. ApIDs are case-insensitive All files on the volumes have 0x691 in the APID area of the filename but contain data from APIDs 0x691 to 0x694 internally. Change description to indicate that this is a placeholder field leftover from earlier versions (or whatever).

nh-p-pepssi-2-pluto-v2. 0/catalog nh-p-pepssi-3-pluto-v2 nh-p-pepssi-2-pluto-v2.0/catalog nh-p-pepssi-3-pluto-v2.0/catalog nh-x-pepssi-2-plutocruise-v2.0/catalog nh-x-pepssi-3-plutocruise-v2.0/catalog dataset.cat (2) ApIDs Data product description/Prefix(es) ===== =================================== 0x691 - PEPSSI High Priority Science/PEP 0x692 - PEPSSI Medium Priority Science/PEP 0x693 - PEPSSI Low Priority Science (Up to 500 PHA events)/PEP 0x694 - PEPSSI Low Priority Science (Up to add'l 500 PHA events)/PEP 0x695 - PEPSSI High Priority Science/PEP 0x696 - PEPSSI Medium Priority Science/PEP 0x697 - PEPSSI Low Priority Science (Up to 500 PHA events)/PEP 0x698 - PEPSSI Low Priority Science (Up to add'l 500 PHA events)/PEP Red items have same description of black items. SIS and pepssi.cat files only mention ApIDs 0x691-0x694. Are these included by mistake or do they need to described properly here and elsewhere?

nh-p-pepssi-2-pluto-v2. 0/catalog nh-p-pepssi-3-pluto-v2 nh-p-pepssi-2-pluto-v2.0/catalog nh-p-pepssi-3-pluto-v2.0/catalog dataset.cat (3) … This P2 Pluto Encounter dataset release provides updates to the Pluto dataset between P1 (data on the ground by 7/31/2015) and P2 (data on the ground by 1/31/2016). All liens from the initial Pluto delivery have also now been resolved. For PEPSSI, most of … Suggest leaving the text as it is but making it a true statement New typo – line 106 “event on 04.July, 2015 (DOY 185)”  “04 July,”

nh-p-pepssi-2-pluto-v2. 0/catalog nh-p-pepssi-3-pluto-v2 nh-p-pepssi-2-pluto-v2.0/catalog nh-p-pepssi-3-pluto-v2.0/catalog nh-x-pepssi-2-plutocruise-v2.0/catalog nh-x-pepssi-3-plutocruise-v2.0/catalog dataset.cat (4) … The PHA event data are 'raw' values and some subset of them are noise or other instrumental artifacts, so PHA events with parameters outside the stated instrument sensitivity limits (see SPECIFICATION above) should be ignored, or, at the very least, used with extreme caution. Please change “above” to “SPECIFICATIONS in the pepssi.cat file” or “SPECIFICATIONS in the PEPSSI instrument catalog file” since it is not “above” in the dataset.cat files (Note the ending “S” on SPECIFICATIONS). Note: This same statement occurs in both the -2- and -3- dataset.cat files. In the calibrated (-3-) data files, the PHA data should not be ‘raw’ and values outside the sensitivity limits of the instrument should not be present.

nh-p-pepssi-2-pluto-v2. 0 nh-p-pepssi-3-pluto-v2 nh-p-pepssi-2-pluto-v2.0 nh-p-pepssi-3-pluto-v2.0 nh-x-pepssi-2-plutocruise-v2.0 nh-x-pepssi-3-plutocruise-v2.0 document/aa_generic_readme/e_filenames.txt Filename/Product IDs: PEP_0123456789_0X691_ENG.FIT | Application ID (ApID) of the telemetry data packet from which the data come (see Note FN2) All files on the volumes have 0x691 in the APID area of the filename but contain data from APIDs 0x691 to 0x694 internally. Change description to indicate that this is a placeholder field leftover from earlier versions (or whatever). Same issue raised for dataset.cat files

Data Evaluation

FV view of level-3 Flux table for day of Pluto C/A (7/14/2015) pep_0299137915_0x691_sci.fit In the May review I showed that the current version of FV was having difficulty reading and interpreting the bits in the FITs data files. In most files, the first record appeared to be ok and the following records were garbled. In some cases, you could see a shifting of data values along the columns of the rows as though the record length was either wrong or being misinterpreted. For this review, I downloaded FV again (dated 9/15/2015 so it should be the same version I used last time) and examined the files. All PEPSSI files I examined looked structurally fine. I can read the time and data columns and everything looks as expected. I don’t know if this is a change in FV, a correction in the FITS headers, or a update in the Windows 10 O/S The first data on July 14, 2015 occur slightly after 18:00 UTC. Closest Approach was at 11:49 UTC. Where are the Pluto data?

nh-p-pepssi-3-pluto-v2.0/data For are least the Pluto calibrated (-3-) data, the files covering the time period between 7/12 – 7/16 appear to all begin at ~18:00 rather than 00:00. This my be a time-tagging issue. However, if it is not, then the data from Pluto C/A (11:49) are missing. Files outside this window have time tags that begin near 00:00 and extend to ~23:59 See Rudy’s presentation starting on slide 32 for a detailed discussion of issues related to the data sets (Cruise and Pluto).

Summary of Liens Correct all liens from the previous review listed on slide 5 Dataset.cat issues to be corrected Update file naming discussion to note that all files use 0x691 in the names regardless of which ApID was used to telemeter the data (do same for e_filenames.txt in /document/aaa_generic_readme area) Either define the contents of ApIDs 0x695-0x698 in the SIS and elsewhere and update the table to reflect that these contain something other than what is in ApIDs 0x691-0x694 or remove these 4 rows from the table. Update the SPECICATIONS pointer from “above” to the pepssi.cat file Fix typo listed on slide 11 AAREADME.TXT – add Pluto flyby date as suggested on slide 8 Data Rudy raises many issues regarding the data processing/calibration that should be addressed. For data files covering the dates 7/12 – 7/16, the files all appear to be missing data from the first ~18 hrs of the day – this needs to be corrected.