New Horizon SDC Specific Liens for Pluto Encounter Data Sets
------------------------------------------------------------

Certification Status: On/Off table must be present before data can be certified or published.  This should be reviewed and OKed by reviewers, but delta review is sufficient for certification at that point.


Metadata (sdc on/off times) are incorrectly compiled.

Is there a time stamp issue?  Identical times often the same for same channel.  Please investigate.  Examples below:
(2,3) (5,6) (7,8) (11,12) (13,14)  ….3917 (way before PE)
(2,3) (5,6) (8,9) (10,11) (12,13) (14,15) for ….8021 (before PE)
(2,3) (7,8) (11,12) (14,15)   ….8022 (during PE)
(1,2) (3,4,5) (6,7) (8,9,10) (11,12) (13,14,15)   ….8033 (after PE)

Apparently the STIM Listing is missing a calibration period in 2014

Some discussion about the fact that the SDC is not always pointed in the ram direction, as assumed, especially during Pluto encounter, but the SDC files contain no geometry information.  Seems like a separate file providing geometry along with times the instrument was turned on, threshholds, etc., would be a reasonable solution.  Suggested that for Pluto encounter, where geometry is well known and data are of high interest, that fairly detailed geometry be provided; whereas for cruise phase, where geometry might be reconstructed,  provide low-cadence geometry or geometry for periods around recorded hits, as a sample for potential users to inspect if they are considering a more detailed study, to gauge what might be found in the data once better kernels are available or more detailed geometry is calculated.


file: 'document/sdc_stim_v0000.tab'
--> This file has no pds label file associated with it.  It is actually found within the file.  This is valid, but different than how the other files were produced.

file: 'document/seq_sdc_pluto.tab'
--> This file seems to be missing entries.  Only entry is on 2015-01-12 for channels ON - is it really correct that the instrument was only commanded once?




General Liens for all New Horizon Pluto Encounter Data Sets
-----------------------------------------------------------

Some very brief, high-level description of when the actual encounter happened,
and maybe where in the directory structure those data are, would be very
helpful to users. [This should probably be in some permanent part of the data
set description that users are likely to see – like the abstract.]

The dataset.cat needs to reflect the state of the Pluto data now, as delivered
(with little Pluto data at very low resolution).

The boilerplate, all-encompassing descriptions that worked reasonably well for
early mission and cruise data are not addressing the needs of users now, who
are looking for the more interesting encounter data, and need to be able to
find the most interesting data easily.  AAREADME should be pared down to only
relevant sections that actually address volume layout and otherwise refer
users to documents.

Please update the references that refer to JPL internal documents, which are not generally accessible to anyone outside JPL, to indicate that the referenced documents are not generally available (in the reference.cat file).



For file: 'aareadme.txt'
--> typo: "The filename prefix may provides additional infomation about the instrument detector." => "The filename prefix may provide additional information about the instrument detector."
--> typo: Missing content "The following URLs were current as of 2007 when the early New occasionally, and ..." between the words "New" and "occasionally".

For file: 'catalog/nh.cat'
--> Add subphase table to the mission.cat description.  It is referenced in SWAP data set catalog file for example.

For file: 'catalog/nhsc.cat'
--> Check statement "more than 4 billion miles from Earth" -> 4.9 billion km from Sun.  Change unit to km.
--> Section on propulsion mentions a "Figure 5" but there is no such figure in the catalog file.  It should say "as shown in Figure 5 of [FOUNTAINETAL2008]."
--> Some of the mission descriptions are still written in future tense, with predicted distances, etc.  These could be updated with more meaningful information.  Emphasis given using asterisks ('*').
--> --> "Pluto and Charon *will first appear* as unresolved bright dots, but the planet and its moon *appear larger* as the encounter date *approaches*. About three months from the closest approach … the cameras on the spacecraft *can make* the first maps."
--> --> "the spacecraft *comes as close as* … when the spacecraft *is closest* to Pluto … it *will take* close-up pictures ..."
--> Is his statement still true: "as of early 2016, no extension to the mission has been approved."
--> Include reference in text: Control rates for each of the spacecraft axes are *shown below in Table II.* ==> "shown in [FOUNTAINETAL2008] Table 2."
--> Spacecraft sketches do not show position of SDC nor is its position described in the document.

For file: 'catalog/ref.cat'
--> ROSENBERGETAL1994: Abbreviate the authors' names appropriately. Also, the DOI is given in two formats; I suggest dropping the URL one.

For file: 'document/codmac_level_definitions.pdf'
--> Describes the NASA Level 1B (Resampled L4) as irreversibly transformed measured values. I assume these are derived from the calibrated L3? Please note the source.

For file: 'document/docinfo.txt'
--> In several places throughout the text, the SSR papers are referenced to 2007 though they should be for 2008.  Also please make reference to the REF_ID used in the reference catalog file when a copy of the paper is present in this directory.

For file: 'document/nh_mission_trajectory.tab'
--> This file ends before the start date of the data sets.  This file only goes through 2014-12-31.

For file: 'document/nh_trajectory.tab'
--> This file is only relevant for Jupiter fly-by.  Why include it here?

For file: 'document/soc_inst_icd.pdf'
--> page 18, 8.1: Note that the type in the spectral range ("1.225-2.5" should be "1.25-2.5").
--> page 54, table 10-2, 10-3: Data format not consistent with the specifications in these two tables
--> page 66, 10.3.4:  The unit for resolved and unresolved sources are reversed
--> page 67, 10.3.6:  Information outdated, and conflict with 10.3.13
--> page 54, table 10-2, 10-3: Data format not consistent with the specifications in these two tables
--> --> For example: '028769/mc0_0287692247_0x536_eng.fit': HOUSEKEEPING table 75 columns and WINDOW_MISMATCHES table 10 columns
--> page 66, 10.3.4:  The unit for resolved and unresolved sources are reversed
--> page 67, 10.3.6:  Information outdated, and conflict with 10.3.13
--> page 115, 13.2.1, 2) the unused channel should be 10 not 11 (which on higher level data products becomes 11)
--> page 121, 13.4.4, 1)  Calibrated Data - Only 9 columns are defined but there are 10 columns.  "j.   Impact Velocity" should be added
--> page ???, 14. : The ICD refers to the RPA as a "low-pass filter".  It is, in fact, a high-pass filter.
--> page 132: It refers to "section 135" which does not exist.  This is probably Section 14.5.10.
--> page 133: It refers to "section 13" which does not exist.  This is probably Section 14.5.10.
--> page 141: typo: "4 time" => "4 times"