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

Certification Status: Certification held pending delta-review of liens directly related to data question (as opposed to typos and general documentation updates).


The AGC Gain CSV SPREADSHEETs under DOCUMENT/ end in 2013 and do not cover the data set observations.  They used tables from the Pluto Cruise data sets instead of the new ones covering the Pluto Encounter data set.

As for SWAP, the initial image data in the PDS labels are not described in any meaningful way in the level 3 data.

Dick Simpson’s presentation notes an odd offset between I and Q values for one of the test sequences that should probably be investigated and explained.

Absolute times are uncertain by as much as 1 s in radiometry, I/Q sampling, and conversion using MET-to-UTC table (important for occultation chord derivation). (per D. Simpson presentation)

Absolute amplitude calibration of radiometer is not understood (important for surface temperature estimation). Derivation of Tsys is missing steps. Measurements are non-physical assuming nominal Tsys. (per D. Simpson presentation).

Dick’s "Comments" file (http://pdssbn.astro.umd.edu/review/201605_NewHorizons/presentations/Simpson_REX_comments_v2.docx) contains a laundry list of mainly documentation issues that should be taken as liens except as followins:  The comment (B1) regarding the I/Q scaling factor only requires action if there is some specific reason of interest to users for the selection of the value used.

For file: 'aareadme.txt'
--> •	Once the tracking dataset (for gravity studies) is complete it would be useful if the aareadme.txt was updated with the data set ID of this dataset so users can find it quickly (and vice-versa, the tracking dataset should have the data set ID which contains the REX data)

For file: 'catalog/dataset.cat'
--> First paragraph, second line should be tabbed or additional newlines should be added to separate it from the rest of the paragraph
--> Filenames/Product IDs naming convention description is not tabbed properly (the arrows don’t align with the filename)
--> The notes from the aareadme.txt naming convention should also be in the dataset.cat naming convention, i.e. Note FN1 and FN2.

For file: 'catalog/rex.cat'
--> There are two headers for "INSTRUMENT OVERVIEW – FLIGHT ELEMENT"
--> DSS-35 was operational in 2015 but is not listed in the "Subsystems – DSN" section or "Location – DSN" section. (No need to add it unless DSS-35 was used by New Horizons)
--> Under "DSCC Transmitter Subsystem", the last sentence says power levels above 20 kW are available only at 70-m stations. 80 kW transmitters are being installed at the 34-m stations, and some are operational today. Was the REX experiment limited to the 20 kW transmitters?
--> Acronyms section, "NIST" says "SPC 10 time relative to UTC [???]", with question marks. (National Institute of Standards and Technology?)

For file: 'document/docinfo.txt'
--> It would be helpful if the document listing were in alphabetical order so they appear in the same order when listing the directory

For file: 'document/codesamples/codeinfo.txt'
--> IDL and Python notes that it requires supporting libraries. The libraries are listed in aareadme.txt but would be beneficial to also list here.

For files: 'data/yyyymmdd_tttttt/*.lbl'
--> The SPICE_FILE_NAME includes CK and SPK. Were only time transformations applied?

For files: 'data/tnf/*.lbl'
--> These labels lack the recommended keyword MISSION_PHASE_NAME and the required keywords SPACECRAFT_CLOCK_START_COUNT and _STOP_