Page History

...

• • • 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-42606

      • Jira
        server Jira Cloud serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-43160

      • Jira
        server Jira Cloud serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-42920

        I misrepresented this at the last meeting, apCorr already HAS a 10 minute heartbeat. It just prints out nonsense numbers.

      • 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-43256

        This has been reviewed and is almost ready to merge, and then we can start having daily / monthly metrics
      • https://rubinobs.atlassian.net/issues/

        Jira
        server Jira Cloud serverId 6dd774b6-00ac-3344-8265-fe491188c468 key

        DM-43357

        multiprofit PSF fitting seems much slower than meas_modelfit; still investigating.
      • New set of errors from calibrateImage.  Maybe no further actions are needed?

        Jira
        server Jira Cloud serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-43248

        Jira
        server Jira Cloud serverId 6dd774b6-00ac-3344-8265-fe491188c468 key DM-43306

    • 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

      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-43179

      Need to check that the psf matching kernel correctly uses spatial variation

...