Sprint 002 agenda - February 1, 2023

Personnel

  • Product Owner: Chad Hanna
  • Scrum master: Rachael Huxford
  • Stakeholders?: TBD

Minutes

Attendance

Victoria, Yun-Jing, Becca, Rachael, Leo, Shio, Shomik, Alex, Ron, Cort, Chad, Divya, Mahsa

Strategy check in (done pre meeting by Chad)
  • There are three new weight 100 issues
  • There is one new weight 30 issue; these should be discussed at the sprint meeting
  • The audited epics look good. Thank you everyone for contributing to it.
Notes from the product owner

I am increasingly worried that we need more focus on ops and less on dev from the whole team. I would like to see the following:

  • Emphasis put on operational review. Does the analysis work, can it be reproduced easily?
  • Emphasis put on quality of life during operations. Do we have the monitoring we need and the follow-up tools we need?
  • Development should only go to support of the above 2 at this point (for online, offline is a different story). For example, LR development needs to focus purely on retractions, etc. Things that we simply cannot have broken
  • We need to start analyzing real data ASAP to find all of the things we missed
  • We need to make sure the LVK is well aware of our work
    • Get online.ligo.org working, Make it a replacement for gwistat
    • Get the test suite being the de facto trusted result for quality of service
Decisions and conclusions

  • NOTE: please put discussion and comments in the comments rather than description in tasks

  • NOTE: assign status closed for tasks when done, use weights for tasks; don’t use labels.

  • NOTE: closing an issue does not close all sub tasks! You must close subtasks first!

  • NOTE: Avoid using tasks to hold information beyond title and weight

  • ACTION: replace pycbc condition strain with gstlal - related to victoria work on injection file format

  • NOTE: lets go sprint review by issue rather than person

  • NOTE: new issues should get weights based on authors opinion about how many hours something takes, but we can change them during sprint planning

  • ACTION: put workflow back as a section in the doc.

  • NOTE: Scrumaster should encourage people to put their progress in git issues and to prepare summary for review. They should also encourage new issues.

  • NOTE: on memory: recompile containers just to be safe?

  • NOTE: Move Operational review to the review project?

General meeting discussion

  • Leo says that there are some LR tasks in good shape that could be wrapped up (so we shouldn’t necessarily drop them) e.g., the bankchisq + chisq. Leo can maybe help?

  • Shio can help with the LR term that is causing the retractions. Leo will work with Shio, Shomik and others to get retractions understood further. Singles penalty can at least address two retractions. I think we need to up it or turn of singles. We still need to have a plan for the doubles retraction.

  • Shomik: has some questions about how to compare between MDCs to figure out what caused them. Please consider working with shomik to address these

  • Cort: Made progress on getting 6 hour offline analysis working. A few issues are already staged as MRs for tonight. Cort’s 6 hours with small bank started and finished. Has started a full manifold test on 6 hours. If it works, will close issue. Then will run on a full chunk. Divya suggests running on the OSG too.

  • Divya worked on issues and epic auditing. Has a dag to make injection frames, got resources for SSM.

  • Rachael, worked on issues auditing, started some paper repos, completed a few IDQ MRs for grafana and reports

  • Yun-Jing: worked on update to lloid with smaller data buffers, but it is slower.