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. Brian Carcich - Publication date: 2016-10-31 - NH-internal archive software version: V2.0 " RECORD_TYPE = STREAM INSTRUMENT_HOST_NAME = "NEW HORIZONS" OBJECT = DATA_SET DATA_SET_ID = "NH-X-LEISA-3-PLUTOCRUISE-V1.0" OBJECT = DATA_SET_INFORMATION START_TIME = 2007-09-18T22:05:01.447 STOP_TIME = 2014-07-20T05:50:13.509 DATA_SET_DESC = " Data Set Overview ================= This data set contains Calibrated data taken by New Horizons Linear Etalon Imaging Spectral Array instrument during the PLUTOCRUISE mission phase. LEISA is an infrared imaging spectrometer. The two-dimensional (2-D) detector is a 256x256-pixel array. Spectral separation is done with a wedged optical etalon filter, which comprises high (2.1-2.25 micron) and low (1.25-2.5 micron) spectral resolution segments. The optics and filter arrangement configure one detector dimension as spatial at constant wavelength and the other dimension as both spectral and spatial. Multiple frames (images) may be taken in sequence, while scanning the Field Of View (FOV) in the spatial+spectral dimension, such that each pixel-sized piece of the observed target will be observed at all wavelengths across multiple frames. The resulting data products in this data set are three-dimensional image cubes, which dimensions are spatial, spatial+spectral, and spatial+time and which shall be convolved into spatial, spatial, and spectral image cubes at a later date. RALPH data taken during Annual CheckOuts 1 through 8 (ACO1-8): ============================================================== Summary (Note 1): ================= - Calibrations and other tests with possible science targets - Neptune as a navigation test target - Sun in Solar Illumination Assembly (SIA) - Vega and Arcturus (star) - Pluto encounter rehearsal in the summer of 2013 - Functional tests Details: ======== Primary RALPH Calibrations and other major observations (Notes 1 and 2): ------------------------------------------------------------------------ During ACO1, ACO2 and ACO4, RALPH took LEISA calibration data using the star Vega as a source; During ACO-2 and ACO-4, RALPH took MVIC calibration data using the clusters M7 and M6. During ACO1 and ACO2, the RALPH instrument observed flat field data for both MVIC and LEISA using the SIA. However these data were not useful for flat fielding because there was varying structure in the images i.e. the light was not evenly illuminating the field of view, and details of the flat are dependent on the position of the Sun in the SIA. In ACO1, RALPH observations for calibration, characterization and interference goals included a stray light test with the sun at an angle of 20-90 degrees from the FOV, to characterize the light leak of LEISA on the incoming and outgoing encounter asymptote, and an interference test between the LEISA and ALICE instruments. During ACO2, RALPH observed Neptune in pan frame mode as an optical navigation test. In ACO2, another stray light test was performed. The geometries simulated observations from the outgoing encounter asymptote with an elongation angle of 13 degrees (sun-spacecraft-target). During ACO3 and ACO5, RALPH had no 3-axis (spacecraft not in spinning mode) observations, only the functional test as described below. In ACO4, RALPH performed a dark current test, taking data while the focal plane cooled down, from 2 to 20h after the decontamination heaters were turned off. RALPH also performed an interference test, simultaneously operating LEISA, LORRI and ALICE. MVIC took color observations of Uranus and Neptune at phase angles not accessible from Earth (44 degrees and 34 degrees, respectively) and optical navigation images of Neptune using the pan frame array. MVIC performed a stray light test as a ride-along to the LORRI observation in ACO4, and LEISA performed a light leak test at an angle of 9 degrees from the sun. RALPH also did an interference test between the MVIC TDI and LORRI modes of operation. In ACO6 through ACO8, RALPH performed rehearsals of the Pluto enounter (ACO6; ACO7), LEISA stellar calibrations (ACO6; ACO8), MVIC stellar calibrations and optical navigation tests (ACO6; ACO7; ACO8), and LEISA test scans for the flat field (ACO8). Functional Test --------------- During all ACOs the RALPH instrument performed one or more functional tests. This test exercised all modes of the instrument at two different rates, and both power sides of RALPH. The test took LEISA raw and subtracted data, and MVIC data using each of the detectors. The integration times included a short and longer time. There was no specific target as often these data were taken when the spacecraft was spinning and the field of view was sweeping across the sky. Note 1 ====== The items listed above are the major RALPH observations, but in the interest of brevity may not include every RALPH observation; refer to the sequence listing for a complete list of all activities. 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_LEISA_PLUTOCRUISE.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 1.0 of this data set. 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 LEISA data is available in the SOC Instrument Interface Control Document (ICD) in the DOCUMENT section of this data set. The LEISA 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 electronics-induced and flat-field signal 2) Apply calibration offset and gain 3) Adjust for integration time, filter width, and pixel solid angle 4) Correct for gain In addition, the calibration procedure calculates various quantities such as error (see note below) 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. 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 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 windowed status of the image, as recorded in the value for the NOTE keyword of the PDS label should be considered when looking at these data. Calibration and data characteristics ------------------------------------ i) Error estimates are all zero. As of late 2016, the code to calculate the values for the Error estimates extension has not been deployed to the SOC, and placeholder code sets all pixel error estimates to zero. When the updated code is deployed to the SOC, some reprocessed observations may be delivered to PDS (e.g. Jupiter encounter data); note that observations from the Launch and Pluto Cruise mission phases have little if any science utility, so there is no incentive to reprocess those data just to provide error estimates. ii) Fixed-pattern noise. There is usually fixed-pattern noise (FPN) in the data that cannot be removed by the flat-field correction. Users need to generate an average of a few run-up frames containing background sky and the FPN, and subtract that average from every frame with a target source present. The number of frames to use will vary by observation, so this operation is not part of the automated pipeline. iii) Scattered light. Although some observations have been taken to characterize scattered light, no photometric modeling of the stray light has been made or applied to the data. Those observations have only been used to optimize the planned imaging at Pluto encounter to minimize the effect of stray light. 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 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. LSB_0123456789_0X53C_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 ** =========== ================================== ============= LEISA LSB, LRW 0X53C - 0X54E * * 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 ===== =========== LSB LEISA, Read minus Reset data LRW LEISA, Raw Read and Reset data 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) ===== =================================== 0x53c - LEISA Lossless (CDH 1)/LRW,LSB 0x54b - LEISA Lossless (CDH 2)/LRW,LSB 0x53d - LEISA Packetized (CDH 1)/LRW,LSB 0x54c - LEISA Packetized (CDH 2)/LRW,LSB 0x53e - LEISA Lossy (CDH 1)/LRW,LSB 0x54d - LEISA Lossy (CDH 2)/LRW,LSB Instrument description ---------------------- Refer to the following files for a description of this instrument. CATALOG LEISA.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. 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-PLUTOCRUISE-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_LEISA_PLUTOCRUISE.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 occured 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 docmentation, 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 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-X-LEISA-2-PLUTOCRUISE-V1.0, may not have corresponding data products in the calibrated data set, NH-X-LEISA-3-PLUTOCRUISE-V1.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_LEISA_PLUTOCRUISE.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. 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 =============================================================== A fundamental truth of managing data from some spacecraft missions is that the intent of any observation is not suitable for insertion into the command stream sent to the spacecraft to execute that observation. As a result, re-attaching that intent to the data that are later downlinked is problematic at best. For New Horizons that task is made even more difficult as the only meta-data that come down with the observation is the unpredictable time of the observation. The task is made yet even more difficult because uplink personnel, who generate the command sequences and initially know the intent of each observation, are perpetually under deadlines imposed by orbital mechanics and can rarely be spared for the time-intensive task of resolving this issue. To make a long story short, 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 point to be made is that 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. Furthermore, for pointing instruments with one or more spatial components to their detectors, a table has been provided in the DOCUMENT/ area with XY (two-dimensional) positions of each inferred target in the primary data products. If those values are several thousand pixels off of a detector array, it is a strong indication that the actual target of that observation is something other than the inferred target, or no target at all e.g. dark sky. Review ====== This dataset was peer reviewed and certified for scientific use on 12-5-2016. " ABSTRACT_DESC = " This data set contains Calibrated data taken by the New Horizons Linear Etalon Imaging Spectral Array instrument during the pluto cruise mission phase. This is VERSION 1.0 of this data set. The spacecraft was in hibernation for much of the Pluto Cruise mission phase, and the focus for RALPH (which includes both MVIC and LEISA sensors) during Annual CheckOuts one through eight (ACO1-8) was preparation for the Pluto Encounter in 2015, including functional tests, and calibrations. Observations performed during this phase for LEISA were for the Pluto Encounter Rehearsal in 2013, a test of the Sun in the Solar Illumination Assembly (SIA), Vega and Arcturus calibrations, and other calibrations (stray light, dark, flat fields, interference with other instruments). " CITATION_DESC = " Stern, A., NEW HORIZONS Calibrated LEISA PLUTO CRUISE V1.0, NH-X-LEISA-3-PLUTOCRUISE-V1.0, NASA Planetary Data System, 2016. " DATA_OBJECT_TYPE = "IMAGE" DATA_SET_COLLECTION_MEMBER_FLG = "N" DATA_SET_NAME = "NEW HORIZONS LEISA PLUTO CRUISE CALIBRATED V1.0" DATA_SET_RELEASE_DATE = 2016-10-31 DATA_SET_TERSE_DESC = " Calibrated data taken by New Horizons Linear Etalon Imaging Spectral Array instrument during the PLUTOCRUISE mission phase. This is VERSION 1.0 of this data set. " DETAILED_CATALOG_FLAG = "N" PRODUCER_FULL_NAME = "BRIAN CARCICH" 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 = "STAR" END_OBJECT = DATA_SET_TARGET OBJECT = DATA_SET_TARGET TARGET_NAME = "SUN" END_OBJECT = DATA_SET_TARGET OBJECT = DATA_SET_TARGET TARGET_NAME = "VEGA" END_OBJECT = DATA_SET_TARGET OBJECT = DATA_SET_HOST INSTRUMENT_HOST_ID = "NH" INSTRUMENT_ID = "LEISA" END_OBJECT = DATA_SET_HOST END_OBJECT = DATA_SET END