| DATA_SET_DESCRIPTION |
Data Set Overview
=================
This data set contains Raw data taken by New Horizons
Long Range Reconnaissance Imager
instrument during the PLUTO mission phase.
LORRI is a narrow angle (Field Of View, FOV = 0.29 degree square), high
resolution (5 microradian/pixel), telescope. A two-dimensional (2-D) CCD
detector, with 1024x1024 pixels (optically active region) operates in
standard frame-transfer mode. LORRI can also perform on-chip 4x4 binning
to produce images of 256x256 pixels. LORRI has no color filters and so
provides panchromatic imaging over a wide bandpass extending
approximately from 350 nm to 850 nm. The common data product is a 2-D
image of brightnesses that can be calibrated to physical units once
color spectrum information is known. Refer to DOCUMENT/SOC_INST_ICD.*
for more detail.
During the Pluto Charon Encounter mission phase starting in January,
2015, there were several sub-phases: three Approach sub-phases, (AP1,
AP2 and AP3); a CORE sequence for the Pluto flyby on 14 July, 2015 (Day
Of Year 195), sometimes also referred to as NEP (Near-Encounter Phase);
three Departure sub-phases (DP1, DP2, DP3). For this second LORRI
delivery for the Pluto mission phase, this data set includes only the
Approach data plus a subset of the CORE and Departure sequences' data
that was downlinked through the end of January, 2016, plus observations
of Kuiper Belt Object (KBO) Plutino 1994 JR1 and a low-resolution ring
search taken in November, 2015. The rest of the Pluto data will be
delivered in future versions of this data set according to the schedule
worked out by the Project and NASA.
This dataset includes (1) Non-Critical and Critical Optical Navigation
(OpNav) observations; (2) Hazard observations; (3) Observations of
Pluto, Charon, Nix, Hydra, Kerberos, and Styx during Approach; and (4)
Pluto Encounter observations, from the day before and the day of
encounter.
Optical Navigation images, identified by NAV in the observation name,
were taken regularly up until 2 days before closest approach. This
dataset also includes three OpNav images from 2 days after closest
approach.
Hazard observations were taken in order to perform a detailed search
for any objects that could only be seen as the spacecraft neared the
Pluto system. Sets of images were taken about every two weeks starting
two months before closest approach. Each set had 8 images, with a
mosaic of 4 images at two different roll angles.
Approach observation objectives were to search for changes with pan
imaging over multiple rotations, perform satellite photometry to
further resolve the orbits of Kerberos, Styx, and possible other
bodies, and image Nix and Hydra.
Encounter observation objectives were to obtain maximum resolution
imaging of the entire surface of Pluto and Charon at regular
longitudinal intervals for cartographic knowledge; to observe Pluto and
Charon at a small (12-30 degrees) solar phase angle to support phase
integrals; and to obtain regional stereo images of Pluto for
stereographic mapping at the highest possible resolution, which is
essential for understanding the relief of features on Pluto, and
understanding the magnitude of geologic processes and the origin of
geologic features.
Every observation provided in this data set was taken as a part of a
particular sequence. A list of these sequences has been provided in
file DOCUMENT/SEQ_LORRI_PLUTO.TAB.
N.B. Some sequences provided may have no corresponding observations.
For a list of observations, refer to the data set index table. This
is typically INDEX.TAB initially in the INDEX/ area of the data set.
There is also a file SLIMINDX.TAB in INDEX/ that summarizes key
information relevant to each observation, including which sequence
was in effect and what target was likely intended for the
observation.
Version
=======
This is VERSION 2.0 of this data set.
The pipeline (see Processing below) was re-run on these data for each
version since the first (V1.0). As a result, ancillary information,
such as observational geometry and time (SPICE), may be updated.
This will affect, for example, the calibration of the data if parameters
such as the velocity or orientation of the target relative to the
instrument, or the recorded target itself, have changed.
See the following sections for details of what has changed over each
version since the first (V1.0). Note that even if this is not a
calibrated data set, the 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.
This P2 Pluto Encounter dataset release provides updates to the Pluto dataset
between P1 (data on the ground by 7/31/2015) and P2 (data on the ground by
1/31/2016). This dataset contains data that may have been downlinked with
lossy compression initially and now has been re-downlinked losslessly. Lossy
data from P1 has been regenerated to increase the number of flagged bad pixels
in the quality map. All liens from the initial Pluto delivery have also now
been resolved. This dataset contains data from the Pluto Encounter timeframe
as well as two ring search observations and imaging of the KBO plutino JR1 in
November of 2015. The additional observations are listed below:
Obs. Name (Request ID), Obs Date, Downlink Start, Downlink End, Obs. Target
DPLR_JR1_LORRI_306A 2015-11-02 2015/325 2015/325 JR1
DPLR_JR1_LORRI_306B 2015-11-02 2015/325 2015/325 JR1
DPLR_JR1_LORRI_306C 2015-11-02 2015/325 2015/325 JR1
DPLR_JR1_LORRI_306D 2015-11-02 2015/325 2015/325 JR1
DPLR_O_RING_DEP_LORRI_305A 2015-11-01 2016/019 2016/027 Ring search
DPLR_O_RING_DEP_LORRI_305B 2015-11-01 2016/029 2016/031 Ring search
PELR_C_LEISA_HIRES 2015-07-14 2015/264 2015/264 Charon observations
PELR_C_LEISA_LORRI_1 2015-07-14 2015/349 2015/349 Charon observations
PELR_C_LORRI 2015-07-14 2015/278 2015/284 Charon observations
PELR_C_LORRI_DEP_1 2015-07-14 2015/322 2015/325 Charon observations
PELR_C_LORRI_FULLFRAME_1 2015-07-14 2015/249 2015/249 Charon observations
PELR_C_LORRI_FULLFRAME_DEEP 2015-07-14 2016/024 2016/024 Charon observations
PELR_C_LORRI_TIMERES_1 2015-07-14 2016/023 2016/024 Charon observations
PELR_C_MVIC_LORRI_CA 2015-07-14 2015/283 2015/283 Charon observations
PELR_C_PLUTOLIGHT_1 2015-07-17 2015/296 2016/023 Charon observations
PELR_C_PLUTOLIGHT_2 2015-07-17 2015/296 2016/023 Charon observations
PELR_H_LORRI_APPR_1d2 2015-07-13 2015/300 2015/300 Hydra observations
PELR_H_LORRI_BEST 2015-07-14 2015/249 2015/249 Hydra observations
PELR_NH_APPR_A_3 2015-06-29 2015/229 2015/229 Nix, Hydra observations
PELR_NH_APPR_A_7_02 2015-07-03 2015/226 2015/226 Nix, Hydra observations
PELR_NH_APPR_B_6_01 2015-07-13 2015/305 2015/305 Nix, Hydra observations
PELR_NH_APPR_B_6_02 2015-07-13 2015/308 2015/308 Nix, Hydra observations
PELR_N_DEP_SOONEST 2015-07-14 2015/248 2015/249 Nix observations
PELR_N_LEISA_LORRI_BEST 2015-07-14 2015/287 2015/287 Nix observations
PELR_N_LORRI_APPR_1d2 2015-07-13 2015/249 2015/249 Nix observations
PELR_N_LORRI_BACKUP 2015-07-14 2015/248 2015/248 Nix observations
PELR_N_ORBIT_B_DOY174 2015-06-23 2015/247 2015/247 Nix observations
PELR_N_ORBIT_B_DOY176 2015-06-25 2015/246 2015/246 Nix observations
PELR_N_ORBIT_B_DOY178 2015-06-27 2015/247 2015/247 Nix observations
PELR_PCNH_MULTI_LONG_1d1_02 2015-07-13 2015/249 2015/249 Pluto, Ch, Nix, Hyd
PELR_PCNH_MULTI_LONG_1d1_06 2015-07-13 2015/249 2015/249 Pluto, Ch, Nix, Hyd
PELR_PC_AIRGLOW_FILL_2_04 2015-07-13 2015/298 2015/298 Pluto, Charon obs
PELR_PC_AIRGLOW_FILL_2_08 2015-07-13 2015/318 2015/318 Pluto, Charon obs
PELR_PC_MULTI_DEP_LONG_2_01 2015-07-14 2015/293 2015/296 Pluto, Charon obs
PELR_PC_MULTI_DEP_LONG_2_05 2015-07-14 2015/295 2015/296 Pluto, Charon obs
PELR_PC_MULTI_LONG_1d2a_01 2015-07-13 2015/248 2015/248 Pluto, Charon obs
PELR_PC_MULTI_MAP_A_3 2015-07-02 2015/229 2015/229 Pluto, Charon obs
PELR_PC_MULTI_MAP_A_5 2015-07-03 2015/229 2015/229 Pluto, Charon obs
PELR_PC_MULTI_MAP_A_6 2015-07-03 2015/226 2015/226 Pluto, Charon obs
PELR_PC_MULTI_MAP_A_7 2015-07-03 2015/223 2015/223 Pluto, Charon obs
PELR_PC_MULTI_MAP_B_17_01 2015-07-13 2015/292 2015/292 Pluto, Charon obs
PELR_PC_MULTI_MAP_B_17_02 2015-07-13 2015/304 2015/305 Pluto, Charon obs
PELR_PC_MULTI_MAP_B_18_02 2015-07-13 2015/293 2015/308 Pluto, Charon obs
PELR_PC_VISUV_MAP_B_11 2015-06-28 2015/236 2015/236 Pluto, Charon obs
PELR_PC_VISUV_MAP_B_12 2015-06-29 2015/236 2015/236 Pluto, Charon obs
PELR_PC_VISUV_MAP_B_19 2015-07-01 2015/229 2015/229 Pluto, Charon obs
PELR_PC_VISUV_MAP_B_3 2015-06-26 2015/246 2015/246 Pluto, Charon obs
PELR_PC_VISUV_MAP_B_5 2015-06-26 2015/246 2015/246 Pluto, Charon obs
PELR_PC_VISUV_MAP_B_6 2015-06-27 2015/244 2015/244 Pluto, Charon obs
PELR_PC_VISUV_MAP_B_9 2015-06-28 2015/244 2015/244 Pluto, Charon obs
PELR_P_DEEPIM 2015-07-15 2015/296 2016/022 Pluto observations
PELR_P_DEP_SOONEST 2015-07-14 2015/358 2016/003 Pluto observations
PELR_P_HIPHASE_HIRES 2015-07-14 2015/315 2016/023 Pluto observations
PELR_P_LEISA_HIRES 2015-07-14 2015/287 2015/348 Pluto observations
PELR_P_LORRI 2015-07-14 2015/250 2015/254 Pluto observations
PELR_P_LORRI_ALICE_DEP_1 2015-07-14 2015/314 2015/321 Pluto observations
PELR_P_LORRI_FULLFRAME 2015-07-13 2015/249 2015/249 Pluto observations
PELR_P_LORRI_FULLFRAME_DEP 2015-07-15 2015/249 2015/249 Pluto observations
PELR_P_LORRI_STEREO_MOSAIC 2015-07-14 2015/201 2015/250 Pluto observations
PELR_P_MPAN_1 2015-07-14 2015/263 2015/291 Pluto observations
PELR_P_MULTI_DEP_LONG_1 2015-07-14 2015/265 2015/266 Pluto observations
PELR_P_MVIC_LORRI_CA 2015-07-14 2015/323 2015/358 Pluto observations
PELR_U_SATPHOT_2 2015-06-26 2015/246 2015/246 Satellite Photometry Mosaic
PELR_U_SATPHOT_3 2015-06-27 2015/237 2015/237 Satellite Photometry Mosaic
PELR_U_SATPHOT_4 2015-06-28 2015/244 2015/244 Satellite Photometry Mosaic
PELR_U_SATPHOT_5 2015-06-29 2015/229 2015/233 Satellite Photometry Mosaic
PELR_U_SATPHOT_7 2015-07-01 2015/229 2015/229 Satellite Photometry Mosaic
PELR_U_SATPHOT_8 2015-07-01 2015/229 2015/229 Satellite Photometry Mosaic
PELR_U_SATPHOT_9 2015-07-03 2015/226 2015/229 Satellite Photometry Mosaic
PELR_U_TBD_1_01 2015-07-13 2015/348 2015/349 Kerberos observation
PELR_U_TBD_1_02 2015-07-13 2015/278 2015/278 Styx observation
PELR_U_TBD_2 2015-07-14 2015/293 2015/293 Kerberos observation
Processing
==========
The data in this data set were created by a software data
processing pipeline on the Science Operations Center (SOC) at
the Southwest Research Institute (SwRI), Department of Space Operations.
This SOC pipeline assembled data as FITS files from raw telemetry
packets sent down by the spacecraft and populated the data labels
with housekeeping and engineering values, and computed geometry
parameters using SPICE kernels. The pipeline did not resample
the data.
The first 34 pixels (51 bytes) of each LORRI image contain housekeeping
information. These bytes are corrupted by LOSSY compression. Please
refer to the DOCUMENT/SOC_INST_ICD.* file for details and implications
in raw and calibrated datasets.
Data
====
The observations in this data set are stored in data files using
standard Flexible Image Transport System (FITS) format. Each FITS
file has a corresponding detached PDS label file, named according
to a common convention. The FITS files may have image and/or table
extensions. See the PDS label plus the DOCUMENT files for a
description of these extensions and their contents.
This Data section comprises the following sub-topics:
- Filename/Product IDs
- Instrument description
- Other sources of information useful in interpreting these Data
- Visit Description, Visit Number, and Target in the Data Labels
Filename/Product IDs
--------------------
The filenames and product IDs of observations adhere to a
common convention e.g.
LOR_0123456789_0X630_ENG.FIT
^^^ ^^^^^^^^^^ ^^^^^ ^^^\__/
| | | | ^^
| | | | |
| | | | +--File type (includes dot)
| | | | - .FIT for FITS file
| | | | - .LBL for PDS label
| | | | - not part of product ID
| | | |
| | | +--ENG for CODMAC Level 2 data
| | | SCI for CODMAC Level 3 data
| | |
| | +--Application ID (ApID) of the telemetry data
| | packet from which the data come
| | N.B. ApIDs are case-insensitive
| |
| +--MET (Mission Event Time) i.e. Spacecraft Clock
|
+--Instrument designator
Note that, depending on the observation, the MET in the data filename
and in the Product ID may be similar to the Mission Event Time (MET)
of the actual observation acquisition, but should not be used as an
analog for the acquisition time. The MET is the time that the data are
transferred from the instrument to spacecraft memory and is therefore
not a reliable indicator of the actual observation time. The PDS label
and the index tables are better sources to use for the actual timing of
any observation. The specific keywords and index table column names for
which to look are
* START_TIME
* STOP_TIME
* SPACECRAFT_CLOCK_START_COUNT
* SPACECRAFT_CLOCK_STOP_COUNT
Instrument Instrument designators ApIDs **
=========== ================================== =============
LORRI LOR 0X630 - 0X63B *
* Not all values in this range are in this data set
** ApIDs are case insensitive
There are other ApIDs that contain housekeeping values and
other values. See SOC Instrument ICD (/DOCUMENT/SOC_INST_ICD.*)
for more details.
Here is a summary of the types of files generated by each ApID
(N.B. ApIDs are case-insensitive) along with the instrument
designator that go with each ApID:
ApIDs Data product description/Prefix(es)
===== ===================================
0x630 - LORRI High-res Lossless (CDH 1)/LOR
0x636 - LORRI High-res Lossless (CDH 2)/LOR
0x632 - LORRI High-res Lossy (CDH 1)/LOR
0x638 - LORRI High-res Lossy (CDH 2)/LOR
0x631 - LORRI High-res Packetized (CDH 1)/LOR
0x637 - LORRI High-res Packetized (CDH 2)/LOR
0x633 - LORRI 4x4 Binned Lossless (CDH 1)/LOR
0x639 - LORRI 4x4 Binned Lossless (CDH 2)/LOR
0x635 - LORRI 4x4 Binned Lossy (CDH 1)/LOR
0x63B - LORRI 4x4 Binned Lossy (CDH 2)/LOR
0x634 - LORRI 4x4 Binned Packetized (CDH 1)/LOR
0x63A - LORRI 4x4 Binned Packetized (CDH 2)/LOR
Instrument description
----------------------
Refer to the following files for a description of this instrument.
CATALOG
LORRI.CAT
DOCUMENTS
LORRI_SSR.*
SOC_INST_ICD.*
NH_LORRI_V###_TI.TXT (### is a version number)
Other sources of information useful in interpreting these Data
--------------------------------------------------------------
Refer to the following files for more information about these data
NH Trajectory tables:
/DOCUMENT/NH_MISSION_TRAJECTORY.* - Heliocentric
LORRI Field Of View definitions:
/DOCUMENT/NH_FOV.*
/DOCUMENT/NH_LORRI_V###_TI.TXT
Visit Description, Visit Number, and Target in the Data Labels
---------------------------------------------------------------
The observation sequences were defined in Science Activity Planning
(SAP) documents, and grouped by Visit Description and Visit Number.
The SAPs are spreadsheets with one Visit Description & Number per row.
A nominal target is also included on each row and included in the data
labels, but does not always match with the TARGET_NAME field's value in
the data labels. In some cases, the target was designated as RA,DEC
pointing values in the form ``RADEC=123.45,-12.34'' indicating Right
Ascension and Declination, in degrees, of the target from the
spacecraft in the Earth Equatorial J2000 inertial reference frame.
This indicates either that the target was either a star, or that the
target's ephemeris was not loaded into the spacecraft's attitude and
control system which in turn meant the spacecraft could not be pointed
at the target by a body identifier and an inertial pointing value had
to be specified as Right Ascension and Declination values. PDS-SBN
practices do not allow putting a value like RADEC=... in the PDS
TARGET_NAME keyword's value. In those cases the PDS TARGET_NAME value
is set to CALIBRATION. TARGET_NAME may be N/A (Not Available or Not
Applicable) for a few observations in this data set; typically that
means the observation is a functional test so N/A is an appropriate
entry for those targets, but the PDS user should also check the
NEWHORIZONS:OBSERVATION_DESC and NEWHORIZONS:SEQUENCE_ID keywords in
the PDS label, plus the provided sequence list (see Ancillary Data
below) to assess the possibility that there was an intended target.
Ancillary Data
==============
The geometry items included in the data labels were computed
using the SPICE kernels archived in the New Horizons SPICE
data set, NH-X-SPICE-6-PLUTO-V1.0.
Every observation provided in this data set was taken as a part of a
particular sequence. A list of these sequences has been provided in
file DOCUMENT/SEQ_LORRI_PLUTO.TAB. In addition, the
sequence identifier (ID) and description are included in the PDS label
for every observation. N.B. While every observation has an associated
sequence, every sequence may not have associated observations. Some
sequences may have failed to execute due to spacecraft events (e.g.
safing). No attempt has been made during the preparation of this data
set to identify such empty sequences, so it is up to the user to
compare the times of the sequences to the times of the available
observations from INDEX/INDEX.TAB to identify such sequences.
Time
====
There are several time systems, or units, in use in this dataset:
New Horizons spacecraft MET (Mission Event Time or Mission Elapsed
Time), UTC (Coordinated Universal Time), and TDB Barycentric
Dynamical Time.
This section will give a summary description of the relationship
between these time systems. For a complete explanation of these
time systems the reader is referred to the documentation
distributed with the Navigation and Ancillary Information
Facility (NAIF) SPICE toolkit from the PDS NAIF node, (see
http://naif.jpl.nasa.gov/).
The most common time unit associated with the data is the spacecraft
MET. MET is a 32-bit counter on the New Horizons spacecraft that
runs at a rate of about one increment per second starting from a
value of zero at
19.January, 2006 18:08:02 UTC
or
JD2453755.256337 TDB.
The leapsecond adjustment (DELTA_ET = ET - UTC) was 65.184s at
NH launch, and the first three additional leapseconds 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 LORRI Principal Investigator:
Andrew Cheng, Johns Hopkins Univ., Applied Physics Lab
Andrew Cheng
Johns Hopkins University
Applied Physics Laboratory
Space Department
11100 Johns Hopkins Road
Laurel, MD 20723
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-LORRI-2-PLUTO-V2.0,
may not have corresponding data products in the calibrated data set,
NH-P-LORRI-3-PLUTO-V2.0.
Data coverage and quality
=========================
Every observation provided in this data set was taken as a part of a
particular sequence. A list of these sequences has been provided in
file DOCUMENT/SEQ_LORRI_PLUTO.TAB. N.B. Some sequences
provided may have zero corresponding observations.
Refer to the Confidence Level Overview section above for a summary
of steps taken to assure data quality.
The LORRI instrument replaces the first 34 12-bit pixels of each
LORRI image (408 bits; 51 bytes) with encoded binary header
information, so those first 34 pixel values in the first row are not
representative of the brightness of the imaged scene at those
locations; these pixels are in the bottom-left corner of images
displayed left-to-right and bottom-to-top. Furthermore, if the image
was LOSSY-compressed before downlink (ApIDs 0x632, 0x635, 0x638,
0x63B *), the header information corrupts the first 40 pixels of the
first 8 rows of the image because of the Discrete Cosine Transform
compression algorithm. The SOC pipeline extracts these data into the
FIRST34 extension of LORRI FITS files, which is also corrupt in
LOSSY-compressed files. The SOC calibration pipeline also flags these
pixels as bad in the QUALITY_MAP extension of calibrated FITS files;
no such flags are available in the raw FITS files; the SOC pipeline
did not flag the additional corrupt pixels beyond the first 34 in
LOSSY-compressed data until the Pluto P2 delivery late in 2016.
* See ApID definitions under the Data section of the Data Set
Description, DATA_SET_DESC, in this data set catalog.
Observation descriptions in this data set catalog
=================================================
Some users will expect to find descriptions of the observations
in this data set here, in this Confidence Level Note. This data
set follows the more common convention of placing those
descriptions under the Data Set Description (above, if the user is
reading this in the DATASET.CAT file) of this data set catalog.
Caveat about TARGET_NAME in PDS labels and observational intent
===============================================================
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.
Review
======
This dataset was peer reviewed and certified for scientific use on
12-5-2016.
|
.png)
.png)
