Data Set Overview :  This data set contains Calibrated data taken by New Horizons Multispectral Visible Imaging Camera instrument during the LAUNCH mission phase.  The Post-Launch mission phase was used mainly for checkout, commissioning and calibration of the Ralph instruments (LEISA & MVIC). For details, refer to the following Ralph activity summary table:  Ralph-001 Functional Test Ralph-002 Sequenced Power Up/Down Test Ralph-004A Pre-door opening imaging and MVIC Frame checkout Ralph-004B TDI Scan Test Ralph-004C LEISA offset test Ralph-005 Door opening Ralph-017 Asteroid flyby Ralph-006 Optical Calibration Ralph-008 MVIC-LORRI coalignment test Ralph-007 LEISA Jupiter scan, MVIC flatfield prescan Ralph-009 Opnav test of Uranus and Neptune Ralph-011 Solar stray light test Ralph-018 Power on/of test of offset problem fix Ralph-019 Light leak test  Every observation provided in this data set was taken as a part of a particular sequence. A list of these sequences follows:  Sequence IDs & start times (end times are the start times of the following Sequence IDs) for the MVIC instrument during the LAUNCH phase of the New Horizons Mission :  Sequence ID: CORA_Ralph-001 Start UTC: 2006-03-21T00:00:00 Start SCLK: 1/0005205117:33045 Description: Initial Ralph Commissioning  Sequence ID: CORA_Ralph-002 Start UTC: 2006-04-11T00:00:00 Start SCLK: 1/0007019517:32631 Description: OK  Sequence ID: CORA_Ralph-004/CORA_Ralph-004_offsets Start UTC: 2006-05-10T00:00:00 Start SCLK: 1/0009525117:32228 Description: Pre-door opening; TDI checkout/OK  Sequence ID: CORA_Ralph-005 Start UTC: 2006-05-28T00:00:00 Start SCLK: 1/0011080317:32041 Description: None  Sequence ID: CORA_Ralph-017T Start UTC: 2006-05-30T00:00:00 Start SCLK: 1/0011253117:32023 Description: table load for 017  Sequence ID: CORA_Ralph-017 Start UTC: 2006-06-11T00:00:00 Start SCLK: 1/0012289917:31920 Description: Asteroid 132524 APL (formerly 2002 JF56)  Sequence ID: CORA_Ralph-006T Start UTC: 2006-06-16T00:00:00 Start SCLK: 1/0012721917:31874 Description: Table load for 006  Sequence ID: CORA_Ralph-006 Start UTC: 2006-06-21T00:00:00 Start SCLK: 1/0013153917:31835 Description: Optical Calibration  Sequence ID: CORA_Ralph-006C Start UTC: 2006-06-29T00:00:00 Start SCLK: 1/0013845117:31760 Description: Optical Cal- LEISA Scans  Sequence ID: CORA_Ralph-007T Start UTC: 2006-08-28T00:00:00 Start SCLK: 1/0019029117:31421 Description: table load 007/008  Sequence ID: CORA_Ralph-008 Start UTC: 2006-08-31T00:00:00 Start SCLK: 1/0019288317:31406 Description: None  Sequence ID: CORA_Ralph-007a/CORA_Ralph-007b Start UTC: 2006-09-04T00:00:00 Start SCLK: 1/0019633917:31388 Description: LEISA Jupiter Scan/MVIC Jupiter Fast Scan  Sequence ID: CORA_Ralph-009a Start UTC: 2006-09-10T00:00:00 Start SCLK: 1/0020152317:31360 Description: None  Sequence ID: CORA_Ralph-011 Start UTC: 2006-09-22T00:00:00 Start SCLK: 1/0021189117:31307 Description: Solar Stray light  Sequence ID: CORA_Ralph-018 Start UTC: 2006-09-23T00:00:00 Start SCLK: 1/0021275517:31303 Description: Power On/Off Test of offset problem 'fix'  Sequence ID: CORA_Ralph-019 Start UTC: 2006-10-17T00:00:00 Start SCLK: 1/0023349117:31213 Description: None  For the list of observations and their parameters, refer to the data set index table (typically INDEX.TAB & CUMINDEX.TAB, initially in the /INDEX/ area of the data set).   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 NAIF/SPICE toolkit from the NAIF PDS node.  The most common time unit associated with the data is 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) over this dataset is 65.184s.  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.    Processing :  The data in this data set were created by a software data processing pipeline on the Science Operation Center (SOC) at the Southwest Research Institute (SWRI), Department of Space Studies. 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.  The calibration of MVIC images comprises the following steps:  1) Remove bias and flat-field pattern 2) Correct for a geometric distortion 3) Absolute calibration (conversion to radiance units)  In addition, the calibration procedure calculates the error and as data quality flag for each pixel and includes those results in the calibrated data product.  There is not yet any correction for scattered light in the calibrated products. A complete assessment of the scattered light field will be made in flight, and corrections will be implemented if necessary. Also, there is no correction for cosmic rays in the calibrated products.  Ongoing in-flight calibration observations will be analyzed to assess the long term stability of the calibration.   Data :  The observations in this data set are stored in data files using standard Flexible Image Transport Sytem (FITS) format. Each FITS file has a corresponding detached PDS label file, named according to a common convention. The FITS files 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 - Other sources of information useful in interpreting these Data - CODMAC Level 3 MVIC data details - Instrument description - Visit Description, Visit Number, and Target in the Data Labels - Unresolved Liens on the Data   Filename/Product IDs --------------------  The filenames and product IDs of observations adhere to a common convention e.g.  ALI_0123456789_0X0AB_ENG_1.FIT ^^^ ^^^^^^^^^^ ^^^^^ ^^^ ^\__/ | | | | | ^^ | | | | | | | | | | | +--File type (includes dot) | | | | | - .FIT for FITS file | | | | | - .LBL for PDS label | | | | | - not part of product ID | | | | | | | | | +-- Version number from the SOC | | | | (Science Operations Center) | | | | | | | +--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 | | | +--MET (Mission Event Time) i.e. Spacecraft Clock | +--Instrument designator  * For those datasets where the NH project is delivering CODMAC Level 1 & 2 data (REX & PEPSSI), ENG and SCI apply to CODMAC Level 1 & 2 data, respectively.   Instrument Instrument designators ApIDs : : : MVIC MC0, MC1, MC2, MC3, MP1, MP2, MPF 0X530 - 0X53A *  * Not all values in this range are used  There are other ApIDs that contain housekeeping values and other values. See the documentation 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 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   Other sources of information useful in interpreting these Data --------------------------------------------------------------  Refer to the following files for more information about these data  NH Trajectory table:  /DOCUMENT/NH_TRAJECTORY.*  RALPH Field Of View definitions:  /DOCUMENT/NH_FOV.* /DOCUMENT/NH_RALPH_V###_TI.TXT     Instrument description ----------------------  Refer to the following files for a description of this instrument.  CATALOG  MVIC.CAT  DOCUMENTS  RALPH_SSR.* NH_RALPH_V###_TI.TXT (### is a version number) SOC_INST_ICD.*   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. The PDS standards 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.   Unresolved Liens on the Data ----------------------------  None exist at the present time.   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-LAUNCH-V1.0.   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 the person whose PDS_USER_ID is ASTERN as described in PERSONNEL.CAT.

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 are not reduced to calibrated (Level 3) data. This issue is raised here to explain why some data products in the raw data set,  NH-X-MVIC-2-LAUNCH-V2.0,  do not have corresponding data products in the calibrated data set,  NH-X-MVIC-3-LAUNCH-V2.0.   Review : The data have been reviewed and validated by the instrument team members, as well as by SOC personnel.   MVIC updates for Data Sets V2.0 :   Improvements to motion distortion ---------------------------------  For MVIC TDI images, the motion distortion correction now corrects for optical distortion, cross-track drift, along-track drift, spacecraft rotation and sets the scan to a common tangential plane centered at the image center.  All interpolation is done using the IDL bilinear interpolation program.