Data Set Overview  :   This data set contains Raw data taken by New Horizons  Long Range Reconnaissance Imager  instrument during the PLUTO mission phase.   LORRI is a narrow angle (Field Of View, FOV : 0.29 degree square), high  resolution (5 microradian/pixel), telescope. A two-dimensional (2-D) CCD detector, with 1024x1024 pixels (optically active region) operates in  standard frame-transfer mode. LORRI can also perform on-chip 4x4 binning to produce images of 256x256 pixels. LORRI has no color filters and so  provides panchromatic imaging over a wide bandpass extending  approximately from 350 nm to 850 nm. The common data product is a 2-D  image of brightnesses that can be calibrated to physical units once  color spectrum information is known. Refer to DOCUMENT/SOC_INST_ICD.*  for more detail.   During the Pluto Charon Encounter mission phase starting in January,  2015, there were several sub-phases: three Approach sub-phases, (AP1,  AP2 and AP3); a CORE sequence for the Pluto flyby on 14 July, 2015  (Day Of Year 195), sometimes also referred to as NEP (Near-Encounter  Phase); three Departure sub-phases (DP1, DP2, DP3); a Transition  sub-phase closing out the Pluto Encounter mission phase ending in late  October, 2016. For this final LORRI delivery for the Pluto mission  phase, this data set includes the Approach data plus all CORE,  Departure and Transition sequences' data downlinked through the end of  October, 2016, including observations of Trans-Neptunian Object (TNO)  15810 Arawn (1994 JR1) and a low-resolution ring search taken in  November, 2015. Transition activities in 2016 include observations of  several KBOs and a calibration campaign.   This dataset includes (1) Non-Critical and Critical Optical Navigation  (OpNav) observations; (2) Hazard observations; (3) Observations of  Pluto, Charon, Nix, Hydra, Kerberos, and Styx during Approach; (4)  Pluto Encounter observations, from the day before and the day of  encounter; (5) Departure observations of Pluto; (6) Departure and  Transition observations of TNOs and calibration stars.   Optical Navigation images, identified by NAV in the observation name,  were taken regularly up until 2 days before closest approach. This  dataset also includes three OpNav images from 2 days after closest  approach.   Hazard observations were taken in order to perform a detailed search  for any objects that could only be seen as the spacecraft neared the  Pluto system. Sets of images were taken about every two weeks starting  two months before closest approach. Each set had 8 images, with a  mosaic of 4 images at two different roll angles.   Approach observation objectives were to search for changes with pan  imaging over multiple rotations, perform satellite photometry to  further resolve the orbits of Kerberos, Styx, and possible other  bodies, and image Nix and Hydra.   Encounter observation objectives were to obtain maximum resolution  imaging of the entire surface of Pluto and Charon at regular  longitudinal intervals for cartographic knowledge; to observe Pluto  and Charon at a small (12-30 degrees) solar phase angle to support  phase integrals; and to obtain regional stereo images of Pluto for  stereographic mapping at the highest possible resolution, which is  essential for understanding the relief of features on Pluto, and  understanding the magnitude of geologic processes and the origin of  geologic features.   Transition observation objectives were to obtain imaging of several  KBOs including a light curve sequence of 15810 Arawn, and to execute a  post-Pluto calibration campaign to feed back into the calibration of  encounter data.   Every observation provided in this data set was taken as a part of a  particular sequence. A list of these sequences has been provided in  file DOCUMENT/SEQ_LORRI_PLUTO.TAB.  N.B. Some sequences provided may have no corresponding observations.   For a list of observations, refer to the data set index table. This  is typically INDEX.TAB initially in the INDEX/ area of the data set.  There is also a file SLIMINDX.TAB in INDEX/ that summarizes key  information relevant to each observation, including which sequence  was in effect and what target was likely intended for the  observation.    Version  :   This is VERSION 3.0 of this data set.   The TARGET_NAME values were expanded and made more consistent across  all instruments with version 3.0 of the data set.   General statement about data set versions after V1.0  ----------------------------------------------------  The pipeline (see Processing below) was re-run on these data for each  version since the first (V1.0). That will typically change only the  FITS headers but not the FITS data of raw data sets. In some cases  this may change the calibration because the calculated geometry of an  observation has changed. See data set version-specific sections below  for significant exceptions to this general statement, i.e. changes to  pipeline processing, calibration processing, and data delivered.   An all-instrument Calibration Campaign occurred in July 2016. For all  instruments, calibrations were updated as of April 2017 which changed  the data in the calibrated data sets. Calibration changes are described  in the data set version-specific sections.   Note that even if this is not a calibrated data set, calibration  changes are listed as the data will have been re-run and there will be  updates to the calibration files, to the documentation (Science  Operations Center - Instrument Interface Control Document:  SOC_INST_ICD) and to the steps required to calibrate the data.     LORRI updates for Pluto Encounter  Data Sets V3.0  :   This P3 Pluto Encounter dataset release includes all data from the  previous two Pluto deliveries and adds data that was downlinked from  1/31/2016 through 10/31/2016. This dataset completes delivery of all  data covering the Pluto Encounter and subsequent Calibration Campaign.   This dataset contains data from the Pluto Encounter timeframe as well  as two ring search observations and imaging of the KBO plutino JR1 in  November of 2015. The additional LORRI observations are listed below:  Request ID|Obs. Start Time (S/C UTC)|Downlink Complete (GRT)|Obs. Target PELR_PC_MULTI_MAP_A_18_L1AH 2015-188_15:54:47 2016-075T10:15:02 Pluto, Charon PELR_PC_MULTI_MAP_B_1 2015-188_22:24:49 2016-120T19:44:12 Pluto, Charon PELR_NH_APPR_B_1_01 2015-188_22:29:11 2016-133T19:26:10 Pluto System PELR_NH_APPR_B_1_02 2015-188_22:33:51 2016-141T09:52:54 Pluto System PELR_PC_MULTI_MAP_B_2 2015-189_07:55:49 2016-120T20:34:17 Pluto, Charon PELR_PC_MULTI_MAP_B_3 2015-189_15:57:49 2016-080T06:46:12 Pluto, Charon PELR_PC_MULTI_MAP_B_4 2015-189_22:35:49 2016-120T21:26:19 Pluto, Charon PELR_PC_MULTI_MAP_B_5 2015-190_04:01:57 2016-120T22:47:14 Pluto, Charon PELR_NH_APPR_B_2_01 2015-190_04:06:21 2016-141T10:33:16 Pluto System PELR_NH_APPR_B_2_02 2015-190_04:11:01 2016-133T18:50:40 Pluto System PELR_PC_MULTI_MAP_B_6 2015-190_15:46:47 2016-075T08:35:32 Pluto, Charon PELR_PC_MULTI_MAP_B_7 2015-190_22:15:47 2016-121T03:01:58 Pluto, Charon PELR_NH_APPR_B_3_02 2015-190_22:24:51 2016-133T17:43:25 Pluto System PELR_PC_MULTI_MAP_B_8 2015-191_07:47:28 2016-063T22:27:56 Pluto, Charon PELR_PC_MULTI_MAP_B_8 2015-191_07:48:43 2016-121T05:18:43 Pluto, Charon PELR_PC_MULTI_MAP_B_9 2015-191_15:49:47 2016-063T20:44:14 Pluto, Charon PELR_U_SAT_RING_L4X4_1 2015-191_17:34:54 2016-239T14:32:24 Ring Search PELR_PC_MULTI_MAP_B_10 2015-191_22:27:47 2016-114T20:26:10 Pluto, Charon PELR_PC_MULTI_MAP_B_11_01 2015-192_02:36:57 2016-114T19:19:06 Pluto, Charon PELR_PC_MULTI_MAP_B_11_02 2015-192_02:38:07 2016-109T05:20:58 Pluto, Charon PELR_NH_APPR_B_4_01 2015-192_02:42:31 2016-133T18:16:56 Pluto System PELR_PC_MULTI_MAP_B_12_L1AH_01 2015-192_15:38:17 2016-115T17:03:00 P, C PELR_PC_MULTI_MAP_B_12_L1AH_02 2015-192_15:39:57 2016-115T18:06:34 P, C PELR_PC_MULTI_MAP_B_13_01 2015-192_22:07:17 2016-113T23:17:03 Pluto, Charon PELR_PC_MULTI_MAP_B_13_02 2015-192_22:08:57 2016-114T03:59:53 Pluto, Charon PELR_NH_APPR_B_5_01 2015-192_22:13:17 2016-126T02:03:39 Pluto System PELR_NH_APPR_B_5_02 2015-192_22:17:56 2016-126T03:01:18 Pluto System PELR_PC_MULTI_MAP_B_14_01 2015-193_07:38:58 2016-131T04:51:44 Pluto, Charon PELR_PC_MULTI_MAP_B_14_02 2015-193_07:42:32 2016-114T07:56:12 Pluto, Charon PELR_PC_MULTI_MAP_B_15_01 2015-193_15:41:17 2016-114T01:59:22 Pluto, Charon PELR_PC_MULTI_MAP_B_15_02 2015-193_15:42:57 2016-097T14:22:34 Pluto, Charon PELR_PC_MULTI_MAP_B_16_01 2015-193_22:19:17 2016-114T14:31:01 Pluto, Charon PELR_PC_MULTI_MAP_B_16_02 2015-193_22:20:57 2016-114T16:00:23 Pluto, Charon PELR_P_CLOUD_1 2015-194_03:34:51 2016-148T22:19:26 Pluto PELR_P_CLOUD_2_a 2015-194_04:03:51 2016-160T10:12:25 Pluto PELR_P_CLOUD_2_b 2015-194_04:23:51 2016-149T03:25:26 Pluto PELR_PC_MULTI_MAP_B_18_01 2015-194_06:35:17 2016-114T17:15:25 Pluto, Charon PELR_P_CLOUD_3_a 2015-194_07:22:01 2016-160T10:57:18 Pluto PELR_U_SAT_RING_L4X4_2 2015-194_07:24:45 2016-232T05:09:12 Ring Search PELR_P_CLOUD_3_b 2015-194_07:35:21 2016-149T04:13:40 Pluto PELR_H_LORRI_APPR_1d1 2015-194_14:26:31 2016-114T21:19:18 Hydra PELR_N_LORRI_APPR_1d1 2015-194_14:33:11 2016-115T02:34:47 Nix PELR_PCNH_MULTI_LONG_1d1_01 2015-194_14:35:51 2016-121T06:09:01 P, C, Nix, Hydra PELR_PC_AIRGLOW_FILL_2_02 2015-194_19:25:13 2016-121T06:44:59 Pluto, Charon PELR_PC_AIRGLOW_FILL_2_06 2015-194_19:50:13 2016-121T07:23:52 Pluto, Charon PELR_P_LORRI_FULLFRAME 2015-194_20:14:07 2016-086T06:28:20 Pluto PELR_PC_MULTI_LONG_1d2a_02 2015-194_21:02:22 2016-148T12:01:13 Pluto, Charon PELR_PC_MULTI_LONG_1d2b 2015-194_23:10:33 2016-151T12:31:03 Pluto, Charon PELR_P_LORRI_TIMERES_1 2015-195_00:33:17 2016-160T17:19:52 Pluto PELR_P_LORRI_TIMERES_2 2015-195_02:36:45 2016-151T16:44:33 Pluto PELR_P_LORRI_TIMERES_3 2015-195_02:49:47 2016-168T15:19:14 Pluto PELR_C_LORRI_FULLFRAME_2 2015-195_02:54:51 2016-151T18:05:20 Charon PELR_P_LORRI_TIMERES_4 2015-195_04:06:21 2016-155T03:49:44 Pluto PELR_N_LORRI_1 2015-195_04:39:16 2016-135T20:22:44 Nix PELR_H_LORRI_1 2015-195_04:56:13 2016-071T09:53:06 Hydra PELR_H_LORRI_BEST 2015-195_07:41:06 2016-094T18:46:49 Hydra PELR_P_LORRI 2015-195_08:17:03 2016-120T03:37:40 Pluto PELR_C_LORRI 2015-195_08:34:55 2016-129T20:10:09 Charon PELR_N_LEISA_LORRI_BEST 2015-195_09:57:13 2016-295T02:23:55 Nix PELR_C_LEISA_HIRES 2015-195_10:23:47 2016-137T10:56:13 Charon PELR_P_LEISA_HIRES 2015-195_10:44:00 2016-297T12:40:10 Pluto PELR_P_MPAN_1 2015-195_11:17:48 2016-181T19:22:26 Pluto PELR_P_MPAN_1 2015-195_11:17:48 2016-181T19:22:26 Pluto PELR_P_MVIC_LORRI_CA 2015-195_11:26:28 2016-263T13:25:25 Pluto PELR_P_MVIC_LORRI_CA 2015-195_11:26:28 2016-263T13:25:25 Pluto PELR_P_MVIC_LORRI_CA 2015-195_11:26:28 2016-263T13:25:25 Pluto PELR_C_MVIC_LORRI_CA 2015-195_11:43:07 2016-179T02:15:29 Charon PELR_P_HIPHASE_HIRES 2015-195_11:58:30 2016-262T06:58:00 Pluto PELR_H_DEP_SOONEST 2015-195_14:44:55 2016-271T06:01:33 Hydra PELR_P_DEP_SOONEST 2015-195_15:06:47 2016-059T21:57:09 Pluto PELR_P_LORRI_DEP_0 2015-195_18:25:54 2016-072T10:54:59 Pluto PELR_PC_MULTI_DEP_LONG_2_01 2015-195_19:06:24 2016-292T02:52:28 Pluto, Charon PELR_PC_MULTI_DEP_LONG_2_04 2015-195_19:34:49 2016-141T11:19:46 Pluto, Charon PELR_P_LORRI_ALICE_DEP_2 2015-195_22:09:06 2016-086T01:44:34 Pluto PELR_N_LORRI_HIPHASE_2 2015-195_23:04:51 2016-136T09:14:46 Nix PELR_P_LORRI_ALICE_DEP_3 2015-196_00:03:11 2016-063T19:38:03 Pluto PELR_P_DEEPIM 2015-196_01:57:27 2016-056T21:09:08 Pluto PELR_H_LORRI_HIPHASE_2 2015-196_02:38:47 2016-099T17:11:25 Hydra PELR_N_LORRI_HIPHASE_3 2015-196_02:43:11 2016-098T15:58:15 Nix PELR_PC_MULTI_DEP_LONG_3_01 2015-196_03:03:51 2016-136T05:19:22 Pluto, Charon PELR_PC_MULTI_DEP_LONG_3_04 2015-196_03:24:03 2016-136T06:44:15 Pluto, Charon PELR_C_LORRI_DEP_2 2015-196_06:55:31 2016-160T09:30:09 Charon PELR_P_LORRI_ALICE_DEP_4 2015-196_07:01:47 2016-136T15:59:54 Pluto PELR_PC_SLIVER_A_1_01 2015-196_15:20:51 2016-115T18:46:42 Pluto, Charon PELR_PC_SLIVER_A_1_02 2015-196_15:23:35 2016-161T04:45:41 Pluto, Charon PELR_PC_SLIVER_A_2_01 2015-196_18:19:25 2016-161T04:51:47 Pluto, Charon PELR_PC_SLIVER_A_2_02 2015-196_18:22:05 2016-172T18:06:53 Pluto, Charon PELR_PC_SLIVER_A_3_01 2015-196_21:17:21 2016-136T16:41:06 Pluto, Charon PELR_PC_SLIVER_A_3_02 2015-196_21:20:01 2016-115T19:26:19 Pluto, Charon PELR_PC_SLIVER_A_4_01 2015-197_00:19:25 2016-172T18:02:54 Pluto, Charon PELR_PC_SLIVER_A_4_02 2015-197_00:22:05 2016-172T17:59:06 Pluto, Charon PELR_N_DEP_A 2015-197_00:28:21 2016-136T11:01:18 Nix PELR_H_DEP_A 2015-197_00:38:19 2016-136T13:33:13 Hydra PELR_PC_SLIVER_A_5_01 2015-197_03:18:51 2016-136T17:22:23 Pluto, Charon PELR_PC_SLIVER_A_5_02 2015-197_03:21:35 2016-161T04:59:02 Pluto, Charon PELR_PC_SLIVER_A_6_01 2015-197_09:17:51 2016-136T18:03:56 Pluto, Charon PELR_PC_SLIVER_A_6_02 2015-197_09:20:35 2016-172T17:54:37 Pluto, Charon PELR_PC_SLIVER_A_7_01 2015-197_15:11:52 2016-136T18:45:12 Pluto, Charon PELR_PC_SLIVER_A_7_02 2015-197_15:14:12 2016-142T11:25:01 Pluto, Charon PELR_PC_SLIVER_A_8_01 2015-197_18:11:21 2016-123T04:48:01 Pluto, Charon PELR_PC_SLIVER_A_8_02 2015-197_18:13:41 2016-123T05:45:29 Pluto, Charon PELR_PC_SLIVER_A_9_01 2015-197_21:10:51 2016-140T14:36:24 Pluto, Charon PELR_PC_SLIVER_A_9_02 2015-197_21:13:11 2016-140T15:18:40 Pluto, Charon PELR_PC_SLIVER_A_10_01 2015-198_00:10:21 2016-140T15:59:57 Pluto, Charon PELR_PC_SLIVER_A_10_02 2015-198_00:12:41 2016-140T12:57:29 Pluto, Charon PELR_C_PLUTOLIGHT_1 2015-198_00:20:14 2016-059T20:06:46 Charon PELR_PC_SLIVER_A_11_01 2015-198_03:09:51 2016-140T16:41:03 Pluto, Charon PELR_PC_SLIVER_A_11_02 2015-198_03:12:11 2016-140T17:22:01 Pluto, Charon PELR_PC_SLIVER_A_12_01 2015-198_07:35:51 2016-123T06:42:34 Pluto, Charon PELR_PC_SLIVER_A_12_02 2015-198_07:38:11 2016-123T07:58:31 Pluto, Charon PELR_PC_SLIVER_A_13_01 2015-198_12:37:51 2016-140T18:03:23 Pluto, Charon PELR_PC_SLIVER_A_13_02 2015-198_12:40:11 2016-140T18:44:35 Pluto, Charon PELR_PC_SLIVER_A_14_01 2015-198_15:37:21 2016-140T19:25:46 Pluto, Charon PELR_PC_SLIVER_A_14_02 2015-198_15:39:41 2016-140T21:45:04 Pluto, Charon PELR_PC_SLIVER_A_15_01 2015-198_18:36:51 2016-140T20:07:16 Pluto, Charon PELR_PC_SLIVER_A_15_02 2015-198_18:39:11 2016-140T20:53:03 Pluto, Charon PELR_PC_SLIVER_A_16_01 2015-198_21:40:11 2016-140T22:55:33 Pluto, Charon PELR_PC_SLIVER_A_16_02 2015-198_21:42:31 2016-141T09:31:49 Pluto, Charon PELR_PC_SLIVER_A_17_01 2015-199_00:35:51 2016-141T12:21:46 Pluto, Charon PELR_PC_SLIVER_A_17_02 2015-199_00:38:11 2016-141T13:12:37 Pluto, Charon PELR_PC_SLIVER_A_18a 2015-199_06:34:51 2016-141T14:25:26 Pluto, Charon PELR_PC_SLIVER_A_18b 2015-199_07:33:51 2016-123T19:28:11 Pluto, Charon PELR_PC_SLIVER_A_19 2015-199_12:33:51 2016-141T18:06:40 Pluto, Charon PELR_PC_SLIVER_A_20 2015-199_15:33:21 2016-123T20:25:57 Pluto, Charon PELR_PC_SLIVER_A_21 2015-199_18:32:51 2016-141T18:48:14 Pluto, Charon PELR_PC_SLIVER_A_22 2015-199_21:32:21 2016-141T19:29:26 Pluto, Charon PELR_PC_SLIVER_A_23 2015-200_00:31:51 2016-123T21:05:49 Pluto, Charon PELR_PC_SLIVER_A_24a 2015-200_06:31:06 2016-141T20:10:54 Pluto, Charon PELR_PC_SLIVER_A_24b 2015-200_07:33:21 2016-124T01:21:37 Pluto, Charon PELR_PC_SLIVER_A_25 2015-200_12:29:51 2016-124T02:35:07 Pluto, Charon PELR_PC_SLIVER_A_26 2015-200_15:29:21 2016-141T20:59:59 Pluto, Charon PELR_PC_SLIVER_A_27 2015-200_18:28:51 2016-141T21:53:44 Pluto, Charon PELR_PC_SLIVER_A_28 2015-200_21:28:21 2016-124T03:36:02 Pluto, Charon PELR_PC_SLIVER_A_29 2015-201_00:27:51 2016-141T23:02:54 Pluto, Charon PELR_PC_SLIVER_A_30 2015-201_06:26:51 2016-142T08:20:53 Pluto, Charon DPLR_PC_SLIVER_A_31 2015-201_12:55:51 2016-142T09:17:55 Pluto, Charon DPLR_PC_SLIVER_A_32 2015-201_15:45:51 2016-142T10:12:25 Pluto, Charon DPLR_PC_SLIVER_A_33 2015-201_18:45:51 2016-124T04:26:51 Pluto, Charon DPLR_PC_SLIVER_A_34 2015-201_21:45:51 2016-149T04:45:54 Pluto, Charon DPLR_PC_SLIVER_A_35 2015-202_00:45:47 2016-142T13:12:14 Pluto, Charon DPLR_PC_SLIVER_A_36 2015-202_03:45:47 2016-124T06:07:18 Pluto, Charon DPLR_PC_SLIVER_A_37 2015-202_04:22:21 2016-142T15:13:26 Pluto, Charon DPLR_PC_SLIVER_202_SCI1A 2015-202_12:21:38 2016-167T15:23:05 Pluto, Charon DPLR_O_RING_DEP_LORRI_202 2015-202_12:59:55 2016-161T18:04:21 Ring Search DPLR_O_RING_DEP_LORRI_202 2015-202_13:00:09 2016-223T08:08:49 Ring Search DPLR_PC_SLIVER_202_SCI1B 2015-202_16:19:38 2016-167T14:41:03 Pluto, Charon DPLR_PC_SLIVER_203_SCI1A 2015-203_03:37:16 2016-167T12:44:40 Pluto, Charon DPLR_PC_SLIVER_203_SCI1B 2015-203_06:35:12 2016-167T10:37:06 Pluto, Charon DPLR_PC_SLIVER_203_SCI1C 2015-203_09:37:16 2016-168T15:39:10 Pluto, Charon DPLR_PC_SLIVER_203_SCI1D 2015-203_12:36:42 2016-167T09:04:20 Pluto, Charon DPLR_PC_SLIVER_204_SCI1A 2015-204_00:29:45 2016-167T08:17:57 Pluto, Charon DPLR_PC_SLIVER_204_SCI1B 2015-204_03:29:14 2016-161T01:02:48 Pluto, Charon DPLR_PC_SLIVER_204_SCI1C 2015-204_06:28:44 2016-167T07:24:10 Pluto, Charon DPLR_PC_SLIVER_204_SCI2A 2015-204_16:53:44 2016-167T06:29:18 Pluto, Charon DPLR_PC_SLIVER_204_SCI2B 2015-204_21:55:44 2016-161T01:53:36 Pluto, Charon DPLR_PC_SLIVER_205_SCI1A 2015-205_06:58:04 2016-167T04:12:22 Pluto, Charon DPLR_PC_SLIVER_205_SCI1B 2015-205_09:53:44 2016-167T03:38:21 Pluto, Charon DPLR_PC_SLIVER_206_SCI1A 2015-206_00:51:14 2016-167T03:05:34 Pluto, Charon DPLR_PC_SLIVER_206_SCI1B 2015-206_03:50:44 2016-166T17:58:02 Pluto, Charon DPLR_PC_SLIVER_206_SCI2A 2015-206_15:48:59 2016-166T18:39:52 Pluto, Charon DPLR_PC_SLIVER_206_SCI2B 2015-206_16:51:14 2016-161T02:42:59 Pluto, Charon DPLR_PC_SLIVER_206_SCI2C 2015-206_21:47:44 2016-166T19:27:34 Pluto, Charon DPLR_PC_SLIVER_207_SCI1A 2015-207_06:46:14 2016-166T20:22:16 Pluto, Charon DPLR_PC_SLIVER_207_SCI1B 2015-207_09:45:44 2016-166T23:21:49 Pluto, Charon DPLR_PC_SLIVER_208_SCI1A 2015-208_01:03:51 2016-167T18:33:25 Pluto, Charon DPLR_PC_SLIVER_208_SCI1B 2015-208_04:03:51 2016-167T19:21:05 Pluto, Charon DPLR_PC_SLIVER_208_SCI2A 2015-208_13:03:47 2016-161T04:38:14 Pluto, Charon DPLR_PC_SLIVER_208_SCI2B 2015-208_13:40:21 2016-168T00:58:39 Pluto, Charon DPLR_PC_SLIVER_208_SCI2C 2015-208_14:10:36 2016-168T02:39:16 Pluto, Charon DPLR_PC_SLIVER_208_SCI2D 2015-208_14:19:38 2016-168T04:46:14 Pluto, Charon DPLR_PC_SLIVER_208_SCI2E 2015-208_15:38:19 2016-172T14:59:28 Pluto, Charon DPLR_PC_SLIVER_208_SCI2F 2015-208_16:44:53 2016-172T12:18:41 Pluto, Charon DPLR_PC_SLIVER_208_SCI2G 2015-208_18:38:58 2016-172T03:01:12 Pluto, Charon DPLR_PC_SLIVER_208_SCI2H 2015-208_21:39:38 2016-172T10:17:09 Pluto, Charon DPLR_PC_SLIVER_209_SCI1A 2015-209_09:56:42 2016-172T17:50:07 Pluto, Charon DPLR_PC_SLIVER_209_SCI1B 2015-209_12:55:16 2016-161T18:45:31 Pluto, Charon DPLR_PC_SLIVER_210_SCI1A 2015-210_03:53:42 2016-172T17:07:20 Pluto, Charon DPLR_PC_SLIVER_210_SCI2A 2015-210_12:47:14 2016-172T16:24:59 Pluto, Charon DPLR_PC_SLIVER_210_SCI2B 2015-210_15:46:44 2016-172T15:42:23 Pluto, Charon DPLR_PC_SLIVER_210_SCI2C 2015-210_18:46:14 2016-172T01:20:32 Pluto, Charon DPLR_PC_SLIVER_210_SCI2D 2015-210_21:45:44 2016-172T18:53:26 Pluto, Charon DPLR_PC_SLIVER_211_SCI1A 2015-211_07:13:44 2016-173T00:43:20 Pluto, Charon DPLR_PC_SLIVER_211_SCI1B 2015-211_10:13:14 2016-173T01:34:47 Pluto, Charon DPLR_PC_SLIVER_211_SCI1C 2015-211_13:12:44 2016-173T02:26:16 Pluto, Charon DPLR_PC_SLIVER_211_SCI1D 2015-211_16:16:04 2016-173T03:27:05 Pluto, Charon DPLR_O_RING_DEP_LORRI_211 2015-211_16:59:55 2016-165T14:52:36 Ring Search DPLR_O_RING_DEP_LORRI_211 2015-211_17:00:09 2016-231T14:47:34 Ring Search DPLR_PC_SLIVER_211_SCI1E 2015-211_19:11:44 2016-173T04:40:52 Pluto, Charon DPLR_O_RING_DEP_LORRI_305B 2015-305_19:24:54 2016-043T18:32:33 Ring Search DPLR_O_RING_DEP_LORRI_305C 2015-305_21:36:54 2016-052T19:59:41 Ring Search TRLR_JR1_LORRI_DEEP 2016-098_18:59:53 2016-105T22:31:22 JR1 TRLR_JR1_LORRI_CLOSE 2016-098_19:49:07 2016-101T03:42:32 JR1 TRLR_JR1_LORRI_LIGHTCURVE_01 2016-098_20:29:55 2016-105T22:34:49 JR1 TRLR_JR1_LORRI_LIGHTCURVE_02 2016-099_01:29:55 2016-106T07:03:34 JR1 TRLR050_01_FunctionalLite 2016-185_02:02:22 2016-185T15:30:57 Calibration TRLR081b_01_NGC3532_full 2016-193_17:11:49 2016-211T11:47:12 NGC3532 TRLR081b_01_NGC3532_full 2016-193_17:13:29 2016-211T11:47:12 NGC3532 TRLR_LORRI_105a_Quaoar 2016-195_01:59:52 2016-206T13:05:48 Quaoar TRLR_LORRI_105b_Quaoar 2016-195_04:08:16 2016-206T13:33:18 Quaoar TRLR_LORRI_109a_JJ124 2016-195_04:59:50 2016-208T13:56:01 JJ124 TRLR_LORRI_109a_JJ124 2016-195_04:59:50 2016-208T13:56:01 JJ124 TRLR_LORRI_107a_JR1 2016-195_05:29:52 2016-218T16:00:52 JR1 TRLR_LORRI_107b_JR1 2016-195_06:29:52 2016-220T17:36:18 JR1 TRLR_LORRI_104a_Ixion 2016-195_07:29:52 2016-224T14:23:20 Ixion TRLR_LORRI_106a_MS4 2016-195_14:59:52 2016-225T06:51:56 MS4 TRLR_LORRI_105c_Quaoar 2016-196_00:05:52 2016-208T14:00:43 Quaoar TRLR_LORRI_105d_Quaoar 2016-196_02:18:16 2016-206T14:28:11 Quaoar TRLR_LORRI_109b_JJ124 2016-196_03:59:50 2016-207T16:37:58 JJ124 TRLR_LORRI_104b_Ixion 2016-196_06:29:52 2016-224T16:43:01 Ixion TRLR_LORRI_106b_MS4 2016-196_07:29:52 2016-226T10:49:20 MS4 TRLR_LORRI_108a_Chiron 2016-196_08:44:50 2016-233T23:26:17 Chiron TRLR102_HD37962_cal 2016-196_09:44:49 2016-292T06:00:41 Calibration TRLR103_HD205905_cal 2016-198_00:49:49 2016-292T06:00:41 Calibration TRLR_LORRI_108b_Chiron 2016-198_08:44:50 2016-237T07:46:36 Chiron    Also, updates were made to the calibration files, documentation, and  catalog files.   There were minor changes to the level 2 LORRI calibration process, as  well as to the LORRI calibration constants for the final Pluto P3 PDS  delivery.   The process change involves gap removal during calibration. Files  with gaps come in many flavors, depending on where the gap lies within  the image. This update recognizes some additional possiblities, mainly  that the gap might be close to the bottom or top of the image (and  therefore the previous algorithm would fail because it filled the gap  with median pixel info from both above and below the gap). The new  algorithm will take the info from one side of the gap exclusively,  when appropriate.   As of V3.0, targets for some stars and radio sources have been updated  so that the TARGET_NAME keyword in the label is accurate and more  descriptive than only STAR or CALIBRATION. However the user should  confirm that targets from the data FITS files, if applicable for a  given instrument, match the label name, as there are a few instances  where the FITS keywords for TARGET, SPCCBTNM, and PNTMTHD are not  accurate. The simplest way to check is to instead look at the RA  and Dec in the keywords SPCBRRA and SPCBRDEC in the FITS file.  This issue mostly only occurs with star targets.     LORRI updates for Pluto Encounter  Data Sets V2.0  :    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). This dataset contains data that may have  been downlinked with lossy compression initially and now has been  re-downlinked losslessly. Lossy data from P1 has been regenerated to  increase the number of flagged bad pixels in the quality map. All  liens from the initial Pluto delivery have also now been resolved.  This dataset contains data from the Pluto Encounter timeframe as well  as two ring search observations and imaging of the KBO plutino JR1 in  November of 2015. The additional observations are listed below:  Obs. Name (Request ID), Obs Date, Downlink Start, Downlink End, Obs. Target DPLR_JR1_LORRI_306A 2015-11-02 2015/325 2015/325 JR1 DPLR_JR1_LORRI_306B 2015-11-02 2015/325 2015/325 JR1 DPLR_JR1_LORRI_306C 2015-11-02 2015/325 2015/325 JR1 DPLR_JR1_LORRI_306D 2015-11-02 2015/325 2015/325 JR1 DPLR_O_RING_DEP_LORRI_305A 2015-11-01 2016/019 2016/027 Ring search DPLR_O_RING_DEP_LORRI_305B 2015-11-01 2016/029 2016/031 Ring search PELR_C_LEISA_HIRES 2015-07-14 2015/264 2015/264 Charon observations PELR_C_LEISA_LORRI_1 2015-07-14 2015/349 2015/349 Charon observations PELR_C_LORRI 2015-07-14 2015/278 2015/284 Charon observations PELR_C_LORRI_DEP_1 2015-07-14 2015/322 2015/325 Charon observations PELR_C_LORRI_FULLFRAME_1 2015-07-14 2015/249 2015/249 Charon observations PELR_C_LORRI_FULLFRAME_DEEP 2015-07-14 2016/024 2016/024 Charon observations PELR_C_LORRI_TIMERES_1 2015-07-14 2016/023 2016/024 Charon observations PELR_C_MVIC_LORRI_CA 2015-07-14 2015/283 2015/283 Charon observations PELR_C_PLUTOLIGHT_1 2015-07-17 2015/296 2016/023 Charon observations PELR_C_PLUTOLIGHT_2 2015-07-17 2015/296 2016/023 Charon observations PELR_H_LORRI_APPR_1d2 2015-07-13 2015/300 2015/300 Hydra observations PELR_H_LORRI_BEST 2015-07-14 2015/249 2015/249 Hydra observations PELR_NH_APPR_A_3 2015-06-29 2015/229 2015/229 Nix, Hydra observations PELR_NH_APPR_A_7_02 2015-07-03 2015/226 2015/226 Nix, Hydra observations PELR_NH_APPR_B_6_01 2015-07-13 2015/305 2015/305 Nix, Hydra observations PELR_NH_APPR_B_6_02 2015-07-13 2015/308 2015/308 Nix, Hydra observations PELR_N_DEP_SOONEST 2015-07-14 2015/248 2015/249 Nix observations PELR_N_LEISA_LORRI_BEST 2015-07-14 2015/287 2015/287 Nix observations PELR_N_LORRI_APPR_1d2 2015-07-13 2015/249 2015/249 Nix observations PELR_N_LORRI_BACKUP 2015-07-14 2015/248 2015/248 Nix observations PELR_N_ORBIT_B_DOY174 2015-06-23 2015/247 2015/247 Nix observations PELR_N_ORBIT_B_DOY176 2015-06-25 2015/246 2015/246 Nix observations PELR_N_ORBIT_B_DOY178 2015-06-27 2015/247 2015/247 Nix observations PELR_PCNH_MULTI_LONG_1d1_02 2015-07-13 2015/249 2015/249 Pluto, Ch, Nix, Hyd PELR_PCNH_MULTI_LONG_1d1_06 2015-07-13 2015/249 2015/249 Pluto, Ch, Nix, Hyd PELR_PC_AIRGLOW_FILL_2_04 2015-07-13 2015/298 2015/298 Pluto, Charon obs PELR_PC_AIRGLOW_FILL_2_08 2015-07-13 2015/318 2015/318 Pluto, Charon obs PELR_PC_MULTI_DEP_LONG_2_01 2015-07-14 2015/293 2015/296 Pluto, Charon obs PELR_PC_MULTI_DEP_LONG_2_05 2015-07-14 2015/295 2015/296 Pluto, Charon obs PELR_PC_MULTI_LONG_1d2a_01 2015-07-13 2015/248 2015/248 Pluto, Charon obs PELR_PC_MULTI_MAP_A_3 2015-07-02 2015/229 2015/229 Pluto, Charon obs PELR_PC_MULTI_MAP_A_5 2015-07-03 2015/229 2015/229 Pluto, Charon obs PELR_PC_MULTI_MAP_A_6 2015-07-03 2015/226 2015/226 Pluto, Charon obs PELR_PC_MULTI_MAP_A_7 2015-07-03 2015/223 2015/223 Pluto, Charon obs PELR_PC_MULTI_MAP_B_17_01 2015-07-13 2015/292 2015/292 Pluto, Charon obs PELR_PC_MULTI_MAP_B_17_02 2015-07-13 2015/304 2015/305 Pluto, Charon obs PELR_PC_MULTI_MAP_B_18_02 2015-07-13 2015/293 2015/308 Pluto, Charon obs PELR_PC_VISUV_MAP_B_11 2015-06-28 2015/236 2015/236 Pluto, Charon obs PELR_PC_VISUV_MAP_B_12 2015-06-29 2015/236 2015/236 Pluto, Charon obs PELR_PC_VISUV_MAP_B_19 2015-07-01 2015/229 2015/229 Pluto, Charon obs PELR_PC_VISUV_MAP_B_3 2015-06-26 2015/246 2015/246 Pluto, Charon obs PELR_PC_VISUV_MAP_B_5 2015-06-26 2015/246 2015/246 Pluto, Charon obs PELR_PC_VISUV_MAP_B_6 2015-06-27 2015/244 2015/244 Pluto, Charon obs PELR_PC_VISUV_MAP_B_9 2015-06-28 2015/244 2015/244 Pluto, Charon obs PELR_P_DEEPIM 2015-07-15 2015/296 2016/022 Pluto observations PELR_P_DEP_SOONEST 2015-07-14 2015/358 2016/003 Pluto observations PELR_P_HIPHASE_HIRES 2015-07-14 2015/315 2016/023 Pluto observations PELR_P_LEISA_HIRES 2015-07-14 2015/287 2015/348 Pluto observations PELR_P_LORRI 2015-07-14 2015/250 2015/254 Pluto observations PELR_P_LORRI_ALICE_DEP_1 2015-07-14 2015/314 2015/321 Pluto observations PELR_P_LORRI_FULLFRAME 2015-07-13 2015/249 2015/249 Pluto observations PELR_P_LORRI_FULLFRAME_DEP 2015-07-15 2015/249 2015/249 Pluto observations PELR_P_LORRI_STEREO_MOSAIC 2015-07-14 2015/201 2015/250 Pluto observations PELR_P_MPAN_1 2015-07-14 2015/263 2015/291 Pluto observations PELR_P_MULTI_DEP_LONG_1 2015-07-14 2015/265 2015/266 Pluto observations PELR_P_MVIC_LORRI_CA 2015-07-14 2015/323 2015/358 Pluto observations PELR_U_SATPHOT_2 2015-06-26 2015/246 2015/246 Satellite Photometry Mosaic PELR_U_SATPHOT_3 2015-06-27 2015/237 2015/237 Satellite Photometry Mosaic PELR_U_SATPHOT_4 2015-06-28 2015/244 2015/244 Satellite Photometry Mosaic PELR_U_SATPHOT_5 2015-06-29 2015/229 2015/233 Satellite Photometry Mosaic PELR_U_SATPHOT_7 2015-07-01 2015/229 2015/229 Satellite Photometry Mosaic PELR_U_SATPHOT_8 2015-07-01 2015/229 2015/229 Satellite Photometry Mosaic PELR_U_SATPHOT_9 2015-07-03 2015/226 2015/229 Satellite Photometry Mosaic PELR_U_TBD_1_01 2015-07-13 2015/348 2015/349 Kerberos observation PELR_U_TBD_1_02 2015-07-13 2015/278 2015/278 Styx observation PELR_U_TBD_2 2015-07-14 2015/293 2015/293 Kerberos observation       Processing  :   The data in this data set were created by a software data  processing pipeline on the Science Operations Center (SOC) at  the Southwest Research Institute (SwRI), Department of Space Operations. This SOC pipeline assembled data as FITS files from raw telemetry  packets sent down by the spacecraft and populated the data labels  with housekeeping and engineering values, and computed geometry  parameters using SPICE kernels. The pipeline did not resample  the data.   The first 34 pixels (51 bytes) of each LORRI image contain housekeeping  information. These bytes are corrupted by LOSSY compression. Please  refer to the DOCUMENT/SOC_INST_ICD.* file for details and implications  in raw and calibrated datasets.    Data  :   The observations in this data set are stored in data files using  standard Flexible Image Transport System (FITS) format. Each FITS  file has a corresponding detached PDS label file, named according  to a common convention. The FITS files may have image and/or table  extensions. See the PDS label plus the DOCUMENT files for a  description of these extensions and their contents.   This Data section comprises the following sub-topics:   - Filename/Product IDs  - Instrument description  - Other sources of information useful in interpreting these Data  - Visit Description, Visit Number, and Target in the Data Labels    Filename/Product IDs  --------------------   The filenames and product IDs of observations adhere to a  common convention e.g.   LOR_0123456789_0X630_ENG.FIT  ^^^ ^^^^^^^^^^ ^^^^^ ^^^\__/  | | | | ^^  | | | | |  | | | | +--File type (includes dot)  | | | | - .FIT for FITS file  | | | | - .LBL for PDS label  | | | | - not part of product ID  | | | |  | | | +--ENG for CODMAC Level 2 data  | | | SCI for CODMAC Level 3 data  | | |  | | +--Application ID (ApID) of the telemetry data  | | packet from which the data come  | | N.B. ApIDs are case-insensitive  | |  | +--MET (Mission Event Time) i.e. Spacecraft Clock  |  +--Instrument designator    Note that, depending on the observation, the MET in the data filename  and in the Product ID may be similar to the Mission Event Time (MET)  of the actual observation acquisition, but should not be used as an  analog for the acquisition time. The MET is the time that the data are  transferred from the instrument to spacecraft memory and is therefore  not a reliable indicator of the actual observation time. The PDS label  and the index tables are better sources to use for the actual timing of  any observation. The specific keywords and index table column names for which to look are   * START_TIME  * STOP_TIME  * SPACECRAFT_CLOCK_START_COUNT  * SPACECRAFT_CLOCK_STOP_COUNT    Instrument Instrument designators ApIDs **  : : :  LORRI LOR 0X630 - 0X63B *   * Not all values in this range are in this data set  ** ApIDs are case insensitive   There are other ApIDs that contain housekeeping values and  other values. See SOC Instrument ICD (/DOCUMENT/SOC_INST_ICD.*)  for more details.    Here is a summary of the types of files generated by each ApID  (N.B. ApIDs are case-insensitive) along with the instrument  designator that go with each ApID:    ApIDs Data product description/Prefix(es)  : :  0x630 - LORRI High-res Lossless (CDH 1)/LOR  0x636 - LORRI High-res Lossless (CDH 2)/LOR  0x632 - LORRI High-res Lossy (CDH 1)/LOR  0x638 - LORRI High-res Lossy (CDH 2)/LOR  0x631 - LORRI High-res Packetized (CDH 1)/LOR  0x637 - LORRI High-res Packetized (CDH 2)/LOR  0x633 - LORRI 4x4 Binned Lossless (CDH 1)/LOR  0x639 - LORRI 4x4 Binned Lossless (CDH 2)/LOR  0x635 - LORRI 4x4 Binned Lossy (CDH 1)/LOR  0x63B - LORRI 4x4 Binned Lossy (CDH 2)/LOR  0x634 - LORRI 4x4 Binned Packetized (CDH 1)/LOR  0x63A - LORRI 4x4 Binned Packetized (CDH 2)/LOR    Instrument description  ----------------------   Refer to the following files for a description of this instrument.   CATALOG   LORRI.CAT   DOCUMENTS   LORRI_SSR.*  SOC_INST_ICD.*  NH_LORRI_V###_TI.TXT (### is a version number)    Other sources of information useful in interpreting these Data  --------------------------------------------------------------   Refer to the following files for more information about these data   NH Trajectory tables:   /DOCUMENT/NH_MISSION_TRAJECTORY.* - Heliocentric   LORRI Field Of View definitions:   /DOCUMENT/NH_FOV.*  /DOCUMENT/NH_LORRI_V###_TI.TXT     Visit Description, Visit Number, and Target in the Data Labels  ---------------------------------------------------------------   The observation sequences were defined in Science Activity Planning  (SAP) documents, and grouped by Visit Description and Visit Number.  The SAPs are spreadsheets with one Visit Description & Number per row.  A nominal target is also included on each row and included in the data  labels, but does not always match with the TARGET_NAME field's value in  the data labels. In some cases, the target was designated as RA,DEC  pointing values in the form ``RADEC:123.45,-12.34'' indicating Right  Ascension and Declination, in degrees, of the target from the  spacecraft in the Earth Equatorial J2000 inertial reference frame.  This indicates either that the target was either a star, or that the  target's ephemeris was not loaded into the spacecraft's attitude and  control system which in turn meant the spacecraft could not be pointed  at the target by a body identifier and an inertial pointing value had  to be specified as Right Ascension and Declination values. PDS-SBN  practices do not allow putting a value like RADEC:... in the PDS  TARGET_NAME keyword's value. In those cases the PDS TARGET_NAME value  is set to CALIBRATION. TARGET_NAME may be N/A (Not Available or Not  Applicable) for a few observations in this data set; typically that  means the observation is a functional test so N/A is an appropriate  entry for those targets, but the PDS user should also check the  NEWHORIZONS:OBSERVATION_DESC and NEWHORIZONS:SEQUENCE_ID keywords in  the PDS label, plus the provided sequence list (see Ancillary Data  below) to assess the possibility that there was an intended target.  These two keywords are especially useful for STAR targets as often  stars are used as part of instrument calibrations, and are  included as part of the sequencing description which is captured  in these keywords.     Ancillary Data  :   The geometry items included in the data labels were computed  using the SPICE kernels archived in the New Horizons SPICE  data set, NH-X-SPICE-6-PLUTO-V1.0.   Every observation provided in this data set was taken as a part of a  particular sequence. A list of these sequences has been provided in  file DOCUMENT/SEQ_LORRI_PLUTO.TAB. In addition, the  sequence identifier (ID) and description are included in the PDS label  for every observation. N.B. While every observation has an associated  sequence, every sequence may not have associated observations. Some  sequences may have failed to execute due to spacecraft events (e.g.  safing). No attempt has been made during the preparation of this data  set to identify such empty sequences, so it is up to the user to  compare the times of the sequences to the times of the available  observations from INDEX/INDEX.TAB to identify such sequences.    Time  :   There are several time systems, or units, in use in this dataset:  New Horizons spacecraft MET (Mission Event Time or Mission Elapsed  Time), UTC (Coordinated Universal Time), and TDB Barycentric  Dynamical Time.   This section will give a summary description of the relationship  between these time systems. For a complete explanation of these  time systems the reader is referred to the documentation  distributed with the Navigation and Ancillary Information  Facility (NAIF) SPICE toolkit from the PDS NAIF node, (see  http://naif.jpl.nasa.gov/).   The most common time unit associated with the data is the spacecraft  MET. MET is a 32-bit counter on the New Horizons spacecraft that  runs at a rate of about one increment per second starting from a  value of zero at   19.January, 2006 18:08:02 UTC   or   JD2453755.256337 TDB.   The leapsecond adjustment (DELTA_ET : ET - UTC) was 65.184s at  NH launch, and the first three additional leapseconds occurred  in at the ends of December, 2009, June, 2012 and June, 2015.  Refer to the NH SPICE data set, NH-J/P/SS-SPICE-6-V1.0, and the  SPICE toolkit documentation, for more details about leapseconds.   The data labels for any given product in this dataset usually  contain at least one pair of common UTC and MET representations  of the time at the middle of the observation. Other portions  of the products, for example tables of data taken over periods  of up to a day or more, will only have the MET time associated  with a given row of the table.   For the data user's use in interpreting these times, a reasonable  approximation (+/- 1s) of the conversion between Julian Day (TDB)  and MET is as follows:   JD TDB : 2453755.256337 + ( MET / 86399.9998693 )   For more accurate calculations the reader is referred to the  NAIF/SPICE documentation as mentioned above.    Reference Frame  :    Geometric Parameter Reference Frame  -----------------------------------   Earth Mean Equator and Vernal Equinox of J2000 (EMEJ2000) is the  inertial reference frame used to specify observational geometry items  provided in the data labels. Geometric parameters are based on best  available SPICE data at time of data creation.    Epoch of Geometric Parameters  -----------------------------   All geometric parameters provided in the data labels were computed at  the epoch midway between the START_TIME and STOP_TIME label fields.     Software  :   The observations in this data set are in standard FITS format  with PDS labels, and can be viewed by a number of PDS-provided  and commercial programs. For this reason no special software is  provided with this data set.    Contact Information  :   For any questions regarding the data format of the archive,  contact   New Horizons LORRI Principal Investigator:   Hal Weaver, Johns Hopkins Univ., Applied Physics Lab   Harold A Weaver   Johns Hopkins University  Applied Physics Laboratory  Space Exploration Sector  11100 Johns Hopkins Road  Laurel, MD 20723-6099  USA

Confidence Level Overview  :  During the processing of the data in preparation for  delivery with this volume, the packet data associated with each  observation were used only if they passed a rigorous verification  process including standard checksums.   In addition, raw (Level 2) observation data for which adequate  contemporary housekeeping and other ancillary data are not available  may not be reduced to calibrated (Level 3) data. This issue is raised  here to explain why some data products in the raw data set,   NH-P-LORRI-2-PLUTO-V3.0,   may not have corresponding data products in the calibrated data set,   NH-P-LORRI-3-PLUTO-V3.0.    Data coverage and quality  :  Every observation provided in this data set was taken as a part of a  particular sequence. A list of these sequences has been provided in  file DOCUMENT/SEQ_LORRI_PLUTO.TAB. N.B. Some sequences  provided may have zero corresponding observations.   Refer to the Confidence Level Overview section above for a summary  of steps taken to assure data quality.   The LORRI instrument replaces the first 34 12-bit pixels of each  LORRI image (408 bits; 51 bytes) with encoded binary header  information, so those first 34 pixel values in the first row are not  representative of the brightness of the imaged scene at those  locations; these pixels are in the bottom-left corner of images  displayed left-to-right and bottom-to-top. Furthermore, if the image  was LOSSY-compressed before downlink (ApIDs 0x632, 0x635, 0x638,  0x63B *), the header information corrupts the first 40 pixels of the  first 8 rows of the image because of the Discrete Cosine Transform  compression algorithm. The SOC pipeline extracts these data into the  FIRST34 extension of LORRI FITS files, which is also corrupt in  LOSSY-compressed files. The SOC calibration pipeline also flags these  pixels as bad in the QUALITY_MAP extension of calibrated FITS files;  no such flags are available in the raw FITS files; the SOC pipeline  did not flag the additional corrupt pixels beyond the first 34 in  LOSSY-compressed data until the Pluto P2 delivery late in 2016.   * See ApID definitions under the Data section of the Data Set  Description, DATA_SET_DESC, in this data set catalog.    Observation descriptions in this data set catalog  :   Some users will expect to find descriptions of the observations  in this data set here, in this Confidence Level Note. This data  set follows the more common convention of placing those  descriptions under the Data Set Description (above, if the user is  reading this in the DATASET.CAT file) of this data set catalog.    Caveat about TARGET_NAME in PDS labels and observational intent  :   The downlink team on New Horizons has  created an automated system to take various uplink products, decode  things like Chebyshev polynomials in command sequences representing  celestial body ephemerides for use on the spacecraft to control  pointing, and infer from those data what the most likely intended  target was at any time during the mission. This works well during  flyby encounters and less so during cruise phases and hibernation.   The user of these PDS data needs to  be cautious when using the TARGET_NAME and other target-related  parameters stored in this data set. This is less an issue for the  plasma and particle instruments, more so for pointing instruments.  To this end, the heliocentric ephemeris of the spacecraft, the  spacecraft-relative ephemeris of the inferred target, and the  inertial attitude of the instrument reference frame are provided  with all data, in the J2000 inertial reference frame, so the user  can check where that target is in the Field Of View (FOV) of the  instrument.   Finally, note that, within the FITS headers of the data products,  the sequence tables, and other NH Project-internal documents used  in this data set and/or inserted into the data set catalog,  informal names are often used for targets instead of the canonical  names required for the TARGET_NAME keyword. For example, during  the Pluto mission phase, instead of the TARGET_NAME '15810 ARAWN  (1994 JR1)' there might be found any of the following: 1994JR1;  1994 JR1; JR1. For all values where the PDS keyword TARGET_NAME  is used (e.g. in PDS labels and in index tables), the canonical,  PDS-approved names are used (if not, please bring this to the  attention of PDS so it can be rectified). However, within the  context of this data set, these project abbreviations are not  ambiguous (e.g. there is only one NH target with 'JR1' in its  name), so there has been, and will be, no attempt to expand such  abbreviations where they occur outside formal PDS keyword values.    Review  :  This dataset was peer reviewed and certified for scientific use on  June 19, 2017.