Attendees:

Notes:

  • Merlin Fisher-Levine 
    • SAWG work.
    • Calibration-y thing that's relevant:
    • Patrick has asked for sequencer changes.
    • Summit is down, and there's a Chilean holiday.
    • Star tracker telescope is coming.
      • CMOS camera with some kind of three kinds of lenses.
      • Tested in Chuck's garden.
      • On the side of the TMA.
      • Defining telescope pointing for ComCam.
      • Seems to be working in testing as long as it is pointing up.
      • Using astrometry.net to find the solver.
    • Tickets review.
    • Rubin Env 5 is coming, but no one knows the timing, dependent on K-T.
      • Bug stopping Silvie's work.
      • RSP containers not necessarily updated to get needed code in place.
  • Andrés Alejandro Plazas Malagón 
    • Writing alarm code for Watcher, into review this week.
      • Currently set to "Serious."
    • Explaining to Patrick what the verification failure means.
    • Improve documentation of the OCPS calibration scripting.
      • Tracking down runtime errors.
      • Updating the needed configuration to reduce user work.
      • Database migration will solve external failure.
    • Make sure that the observers are running things.
      • Failure when data is taken and things fail, can we resume from the existing data.
  • Christopher Waters 
    • TTS does not have calibration files.
    • Transmission curve work.
    • Documentation of ip_isr
    • Adam Snyder crosstalk exists.
    • BOT calibrations are certified.
    • Talk with Tim about DM-36284.
    • New sequencer calibrations once Telescope is up/Latiss.
  • Robert Lupton 
    • Only here this week.
    • Working on getting CAB.
    • Summit support on a holiday.
  • Eli Rykoff 
    • Switching from Pandas to PyArrow.
      • Do not use DataFrame storage class.
    • Transmission curve work.
      • Adding system_transmission handling to ISR.
      • Needs to find grizy DECam data to put in as testdata.
        • Contact Mario.
    • DECal exists, but isn't necessarily usable and adaptable for our calibration.
      • Take the method, and implement that rather than using unknown code.
    • Rolling cadence impact on global calibration.
      • At least the first two years are "less rolling," so that should yield a decent amount of data for calibrations.
      • Except we may be making coadds as well as alerts, which might lead to a rolling method.
      • Need to keep an eye on what the strategy.
      • Neighboring band data will be taken ~30 minutes after the initial.
        • Which will correlate the calibrations.