New Horizons' Extended Mission December 2020 K3 External Peer review Presentations: https://sbnreview.astro.umd.edu/202012_NH_KEM/notes-presentations/ Liens begin with the initials of the provider(s) of the lien so clarifications can be sought in the presentations if required. =============================================== Datasets Reviewed: NH-A-ALICE-2-KEM1-V4.0 NH-A-ALICE-3-KEM1-V4.0 NH-A-LEISA-2-KEM1-V4.0 NH-A-LEISA-3-KEM1-V4.0 NH-A-LORRI-2-KEM1-V4.0 NH-A-LORRI-3-KEM1-V4.0 NH-A-MVIC-2-KEM1-V4.0 NH-A-MVIC-3-KEM1-V4.0 NH-A-PEPSSI-2-KEM1-V4.0 NH-A-PEPSSI-3-KEM1-V4.0 NH-A-REX-2-KEM1-V3.0 NH-A-REX-3-KEM1-V3.0 NH-A-SDC-2-KEM1-V4.0 NH-A-SDC-3-KEM1-V4.0 NH-A-SWAP-2-KEM1-V4.0 NH-A-SWAP-3-KEM1-V4.0 =============================================== General liens that affect all data sets: files: 'calib/*/*.lbl' --> (XZ) Some files in the calib or doc folder are exactly the same as the previous version. But some PRODUCT_CREATION_TIME in their attached .lbl changed, while some didn’t. Please be consistent. (Example case MVIC but may apply elsewhere). file: 'catalog/nhsc.cat' --> (RF) Missing the ('Oxford') comma after SWRI on line 25. file: 'catalog/nh_kem.cat' --> (TF) In the 'Mission Design' section, please update the tenses to reflect that MU69 event is in the past. --> --> (RF) Note the "will pass" vs "has passed" 2014 MU69 as an example. --> (TF) In the 'KEM 1 Encounter' section, minor typo: 'January 1, 2019 ,'. Please remove the space between 2019 and the comma. --> (TF/AP) In the 'KEM 1 Encounter' section, minor typo: 'zodial' to 'zodiacal'. files: 'document/*.lbl' --> (XZ) Some files in the calib or doc folder are exactly the same as the previous version. But some PRODUCT_CREATION_TIME in their attached .lbl changed, while some didn’t. Please be consistent. (Example case MVIC but may apply elsewhere). file: 'document/nh_mission_trajectory.tab' --> (SJ/SBN-TB) Values at same times differ substantially from those provided in the May 2020 review version of this file. Values begin to differ by small amounts (<1 km) in the first few records and then grow in difference with time. Appears to be a new ephemeris kernel set, but the label does not provide a list of kernels. Everything is likely fine. Strongly suggest including a list of kernels used to produce the file in its label. Note: The SWAP team provided traj_2006_2021_1d.tab files do not have this issue. file: 'document/soc_inst_icd.pdf' --> (PDS-EN) On page 4 (actual page 12), All Level 2 filenames are "the first three letters of the instrument name (i.e. ali, lei, lor, mvi, pep, rex, sdc, or swa)". The LEISA names are "lsb*" not "lei*". The MVIC names are "mc0*", "mc1*" "mc2*", or "mc3*" not "mvi*". --> --> (SBN-TB) This appears to be the case since the beginning of the mission, but should verify in case this was a change mid-mission. We do not want to invalidate the prior mission phases with this change. --> (RF) The title of Section 14.11 "SWAP Publications to Date" should probably be renamed to "SWAP Example publications" since there have been no updates since 2013. --> (RF) On page 94, there is a duplicate word: "such such" => "such" --> (RF) On page 106, there is an unnecessary word: "we found that we neglecting". Remove the second 'we'. =============================================== Additional liens for: *ALICE* Certification Status: Certified, with minor liens. [NONE] =============================================== Additional liens for: *LEISA* Certification Status: Not Certified, requires delta review. file: 'catalog/catinfo.txt' --> (SJ) Update web address to use "https" instead of "http"." This was done for all other instruments. file: 'catalog/dataset.cat' --> (SBN-TB) Two raw files were dropped since the prior L2 (v3.0) data set. Team has said they "are not helpful and will not produce calibrated files because they are inherently different than our regular data." A note should be added to the dataset catalog file in version history. Something like removed all raw files that could not be calibrated for XYZ reason. files: 'data/*/*.fit' --> (PDS-SBN) A PDS user has brought it to our attention that the LEISA data have problems with their quaternion extension (extension 7 in the FITS files). All of the Z components have values of zero, even when the .lbl files and FITS header keywords suggest that the Z components are non-zero. It is unfortunate that this problem was not caught in the past, as it applies to all LEISA data sets, going back to launch. --> (PDS-SBN) The quaternion extension (fits extension 7) object is defined as an image but should described as a table and table might be a better format to consider. The same use of image object vs. table object format applies for the housekeeping data in extension 8. PDS-SBN requires that at minimum the PDS label is fixed to describe this object as a table instead of an image, but for the FITS users it would also be best to fix the FITS header (and extension) to make it a table. PDS-SBN can assist with sorting this out. --> (MD) Arrokoth is clearly detected from 3.06e5 km inward, but files from 4.10e5 and 1.21e6 km contain all zeroes. This should be investigated and confirmed to be correct or not. --> (MD/AM) MU69 scan direction is "upward" for d = 1.04e5 km and larger. In each case it was ~1 row per step in l. But it’s still downward for 6.55e4 and 3.12e4 km. Please check. Is there a flag for this? --> (AM) For image '20190905_042999/lsb_0429990719_0x53c_eng.*', the target is listed as SUN. Is this correct? Other information in the label file suggests this is a flat using the Sun as a target. Please verify this is correct. Of note, the other image in this folder has image name 'dark', which makes sense based on the appearance. =============================================== Additional liens for: *LORRI* Certification Status: Certified, with minor liens. files: 'data/*/*.fit' (Postponed K2 LIEN + history) --> 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. --> --> --> JAR: We will look into the Target in FOV and ScanRate to see how the code determines these values. We will try to fix for future versions. --> --> --> SBN-TB: Sounds good. --> --> --> SBN-TB: Looking at the example from the previous lien, I see that the TRGFOVN was changed, but the SCANRATE was not. Should it have? --> --> --> JAR: The SCANRATE is not calculated as a part of the LORRI pipeline. --> --> --> TB: Then is this keyword not applicable or could be but was never calculated. I ask because we would not want to mislead users in thinking there is no SCANRATE, when in fact it was just not calculated and that is why the -999.0 value was present. (CAN WAIT TO RESOLVE POST REVIEW if only need to document) file: 'document/lorri_exposure_offset_pds_v3.lbl' --> (PDS-EN) DOCUMENT_TOPIC_TYPE = "Duration of Image collection" should be all caps. Please replace by DOCUMENT_TOPIC_TYPE = "DURATION OF IMAGE COLLECTION". =============================================== Additional liens for: *MVIC* Certification Status: Certified, with minor liens. file: 'catalog/dataset.cat' --> (TF) DATA_SET_DESC: In the 'Version' section, third paragraph, the last sentence lists the types of tests and observations done (Ring/Coma Search, Look Back at Pluto, etc). This sentence is very awkward. Suggest prefacing it with "A number of [tests, scans, ??] were conducted, including ..." =============================================== Additional liens for: *PEPSSI* Certification Status: Certified, with minor liens. Comment: (SJ) Neither the DS.CATs nor the labels for the Jan 1, 2019 file list MU69 (Arrokoth) as a TARGET (TARGET = “SOLAR WIND”). It’s mentioned in the dataset description of the DS.CAT but wouldn’t show up in a search for data associated with this target. --> (SBN-TB) Should this be the case? file: 'catalog/pepssi.cat' --> (RF) Under the section: Data sampling and priority for TOF-only data (lines 247-250), "the N3 PHA data uses a different priority scheme than the N2 PHA data (this may be changed in a future software update, but that hasn't happened of June, 2016)." What about this data set? Since the instrument commanding for v4.0 has already occurred, the instrument team should already know if they have changed the priority scheme. =============================================== Additional liens for: *REX* Certification Status: Certified, with minor liens. file: 'catalog/dataset.cat' --> (AR/PDS-SBN) Add note about the limitations of the data set, and why (since the reference TNF files may not be available) directory: 'data/tnf' --> (AR) I found that some files contain 3-way Doppler data, but the corresponding uplink ramp frequencies were missing for the transmitting stations. If possible please provide or complete the missing TRK-2-34 data. --> (AR) Missing many TRK-2-23 files necessary to analyze much of the data. --> --> (PDS-SBN) Please attempt to get the missing data from the DSN to include in the data sets if at all possible. files: 'data/tnf/*.lbl' --> (PDS-EN) These labels are missing SPACECRAFT_CLOCK_START_COUNT and SPACECRAFT_CLOCK_STOP_COUNT and should have MISSION_PHASE_NAME. Suggest adding the keywords to the labels. --> --> (SBN-TB) If these keywords are not applicable and are added, please set the value to "N/A". --> (AR) The DSN_STATION_NUMBER keyword is missing in the labels. Please add. --> (AR) The start and stop times indicated in the PDS3 labels appears incorrect. See slide 5 table for examples. files: 'document/tnfsis.*' --> (AV) The version of the reference document is not the right one for this archive. The latest version (DSN No. 820-013, TRK-2-34, Rev. P, 2017) is more relevant to this archive and should be included in its place. file: 'document/rex_activities_kem1.pdf' --> (DB) Mix up of dates vs DOY. Details: ------------- On page 2 and 3 the document states there was radio path characterization on: * 08/01/2019, however, the apparent date is 08/08/2019 (DOY 220) * 10/03/2019, however, the apparent date is 10/19/2019 (DOY 292) * 10/24/2019, however, the apparent date is 11/14/2019 (DOY 318) * 12/05/2019, however, the apparent date is 12/21/2019 (DOY 355) * 01/06/2020, however, the apparent date is 01/09/2020 (DOY 009) * 02/10/2020, however, the apparent date is 02/11/2020 (DOY 042) * 03/02/2020, however, the apparent date is 03/10/2020 (DOY 070) On page 3 it states there was calibration campaign on 08/22/2019, however, the apparent date is 09/04/2019 (DOY 247). This calibration campaign includes a radio path characterization on 09/09/2019 (DOY 252) which should also be stated in the header ------------- =============================================== Additional liens for: *SDC* Certification Status: Certified, with minor liens. file: 'catalog/dataset.cat' --> (SBN-TB) The 'data/20190101_040864/' directory was dropped since the last data set version (v3.0). The team reported "all data in this file is duplicated in 20190106_041033\sdc_0410334728_0x700_sci.fit". We should add a similar statement to dataset.cat file version history as was done for PEPSSI (updated to apply to SDC's particular situation): "Also note that file names may change between versions if start/stop times are updated when additional data are downlinked." file: 'document/sdc_stim_v0003.tab' --> (AP) This file was last updated 2019-04-20. Please double-check if this is fully up to date for this release. files: 'document/sdc_*.tab' --> (AD) These files have varying end dates. Please verify that we have the most current versions. =============================================== Additional liens for: *SWAP* Certification Status: Certified, with minor liens. Comment: (SJ) Neither the DS.CATs nor the labels for the Jan 1, 2019 file list MU69 (Arrokoth) as a TARGET (TARGET = “SOLAR WIND”). It’s mentioned in the dataset description of the DS.CAT but wouldn’t show up in a search for data associated with this target. --> (SBN-TB) Should this be the case? files: 'document/data_summary_plots/*' --> (RF slide 38) Ex: 'swap_001day_201903102359.png' looks like the plotting package software failed where you really want to convey that there is no data for the time frame covered by the plot. Empty plot frames with the words “no data” are much better because you see right away that the reason for the empty frame is that there was no data to plot and it was not due to a failure in the plotting software. files: 'document/traj/*' --> (SJ) no BC after 2019, etc. Please verify that this is a labelling error and that the correct kernels were used to generate the data file (don’t match the set in the SWAP data file labels).