Index of /holdings/nh-j-lorri-3-jupiter-v1.0

Icon  Name                    Last modified      Size  Description
[DIR] Parent Directory - [DIR] DOWNLOAD/ 03-Oct-2008 13:38 - [DIR] index/ 03-Oct-2008 13:37 - [DIR] document/ 03-Apr-2008 12:57 - [DIR] data/ 26-Mar-2008 11:36 - [DIR] VOLUME/ 26-Mar-2008 11:33 - [DIR] CODE/ 17-Jan-2008 14:31 - [DIR] catalog/ 08-Dec-2007 15:07 - [DIR] calib/ 03-Dec-2007 17:51 - [TXT] dataset.html 31-Jul-2017 21:06 2.6K [   ] 03-Apr-2008 13:04 5.5K [PDS catalog file] [TXT] aareadme.txt 21-Feb-2008 23:51 59K
PDS_VERSION_ID                = PDS3                                          
RECORD_TYPE                   = STREAM                                        
OBJECT                        = TEXT                                          
  PUBLICATION_DATE            = 2008-02-22                                    
  NOTE                        = "The NH LORRI Jupiter encounter               
                                 Calibrated Data Archive                      
                                 Be sure to read the Required Reading         
                                 note below before using the data in          
                                 this archive.                                
END_OBJECT                    = TEXT                                          
The NH LORRI JUPITER Calibrated Data Archive                                  
   This document provides an overview of this dataset of                      
   the New Horizons (NH)                                                      
     LORRI JUPITER Calibrated                                                 
   Data Archive, including a general listing of the dataset contents.         
   This dataset contains flight data leading up to and including the          
     Jupiter encounter                                                        
   for the                                                                    
     Long Range Reconnaissance Imager                                         
   instrument of the New Horizons mission. These data were collected          
   up to                                                                      
   . See the Mission catalog file NH.CAT in the /CATALOG/ directory for a     
   description of the New Horizons mission.                                   
Required Reading                                                              
   The information contained in all documents included with, and              
   referenced in, this archive, is an integral part of this archive.          
   Specifically, the information contained in the SOC Instrument              
   Interface Control Document (ICD), and in the documents submitted           
   for publication in Space Science Reviews in 2007, is crucial to            
   understanding the data in this archive.  As such, the producers            
   of this archive have included the best possible version of these           
   documents with this archive.                                               
   * SOC Instrument Interface Control Document (AKA the ICD)                  
     The ICD specifies the interfaces between the New Horizons                
     Science Operations Center (SOC) and the instrument pipeline, which       
     process data from raw to calibrated units.  The ICD's purpose is to      
     define the various aspects of the interfaces in sufficient detail        
     to establish a clear understanding between the SOC and the               
     instrument team to allow for a parallel pipeline development.            
     In addition to mission-wide information, the ICD contains an entire      
     section devoted to the details of the LORRI instrument.  The             
     most important aids provided to the user of this archive by the ICD      
       * Descriptions of the data files that comprise the                     
         data portion of this archive.                                        
       * Descriptions of the calibration methodology of the                   
         LORRI instrument data.                                               
       * Overview descriptions of the LORRI instrument theory                 
         and operations.                                                      
       * References to more detailed documentation.                           
   * LORRI Space Science Reviews documents (AKA SSR paper(s))                 
     Scientific papers describing the New Horizons mission,                   
     spacecraft, mission design, payload and instruments were submitted       
     to the publication Space Science Reviews in 2007 after the Jupiter       
     encounter; refer to the references catalog for full citations.           
     The LORRI instrument and payload overview SSR papers, I.E.               
       Cheng, A. F., et al., 2007 [CHENGETAL2007]                             
       Weaver, H.A., et al., 2007 [WEAVERETAL2007],                           
     provide details of the LORRI theory, design, ground testing              
     and calibration, operational considerations, and post-launch             
     checkout results.                                                        
     Because of time and copyright restrictions, the SSR papers could not     
     be included in this archive in their peer-reviewed and published form.   
     However, Space Science Reviews did agree to allowing the submitted       
     versions of these papers to be included in this archive.  This has       
     been done with the initial version of this archive as a convenience      
     to the user of this archive.  However, it should be noted that           
     (1) NASA archive procedures do not guarantee that archive                
         documentation will remain with archive data as archives are          
         migrated to newer media.  Therefore, it may in the future be         
         up to the user of this archive to use the references provided        
         to obtain the documents.                                             
     (2) There will be changes made to the submitted papers before they       
         are published.  Where any differences exist between the              
         submitted versions of these documents in this archive and the        
         final published versions, the final published versions should        
         be considered authoritative, and it is up to the user of this        
         archive to assess if any such differences will affect their use      
         of this archive.                                                     
   All reasonable efforts have been made to include the documents in          
   multiple formats in the document portion of this archive.  Where           
   that was not possible due to copyright restrictions, references            
   to the documents have been included in this archive, and it is             
   up to the user of this archive to obtain a copy of such documents.         
Volume Format                                                                 
   This volume has been formatted according to the PDS Standards              
   Version 3.7.                                                               
   This volume does not contain any Extended Attribute Records (XAR).         
   Thus, some VAX/VMS users may have problems accessing files on this         
File Formats                                                                  
   All text documents and other meta information files such as                
   descriptions, PDS object definitions and detached PDS labels are           
   stream format files, with a carriage return (ASCII 13) and a line          
   feed character (ASCII 10) at the end of the record.  This allows           
   the files to be read by most current operating systems.                    
Volume Contents                                                               
   Files on this volume are organized into a set of subdirectories            
   below the top-level directory. The following table shows the general       
   structure and content of these directories, but does not exhaustively      
   list every file in each directory.  See the *INFO.TXT files in each        
   top-level sub-directory for specific information about the files           
   under that directory.                                                      
   In this table, directory names are surrounded by forward slashes (/),      
   and the top-level of the volume is indicated by a single forward slash.    
   /                     Top level of volume.                                 
   +-- AAREADME.TXT      The AAREADME file                                    
   +-- VOLDESC.CAT       Description of the logical contents of this volume.  
   +--/DOCUMENT/           Directory containing dataset-related documents.    
   |  |                    ***N.B. These documents describe the               
   |  |                              instrumentation and data of              
   |  |                              this mission and are required            
   |  |                              reading for anyone who desires           
   |  |                              to get the most out of the data.         
   |  |                    ***N.B. The list of files here is not              
   |  |                              exhaustive; see DOCINFO.TXT for          
   |  |                              a complete list of the files             
   |  |                              in this directory.                       
   |  |                                                                       
   |  +-- DOCINFO.TXT      Description of files in the DOCUMENT directory.    
   |  |                    - Refer to this file for further                   
   |  |                      details on the documents available.              
   |  |                                                                       
   |  +-- SOC_INST_ICD.LBL SOC Instrument Interface Control Document (ICD)    
   |  |                    - PDS label for all components                     
   |  +-- SOC_INST_ICD.*   SOC Instrument Interface Control Document          
   |  |                    - MSWord, PDF, ASC formats                         
   |  |                    - Describes all NH instruments' data formats       
   |  |                    ***N.B. This is one of the most important          
   |  |                            documents for this data set.               
   |  |                                                                       
   |  +-- /SOC_INST_ICD_IMAGES/        Sub-directory for ICD                  
   |  |   |                              image components.                    
   |  |   |                                                                   
   |  |   +-- SOC_INST_ICD_*.PNG              ICD components which            
   |  |                                         are awkward to present in     
   |  |                                         text form (equations,         
   |  |                                         figures, etc) provided        
   |  |                                         as PNG images.                
   |  |                                        - See SOC_INST_ICD.LBL         
   |  |                                           for a complete list.        
   |  |                                                                       
   |  +-- LORRI_SSR.LBL    PDS label for LORRI SSR Paper                      
   |  |                    - for all components                               
   |  +-- LORRI_SSR.*      LORRI Space Science Reviews (SSR) Paper            
   |  |                    - MSWord, PDF, ASC formats                         
   |  |                    - Describes the instrument                         
   |  |                    ***N.B. This is another of the most important      
   |  |                            documents for this data set.               
   |  |                                                                       
   |  +-- /LORRI_SSR_IMAGES/          Sub-directory for SSR                   
   |  |   |                              image components.                    
   |  |   |                                                                   
   |  |   +-- LORRI_*.PNG                      SSR components which           
   |  |                                         are awkward to present in     
   |  |                                         text form (equations,         
   |  |                                         figures, etc) provided        
   |  |                                         as PNG images.                
   |  |                                        - See LORRI_SSR_IMAGES.LBL     
   |  |                                           for a complete list.        
   |  |                                                                       
   |  +-- PAYLOAD_SSR.LBL  PDS label for all Payload SSR Paper components     
   |  +-- PAYLOAD_SSR.*    Payload Space Science Reviews Paper                
   |  |                    - Overview of the NH instrument payload            
   |  |                    - MSWord, PDF, ASC formats                         
   |  |                                                                       
   |  +--/PAYLOAD_SSR_IMAGES/        Sub-directory for Payload SSR            
   |  |  |                            image components                        
   |  |  |                                                                    
   |  |  +-- PAYLOAD_SSR_*.PNG                 Payload SSR components which   
   |  |                                         are awkward to present in     
   |  |                                         text form (equations,         
   |  |                                         figures, etc) provided        
   |  |                                         as PNG images.                
   |  |                                        - See PAYLOAD_SSR_IMAGES.LBL   
   |  |                                           for a complete list         
   |  |                                                                       
   |  +->NH_TRAJECTORY.LBL           Label for Spacecraft Jupiter-relative    
   |  |                               trajectory                              
   |  +->NH_TRAJECTORY.*             NH Spacecraft Jupiter-relative trajectory
   |  |                                                                       
   |  +->NH_MET2UTC.*                Conversion table between Spacecraft      
   |  |                               Mission Elapsed Time (MET) and UTC.     
   |  |                                                                       
   |  +->NH_FOV.*                    NH pre-flight Field-Of-View figure       
   |  |                                                                       
   |  +->NH_LORRI_V###_TI.TXT        LORRI SPICE                              
   |  |                                I-Kernel, provided as a convenience    
   |  |                                to the user with an attached PDS label.
   |  |                              - The SPICE kernels will be delivered    
   |  |                                separately; this file is only          
   |  |                                provided here as documentation of      
   |  |                                the instrument field of view.          
   |  |                                                                       
   |  +->QUAT_ZXYZ_J2K_TO_INSTR.LBL  Quaternion description target file for   
   |  |->QUAT_ZXYZ_J2K_TO_INSTR.ASC   PDS data label pointer QUATERNION_DESC. 
   |  |                              - PDS label + ASCII document             
   |  |                                                                       
   |  +--/SAMPLES/         Sub-directory containing data samples              
   |     |                                                                    
   |     +--SAMPINFO.TXT       Description of files in the SAMPLE directory   
   |     |                     *** N.B. Refer to this file for further        
   |     |                              details on the sample files           
   |     |                              available.                            
   |     +--LORRI_SAMPLES.LBL  Detached PDS label for data                    
   |     |                       sample files                                 
   |     +--*.ASC              Data sample files                              
   |                           - Subset of LORRI instrument data              
   |                             converted to ASCII so archive users can      
   |                             confirm that they are correctly reading the  
   |                             binary data files.                           
   |                            - See LORRI_SAMPLES.LBL                       
   |                               for a complete list.                       
   |--/CATALOG/            Directory containing PDS catalog objects.          
   |  |                                                                       
   |  +-- CATINFO.TXT          Description of files in the CATALOG directory. 
   |  |                        *** N.B. Refer to this file for further        
   |  |                                 details on the catalog files          
   |  |                                 available.                            
   |  +-- DATASET.CAT          Description of                                 
   |  |                          LORRI JUPITER                                
   |  |                        data set.                                      
   |  +-- LORRI.CAT            Description of the LORRI instrument.           
   |  +-- NH.CAT               Description of the mission.                    
   |  +-- NHSC.CAT             Description of the spacecraft.                 
   |  +-- PERSONNEL.CAT        Personnel involved in creating this archive.   
   |  +-- REF.CAT              References to works cited in catalog objects.  
   |  +-- *.CAT                Target catalog files; see CATINFO.TXT or       
   |                            /VOLDESC.CAT for a complete list.             
   +--/DATA/               Top-level data directory                           
   |  |                    *** N.B. SUB-DIRECTORIES OF THIS DIRECTORY WILL    
   |  |                             CONTAIN LORRI DATA FOR THE                
   |  |                             Jupiter encounter                         
   |  |                                                                       
   |  +--/YYYYMMDD_SCRMET/   Sub-directories of /DATA/ containing data files  
   |     |                   - See below for a description of the             
   |     |                     data directory naming convention.              
   |     |                                                                    
   |     +-- *.LBL            Detached PDS label files describing FITS files  
   |     +-- *.FIT            LORRI data as FITS format files                 
   |                          - See Filenames and Product IDs below           
   |                          - See /INDEX/INDEX.LBL and /INDEX/INDEX.TAB     
   |                             for a complete list                          
   +--/CALIB/              Top-level directory containing                     
   |  |                      LORRI                                            
   |  |                    calibration files.                                 
   |  |                                                                       
   |  +-- CALINFO.TXT      Description of files in the CALIB directory        
   |  +-- *.LBL            Detached PDS labels for LORRI                      
   |                         calibration files.                               
   |                       - See CALINFO.TXT for a complete list.             
   +--/INDEX/              Directory containing index files.                  
      +-- INDXINFO.TXT     Description of files in the INDEX directory        
      +-- CUMINDEX.TAB     Cumulative index table of data in this dataset.    
      +-- CUMINDEX.LBL     PDS label for CUMINDEX.TAB file.                   
      +-- INDEX.TAB        Index table of data on this volume                 
      +-- INDEX.LBL        PDS label for INDEX.TAB file.                      
Filenames and Product IDs                                                     
The filenames of data files and the Product IDs of observations adhere        
to a common convention e.g.                                                   
         ^^^ ^^^^^^^^^^ ^^^^^ ^^^ ^\__/                                       
         |        |       |    |  | ^^                                        
         |        |       |    |  |  |                                        
         |        |       |    |  |  +--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 Raw data *                          
         |        |       |       SCI for Calibrated data *                   
         |        |       |                                                   
         |        |       +--Application ID (ApID) of the telemetry data      
         |        |          packet from which the data come                  
         |        |                                                           
         |        +--Spacecraft Receipt Mission Elapsed Time (SCRMET)         
         +--Instrument/observation designator                                 
Note that, depending on the observation, the SCRMET in the data               
filename and in the Product ID may be similar to the Mission Elapsed Time     
(MET) of the actual observation acquisition, but should not be used as an     
analog for the acquisition time.  The SCRMET 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                                               
Data directory naming convention                                              
All of the data files in this dataset are under, but not in, the top-level    
/DATA/ directory.  Sub-directories, based on the SCRMET (see above) of the    
top-level /DATA/ directory have been provided to increase the granularity of  
data storage locations which in turn keeps there from being too many data     
files in any one directory.  The granularity implemented is one sub-directory 
per 10,000 counts of the SCRMET (see Filenames and Product IDs section above).
The subdirectory names on this volume reflect that granularity.  These        
names are of the form                                                         
where SCRMET is a grouping of the first six digits of the ten-digit SCRMET    
count, and YYYY, MM, and DD are the year, month and day of the first          
possible SCRMET corresponding to that six-digit SCRMET prefix.  Any data file 
will be located in a directory whose six-digit SCRMET prefix matches that     
of the data file.                                                             
Since each count represents about one second, there may be as many as nine    
six-digit SCRMET prefixes with the same YYYYMMDD values.  Also, since days    
will not start or end exactly on 10,000 count SCRMET boundaries, directories  
with the naming convention may span day boundaries.  That is, the YYYYMMDD    
value corresponding to the start of a 10,000 count SCRMET range may not be    
the same as the YYYYMMDD that corresponds to the end of that range.           
Explanation of granularity                                                    
The granularity of sub-directories under /DATA/ on this volume has been       
copied from that used on the Science Operations Center (SOC) where the        
data files were originally generated.  On the SOC, the same granularity       
was implemented across all eight New Horizons instruments' directory          
structures.  Because the mission instruments generate data files at           
varying rates, from one or more data files per second to one or more days     
per data file, a compromise granularity of 10,000 SCRMET counts was chosen,   
and propagated to this volume.                                                
Suggested FITS & PDS software                                                 
        For working with PDS-labeled data, software packages are available    
at Planetary Data System (PDS) nodes (as of 2007).  Several other options     
for reading either FITS or PDS-labeled data are listed here.  If not          
included in the text below, references to the packages may be either found    
at one or more PDS nodes or found via a search engine.  Data users            
planning to write custom software should refer to the PDS label               
description in the subtopics that follow for a general introduction and       
to the PDS Standards document available at PDS nodes.                         
The following URLs are current as of 2007.                                    
Readers and viewers (Package name, format handled by it, and URL):            
 READPDS  PDS           
 NASAVIEW PDS               
 FV       FITS         
 DS9      FITS                            
Development toolkits for IDL (                    
 OAL      PDS                           
 ASTRO    FITS                                
Development toolkits for C & FORTRAN:                                         
 OAL      PDS                           
 CFITSIO  FITS            
Development toolkit for Python and Perl:                                      
 PyFITS      FITS  FITS                 
General FITS info and many more references may be found at                    
N.B.  The following description of PDS labels is only meant to be             
      sufficient to write a program to read the data, and is                  
      therefore not a complete exposition.  For full details                  
      of the PDS standards, refer to the source from which this               
      dataset was obtained.                                                   
      PDS label overview                                                      
        Each PDS label file is a multi-record flat ASCII file describing the  
Data Units in a corresponding FITS data file that represent a single          
observation or group of observations.                                         
        A FITS file is made up of one or more contiguous 2880-byte records.   
Each Data Unit (DU) in a FITS data file comprises one or more records.  The   
data in each DU starts at the first byte of the DU and is arranged as         
in the PDS label.  If the data in a DU do not end at a 2880-byte boundary,    
then that DU is padded out to the boundary.                                   
        Each record in a PDS label is 80 bytes long comprising 78 printable   
7-bit ASCII characters and/or spaces and ending with a carriage return and a  
line feed.  Most records are of the form                                      
KEYWORD = VALUE                                                               
where KEYWORD is the name of a quantity, and VALUE represents the value of    
that quantity.  Spaces before, after, and between the keyword, the equals     
sign, and the value(s) are not significant.                                   
        String values may span multiple records, and are usually delimited    
by (i.e. enclosed in) double quotes.  Strings contain no double quotes.       
Some string values, such as UTC times, are not enclosed in quotes.            
        Integer & floating point numeric values are displayed without quotes. 
        Multiple values for a single keyword are indicated by enclosing the   
values in parentheses or curly braces and separating the values with commas.  
        Comments are initiated by a contiguous forward-slash & asterisk pair  
(i.e. /*) on the left and continue to the end of a single record where they   
are usually terminated by a matching asterisk & forward-slash pair (*/).      
        Blank lines may be inserted between other lines to enhance            
        1) PDS pointers                                                       
           Pointers are special cases of keyword/value pairs in the PDS label,
and define where each DU starts in the FITS file; pointers look like this:    
^HEADER               =  "XYZ.FIT"        /* Primary Header DU (HDU) */       
^IMAGE                = ("XYZ.FIT",11)    /* Primary DU              */       
^ERROR_HEADER         = ("XYZ.FIT",22)    /* Extension #1 HDU        */       
^ERROR_IMAGE          = ("XYZ.FIT",31)    /* Extension #1 DU         */       
^HOUSEKEEPING_HEADER  = ("XYZ.FIT",43)    /* Extension #2 HDU        */       
^HOUSEKEEPING_TABLE   = ("XYZ.FIT",44)    /* Extension #2 DU         */       
^THRUSTERS_HEADER     = ("XYZ.FIT",45)    /* Extension #3 HDU        */       
^THRUSTERS_TABLE      = ("XYZ.FIT",51)    /* Extension #3 DU         */       
           N.B. The single quotes in the examples above are double quotes     
                in the actual labels.                                         
           Pointer keywords HEADER and IMAGE refer to the Primary Header      
Data Unit (HDU) and Primary Data Unit, respectively.  Pointer keywords that   
end in _HEADER refer to Extension HDUs.  Pointer keywords that end in _IMAGE  
or _TABLE or _ARRAY refer to Extension DUs.                                   
           The text after the equals sign in each pointer is usually enclosed 
by parentheses and comprises the filename of the file where the DU resides and
the DU's location in that file.  The filename and the location are delimited  
by a comma.  The filename is a string enclosed in double quotes, and the DU   
location is a decimal integer value indicating the cardinal location in the   
file of the first 2880-byte record of the DU.                                 
           For example, the ^IMAGE DU above, with a location value of 11,     
starts at an offset of 28800 bytes (= [11-1]*2880) from the first byte of the 
           If only the filename is given, with neither the parentheses nor the
comma nor the location, then the DU starts at the beginning of the file i.e.  
the location is implicitly set to one.                                        
        2) OBJECT stanzas                                                     
           Each pointer in a PDS label will have a corresponding OBJECT       
stanza.  OBJECT stanzas comprise the lines between corresponding              
'OBJECT=<object_name>' & 'END_OBJECT=<object_name>' keyword lines.            
           OBJECT stanzas referring to TABLEs will contain one or more        
'OBJECT=COLUMN'/'END_OBJECT=COLUMN' stanzas.                                  
           See the comments (/* ... */) to the right of the keywords in the   
example below to understand the OBJECTs and keywords that describe binary     
********** N.B.  This example does not describe every keyword **********      
**********       that will be present in each table, but only **********      
**********       those necessary to read and understand the   **********      
**********       arrangement of the data in the DU to which   **********      
**********       OBJECTs refer.  Refer to the PDS standards   **********      
**********       for more details.                            **********      
********** Example starts after the next line                 **********      
^S_TABLE      = ("XYZ.FIT",51)    /* EDU #3;  Data table    */                
OBJECT = S_TABLE  /* Start of object describing data of pointer ^S_TABLE */   
  INTERCHANGE_FORMAT = BINARY                                                 
  ROWS = 463                /* Table comprises 463 rows */                    
  COLUMNS = 97              /* Table comprises 97 columns */                  
  ROW_BYTES = 1080          /* Each row comprises 1080 bytes */               
  DESCRIPTION = "..."                                                         
  OBJECT = COLUMN           /* OBJECT describing column 1 */                  
    NAME = STATUSES         /* Column name */                                 
    COLUMN_NUMBER = 1       /* Column location within row */                  
    DATA TYPE = MSB_INTEGER /* Column data element type */                    
    ITEMS = 3               /* Number of data elements in column */           
    ITEM_BYTES = 2          /* Size of each data element in column */         
    START_BYTE = 1          /* Byte location in row of 1st byte of column */  
    BYTES = 6               /* Column width (bytes); <= ITEMS*ITEM_BYTES */   
    DESCRIPTION = "..."                                                       
  END_OBJECT = COLUMN                                                         
  OBJECT = COLUMN           /* OBJECT describing column 2 */                  
    NAME = TEMPERATURE      /* Column name */                                 
    COLUMN_NUMBER = 2       /* Column location within row */                  
    DATA TYPE = IEEE_REAL   /* Column data type */                            
    ITEMS = 1               /* Number of data elements in column */           
    ITEM_BYTES = 4          /* Size of each data element in column */         
    START_BYTE = 7          /* Byte location in row of 1st byte of column */  
    BYTES = 4               /* Column width (bytes); <= ITEMS * ITEM_BYTES */ 
    DESCRIPTION = "..."                                                       
  END_OBJECT = COLUMN                                                         
END_OBJECT = S_TABLE  /* End of object S_TABLE */                             
********** Example ends before the previous line       *****************      
           In the example above:                                              
           - the table S_TABLE starts at byte 144001 ((51-1)*2880 + 1)        
             of the file, and comprises 97 rows each of width 1080 bytes.     
           - the first column, named STATUSES, in each row starts at the      
             1st byte of that row and comprises three MSB-first 16-bit        
             integers using 6 bytes total on each row.                        
           - the second column, named TEMPERATURE, in each row starts at      
             the seventh byte of that row and comprises one IEEE 32-bit       
             floating point value using four bytes total on each row.         
           - Subsequent rows are offset 1080 bytes from the previous row.     
      Generic PDS label details                                               
        The PDS label has meta-data which describe the circumstances          
surrounding the data in the FITS file. These meta-data are in keyword and     
value pairs (e.g. the pointers above) and each of these keywords is described 
in the PDS Data Dictionary plus the New Horizons mission- specific local data 
dictionary supplemental items, both of which are available in this archive.   
        All FITS Header Data Units (HDUs) and Data Units are described in the 
PDS labels.  In some cases, no Data Unit will be described in the PDS label   
because there is nothing to describe i.e. it is not present in the FITS file. 
        PDS LABELS:  Column Descriptions in binary tables                     
        FITS extensions may contain data that are a subset of                 
        instrument and/or spacecraft housekeeping telemetry packets           
        formatted as binary tables.  Where possible, each column              
        included in such extensions has a DESCRIPTION field something         
        like this (double quotes have been replaced by single quotes):        
         DESCRIPTION   = '                                                    
              Full Mnemonic:                                                  
              General Description:                                            
                A bit indicating the beginning of a 64-second cycle           
              Conversion:  STATES                                             
              - [lo:hi]=state description:                                    
              Subsystem:  SWAP                                                
              Packet ApID:  0X584                                             
              Byte Offset within ApID packet:  10                             
              Bit Offset within Byte of ApID packet:  0                       
              Bit Length within ApID packet:  1                               
              Type of value:  UNSIGNED                                        
              Units:  N/A                                                     
        The sub-fields used in these DESCRIPTION fields are as follows:       
        Full Mnemonic:  The complete mnemonic used in the definition          
                        of the packet.  The COLUMN name will typically        
                        be a subset of this mnemonic.                         
        General Description:  A description of the column                     
        Extended Description:  More information                               
                               - this field is not always present             
        Conversion:  This item describes the conversion of the value          
                     found in the column to a meaningful quantity.            
                     It takes one of two forms:  STATES and polynomial.       
                     If the conversion form is STATES, then the bits of       
                     the column are combined into an integer and compared     
                     against the ranges list.  In the example above, if the   
                     value of the bit is zero, then the SWAP_RT.SEC64T        
                     column represents a continuing state.  If the value of   
                     the bit is 1, then the SWAP_RT_SEC64T column indicates   
                     that a new 64-second cycle has just begun.               
                     If the conversion form is polynomial, then the bits of   
                     the column are combined into an integer and used as      
                     the independent value of the polynomial with the         
                     coefficients given.  For example, if the integer         
                     value of a column is 100,  and its conversion looks      
                     like this:                                               
                       Conversion:  polynomial coefficients:                  
                         Order 0:  0.92516257733262                           
                         Order 1:  0.979219301744176                          
                      Then the derived value of this instrument is            
                         0.925 + (0.97922 * 100) = 98.847                     
        Subsystem:  Which subsystem generated the packet                      
        Packet ApID:  The Application ID of the packet                        
        Byte & Bit Offsets & Bit Length:  the location of the column's        
                                          value in the packet, including      
                                          the 10-byte CCDS header.            
        Type of value:  For integer values, whether the value                 
                        is signed or unsigned                                 
        Units:  Nominal units of the derived column values                    
Whom to Contact for Information                                               
   New Horizons LORRI Principal Investigator:                                 
      Andrew Cheng                                                            
      Johns Hopkins University                                                
      Applied Physics Laboratory                                              
      Space Department                                                        
      11100 Johns Hopkins Road                                                
      Laurel, MD   20723                                                      
      See also PDS_USER_ID                                                    
      in CATALOG/PERSONNEL.CAT for additional contact information.            
   New Horizons Science Operation Center (SOC):                               
      Joe Peterson                                                            
      Southwest Research Institute (SWRI)                                     
      Department of Space Studies                                             
      1050 Walnut Street, Suite 400                                           
      Boulder, CO   80302