New Horizons assorted liens =========================== NH-X-REX-2-LAUNCH-V1.0 NH-X-REX-3-LAUNCH-V1.0 NH-J-REX-2-JUPITER-V1.0 NH-J-REX-3-JUPITER-V1.0 NH-X-REX-2-PLUTOCRUISE-V1.0 NH-X-REX-3-PLUTOCRUISE-V1.0 errata.txt - File is not mentioned and does not exist. NH_REX_V100.TXT - DESCRIPTION is not a valid keyword for OBJECT = TEXT. - CAVEATS paragraphs 1 and 2 are nearly identical to DESCRIPTION paragraphs 2 and 3. Possibly drop DESCRIPTION and put everything into NOTE. - Need to make sure equivalent two-way tracking data makes its way into the archive for Pluto encounter. These will be the equivalent to the DSN raw radio data from other missions, but will have to come from a different source. REX_AGCGAIN{A,B}.LBL - DOCUMENT_NAME is not an allowed keyword in a SPREADSHEET object definition, but NAME is allowed (line 18). - DESCRIPTION needs to explain what documentation is provided and the units for the field (field 3). - Field 6 should be calendar format (lines 56-57). - Field 4 typo under DESCRIPTION "inforation." - Field 6 typo under DESCRIPTION "calendate." REX_SSR.LBL: PUBLICATION_DATE should be 2007-01-08 according to the first page of the PDF SAMPLES: The examples of unpacked binary files are from a different data set SEQ_REX_LAUNCH - PDS data/time datat type would be better than character. Omit double quotes (column 3). - Statement that ?end time of each (sequence) is the start time of the next sequence? may be accurate when applied to REX alone; but it seems dubious for the mission as a whole. New Horizons REX ========================= NH-X-REX-2-LAUNCH-V1.0 NH-X-REX-3-LAUNCH-V1.0 NH-J-REX-2-JUPITER-V1.0 NH-J-REX-3-JUPITER-V1.0 NH-X-REX-2-PLUTOCRUISE-V1.0 NH-X-REX-3-PLUTOCRUISE-V1.0 - Create PERSONNEL.CAT to store references - Target name is listed as N/A - NH-X-REX-*-LAUNCH-V1.0: The reference "TYLERETAL2008" under catalog/dataset.cat is not defined in a REFERENCE_KEY_ID in the label - NH-X-REX-*-PLUTOCRUISE-V1.0: Under catalog/dataset.cat, one of the TARGET_NAME values is "N/A" - Make sure document/owenetal2012.{lbl,pdf} files get added to LORRI EDR data sets; they are currently only in RDR data sets. aareadme.txt - "FITS Suport Office" should be "FITS Support Office" (line 489) document/ - rex_ssr.pdf, lumineetal1995.pdf, payload_ssr.pdf, soc_inst_icd*.pdf need text versions. extras - Rename "document/extras" directory to something that does not imply "extras" or software that will be supported - newrex_dump_rof.bash: case-sensitive string IMAGE needs to be replaced with ARRAY (two occurances) - Add OSX versions of the scripts samples - Use {} instead of () catalog/ - Missing catalog files for KERBEROS, STYX, 136108 HAUMEA, and MAKEMAKE. They are not currently in the PDS3 catalog, so they need to be provided. - Make sure the most current version of this catalog file is supplied. nh.cat - Line wraps in the second paragraph of "Misison phases" need to be better formatted. - Under "Mission Phases" section, the paragraph before the mission phase table should be better formatted. - Last sentence before the mission phase table in the "Mission Phases" section should change "was planned to be" to "is planned to be" dataset.cat - The ABSTRACT_DESC "VERSION" number is missing. - The CITATION_DESC "VERSION" number is missing for the data set name. - The DATA_SET_NAME "VERSION" number is missing. - The DATA_SET_TERSE_DESC "VERSION" number is missing. - The DATA_SET_DESC "VERSION" number is missing. in the 'Data Set Overview' and 'Version' sections. - A Data Coverage and Quality summary should be added under CONFIDENCE_LEVEL_NOTE. - Add a reference to the sequence table to the (new) “Data Coverage and Quality” section in the CONFIDENCE_LEVEL_NOTE. Index/index{lbl,tab} - Date/time values should not be enclosed in quotes and should be specified as DATA_TYPE = TIME for consistency with other PDS data sets. k.nh-x-rex-2-launch-v1.0/data/,l.nh-x-rex-3-launch-v1.0/data: - Mismatches with -rex-3- such that one has a file the that the other has no equivalent - Mixmatches with -rex-3- only in SOC version number k.nh-x-rex-2-launch-v1.0/data/20060419/*.lbl - 4422 labels in these directories have near duplicates with the same START_TIME and STOP_TIME but different INST_CMPRS_TYPE (NOTCOMP or LOSSLESS) and TELEMETRY_APPLICATION_ID (0x7b0 or 0x7b1). - Every other label beneath data has INST_CMPRS-TYPE = NOTCOMP - Only rex_0007754204_0x7b0_eng_1.lbl, rex_0007754204_0x7b1_eng_1.lbl, and rex_0007768342_0x7b1_eng_1.lbl have unique START_TIME 1.nh-x-rex-3-launch-v1.0/data/20060419/*.lbl - 4415 labels in these directories have near duplicates with the same START_TIME and STOP_TIME but different INST_CMPRS_TYPE (NOTCOMP or LOSSLESS) and TELEMETRY_APPLICATION_ID (0x7b0 or 0x7b1). o.nh-x-rex-2-plutocruise-v1.0/data/, p.nh-x-rex-3-plutocruise-v1.0/data/ - Mismatches with -rex-3- such that one has a file the that the other has no equivalent. - Mixmatches with -rex-3- only in SOC version number (64 files total). nh-x-rex-2-plutocruise-v1.0/data/20110520_016820/rex_0168205926_0x7b1_eng_1.* - .lbl is missing #6 (HOUSEKEEPING_0x096). This may be from the EXTENSION_SSR_SH_HEADER being defined twice. This problem may also be in other labels. o.nh-x-rex-2-plutocruise-v1.0/index/index.tab - List the tabels in data/tnf/ even if fiels in index.tab are blank. SEQ_REX_LAUNCH - PDS data/time datat type would be better than character. Omit double quotes (column 3). - Statement that “end time of each (sequence) is the start time of the next sequence” may be accurate when applied to REX alone; but it seems dubious for the mission as a whole. SOC_INST_ICD_REX.{LBL,PDF} - 12.1, end of second paragraph: “ … which radiate an uplink signal that is detected and measured by REX on-board the spacecraft.” There is no “detection” of the uplink signal on the spacecraft; detection takes place during processing of the samples on the ground. - 12.1, experiment 3, first line: “… designed to measure the hemispherically averaged surface emission …” During the radiometry observations, Pluto will subtend an angle of about 14° at the spacecraft. Since HGA beamwidth is 0.6°, the target will be easily resolved. There is certainly spatial averaging as the beam sweeps across the night side, but the measurements are not “hemispherically” averaged. - 12.1, 3rd line from end of page 105 (and elsewhere): “ … one-way uplink tracking signal …” should be replaced by “ … one-way uplink signal …” - 12.1, page 106, end of first paragraph: Extend the final sentence as follows: “ … the lunar occultation data are described by labels and by DOCUMENT/TNFSIS.LBL.” - 12.2, first line: “After receiving the command to start taking data …” CATALOG/REX.CAT states that sampling is “constant” from the time REX is powered up, implying that there is no command to start taking data. These two descriptions need to be reconciled. Likewise, the statement at the beginning of the next paragraph, implying that there is a command to stop taking data, needs to be revised. - 12.2, lines 1-2: “ … start taking data on the next 1 PPS strobe … the REX FPGA starts generating a continuous stream of data …” CATALOG/REX/CAT states that data collection and storage are asynchronous with respect to the 1PPS markers. As a result, there can be partial frames at both the beginning and end of a data taking event, which lead to C&DH errors if compression is attempted. These two descriptions need to be reconciled. - 12.2.1.1.2, first line: “In bit positions 6, 5 & 4 …” Need to define the bit numbering convention somewhere in the document. From Table 12-3, I infer that the convention is b7, b6, … b1, b0 right to left; so a reference to the PDS Standards Reference v3.8 (Appendix C) could be used. - 12.2.1.1.2, line 2: “ … all other bits are normally zero.” What does an abnormal setting indicate? - Table 12-4: Since the information in the rightmost column is never used (all descriptions in the text use 1-based counting), it should be omitted. - 12.2.1.2.3, line 3: Typo “tage.” - Table 12-6: missing bracket in row 4 (...ROF[15...). - 12.2.4, Text could use some technical editing. - Table 12-7, row 2: According to page 157, EDU numbering starts at 1; but the table shows 0 . - 12.2.4.1, first line: Typo “The the” - 12.2.4.2.1, line 2: Typo “n” - 12.2.4.2.2, line 3: Typo “stoed” - 12.2.4.2.3: Referring to FITS headers and PDS labels is not very helpful to the reader. It also means that validation depends entirely on what is in the data products themselves and not on some external specification against which the products can be compared. To compound the problem, the PDS label refers users back to this document. - 12.2.5, line 4: Typo “tointerpret” - 12.2.6, This section needs to be fleshed out. - 12.3.1.1: CATALOG/REX.CAT is missing the AGC setting in the expression for mV. - 12.3.1.2, Expression for dBm needs explanation. - 12.3.1.2, An explanation for what makes the AGC "automatic" is needed. - 12.3.2: “in the EDU 2 BINTABLE, the radiometry values represent rates instead of accumulating values” is not correct. The radiometry values are derived from accumulator rates, but they are measurements of power. - 12.3.2.4.1 and 12.3.2.4.2 seem unnecessary - 12.3.6: “Calibration Files Needed: None, all calibration factors are in the source code and listed above” does not appear to be correct. According to 12.3.1.2, “A state table of commanded, per-Side AGC settings … is stored in the Uplink DataBase … and … the pipeline retrieves the appropriate values based on the observation time of the FITS file …”