...
Apologies
- Eric Bellm (Rubin ToO workshop)
- Arun Kannawadi
- Christopher Waters
Agenda
- Announcements:
- Think whether there are any non-quality metrics we you would feel proud of during steady state operations: https://rtn-077.lsst.io
- How did last time go?
- Other than the ComCamSim Pipeline sprint what got done?
Jira server Jira Cloud serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-41929 - Made some backports
Jira server Jira Cloud columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-42088 Jira server Jira Cloud columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-42774 - LATISS Prompt Processing has updated to the default ApPipe of the w_2024_10 stack on Mar 7th, so it has started to use calibrateImage task.
- Not done yet but in review--DM-43083 is adding the option to run maskStreaksTask to detectAndMeasure, so it partially addresses DM-42087 below. A separate ticket will turn of streak masking in characterizeImage and turn it on in detectAndMeasure.
- Lots of StarTracker stuff inc a nice new TMA pointing model
- Standing up Rapid Analysis at USDF, hopefully in time for OR3.
- Many many things happening in parallel, hopefully
- Josh finished
is ready for reviewJira server Jira Cloud serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-41764 - DM-43176 Prompt Processing has switched t
- Other than the ComCamSim Pipeline sprint what got done?
- Announcements:
- What REMAINING emergent issues did we fail to fix or questions we didn't answer?
- There's already a "refcats" run collection The butler on the summit needs some surgery, but it doesn't have to be a Jim Bosch level surgeon:
Jira server Jira Cloud serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-42295 - YA owes Fred a resource usage analysis on
Jira server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-41790 Jira server Jira Cloud serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-42087 Jira server Jira Cloud serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-41764 Jira server Jira Cloud serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-42606 Jira server Jira Cloud serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-43160
I misrepresented this at the last meeting, apCorr already HAS a 10 minute heartbeat. It just prints out nonsense numbers.Jira server Jira Cloud serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-42920
This has been reviewed and is almost ready to merge, and then we can start having daily / monthly metricsJira server Jira Cloud columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-43256
- There's already a "refcats" run collection The butler on the summit needs some surgery, but it doesn't have to be a Jim Bosch level surgeon:
- What NEW emergent issues came up?
- We've gotten some error reports from NAOJ from the ongoing HSC PDR4 processing, but they look like issues we've already fixed and backported at first glance. Trying to confirm the version they're using now.
Jira server Jira Cloud serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-43366
- What REMAINING emergent issues did we fail to fix or questions we didn't answer?
...