Sprint 029 agenda - Septembert 21, 2023

• Strategy check in (to be completed by product owner prior to meeting)
  • Look in on recent issue activity
  • look over the epic list and the road map to make sure we are still happy with the big picture
  • Add last minute issues to epics
• Sprint review
• Sprint retrospective
  • Screenshot burndown
• Sprint planning:
  • Consult product owner notes below
  • go over the sprint planning dashboard and move tasks into the current sprint board.
    • At Risk Issues
    • Needs attention Issues
    • On track
    • unprioritized The Scrum Master should work with the team to assign a health for these in the coming sprint
  • go around the room and assign tasks
    • Assign ROTA members
    • Does everyone have a task?
    • Does everyone’s hours add up to what is reasonable?
  • choose a scrum master

Personnel

• Product Owner: Chad
• Scrum master: TBD
• Stakeholders?: TBD

Strategy check in and product owner notes (done pre meeting by Chad)

• PO flagged issues

• What is keeping me up at night?

  • status of offline code. The development has been great, but I worry about getting everything merged to master and released quickly so that we can start putting out fully reveiwed results.
  • getting started on injection runs. I realize that we are being held up by this, but I think we need to try whatever we can to anticipate the dev work remaining (if any) and push this through so that we can hit go as soon as possible. I have a strong preference for this to run on the IGWN grid.
  • refiltering - must be settled no later than January
  • GWTC 4
    • I am officially the catalog data project manager. I think we should take control on how to get the ball rolling, e.g., https://ldas-jobs.ligo.caltech.edu/~chad.hanna/gwtc4
  • Virgo integration
    • If the SNR optimizer is our baseline plan, we need to get on that ASAP.
  • Online injection running
    • We need it! And also Rachael needs a one month comparison for her thesis.
  • O4b online: We have to decide what features are going to make it. Here is my take
    • New extinction model - must have, but I don’t think the dev work has started for online, right?
    • Bank Chisq - must have
    • IDQ with Richard’s implementation - must have. Can we target something simple? How about a clean bin and dirty bin where dirty is populated when iDQ has a FAP of XXX
    • What code will we use? Note we need to at least pull in (and test these versions in MDCS???). Note I am thinking of yun-jings interpolator bug fix.
  • CI
    • I have dropped the ball on making sure that we are making progress on big picture CI goals. I would like to start ingegrating Siddharth and Ron into helping to support OSG / IGWN running even more and to harden low latency infrastructure further.
    • We need to get CC* PIs into a permanent situation, i.e., a new headnode.
      • IGC++ onboarding session to singularity and condor on the CC* nodes? here
    • Penn State cluster accounting - we need to make sure we have accurate results in order to ger more computers.
  • Knowledge transfer:
    • We need at least two Divya’s, two Rachaels, and two Beccas. Lets identify those people now and do a systematic knowledge transfe