11:00 Eastern; 08:00 Project/Pacific Time. bluejeans.com/426716450

Attendees

Notes

  • Airmass...?

Christopher Waters

  • Working on linearity
    • Filed an RFC (RFC-665).
    • Only one comment so far.
  • Would like to move as much ISR-relevant code as possible to ip_isr; cp_pipe should depend on ip_isr rather than the other way around.
    • Also perhaps moving defects from meas_algorithms; not sure how much disruption that would cause.
  • Thinking about ci_cpp.
    • Would have a separate versions for Gen 2 and Gen 3, and a per-camera data repository (initially LATISS).
    • Merlin refers to ci_ctio — can we use ci_cpp to check ingest, etc, as well as task functionality?
    • We discussed what the structure of this would be like — e.g.
      • Should it be ci_cpp, or ci_latiss? Why isn't it parallel to ci_hsc?
      • Could we do something to make writing unit tests in cp_pipe?
    • Many possible considerations here, but we'd like Chris to have chance to think about it then make fast progress!

Andrés Alejandro Plazas Malagón

  • Still waiting for a response from John P. on DM-19903.
  • Working on defects on DM-21720, blocked by DM-23282, which we'll ask Kian-Tat Lim  to prioritize.
  • DM-21221 needs to be marked as done, because it is.
  • Started looking at DM-20070; previously agreed that this isn't the highest priority, but is blocked on other tickets.
  • Top priority is to fix emergent issues identified by Merlin Fisher-Levine where possible. We're going to hear about them next...

Merlin Fisher-Levine

  • Filed a couple of tickets:
    • Top priority: DM-23238 (per-row overscan removal).
    • Multiple header problems; so far, Architecture has been responsive in addressing them.
  • Lots of discussion about the support / release model for software on the mountain.
    • We should be careful when discussing this to differentiate between the control code, the ingest code, and the analysis code, as they should each have different levels of calcification wrt version control/rigorousness of checking.
  • Actively working on Spectractor with Jeremy before he goes on holiday at ~the end of this week.
    • He is currently very engaged.
    • Merlin providing shims to enable Jeremy to run LATISS images through Spectractor.
    • Have managed to drive Spectactor based on LATISS data is Spectractor native command line mode; Merlin still working on stack engineering.
  • Suggested adding an auxtel-critical label to issues that are blocking progress on AuxTel.
  • Some discussion of git logistics.