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

Document/propose how difference image photometry would be tied together across transitions between templates

    Details

    • Team:
      DM Science

      Description

      The present plan for difference imaging is to use roughly annual templates. With the plan for re-computing difference-imaging data products in Data Releases, we should understand how we will support users who wish to stitch together a full multi-year relative-photometry light curve from the results.

      There are a range of possibilities of levels of hand-holding that we might provide. The answer affects whether properly "stitched" light curves would be available, e.g., through a TAP service and/or the Portal, or only as a user-derived data product in the Notebook Aspect requiring the user to perform the cross-normalization themselves based on some auxiliary zero-point information provided.

      A closely related issue applies, perhaps with modest additional complications, for joining Data Release difference imaging photometry to the "live" Prompt DIASource records.

        Attachments

          Activity

          gpdf Gregory Dubois-Felsmann created issue -
          gpdf Gregory Dubois-Felsmann made changes -
          Field Original Value New Value
          Risk Score 0
          Hide
          gpdf Gregory Dubois-Felsmann added a comment -

          Somewhat related to this ticket (and perhaps worthy of a separate ticket), there are various gaps of data which we will not automatically provide in pre-computed tables, such as “conventional” forced photometry for known (from the last DR) Objects for recent, post-DR, epochs, and difference-f.p. for all epochs for all Objects. Which part of that space will we cover with fully pre-written, turn-key, tools available to our users, and what will those tools be? Fully configured PipelineTask-based pipelines that need only be launched on a list of input objects/sources/coordinates and can be run at large scale using our workflow tools? Internet-accessible Web APIs? Point-and-click screens in the Portal? Or will we just provide "do it yourself" instructions for how to assemble the right Tasks to do the job?

          Show
          gpdf Gregory Dubois-Felsmann added a comment - Somewhat related to this ticket (and perhaps worthy of a separate ticket), there are various gaps of data which we will not automatically provide in pre-computed tables, such as “conventional” forced photometry for known (from the last DR) Objects for recent, post-DR, epochs, and difference-f.p. for all epochs for all Objects. Which part of that space will we cover with fully pre-written, turn-key, tools available to our users, and what will those tools be? Fully configured PipelineTask-based pipelines that need only be launched on a list of input objects/sources/coordinates and can be run at large scale using our workflow tools? Internet-accessible Web APIs? Point-and-click screens in the Portal? Or will we just provide "do it yourself" instructions for how to assemble the right Tasks to do the job?

            People

            • Assignee:
              ctslater Colin Slater
              Reporter:
              gpdf Gregory Dubois-Felsmann
              Watchers:
              Eric Bellm, Gregory Dubois-Felsmann, Leanne Guy
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Summary Panel