New Horizons' Extended Mission May 2020 K2 External Peer review Meetings notes: https://docs.google.com/document/d/1X4Mi9yTmzjtemeGQqHxlzhpo7rLqaIXp8tgjQtDaNz8/edit?usp=sharing Presentations: https://sbnreview.astro.umd.edu/202005_NH_KEM/notes-presentations/ =============================================== Datasets Reviewed: NH-A-ALICE-2-KEM1-V3.0 NH-A-ALICE-3-KEM1-V3.0 NH-A-LEISA-2-KEM1-V3.0 NH-A-LEISA-3-KEM1-V3.0 NH-A-LORRI-2-KEM1-V3.0 NH-A-LORRI-3-KEM1-V3.0 NH-A-MVIC-2-KEM1-V3.0 NH-A-MVIC-3-KEM1-V3.0 NH-A-PEPSSI-2-KEM1-V3.0 NH-A-PEPSSI-3-KEM1-V3.0 NH-A-REX-2-KEM1-V2.0 NH-A-REX-3-KEM1-V2.0 NH-A-SDC-2-KEM1-V3.0 NH-A-SDC-3-KEM1-V3.0 NH-A-SWAP-2-KEM1-V3.0 NH-A-SWAP-3-KEM1-V3.0 =============================================== General liens that affect all data sets: SPICE files --> Finalize the SPICE data set with NAIF. Suggestion: Consider adding a new document that discusses the science objectives and measurements of the various instruments in the post-Pluto mission. This could be just a text file to address the comments that Rudy has raised in the last few reviews, but would have lower impact than updating the SIS and catalog files. This information can probably be easily extracted from the extended mission proposal. See pepssi_Joy.pdf slide 9. DATA Labels --> SBN-TB: I have probably already asked this before, but why does the data labels get updated SPICE and geometry information each time NH team redelivers the data set even though no data label is expected to change? The spice file list is changed, and sometimes a geometry keyword or two. If possible, can this be turned off? It makes checking for changes very tedious. Also, supposedly the same geometry and spice keywords in the FITS headers are not updating their information as is done with the PDS label. This means that there information in one place that is not the same in the other. It is probably best to have the PDS label likewise not update. I will also note that not every data set has this happen upon redelivery. For instance the delivery that went to the external peer review and the delivery immediately before it, had ALICE, LEISA, LORRI, MVIC, and REX were affected. Example: =================== diff -rw 2020-04-24/nh-a-alice-3-kem1-v3.0/data/20181230_040851/ali_0408519517_0x4b6_sci.lbl 2020-05-05/nh-a-alice-3-kem1-v3.0/data/20181230_040851/ali_0408519517_0x4b6_sci.lbl 237c237 < , "new_horizons_2128.tsc" --- > , "new_horizons_2149.tsc" 296,297c296,297 < , "merged_nhpc_2018_v099.bc" < , "merged_nhpc_2019_v016.bc" --- > , "merged_nhpc_2018_v100.bc" > , "merged_nhpc_2019_v018.bc" 300c300,302 < , "merged_nhpc_2020_03_v002.bc" --- > , "merged_nhpc_2020_03_v004.bc" > , "merged_nhpc_2020_04_v002.bc" > , "nhpc_2020_122_01.bc" =================== file: 'catalog/dataset.cat' --> DATA_SET_DESC: For the version history, is the only major change really the inclusion of additional data? Are there any other changes, like new extensions, re-calibrated images, etc? For PEPSSI and SWAP it does not mention the splitting of data files that were discovered before the peer review. To a user expecting the data to be unchanged, it would be worth noting so they are not mislead. --> TF: typo (see lorri_mvic_Farnham.pdf slide 5 and 12) that affects all data sets --> --> The text "in at" in the text "occurred in at the ends of 12/2009, ..." file: 'catalog/nh_kem.cat' --> There is at least one “TBD” in the mission catalog file. Please update. See swap_Frahm.pdf slide 7. file: 'catalog/nhsc.cat' --> The spacecraft catalog file has not been updated for the extended mission target. See swap_Frahm.pdf slide 9 for suggested wording and description. Suggest in the Payload section replacing "The payload comprises seven instruments:" with "The instrumentation chosen for the payload is adequate to observe and return new information on a multitude of additional objects in the solar system for which the New Horizons spacecraft will encounter, but were mainly chosen to highlight measurements at Pluto. The seven instruments which comprises the scientific payload, highlighting measurement capabilities at Pluto, are:" file: 'voldesc.cat' --> ZX: Note that the data set version number is listed alongside the phase name. Please correct. Found in DESCRIPTION in two places. See mvic_ZouXD.pptx slide 5 for details. =============================================== Additional Liens for: *ALICE* Certification: Accepted for archiving. [NONE] =============================================== Additional Liens for: *LEISA* Certification: Certified, with minor liens. MS notes that sometimes, due to viewing geometry, the sense of movement of the sky from frame to frame reverses. It’s not clear if this is an inherent issue of pushbroom cameras, or if the typical user should be advised that this reversal exists in the data. AM notes that he only saw the reversal noted by MD in the last two image cubes added since the last review. If feasible, please provide a note regarding the apparent motion reversal during encounter at an appropriate place in the data set documentation. file: 'calib/calinfo.txt' --> MD: typo - "I is the **intergration** time, seconds". See leisa_diSanti.pdf slide 17. directory: 'data/' --> Please investigate the following two issues raised at the end of Adam McKay’s presentation (leisa_McKay.pptx). They don’t seem to be data issues, but they may require some additional explanation or caution for the user (most likely in the data set catalog file). --> --> AM: lsb_0408619338_0x53c_eng.fit and Isb_0408614341_0x53c_eng.fit look different from others, although clearly contains data. 341 looked normal last time though, 338 looks the same. See slide 4. --> --> AM: Not sure what image in folder 20181231_040859 should be, label file say MU69, but don’t see consistent object present in stack. See slide 5. =============================================== Additional Liens for: *LORRI* Certification: Certified, with minor liens. file: 'catalog/dataset.cat' --> TF: typos (see lorri_mvic_Farnham.pdf slide 5) --> --> Remove comma in text "LORRI did LightCurves, and Imaging." --> --> The text "in at" in the text "occurred in at the ends of 12/2009, ..." file: 'nh-a-lorri-2-kem1-v3.0/data/20180915_039928/lor_0399289948_0x633_eng.lbl' --> EN-RC: The corresponding bytes in the data file (.fit) only has 8 bytes of data, not 20. Suggest to either pad the data file with space or change BYTES = 8 in the labels. =================== - Lines 819+: OBJECT = COLUMN NAME = "ARCHDATE" BYTES = 20 COLUMN_NUMBER = 10 DATA_TYPE = "CHARACTER" START_BYTE = 38 =================== files: 'data/*/*.fit' --> Suggestions to be taken to update/correct FITS headers for future data set version (see lorri_ZouXD.pptx slide 5). Do not update the current K2 data sets. --> --> keyword TRGFOVN = 0 should be 1 for MU69 images. --> --> keyword SCANRATE = -999.0 does not seem correct. =============================================== Additional Liens for: *MVIC* Certification: Certified, with minor liens. file: 'nh-a-mvic-2-kem1-v3.0/data/20190103_040879/mpf_0408793006_0x539_eng.lbl' --> EN-RC: The corresponding bytes in the data file (.fit) only has 8 bytes of data, not 20. Suggest to either pad the data file with space or change BYTES = 8 in the labels. =================== - Lines 819+: OBJECT = COLUMN NAME = "ARCHDATE" BYTES = 20 COLUMN_NUMBER = 10 DATA_TYPE = "CHARACTER" START_BYTE = 38 =================== =============================================== Additional Liens for: *PEPSSI* Certification: Level 2 - Certified; Level 3 - Certification held pending correction of labels. Reviewers are willing to review revised labels, which will be supplied. Note that there are other mission phases of NH data sets posted online and archived that have two serious issues mentioned below. Since PDS4 migration is relatively imminent, an errata file with the PDS3 data is a reasonable way to proceed until the errata can be applied as part of migration. files: 'document/pep_bti.*' --> SJ: Check to see if the file is incomplete. Last entry is 2019-01-09. See pepssi_Joy.pdf slide 9. files: '*-3-*/data/*/*.lbl' --> RF: The EXTENSION_PHA_HIGH_ION_TABLE has an incorrect definition (in at least the S_Incident_Energy column) for sulfur because the description indicates that it is a proton instead of sulfur. See pepssi_Frahm.pdf slide 11. --> --> SJ: For other archived data sets, all files inspected, including KEM, Pluto and plutocruise files have the S_Incident_Energy column described as "Incident Energy if proton(keV)". See pepssi_Joy.pdf slide 16. Should add issue to errata.txt file for these archived pre-KEMENCOUNTER data sets. --> SJ/RF: The PHA_LOW_ION and PHA_HIGH_ION column descriptions need to fixed. Appears to be software failure to automatically populate description. Errors are observed in multiple columns and multiple extension tables. See pepssi_Joy.pdf slide 15 and pepssi_Frahm.pdf slide 12. The error messages in the table column descriptions is a serious issue that needs to be corrected, even though this has managed to pass review unnoticed in the past (these fields are buried deep in the label). Steve searched for this in level 2 data and did not find the problematic descriptions. --> --> SJ: All KEM and Pluto datasets, including those certified and online have the “Auto description failed:” error. The plutocruise data do not have this error because the structure of the PHA_LOW_ION and PHA_HIGH_ION tables were different, and did not contain the columns that now give the errors. See pepssi_Joy.pdf slide 16. Should add issue to errata.txt file for these archived pre-KEMENCOUNTER data sets. =============================================== Additional Liens for: *REX* Certification: Certified, with minor liens. file: 'document/rex_activities_kem1.pdf --> If possible, please update the rex_activities_kem1.pdf to include the 2019-03-21, 2019-04-19, 2019-05-07, and 2019-07-10 radio path characterization activities. (See rex_Buccino.pdf slide 3) file: 'index/checksum.lbl' --> Label has wrong number of ROWS and records. =============================================== Additional Liens for: *SDC* Certification: Certification held pending the essential document updates. These will be reviewed by the reviewers via email when they are available. directory: 'document/' --> AP: In the document/ folder, there are a collection of variously formatted "ON/OFF" timing data files which allow the user to reconstruct hit rates from the data itself; however: current files are only up to around February 2019. Should be updated. See sdc_Poppe.pdf slide 11. --> AP: In the document/ folder, there is a figure ‘nh_pos_vel_angle.png’, which is only current up to ~2017; should be updated. See sdc_Poppe.pdf slide 11. --> AP: In the document/ folder, there is an ‘sdcram.csv’ file which documents the angle between the SDC boresight and NH spacecraZ velocity vectors; however, it is only current up to the end of 2017; does this need to be updated as well? See sdc_Poppe.pdf slide 11. --> Slide 5 of Addie D.’s presentation (sdc_Dove.pdf slide 5) contains a list of various documents which include end dates that vary from the data set and from each other. Please check the documents in this list for updates. (Andrew P. notes that updated versions of these files are needed to use the data.) =============================================== Additional Liens for: *SWAP* Certification: Certification held pending correction of PDF calibration document. This will be handled by email over the next week. Please investigate why the ending time of the level 3 data set is not the same as the ending time of the level 2 data set. The answer should likely be noted in the dataset catalog file for at least one of those data sets. See swap_Frahm.pdf slide 5. file: 'catalog/dataset.cat' --> There is a strange "mission phase*" and "date*" notation in the dataset catalog file that should be replaced with something meaningful. See swap_Frahm.pdf slide 6. files: 'data/*/*.lbl' --> RF: typo in column 83 description. "EEPROM 2" => "EEPROM 1". See swap_Frahm.pdf slide 46. dirctory: 'document/traj/' --> Please confirm or update the SPICE kernels list in the document/traj directory. See swap_Joy.pdf slies 7-8. file: 'document/swap_cal.pdf' --> The document is missing its equations along with other abnormalities (bad text, font type and size changes, etc). Appears to have been affected when the document was converted to PDF/A. See swap_Frahm.pdf slides 11-16. Confirm with reviewers after fixed. PDS-SBN can assist with converting the document.