New Horizons Kuiper Extended Mission 2 (KEM2) K6 Review Hybrid virtual/in-person review Attendees (at start): Ludmilla Kolokova Gerbs Bauer Anne Raugh Brian Enke David Malaspina Joel Parker Mike DiSanti Rudy Frahm Tilden Barnes Brian Keeney Steve Joy Alex Doner Caden Gobat Dennis Bodewits Jamey Szalay Tony Farnham Olga Harrington Pinto Eric Fattig Ben Hirsch New Horizons PEPSSI KEM2 Raw, Calibrated Data Reviewers: Steve Joy, Rudy Frahm Steve's Presentation A quick overview of his review procedure, which has been the same across many reviews of these instruments and involves using beyondcompare to compare old and new versions of the data. Documents PEPSSI_BTI_GoodTimeIntervalsBadTimeIntervals_2022_149.txt described on ICD page 96 is missing. This file (and lbl) should be added to the archive. Liens The PEPSSI chapter of the soc_icd should be updated at some point to more completely describe the operational consequences of the FSW 5 update. There's an author's note that needs to be edited. Joel and Brian: No PEPSSI rep on the phone yet. Anne: I don't know how many reviews we're going to have to nag them to get these missing files supplied (for flight software version updates). Anne: With PEPSSI migration to PDS4, I'd be asking whether it makes sense to divide them up into collections by mission phase, or if it's treated as one massive dataset by user. Steve: One dataset with things that have happened along the way. Joel: We've got Caden online to help with PDS4 migration. Rudy: Want to make the point that some software version updates are relevant only for certain datasets and not across the board. Rudy's Presentation Bad time interval file has been renamed (this is mentioned) and moved to doc directory as pep_bti.tab. There are times in the file that are odd--start and end times that are the same. Should the mission name be New Horizons Kuiper Belt Extended Mission 2? in _calpar.tab. Data quick look spectrograms BOX15 strange value Liens (do not hold up cert) Evalute NULL times in BIT file Update calpar tab files Evaluate Low Ion TOF band for pixel 15 Nothing here is an issue that would confuse users. Tilden: Are you hoping for discussion on the pixel 15 issue? Rudy: I'm looking for the team to come back and say this file is ignored and the values are in the same as in the FITS files or something like that. Or something in the ICD that says ignore this pixel. Anne: What caught my ear is the 8-bit vs 16-bit. If data type is incorrect of unexpected, that would be problematic. Rudy: There's nothing in the ICD or data files that says it's not (an issue?). The values which give 0 for the intensity for the boxes that are every other one have start and stop values that are all the same, so they are intended to be 0. Steve: They did discuss in the flight software update that they were doing things differently across boundaries. Steve: For other boxes, min value is same-ish as max value of previous step. Rudy: ICD says below 20 ns, data not valid. Quick look are not used for science but they are in the same files that are, so changing is problematic. Rudy: That's why my recommendation is to leave alone until next delivery, because the actual data is fine. Certification: Yes New Horizons SWAP KEM2 Raw, Calibrated Data Reviewers: Rudy Frahm, Steve Joy Rudy's Presentation docinfo.txt --> This file has changed from previous versions. Steve: Done with my request. Joel: But we need to document that change. Superseded files are in l2 but not l3 directory. If they contain extra data, why not in l3 also? Brian Enke: docinfo.txt was updated, but change is easy to overlook because it's a /* rather than full list of files. So maybe we can just call attention to that better. Superseded files are all 0x585 files which do not show up in calibrated dataset. They're raw only files Steve's Presentation Documentation - beyondcompare seemed to think some weren't utf-8, but rudy did thorough analysis and they're all fine. Thinks it's just a transmission or decompression issue. Tilden: They're all 7-bit ASCII (so UTF-8 shouldn't be relevant). Certification: Yes New Horizons SDC KEM2 Raw, Calibrated Data Reviewers: Jamey Szalay, David Malaspina Jamey's Presentation Data level 2 is this physical or a data issue for the oscillating temperature issue. Alex Doner: I believe this lines up with the hibernation phase, but I'm going to investigate more thoroughly. Jamey: have you seen SDC temp oscillate like this before? Alex: Never quite this consistently before. Jamey: I think there's a correlation between temperature and counts. Brian: All of these dates are in the kem1 mission phase. When I set up pipeline for kem2, I had to play some games with housekeeping data. So I'm wondering if I didn't get something quite right when I set that up. Volatages have constant values that don't appear to be correct. ex: p2_5_adc_volt Alex: I think the byte-value isn't being converted to the voltage correctly. Rudy: There are temperature oscillations for PEPSSI too. David's Presentation Documentation - Detectors are numbered, but couldn't find documentation about which one is which. So when looking at the actual instrument on NH, can't figure out which is which. - Data flags are not clear. THere are 2 vresions of OK. No data in housekeeping, because it say they have 0 dimensions. Alex: We turn instrument off during thruster firing, so that should be empty. Brian: I'm a little suspicious that we might have missed some housekeeping data. Did you notice any correlation between missing data and MET times in filenames? Around MET 539..., I don't see any HK data in the pipeline prior to that, and that doesn't look right. Wondering if this is a pipeline issue we haven't seen before. Certification: not certified New Horizons LEISA KEM2 Raw, Calibrated Data Reviewers: Mike DiSanti, Olga Harrington Pinto Mike's Presentation No major liens. Requests a keyword in the label files that establishes the "sense" of data cubes--the direction of motion of the target when stepping through lambda. Minor confusion about target vectors in .lbl files, but PDS3 keyword names will not be changed at this point. Olga's Presentation In the aareadme.txt the table of contents is missing “Science Data Content” and “Boilerplate Disclaimer” aareadme.txt does not include Download or Notes folders, but these are PDS internal directories and not part of the archive. In the document folder “seq_leisa_kem2.tab” is empty. Question as to whether it should be, and if so is there an explanation as to why. Typo ‘winow’ – ‘window’; under Frames 1 through N1 in leisa.cat in catalog folder Certification: Yes New Horizons LORRI KEM2 Raw Data Reviewers: Dennis Bodewits, Charles Schambeau Dennis's Presentation Asks if PNG files in document directory need to be converted to PDF. Data Error images have values of -0 when disaplyed in DS9, which shouldn't be possible. Consensus is that this is a DS9 problem rather than a problem with the FITS images themselves (or the labels). Headers are labeled KEM1 but should be KEM2. Discrepancy between TARGET (MU69) and TRGFOVN keyword (0) in FITS header. This is a result of the TARGET being defined as the intent of the observation, but TRGFOVN being a figure calculated from SPICE. Charles's Presentation (cannot attend, Dennis presents in his place) No aareadme.txt backup file found in document directory. Possible discrepancy between SOC ICD page 36, table 9-1 description of FITS file extension and the extensions as read out by astropy. Discrepancy between RA/DEC FITS WCS and values obtained by JPL Horizons. Tony Farnham investigated and determined that the values in the FITS headers are correct. Certification: Yes