Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-18387

Write a task to make a visit->coadd match table

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Story Points:
      3
    • Epic Link:
    • Team:
      Data Release Production

      Description

      The QA dashboard project will require some way to look up information on source matching between visits and coadds. As Lauren MacArthur and Yusra AlSayyad and I discussed a few weeks ago, one simple way to do this would be to write a match table that persists this information. This table would be per-tract, and indexed by coadd ID, contain a column for each visit, the contents of which would be the best match ID (if exists) from the corresponding visit table.

      The actual matching algorithm can be improved in the future; for now, I will implement what I was doing before when I was making MatchedCatalog objects for the visit-level notebook visualization stuff I was previously working on.

        Attachments

          Issue Links

            Activity

            Hide
            cmorrison Chris Morrison added a comment -

            See review on Github.

            Show
            cmorrison Chris Morrison added a comment - See review on Github.

              People

              • Assignee:
                tmorton Tim Morton
                Reporter:
                tmorton Tim Morton
                Reviewers:
                Chris Morrison
                Watchers:
                Chris Morrison, John Swinbank, Tim Morton, Yusra AlSayyad
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: