PDS_VERSION_ID = PDS3 LABEL_REVISION_NOTE = " For New Horizons, this LABEL_REVISION_NOTE is used to keep track of when the template is used to generate a DATASET.CAT file for a data set. - Publication date: 2017-04-30 - NH-internal archive software version: V2.0 2017-12-01: The dataset delivered in 2017 includes updates to TARGET_NAME values as well as updated calibrations based on a spacecraft Calibration Campaign conducted in 2016. " RECORD_TYPE = STREAM INSTRUMENT_HOST_NAME = "NEW HORIZONS" OBJECT = DATA_SET DATA_SET_ID = "NH-P-MVIC-3-PLUTO-V3.0" OBJECT = DATA_SET_INFORMATION START_TIME = 2015-03-03T12:38:55.871 STOP_TIME = 2016-07-16T00:34:12.249 DATA_SET_DESC = " Data Set Overview ================= This data set contains Calibrated data taken by New Horizons Multispectral Visible Imaging Camera instrument during the PLUTO mission phase. MVIC is a visible and near-infrared imager. MVIC comprises seven separate CCD two-dimensional arrays; all rows are 5024 pixels across with twelve pixels at either end of each row optically inactive. The single Pan Frame array is a panchromatic frame-transfer imager, 5024x128 pixels, that typically takes multiple frames in each observation. The common Pan Frame data product is an image cube in three dimensions: spatial; spatial; image frame, equivalent to time. Of the remaining six arrays, 5024x32 pixels each, two are panchromatic (unfiltered), and the remaining four are under filters and called the color arrays: Near-InfraRed (NIR); methane (CH4); Red; Blue. All six are operated in Time-Delay Integration (TDI) mode; the TDI arrays are in some ways similar to line cameras. In TDI mode, the spacecraft and MVIC boresight are scanned across the target at a rate that matches the charge transfer clock rate across the rows of the CCDs. Ideally the rates are matched, so as the charges are read by the analog-to-digital converter off the last line of the array, each pixel reading is near-proportional to the brightness of the same piece of the target as its image moved across the array, accumulating charge on each row. In TDI mode it is the product of the per-row charge clock rate and the duration of the observation that determines the number of rows each the image, and the image can be arbitrarily long; the number of rows (32) in each array is not relevant in determining the size of the image. The common data product for each of the TDI arrays is a 2-D image, of arbitrary length as noted earlier. 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 ending in late October, 2016 and closing out the Pluto Encounter mission phase. For this final Ralph-MVIC delivery for the Pluto mission phase, this data set includes the Approach data plus plus all CORE and Departure sequences' data, including observations of a low-resolution Pluto ring search taken in November, 2015, and finally Transition sequence data covering functional tests and star calibrations performed in mid-2016. On Approach during April, May and June of 2015, MVIC operations included the following: functional tests; full color observations of the Pluto, Charon and the other Plutonian satellites; Critical and Non-critical Optical Navication (OpNav or NAV) observations. The color observations were grouped over several 6-day periods to obtain a full rotation of Pluto and Charon. This dataset includes the first PC_VISUV_MAP for MVIC at about 19 days before encounter, a color TDI observation looking for changes in color and composition over multiple rotations, to meet the goal of understanding the time variability of Pluto's surface. These observations were repeated daily over that week leading up to encounter. From the day of encounter, this data set includes data from three CORE observations: (1) Pluto/Charon color map (PC_MULTI_MAP) about a day before the Time of Closest Approach (P-1d); (2) Pluto and Charon color scan at P-5h (PC_COLOR_1); (3) Nix color scan (N_COLOR_2). The PC_MULTI_MAP observation, the last one of which is included in this dataset, met multiple goals including imaging for color and surface composition maps of the Pluto and Charon hemispheres, Pluto and Charon phase integrals with resolved whole-disk images near 15 degrees, and imaging Pluto hazes on approach. Secondary goals are Pluto and Charon color high and low phase imaging to enable integrating over wavelength to determine the bolometric Bond albedo, and also to investigate the surface microphysics of Pluto and Charon, studying compositional and textural stratification in the surface as a function of terrain type. The N_COLOR series provided Nix high-resolution resolved color images. 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_MVIC_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. MVIC 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. It includes the additional observations below for MVIC: PEMV_01_PC_Multi_Map_A_18 2015-188_16:44:09 2016-097T18:02:21 Pluto, Charon PEMV_01_PC_Multi_Map_B_2 2015-189_09:04:09 2016-260T03:34:44 Pluto, Charon PEMV_01_PC_Multi_Map_B_3 2015-189_17:06:14 2016-095T20:48:31 Pluto, Charon PEMV_01_PC_Multi_Map_B_5 2015-190_03:40:28 2016-260T11:35:23 Pluto, Charon PEMV_01_PC_Multi_Map_B_6 2015-190_16:55:29 2016-095T22:56:44 Pluto, Charon PEMV_01_PC_Multi_Map_B_8 2015-191_08:54:53 2016-267T09:59:05 Pluto, Charon PEMV_01_PC_Multi_Map_B_9 2015-191_16:51:38 2016-266T11:36:17 Pluto, Charon PEMV_02_PC_Multi_Map_B_9 2015-191_16:54:28 2016-098T05:33:45 Pluto, Charon PEMV_01_PC_Multi_Map_B_11 2015-192_03:33:58 2016-267T09:18:50 Pluto, Charon PEMV_01_PC_Multi_Map_B_12 2015-192_16:46:18 2016-267T12:43:06 Pluto, Charon PEMV_02_PC_Multi_Map_B_12 2015-192_16:49:08 2016-268T06:19:29 Pluto, Charon PEMV_01_PC_Multi_Map_B_14 2015-193_08:22:29 2016-260T14:53:02 Pluto, Charon PEMV_01_PC_Multi_Map_B_15 2015-193_16:51:03 2016-175T13:40:09 Pluto, Charon PEMV_01_PC_Multi_Map_B_17 2015-194_03:37:27 2016-261T12:54:18 Pluto, Charon PEMV_01_PC_Multi_Map_B_18 2015-194_07:37:55 2016-178T17:49:36 Pluto, Charon PEMV_02_PCNH_Multi_Long_1d1 2015-194_14:45:27 2016-072T10:19:11 P,C, Nix, Hydra PEMV_01_PCNH_Multi_Long_1d1 2015-194_14:49:49 2016-073T00:27:20 P,C, Nix, Hydra PEMV_01_PC_LyMap 2015-194_16:23:01 2016-165T17:29:13 Pluto, Charon PEMV_01_PC_Multi_Long_1d2 2015-194_21:07:43 2016-192T07:45:52 Pluto, Charon PEMV_01_U_TBD_1 2015-194_23:53:45 2016-183T06:40:41 Styx PEMV_01_PC_Color_TimeRes 2015-195_02:47:02 2016-094T06:50:27 Pluto, Charon PEMV_01_N_Color_1 2015-195_04:36:05 2016-073T19:27:17 Nix PEMV_01_H_Color_1 2015-195_04:53:26 2016-187T08:25:21 Hydra PEMV_01_PC_Color_1 2015-195_06:49:08 2016-065T07:41:45 Pluto, Charon PEMV_01_H_Color_Best 2015-195_07:36:05 2016-185T21:21:57 Hydra PEMV_01_N_Color_2 2015-195_08:02:39 2016-075T07:20:33 Nix PEMV_01_N_Color_Best 2015-195_09:11:51 2016-180T12:05:01 Nix PEMV_01_P_LORRI_STEREO_Mosaic 2015-195_10:18:40 2016-272T04:16:47 Pluto PEMV_01_C_Color_2 2015-195_10:40:11 2016-188T12:48:30 Charon PEMV_01_P_Color2 2015-195_11:05:25 2016-191T14:52:18 Pluto PEMV_01_N_Mpan_CA 2015-195_11:14:32 2016-056T17:10:51 Nix PEMV_01_P_MP_Photoslew 2015-195_11:50:47 2016-087T20:01:12 Pluto PEMV_01_P_CharonLight 2015-195_12:08:13 2016-066T02:30:01 Pluto PEMV_01_N_Dep_Soonest 2015-195_15:00:28 2016-134T04:59:30 Nix PEMV_01_P_Multi_Dep_Long_1 2015-195_15:19:50 2016-184T18:29:24 Pluto PEMV_01_PC_Multi_Dep_Long_2 2015-195_19:09:43 2016-073T08:25:15 Pluto, Charon PEMV_01_U_TBD_4 2015-196_02:47:27 2016-190T07:22:45 Pluto System PEMV_02_U_TBD_4 2015-196_02:56:57 2016-190T10:08:55 Pluto System PEMV_01_PC_Multi_Dep_Long_3 2015-196_03:07:26 2016-187T15:48:11 Pluto, Charon PEMV_02_O_RingDep_A_1 2015-196_18:34:41 2016-190T17:32:38 Ring Search PEMV_01_PC_Ralph_Charon_270deg 2015-197_18:38:44 2016-185T13:45:33 P, C PEMV_01_PC_Ralph_N2_Bright 2015-198_07:43:29 2016-179T17:51:05 Pluto, Charon PEMV_01_PC_Ralph_Pluto_CO 2015-199_07:39:46 2016-181T03:54:13 Pluto, Charon PEMV_01_PC_Ralph_Enc_Hem_Dep 2015-199_15:41:45 2016-188T13:33:13 Pluto, Charon PEMV_01_PC_Ralph_Dark_Area 2015-200_07:39:47 2016-147T10:14:22 Pluto, Charon PEMV_01_PC_Ralph_Charon_90Deg 2015-200_23:38:49 2016-155T18:08:32 Pluto, Charon DPMV_01_O_RING_DEP_MVICFRAME_202 2015-202_13:59:37 2016-254T13:18:31 Ring Search DPMV_01_O_RING_DEP_MVICFRAME_211 2015-211_17:49:37 2016-261T04:34:22 Ring Search DPMV_O_RING_DEP_MVICFRAME_305A 2015-305_18:33:42 2016-040T00:34:57 Ring Search DPMV_O_RING_DEP_MVICFRAME_305B 2015-305_20:11:37 2016-040T00:19:39 Ring Search DPMV_O_RING_DEP_MVICFRAME_305C 2015-305_22:23:37 2016-063T06:43:20 Ring Search TRRL_X_RALPH_FUNCLITEA_182__021aFuncColor 2016-182_01:38:44 2016-182T14:33:15 TRRL_X_RALPH_FUNCLITEA_182__021aFuncPan1 2016-182_01:40:46 2016-182T14:36:29 TRRL_X_RALPH_FUNCLITEA_182__021aFuncPan2 2016-182_01:42:47 2016-182T14:39:45 TRRL_X_RALPH_FUNCLITEA_182__021aFuncPanFrame 2016-182_01:44:51 2016-182T15:26:06 TRRL_X_RALPH_FUNCLITEB_182__021bFuncColor 2016-182_02:13:44 2016-182T16:53:20 TRRL_X_RALPH_FUNCLITEB_182__021bFuncPan1 2016-182_02:15:46 2016-182T16:56:21 TRRL_X_RALPH_FUNCLITEB_182__021bFuncPan2 2016-182_02:17:47 2016-182T16:59:13 TRRL_X_RALPH_FUNCLITEB_182__021bFuncPanFrame 2016-182_02:19:51 2016-182T17:43:21 TRMV_M6M7_023A_CAL_197_Color 2016-197_21:59:27 2016-214T17:26:45 Calibration TRMV_M6M7_023A_CAL_197_Pan2 2016-197_22:08:43 2016-214T13:46:02 Calibration TRMV_M6M7_023A_CAL_197_Pan1 2016-197_22:15:43 2016-214T14:21:53 Calibration TRMV_M6M7_023A_CAL_197_PanFrame 2016-197_22:23:47 2016-209T12:50:08 Cal. TRMV_M6M7_023B_CAL_197_Color 2016-197_22:36:27 2016-215T04:56:48 Calibration TRMV_M6M7_023B_CAL_197_Pan2 2016-197_22:44:43 2016-214T14:38:08 Calibration TRMV_M6M7_023B_CAL_197_Pan1 2016-197_22:52:43 2016-214T14:53:57 Calibration TRMV_M6M7_023B_CAL_197_PanFrame 2016-197_23:00:47 2016-208T13:48:42 Cal. TRMV_HD205905_047A_01_CAL_197 2016-198_00:06:27 2016-202T10:24:00 Calibration TRMV_HD205905_047A_02_CAL_197 2016-198_00:14:45 2016-202T11:21:13 Calibration TRMV_HD205905_047B_01_CAL_197 2016-198_00:24:27 2016-202T13:30:42 Calibration TRMV_HD205905_047B_02_CAL_197 2016-198_00:33:45 2016-202T13:48:37 Calibration Also, updates were made to the calibration files, documentation, and catalog files. For any data previously delivered as sub-frame windows, this delivery will fill in the image data outside those windows. Changes to the calibration involved only changes to the spectrum-specific calibration constants provided in FITS headers and in PDS labels; the calibrated Data Number values in the calibrated data set, excluding image data outside the sub-frame windows mentioned above, will not be substantively changed. 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. MVIC 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). Some data that had been downlinked as a subframe in the last delivery now has been re-downlinked for the full frame image. All liens from the initial Pluto delivery have also now been resolved. The dataset includes the additional observations below: Obs. Name (Request ID), Obs Date, Downlink Start, Downlink End, Obs. Target DPMV_O_RING_DEP_MVICFRAME_305A 2015-11-01 2016/003 2016/030 Ring Search Observation PEMV_01_C_Color_2 2015-07-14 2015/266 2015/266 Charon Observation PEMV_01_C_MVIC_LORRI_CA 2015-07-14 2015/312 2015/312 Charon Observation PEMV_01_H_Color_1 2015-07-14 2015/283 2015/283 Hydra Observation PEMV_01_H_Color_Best 2015-07-14 2015/283 2015/283 Hydra Observation PEMV_01_N_Color_Best 2015-07-14 2015/283 2015/329 Nix Observation PEMV_01_N_Mpan_CA 2015-07-14 2015/347 2015/347 Nix Observation PEMV_01_PC_Color_1 2015-07-14 2015/283 2015/283 Pluto and Charon obs PEMV_01_PC_Multi_Dep_Long_3 2015-07-15 2015/283 2015/283 Pluto and Charon obs PEMV_01_PC_Multi_Long_1d2 2015-07-13 2015/282 2015/282 Pluto and Charon obs PEMV_01_PC_Multi_Map_A_18 2015-07-07 2015/279 2015/279 Pluto and Charon obs PEMV_01_PC_Multi_Map_A_3 2015-07-02 2015/229 2015/229 Pluto and Charon obs PEMV_01_PC_Multi_Map_A_5 2015-07-03 2015/229 2015/229 Pluto and Charon obs PEMV_01_PC_Multi_Map_B_15 2015-07-12 2015/282 2015/282 Pluto and Charon obs PEMV_01_PC_Multi_Map_B_17 2015-07-13 2015/286 2015/286 Pluto and Charon obs PEMV_01_PC_Multi_Map_B_3 2015-07-08 2015/279 2015/279 Pluto and Charon obs PEMV_01_PC_Multi_Map_B_6 2015-07-09 2015/279 2015/279 Pluto and Charon obs PEMV_01_PC_Ralph_Charon_270deg 2015-07-16 2015/283 2015/283 Pluto and Charon obs PEMV_01_PC_Ralph_Charon_90Deg 2015-07-19 2015/284 2015/284 Pluto and Charon obs PEMV_01_PC_Ralph_Dark_Area 2015-07-19 2015/284 2015/284 Pluto and Charon obs PEMV_01_PC_Ralph_Enc_Hem_Dep 2015-07-18 2015/283 2015/283 Pluto and Charon obs PEMV_01_PC_Ralph_N2_Bright 2015-07-17 2015/283 2015/283 Pluto and Charon obs PEMV_01_PC_Ralph_Pluto_CO 2015-07-18 2015/283 2015/283 Pluto and Charon obs PEMV_01_PC_VISUV_MAP_B_12 2015-06-29 2015/233 2015/233 Pluto and Charon obs PEMV_01_PC_VISUV_MAP_B_19 2015-07-01 2015/229 2015/229 Pluto and Charon obs PEMV_01_PC_VISUV_MAP_B_3 2015-06-26 2015/246 2015/246 Pluto and Charon obs PEMV_01_PC_VISUV_MAP_B_6 2015-06-27 2015/244 2015/244 Pluto and Charon obs PEMV_01_PC_VISUV_MAP_B_9 2015-06-28 2015/237 2015/237 Pluto and Charon obs PEMV_01_P_Color2 2015-07-14 2015/260 2015/262 Pluto Observation PEMV_01_P_HiPhase_HiRes 2015-07-14 2015/255 2015/255 Pluto Observation PEMV_01_P_MPan1 2015-07-14 2015/280 2015/280 Pluto Observation PEMV_01_P_Multi_Dep_Long_1 2015-07-14 2015/278 2015/278 Pluto Observation PEMV_01_P_MVICFlat_Col_1 2015-07-14 2015/253 2015/253 Pluto Observation PEMV_01_P_MVICFlat_Col_2 2015-07-14 2015/253 2015/253 Pluto Observation PEMV_01_P_MVICFlat_Pan_First 2015-07-14 2015/253 2015/253 Pluto Observation PEMV_01_P_MVICFlat_Pan_Second 2015-07-14 2015/253 2015/253 Pluto Observation PEMV_01_P_MVIC_LORRI_CA 2015-07-14 2015/272 2015/272 Pluto Observation PEMV_01_U_TBD_1 2015-07-13 2015/282 2015/283 Kerberos and Styx obs PEMV_02_PC_Multi_Map_B_9 2015-07-10 2015/279 2015/279 Pluto and Charon obs PEMV_02_P_MVICFlat_Col_1 2015-07-14 2015/253 2015/253 Pluto Observation PEMV_02_P_MVICFlat_Col_2 2015-07-14 2015/253 2015/253 Pluto Observation PEMV_02_P_MVICFlat_Pan_First 2015-07-14 2015/253 2015/253 Pluto Observation PEMV_02_P_MVICFlat_Pan_Second 2015-07-14 2015/253 2015/253 Pluto 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. Calibration =========== Detailed information about calibration of MVIC data is available in the SOC Instrument Interface Control Document (ICD) in the DOCUMENT section of this data set. The MVIC calibration will only be briefly summarized here; refer to the ICD for details about what is summarized here. The calibration of MVIC images comprises the following steps: 1) Remove bias and flat-field pattern 1.1) The result is an absolute calibration in raw DATA NUMBER units (DN), with pixel values proportional to the incoming signal 2) Supply target source spectrum-dependent factors to scale from absolute DN to scientific (flux and radiance) units; refer to the DOCUMENT/SOC_INST_ICD*.* for more detail. In addition, the calibration procedure calculates the error and a data quality flag for each pixel and includes those results in the calibrated data product as additional PDS OBJECTs (FITS extensions) appended to the main OBJECT with the data image. The quality flag PDS OBJECT is an image of values of the same size as the main IMAGE product, with each quality flag pixel mapped to the corresponding pixel in the main product. A quality flag value of zero indicates a valid pixel; a non-zero value indicates an invalid pixel (e.g. missing data outside the window(s) of data intended to be downlinked). Note that for windowed products, all pixels in an image are not returned in the downlink telemetry. In the raw data, the pipeline sets such pixels to zero DN (Data Number); the calibration processes those zero-DN pixels as if they were real raw values, but also flags them as missing data in the quality flag PDS OBJECT (FITS extension). Displaying such images using an automatic stretch (contrast enhancement) may result in a confusing result with the majority of the displayed image appearing as an inverse of the calibration (calibration of zero values); therefore the quality flag PDS OBJECT should always be checked when looking at these data. Note also that, at the time these data were created (late 2014), the Science Operations Center (SOC) data processing pipeline did not have the capability to merge multiple windows from a single observation. As a result, in some cases one observation's products in raw and and calibrated data sets may come from different windows. This is normal, but it can have some noticeable side-effects: i) Mismatches in windowing parameters between raw and calibrated products for the same observation. Either the windowing parameters differ, or one may be windowed and the other a non-windoed, full image. ii) START_TIME and STOP_TIME mismatches between versions of the same TDI observations with different windows. The start and stop times of TDI MVIC products are dependent on the start and stop lines of the window: if the first line of the window is not the first line of the observation, the START_TIME of the product will be delayed from the start time of the observation; similarly the last line of a window that is not the last line of the observation results in a STOP_TIME that is earlier than the stop time of the observation. Since there is only one version of each observation in any single MVIC data set, this will not be noticeable within any single data set. However, when comparing versions of the same observation from raw and calibrated data sets, it is possible that the START_TIME and STOP_TIME values for that observation will differ between the data sets. iii) The shift in start and stop times will also affect the calculation of mid-observation times. iv) The mid-observation time is used as the lookup in SPICE calls, so the shift in time will affect calculated geometry values As part of the preparation for the Pluto flyby in Spring, 2015, the SOC pipeline was updated to all it to merge multiple windows and/or full images of the same observation into a single product. so it is expected that future MVIC data sets will have raw and calibrated products with consistent windowing parameters, times and geometries. A PDS OBJECT CALGEOM (FITS extension) with a correction for geometric distortion, present in previous versions of MVIC data sets, has been removed from these and future PDS calibrated data sets. Geometric distorion will be addressed in higher-level products, as it involves resampling the data. 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. MC0_0123456789_0X530_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 ** =========== ================================== ============= MVIC MC0, MC1, MC2, MC3, MP1, MP2, MPF 0X530 - 0X54A * * 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 meanings of each instrument designator: Instr Dsgn. Description ===== =========== MC0 MVIC, Color TDI, Red filter MC1 MVIC, Color TDI, Blue filter MC2 MVIC, Color TDI, Near-InfraRed (NIR) filter MC3 MVIC, Color TDI, Methane (CH4) filter MP1 MVIC, Panchromatic TDI CCD 1 MP2 MVIC, Panchromatic TDI CCD 2 MPF MVIC, Panchromatic frame (5024 pixels) See SOC Instrument ICD (/DOCUMENT/SOC_INST_ICD.*) for 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) ===== =================================== 0x530 - MVIC Panchromatic TDI Lossless (CDH 1)/MP1,MP2 0x53f - MVIC Panchromatic TDI Lossless (CDH 2)/MP1,MP2 0x531 - MVIC Panchromatic TDI Packetized (CDH 1)/MP1,MP2 0x540 - MVIC Panchromatic TDI Packetized (CDH 2)/MP1,MP2 0x532 - MVIC Panchromatic TDI Lossy (CDH 1)/MP1,MP2 0x541 - MVIC Panchromatic TDI Lossy (CDH 2)/MP1,MP2 0x533 - MVIC Panchromatic TDI 3x3 Binned Lossless (CDH 1)/MP1,MP2 * 0x542 - MVIC Panchromatic TDI 3x3 Binned Lossless (CDH 2)/MP1,MP2 * 0x534 - MVIC Panchromatic TDI 3x3 Binned Packetized (CDH 1)/MP1,MP2 * 0x543 - MVIC Panchromatic TDI 3x3 Binned Packetized (CDH 2)/MP1,MP2 * 0x535 - MVIC Panchromatic TDI 3x3 Binned Lossy (CDH 1)/MP1,MP2 * 0x544 - MVIC Panchromatic TDI 3x3 Binned Lossy (CDH 2)/MP1,MP2 * 0x536 - MVIC Color TDI Lossless (CDH 1)/MC0,MC1,MC2,MC3 0x545 - MVIC Color TDI Lossless (CDH 2)/MC0,MC1,MC2,MC3 0x537 - MVIC Color TDI Packetized (CDH 1)/MC0,MC1,MC2,MC3 0x546 - MVIC Color TDI Packetized (CDH 2)/MC0,MC1,MC2,MC3 0x538 - MVIC Color TDI Lossy (CDH 1)/MC0,MC1,MC2,MC3 0x547 - MVIC Color TDI Lossy (CDH 2)/MC0,MC1,MC2,MC3 0x539 - MVIC Panchromatic Frame Transfer Lossless (CDH 1)/MPF 0x548 - MVIC Panchromatic Frame Transfer Lossless (CDH 2)/MPF 0x53a - MVIC Panchromatic Frame Transfer Packetized (CDH 1)/MPF 0x549 - MVIC Panchromatic Frame Transfer Packetized (CDH 2)/MPF 0x53b - MVIC Panchromatic Frame Transfer Lossy (CDH 1)/MPF 0x54a - MVIC Panchromatic Frame Transfer Lossy (CDH 2)/MPF * as of October, 2014, 3x3 modes have not been used Instrument description ---------------------- Refer to the following files for a description of this instrument. CATALOG MVIC.CAT DOCUMENTS RALPH_SSR.* SOC_INST_ICD.* NH_RALPH_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 RALPH Field Of View definitions: /DOCUMENT/NH_FOV.* /DOCUMENT/NH_RALPH_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_MVIC_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 RALPH Principal Investigator: Alan Stern, Southwest Research Institute S. Alan Stern Southwest Research Institute (SwRI) Department of Space Studies 1050 Walnut Street, Suite 400 Boulder, CO 80302 USA " CONFIDENCE_LEVEL_NOTE = " 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-MVIC-2-PLUTO-V3.0, may not have corresponding data products in the calibrated data set, NH-P-MVIC-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_MVIC_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. During functional tests, some TDI images with prefixes like mc0, mc1, mc2, mc3, mp1, and mp2 will have a height (PDS keyword LINES) of less than 100 lines (values of 32, 33, 52, and 96 are common) and a width (LINE_SAMPLES) of 5024, giving the impression of a noodle-like image. These images were only generated to confirm proper operation of MVIC and are unlikely to have any scientific value. Functional test images can usually be identified by the case-insensitive string 'func' in the value of the NEWHORIZONS:SEQUENCE_ID keyword in the PDS label. 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. " ABSTRACT_DESC = " This data set contains Calibrated data taken by the New Horizons Multispectral Visible Imaging Camera instrument during the Pluto encounter mission phase. This is VERSION 3.0 of this data set. This data set contains MVIC observations taken during the the Approach (Jan-Jul, 2015), Encounter, Departure, and Transition mission sub-phases, including flyby observations taken on 14 July, 2015, and departure and calibration data through late October, 2016. This data set completes the Pluto mission phase deliveries for MVIC. This is version 3.0 of this dataset. Changes since version 2.0 include the addition of data downlinked between the end of January, 2016 and the end of October, 2016, completing the delivery of all data covering the Pluto Encounter and subsequent Calibration Campaign. It includes multi- map observations from the Approach phase, observations of the moons, hi- res, full-frame observations from Pluto Encounter and Departure, and ring search observations. There may be some overlap between prior datasets and this dataset, due to only partial, windowed, or lossy data in prior datasets. This dataset also includes functional tests from the Calibration Campaign, including calibration observations of the M6 and M7 clusters, and HD205905. Also, updates were made to the calibration files, documentation, and catalog files. For any data previously delivered as sub-frame windows, this delivery will fill in the image data outside those windows. Changes to the calibration involved only changes to the spectrum-specific calibration constants provided in FITS headers and in PDS labels; the calibrated Data Number values in the calibrated data set, excluding image data outside the sub-frame windows mentioned above, will not be substantively changed. " CITATION_DESC = " Stern, A., NEW HORIZONS Calibrated MVIC PLUTO ENCOUNTER V3.0, NH-P-MVIC-3-PLUTO-V3.0, NASA Planetary Data System, 2018. " DATA_OBJECT_TYPE = "IMAGE" DATA_SET_COLLECTION_MEMBER_FLG = "N" DATA_SET_NAME = "NEW HORIZONS MVIC PLUTO ENCOUNTER CALIBRATED V3.0" DATA_SET_RELEASE_DATE = 2017-04-30 DATA_SET_TERSE_DESC = " Calibrated data taken by New Horizons Multispectral Visible Imaging Camera instrument during the PLUTO mission phase. This is VERSION 3.0 of this data set. " DETAILED_CATALOG_FLAG = "N" PRODUCER_FULL_NAME = "TIFFANY FINLEY" END_OBJECT = DATA_SET_INFORMATION OBJECT = DATA_SET_MISSION MISSION_NAME = "NEW HORIZONS" END_OBJECT = DATA_SET_MISSION OBJECT = DATA_SET_REFERENCE_INFORMATION REFERENCE_KEY_ID = "N/A" END_OBJECT = DATA_SET_REFERENCE_INFORMATION OBJECT = DATA_SET_TARGET TARGET_NAME = "CALIBRATION" END_OBJECT = DATA_SET_TARGET OBJECT = DATA_SET_TARGET TARGET_NAME = "CHARON" END_OBJECT = DATA_SET_TARGET OBJECT = DATA_SET_TARGET TARGET_NAME = "HD 205905" END_OBJECT = DATA_SET_TARGET OBJECT = DATA_SET_TARGET TARGET_NAME = "HYDRA" END_OBJECT = DATA_SET_TARGET OBJECT = DATA_SET_TARGET TARGET_NAME = "KERBEROS" END_OBJECT = DATA_SET_TARGET OBJECT = DATA_SET_TARGET TARGET_NAME = "M7" END_OBJECT = DATA_SET_TARGET OBJECT = DATA_SET_TARGET TARGET_NAME = "NIX" END_OBJECT = DATA_SET_TARGET OBJECT = DATA_SET_TARGET TARGET_NAME = "PLUTO" END_OBJECT = DATA_SET_TARGET OBJECT = DATA_SET_HOST INSTRUMENT_HOST_ID = "NH" INSTRUMENT_ID = "MVIC" END_OBJECT = DATA_SET_HOST END_OBJECT = DATA_SET END