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

Calculate the PSF for DCR coadds

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: pipe_tasks
    • Labels:
      None
    • Story Points:
      10
    • Epic Link:
    • Sprint:
      AP S19-6
    • Team:
      Alert Production

      Description

      Following the pattern already established for standard coadds.

        Attachments

          Issue Links

            Activity

            Hide
            sullivan Ian Sullivan added a comment - - edited

            The pull request is in pipe_tasks, though it may not automatically show up.

            These changes add two ways of calculating a better PSF for DcrCoadds: the first is always done, and simply restricts the input PSFs from the calexps to those with the smallest size. The second change takes more time, and so I made it optional. It runs proper source detection and measurement on the final stacked coadd, selects stars, and measures the PSF. Compared to everything else, that doesn't add THAT much time, so I turned it on by default. I could also just remove the option, and have it always run.

            Show
            sullivan Ian Sullivan added a comment - - edited The pull request is in pipe_tasks , though it may not automatically show up. These changes add two ways of calculating a better PSF for DcrCoadds: the first is always done, and simply restricts the input PSFs from the calexps to those with the smallest size. The second change takes more time, and so I made it optional. It runs proper source detection and measurement on the final stacked coadd, selects stars, and measures the PSF. Compared to everything else, that doesn't add THAT much time, so I turned it on by default. I could also just remove the option, and have it always run.
            Hide
            Parejkoj John Parejko added a comment -

            Thanks for the cleanups. I'll let the log.info thing go for now, but please file a ticket about exploring options for where to put that information that isn't in the log, since it's useful numeric info that is hard to extract from a log. I could see some kind of database (sqlite?) in the gen3 butler land that gets populated with weights, airmasses, angles, etc. per visit.

            Show
            Parejkoj John Parejko added a comment - Thanks for the cleanups. I'll let the log.info thing go for now, but please file a ticket about exploring options for where to put that information that isn't in the log, since it's useful numeric info that is hard to extract from a log. I could see some kind of database (sqlite?) in the gen3 butler land that gets populated with weights, airmasses, angles, etc. per visit.

              People

              • Assignee:
                sullivan Ian Sullivan
                Reporter:
                swinbank John Swinbank
                Reviewers:
                John Parejko
                Watchers:
                Eric Bellm, Ian Sullivan, John Parejko, John Swinbank
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel