| DATA_SET_DESCRIPTION |
Data Set Overview : This data set contains Raw data taken by New Horizons Multispectral Visible Imaging Camera instrument during the JUPITER mission phase. The Ralph (LEISA & MVIC) Jupiter activities included calibration observations using Callisto and Jupiter as a target, scientific observations of Jovian targets, opnav test observations of Callisto, and mapping of solar input aperture. 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 JUPITER phase of the New Horizons Mission : Sequence ID: JEMV_JRALPHCAL01 Start UTC: 2007-01-31T05:42:00 Start SCLK: 1/0032528037:30770 Description: FORCED; Ralph - MVIC blue rapid flat Sequence ID: JEMV_GECLIPSE01 Start UTC: 2007-02-25T09:00:00 Start SCLK: 1/0034699917:30613 Description: GANYMEDE; Eclipse; 02/25/07 09:35 Need to know how the data taking is spread through the eclipse period. Assume for now that this one and the next one can be intermixed with potentially additional slews between Io and Europa Sequence ID: JEMV_IECLIPSE01 Start UTC: 2007-02-25T19:10:00 Start SCLK: 1/0034736517:30609 Description: IO; Io Eclipse; 02/25/07 19:34 - 02/25/07 19:34 Sequence ID: JEMV_IHIRESIR01 Start UTC: 2007-02-26T18:25:00 Start SCLK: 1/0034820217:30601 Description: IO; Hi-res coverage, composition; Timing flexible Sequence ID: JEMV_IHIRES01 Start UTC: 2007-02-26T20:52:00 Start SCLK: 1/0034829037:30600 Description: IO; Hi-res coverage, Pele on limb; 02/26/07 19:52 - 02/26/07 21:52 Sequence ID: JEMV_IHIRESIR02 Start UTC: 2007-02-27T05:25:00 Start SCLK: 1/0034859817:30596 Description: IO; Hi-res coverage, composition; Timing flexible Sequence ID: JEMV_EECLIPSE01 Start UTC: 2007-02-27T10:24:00 Start SCLK: 1/0034877757:30593 Description: EUROPA; Eclipse; 02/27/07 10:36 Need to know how the data taking is spread through the eclipse period. Assume for now that this one and the next one can be intermixed with potentially additional slews between Io and Europa Sequence ID: JEMV_IECLIPSE03 Start UTC: 2007-02-27T13:46:00 Start SCLK: 1/0034889877:30592 Description: IO; Io Eclipse; 2/27/07 14:10 Target so Alice and LEISA integrations can be done with the same pointing. Sequence ID: JEMV_IHIRESIR03 Start UTC: 2007-02-28T04:30:00 Start SCLK: 1/0034942917:30584 Description: IO; Hi-res coverage, composition; Timing flexible Sequence ID: JEMV_JRALPHCAL02 Start UTC: 2007-02-28T06:00:00 Start SCLK: 1/0034948317:30583 Description: JUPITER; MVIC terminator flat Sequence ID: JEMV_IHIRES05 Start UTC: 2007-02-28T11:00:00 Start SCLK: 1/0034966317:30581 Description: IO; Hi-res coverage- Prometheus on limb; Timing flexible Sequence ID: JEMV_ISHINE01 Start UTC: 2007-02-28T13:05:00 Start SCLK: 1/0034973817:30580 Description: IO; Jupiter shine; 02/28/07 12:00 - 02/28/07 14:00 Sequence ID: JEMV_IHIRESIR04 Start UTC: 2007-03-01T00:25:00 Start SCLK: 1/0035014617:30573 Description: IO; Hi-res nightside- Pele on limb; Timing flexible Sequence ID: JEMV_INITEMON02 Start UTC: 2007-03-01T04:20:00 Start SCLK: 1/0035028717:30571 Description: IO; High Phase Monitoring; Timing flexible Sequence ID: JEMV_INITEMON03 Start UTC: 2007-03-01T07:30:00 Start SCLK: 1/0035040117:30569 Description: IO; High phase monitoring; Timing flexible Sequence ID: JEMV_IECLIPSE04 Start UTC: 2007-03-01T08:25:00 Start SCLK: 1/0035043417:30569 Description: IO; Io Eclipse; 3/1/07 8:38 Target so Alice and LEISA integrations can be done with the same pointing. Sequence ID: JEMV_ISHINE02 Start UTC: 2007-03-01T22:00:00 Start SCLK: 1/0035092317:30561 Description: IO; Jupiter shine; 03/01/07 21:00 - 03/01/07 23:00 Sequence ID: JEMV_INITEMON05 Start UTC: 2007-03-02T06:00:00 Start SCLK: 1/0035121117:30557 Description: IO; High phase monitoring: Tvashtar on limb; Timing flexible Sequence ID: JEMV_OPNAV01 Start UTC: 2007-03-02T07:30:00 Start SCLK: 1/0035126517:30556 Description: CALLISTO; Callisto Op Nav Sequence ID: JEMV_OPNAV02 Start UTC: 2007-03-02T08:45:00 Start SCLK: 1/0035131017:30556 Description: CALLISTO; Callisto Op Nav Sequence ID: JEMV_OPNAV03 Start UTC: 2007-03-02T10:00:00 Start SCLK: 1/0035135517:30555 Description: CALLISTO; Callisto Op Nav Sequence ID: JEMV_IKODAK01 Start UTC: 2007-03-02T10:24:00 Start SCLK: 1/0035136957:30555 Description: IO; Io/Europa conjunction; Timing from -6 to -6.5 days, Sequence ID: JEMV_IECLIPSE05 Start UTC: 2007-03-03T04:00:00 Start SCLK: 1/0035200317:30546 Description: IO; High phase monitoring; Timing flexible 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. 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 2 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-JUPITER-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.
|
.png)
.png)
