February 2020 New Horizons Review ================================= LEISA KEM1 v2.0 Liens ===================== Reviewers: Mike DiSanti, Adam McKay =================================== DATA --> While Vega scan direction is as expected (target moved upward through lambda), MU69 scan direction is reversed (target moved downward through lambda). Is this due to S/C roll? Is there a key word indicator in the .lbl file? --> Both Vega and MU69 data show some "wobble" in the x-direction, more so for Vega, less so for MU69. Difficult to extract Vega spectrum, due to spatial smearing. Will be less important for MU69, especially toward closest flyby approach of ~3500 km. Owing to the reversal in scan direction for MU69, the algorithm to register MU69 data toward closest approach needs revision. Certainly feasible though as downward drift rate appears constant, as expected. --> lbl files says images are 16-bit, but actual values max out at 12 bits. Please add a note explaining why this is the case. file: lsb_0408619338_0x53c_eng/sci.fit --> Looks different from others, although it clearly contains data. All values outside of the scan region are 0. Richard Chen Engineering Review =============================== nh-a-leisa-*/data/*.lbl - Please provide target.cat files for TARGET_NAME = "2014 OS393" TARGET_NAME = "2014 PN70" nh-a-leisa-*/document/soc_inst_icd.pdf - Page 29: Extension 5 - Error estimates for each pixel 256 X 256 X 1 floating point array Extension 6 - Data quality flags for each pixel 256 X 256 X 1 floating point array In the .fit file (and .lbl) I spot checked (lsb_0408614341_0x53c_sci.fit), the 3rd dimension is 285 (i.e. N), not 1. Certification: Certified