Uploaded image for project: 'Request For Comments'
  1. Request For Comments
  2. RFC-709

Modify requirements on coadds in LSE-61 to bring in line with DRP plans and DPDD

    XMLWordPrintable

    Details

    • Type: RFC
    • Status: Implemented
    • Resolution: Done
    • Component/s: DM
    • Labels:

      Description

      DRP plans for archiving and serving coadds to users have changed. Only per-band deep coadds will be archived. All other flavours of coadds, if generated by DM, will not be archived, rather, DM will provide the software, metadata and provenance information necessary for end users to generate them on demand

      The DPDD is being updated to bring it in line with these plans in DM-23248. The following specific changes are also needed to the DMSR:

      ------------------------------
      1.4.1 Persisting Data Products
      ID: DMS-REQ-0334 (Priority: 1b)

      Specification: All per-band deep coadds and best seeing coadds shall be kept indefinitely and made available to users.

      Discussion: This requirement is intended to list all the data products that must be archived rather than regenerated on demand. DMS-REQ-0069 indicates in discussion that Processed Visit Images are not archived. DMS-REQ-0010 indicates in the discussion that Difference Exposures are not archived.

      Change to

      ID: DMS-REQ-0334 (Priority: 1b)

      Specification: All per-band deep coadds shall be kept indefinitely and made available to users.

      Discussion: This requirement is intended to list all the data products that must be archived rather than regenerated on demand. DMS-REQ-0069 indicates in discussion that Processed Visit Images are not archived. DMS-REQ-0010 indicates in the discussion that Difference Exposures are not archived.

      ----------------------------
      1.4.7 Multi-band Coadds

      ID: DMS-REQ-0281 (Priority: 1b)

      Specification: The DMS shall periodically create Multi-band Coadd images which are constructed similarly to Deep Detection Coadds, but where all passbands are combined.

      Discussion: The multi-color Coadds are intended for very deep detection.

      Change to

      ID: DMS-REQ-0281 (Priority: 1b)

      Specification: The DMS shall periodically create Multi-band Coadd images which are constructed similarly to Deep Detection Coadds, but where all passbands are combined. These Coadds will not be archived.

      Discussion: The multi-color Coadds are intended for very deep detection. DM will provide software, metadata and provenance information sufficient to allow these coadds to be recreated on-demand by end-users.

      --------------------------------
      1.4.8 Best Seeing Coadds
      ID: DMS-REQ-0330 (Priority: 2)

      Specification: Best seeing coadds shall be made for each band (including multi-color).

      Discussion: DMS-REQ-0279 states that seeing-based co-adds should be possible. This requirement states that they shall be made.

      Change to

      ID: DMS-REQ-0330 (Priority: 2)

      Specification: Best seeing coadds shall be made for each band (including multi-color). These Coadds will not be archived.

      Discussion: DMS-REQ-0279 states that seeing-based co-adds should be possible. DM will provide the software, metadata and provenance information necessary to allow these coadds to be recreated on-demand by end-users.
      -------------

      1.4.9 PSF-Matched Coadds
      ID: DMS-REQ-0335 (Priority: 1b)

      Specification: One (ugrizy plus multi-band) set of PSF-matched coadds shall be made but shall not be archived.

      Discussion: These are used to measure colors and shapes of objects at "standard" seeing. Sufficient provenance information will be made available to allow these coadds to be recreated by Level 3 users.

      Change to

      ID: DMS-REQ-0335 (Priority: 1b)
      Specification: One (ugrizy plus multi-band) set of PSF-matched coadds shall be made but shall not be archived.

      Discussion: These are used to measure colors and shapes of objects at "standard" seeing. DM will provide software, metadata and provenance information sufficient to allow these coadds to be recreated on-demand by end-users.

        Attachments

          Issue Links

            Activity

            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            Leanne Guy asked me to update the original requirements changes for consistency with the modifications to flowdown and the reorganization of the data-archiving requirements.

            The updated proposal is attached as RFC-709_recommendations-v2.txt.

            Note that I have kept the "shall create" / "shall be made" forms originally proposed above, rather than John Swinbank's alternative of "shall be capable of making".  I am not sure that this question was closed one way or the other above; I invite John and Leanne Guy, and others, to come to a final conclusion.

            Show
            gpdf Gregory Dubois-Felsmann added a comment - Leanne Guy asked me to update the original requirements changes for consistency with the modifications to flowdown and the reorganization of the data-archiving requirements. The updated proposal is attached as  RFC-709_recommendations-v2.txt . Note that I have kept the "shall create" / "shall be made" forms originally proposed above, rather than John Swinbank 's alternative of "shall be capable of making".  I am not sure that this question was closed one way or the other above; I invite John and Leanne Guy , and others, to come to a final conclusion.
            Hide
            lguy Leanne Guy added a comment -

            Thanks Gregory Dubois-Felsmann for the very comprehensive updates. I think this takes into account all the issues raised on this RFC and presents a good restructuring and clarification of the requirements on data archiving. This is good to go.

            Show
            lguy Leanne Guy added a comment - Thanks Gregory Dubois-Felsmann for the very comprehensive updates. I think this takes into account all the issues raised on this RFC and presents a good restructuring and clarification of the requirements on data archiving. This is good to go.
            Hide
            lguy Leanne Guy added a comment - - edited

            Some copy paste errors fixed in RFC-709_recommendations-v3.txt

            Show
            lguy Leanne Guy added a comment - - edited Some copy paste errors fixed in RFC-709_recommendations-v3.txt
            Hide
            tjenness Tim Jenness added a comment -

            This LCR has been approved so the implementation can be finalized.

            Show
            tjenness Tim Jenness added a comment - This LCR has been approved so the implementation can be finalized.
            Hide
            tjenness Tim Jenness added a comment -

            Change Request (2543) - (Modify LSE-61 Coadds Requirements to Align with DPDD
            + DRP Plans) has been fully implemented. Please notify all relevant team
            members. For more information about the change request, please visit
            (https://project.lsst.org/groups/ccb/node/4418).

            Show
            tjenness Tim Jenness added a comment - Change Request (2543) - (Modify LSE-61 Coadds Requirements to Align with DPDD + DRP Plans) has been fully implemented. Please notify all relevant team members. For more information about the change request, please visit ( https://project.lsst.org/groups/ccb/node/4418 ).

              People

              Assignee:
              lguy Leanne Guy
              Reporter:
              lguy Leanne Guy
              Watchers:
              Colin Slater, Gregory Dubois-Felsmann, Jim Bosch, Leanne Guy, Tim Jenness, Zeljko Ivezic
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Planned End: