Sprint 010 agenda - April 5, 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 009 review
- check out the sprint management dashboard and go over issues that were closed
Sprint 009 retrospective
- Screenshot burndown
- go over the burndowns
- check out the sprint management dashboard and go over issues that were not closed
Sprint 010 planning:
- Consult product owner notes below
- go over the sprint planning dashboard and move tasks into the sprint 009 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 Hanna
Scrum master: TBD
Stakeholders?: TBD

Minutes

Attendance

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

These are things that I feel like are looming over us but very close to resolving

Online MDC - things to be fixed/changed for MDC12
- Pastro - is that now solved? Victoria’s recent plots seem to look pretty good. We need just a couple more definititve statements on this and we should try to wrap this up this sprint
- I think it is time to start building more QoL tools and services for our observation run, e.g., additional diagnostic plots such as
  - dt dphi LR terms
  - custom event pages showing details about the state of the analysis around events
  - ability to run code to follow up events in case e.g., an analysis was down etc
Online real data
- A discovery is possible and we want to be ready
- Did we restart with the fix to PSD message and reburn in? I am worried that or LR distribution was too wonky and the hypothesis was horizon history. We need to sort that out.
- Be ready to upload to gracedb and to setup alerts if possible
Code versions
- Is it time to start working towards a release and plan for how we do O4 code updates and management (online primarily)
Offline analysis
- We need to close the loop on R&P injections plan, things are looking good there though!
- We need to close the loop on online rerank but things are looking good there too
- Offline workflow rework: going through a small bns test recently has solidified my optinion that our current workflow tries to automate too much and we are constantly hacking around it. I would like to see continued pushing towards modular bits that are well polished and can be combined together to solve a particular problem. Some of this work has already begun, but I think that we still need to discuss it further, but off the top of my head we need
  - A svd bank dag that is robust (I think this exists)
  - an injection file making dag that is robust*
  - an injection frame generation dag that is robust*
  - (* R&P will do this for us, but we still need to be able to do it ourselves)
  - a PSD measuring dag that is robust
  - a filtering only dag that is robust
  - an injection filtering only dag that is robust
  - a rank (rerank) dag that is robust
- The filtering dags should be written to scale on the OSG and support
  - One SVD bank per job processing more time
  - We need to check that the clustering built into gstlal inspiral is “good enough” to produce small files for the rerank (it seems to be true online)
Calibration monitoring
- It seems we have no choice but to get things working in Conda igwn
Online.ligo.org
- We need to put on a good showing here when meeting with David and Peter, you only have one chance at a good first impression.
Papers
- Performance
- Count tracker
- LR
CC* compute for the PIs and tracking our OSG contributions.

ISSUES OF NOTE

Perhaps things that need issues?

Performance paper