October 2018 New Horizons SDC KEM Cruise 1 Raw/Calibrated Liens =============================================================== Certification Status: Not Certified, delta review required. Need to review over updated documentation regarding coincident events. START/STOP_TIME --> It was noted that for some instruments that there may be an overlap of data between the Pluto Encounter and the KEM mission phases. It was decided during the review to have the data live in the current KEM data sets. But please document in the dataset.cat and nh_kem.cat file of this fact, where it occurs, and ensure the START/STOP_TIME values are correct in the dataset.cat file. Ancillary Data --> Inconsistencies in timing, length of included data within the data files. nominal included data goes until 2017-12-17. In both level 2 & 3: --> --> documents/sdcram only goes until 2016-12-31 --> --> documents/sdc_on_off_times_v0830.tab (and _alt.tab) only until 2017-01-24 --> --> documents/sdc_on_off_cmd_v001.tab (and _alt.tab) only until 2016-10-16 --> --> documents/sdc_on_3d_v0830.tab only until 2017-01-21 --> --> documents/sdc_off_3d_v0380.tab only until 2016-10-19 Many hits come in clusters of many channels at same time – quality flag of “OK”, "OK" implies no thruster firing. --> SOC to Instrument Pipeline ICD: “The maximum number of recorded hits in one second on a given channel for SDC is in general 3. The way the timing works it is possible to get up to 5 hits/second. However, if more than one hit is recorded in one second (instrument wide) this is considered a coincident event and will be flagged. The science processing interprets such an event as s/c noise and removes it.” --> The Raw Data contain many of these coincident events that are not being removed. --> Clarification required in documentation about when data should be flagged and/or removed. --> Reason for the coincident events needs to be documented. --> May need to add errata.txt file to other mission phases for this issue. files: calib/*.tab --> DATA_SET_ID typo: DATA_SET_ID = "__MACRO_DATASET_UPPER__" file: catalog/dataset.cat --> CONFIDENCE_LEVEL_NOTE "Review" section: consider making this statement generic, change from “certified for scientific use on TBD.” to “certified for scientific use by the PDS.” --> -2- and -3- dataset.cat effectively the same file. Descriptions are very generic and do not contain any specific discussion of these particular data. --> "When considering this data set, note that the SDC channel thresholds were increased to their 'high' settings starting on 9/21/2017 (or 39.5 AU) due to unexpected noise following instrument testing for the MU-69 encounter." --> --> which instrument testing? stimulated calibration (document/sdc_stim_v0002.tab) lists the last stimulated calibration as 2016-07-08. --> --> what are the downstream implications for this? is the detector just not sensitive anymore? --> --> related: engineering (level2) dataset on 20170921 has a *large* number of files, some of which are only a couple of data points, showing the fluctuations and then increase in the threshold level --> ABSTRACT_DESC: In the first paragraph they call this mission phase "Kuiper Belt cruise 1 mission phase", but in the data files, they call it "CRUISE TO FIRST KBO ENCOUNTER". Should be consistant. --> ABSTRACT_DESC: Please specify the actual date range of the data found in the data set, or that could be found within the dataset. Currently they specify when data was downlinked, or that data is found between START_TIME and STOP_TIME (which should be replaced with actual values). --> In CONFIDENCE_LEVEL_NOTE: DOCUMENT/SEQ_LORRI_PLUTO.TAB is mentioned, but this document does not exist yet. Update this text. file: catalog/nh.cat --> Remove from these KEM data sets. Provide updated copy to PDS for ingestion. --> There is a reference to a missing note in both raw and calibrated folders: “4 These mission phase dates and/or designations are still under consideration and will most likely change in future versions of this mission catalog.” It should be deleted because note 4 refers to KEM phase. file: catalog/nh_kem.cat --> MISSION_DESC should unambiguously give the values of MISSION_PHASE_NAME. It currently has: =================== Full MISSION_PHASE_NAME, Short name Start(1,3) Stop(2,3) plus optional Description ---------- ---------- --------- ------------------------- KEMCRUISE1 2016-10-26 2018-08-14 KEM CRUISE1, KBO1 CRUISE, Pluto-KBO1 Cruise, Kuiper belt Extended Mission (KEM) first cruise (4) KEM1 2018-08-14 TBD KEM1 ENCOUNTER, KBO1 ENCOUNTER, KBO1 approach, flyby, post-encounter (4) =================== --> --> Please make it clear what the valid values being used for MISSION_PHASE_NAME are. Note that all values should be in all caps. --> --> Note that none of the values above are currently being used in a data set. It is okay to list future values, but the current value is also needed. --> --> Please add "CRUISE TO FIRST KBO ENCOUNTER" in the table above --> Missing acronyms: (KB) for Kuiper Belt, (KBO) for Kuiper Belt Object. --> "Characterize regolity scattering properties of MU69 and any satellites and rings." Change "regolity" to "regolith". --> Worth mentioning the ambiguity of the start_date (and overlap of data between prior mission phase) for some instruments. --> line 225, regolith misspelled. --> typo in kem1 cruise phase disc: "The name and times chose for this mission phase" (chosen) --> There is a reference to a missing note in both raw and calibrated folders: “4 These mission phase dates and/or designations are still under consideration and will most likely change in future versions of this mission catalog.” It should be deleted because note 4 refers to KEM phase. file: catalog/sdc.cat --> ) No particle events over 2.8E-10 g (3 μm) as of late 2016. Reason under active discussion by science team and eventually addressed in a future delivery of SDC data sets. Any larger particles found in this data set? Status of these discussions? Plan to address? directory: data/ --> Many data files were removed after it was mentioned that they were labeled as being part of the "PLUTO ENCOUNTER" mission phase. Please add these data back. --> --> nh-x-sdc-2-kemcruise1-v1.0/data/20161017_034136/sdc_0341369528_0x700_eng.lbl --> --> nh-x-sdc-2-kemcruise1-v1.0/data/20161018_034136/sdc_0341369529_0x700_eng.lbl --> --> nh-x-sdc-2-kemcruise1-v1.0/data/20161021_034136/sdc_0341369530_0x700_eng.lbl --> --> nh-x-sdc-2-kemcruise1-v1.0/data/20161024_034136/sdc_0341369531_0x700_eng.lbl --> --> nh-x-sdc-2-kemcruise1-v1.0/data/20161025_034136/sdc_0341369532_0x700_eng.lbl --> --> nh-x-sdc-3-kemcruise1-v1.0/data/20161017_034136/sdc_0341369528_0x700_sci.lbl --> --> nh-x-sdc-3-kemcruise1-v1.0/data/20161018_034136/sdc_0341369529_0x700_sci.lbl --> --> nh-x-sdc-3-kemcruise1-v1.0/data/20161021_034136/sdc_0341369530_0x700_sci.lbl --> --> nh-x-sdc-3-kemcruise1-v1.0/data/20161024_034136/sdc_0341369531_0x700_sci.lbl --> --> nh-x-sdc-3-kemcruise1-v1.0/data/20161025_034136/sdc_0341369532_0x700_sci.lbl files: 'data/*/*.lbl' --> MISSION_NAME: Change value from "NEW HORIZONS" to "NEW HORIZONS KUIPER BELT EXTENDED MISSION" file: data/*/*eng.lbl --> typo: in EXTENSION_HK_0X00D_TABLE->DESCRIPTION: Miscellaneouse => Miscellaneous file: document/docinfo.txt --> aareadme_bu.txt listed here not included in the directory. file: document/nh_met2utc.lbl & nh_met2utc.tab --> These files need to be updated to include the current data. The last entry in the tab file is on January 2, 2016. Data should continue through the time covered by the data submitted in this archive. --> Suggestion: converts MET to date (neat, but wouldn’t it be better if they included a routine? Times are provided every 500,000 seconds...) file: document/sdcram.csv --> new file - not in other datasets? No other references to this document in other parts of the dataset, however. Probably not used for the level 3 product, but should be carefully considered for any analysis. --> --> Please add references where appropriate. Possible locations: dataset.cat, icd, etc file: document/sdcram.lbl --> Line 73: "Two ounter fields..." Change "ounter" to "counter" --> Line 76: Change "comprsing" to "comprising" --> Line 78: Change "4)" to "5)" for heading and all subheadings. --> Line 79: Change "dector" to "detector" --> Line 105, awkward sentence: "Subtleties, such as how much the ram direction is from pointing directly away from the Sun, are ignored." --> Line 293: Change "MINIMUM SDC BORE-RAM ANGLE" to "MAXIMUM SDC BORE-RAM ANGLE" file: document/sdc_{off,on}_3d_v0830.lbl --> "This table includes only only those time periods with a duration of at least three days. This was requested by the reviewers during the peer review of this data set." Delete repeated "only." file: document/sdc_on_off_cmd_v0001.lbl and sdc_on_off_cmd_v0001_alt.lbl --> Repeated phrasing: "The ordering of events in this file is by time, then channel number. This INCLUDES ONLY those events initiated by spacecraft commanding. This EXCLUDES those events initiated by SDC autonomy. The ordering of events in this file is by time, then channel number." file: document/sdc_stim_v0002.tab --> Line 9 is too long, making the data start at the wrong spot. file: document/seq_sdc_*.* --> Please add these files as was done for PC and PE mission phases. file: index/index.lbl & index.tab --> This Level 3 index file looks odd to me. In the label description only describes the option for “Level 1” or “Level 2”, despite this being a Level 3 archive. In the table files are listed the “Level 2”; however, the names of the data files described in the table are the Level 3 file names. I checked the Level 2 archive. The Level 2 table shows “Level 1” in the field and Level 2 file names are shown. --> --> Edit the column DESCRIPTION to reflect what these values mean and/or what standard they are using. For instance these might signify CODMAC level (not in NH case). You can also just state that Level 1 mean raw data, and Level 2 means calibrated, or what ever the case actually may be. file: index/indxinfo.txt --> mentions "SLIMINDX.TAB - Narrow version of INDEX.TAB, less than 80-columns wide." but SLIMINDX.TAB is really 85 characters wide. file: index/slimindx.tab --> Same problem as seen in previous review: duplicate entries. Two datasets for the same time periods from 20170403-20170912 and 20171022-20171118. --> Suggestion: If the actual target is not specified here (i.e. CALIBRATION vs RHO LEO), please add a new column to specify it. file: 'voldesc.cat' --> DESCRIPTION: In the first paragraph they call this mission phase "Kuiper Belt cruise 1 mission phase", but in the data files, they call it "CRUISE TO FIRST KBO ENCOUNTER". Should be consistant. --> VOLUME_SET_NAME: Values must be in all caps. Last edited by SBN:B.Hirsch and SBN:T.Barnes on 2018-10-19