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

DMS-REQ-0009 has a dangling reference to -0007.

    Details

    • Team:
      DM Science

      Description

      The current draft (Feb 2017) version of LSE-61 includes, under DMS-REQ-0009, a relationship with DMS-REQ-0007.

      DMS-REQ-0007 is not otherwise mentioned in this document.

        Attachments

          Issue Links

            Activity

            Hide
            tjenness Tim Jenness added a comment -

            Here's the text. Some of these are empty, some are "obvious", and some are duplicates.

            DMS-REQ-0003: Create and Maintain Science Data Archive

            Specification: The LSST project shall create and manage an archive of all its public data products and the raw data necessary to reproduce them. In addition, the archive shall contain all necessary engineering and calibration data for the full understanding of the performance and operation of the Observatory.

            DMS-REQ-0005: Produce Data Releases

            Specification: All Level 2 Data Products shall be made public as part of periodic coherent Data Releases.

            DMS-REQ-0007: Pipeline Infrastructure

            Specification: The DMS shall provide Processing, Storage, and Network resources capable of executing the DMS Data Release pipelines over all pre-existing survey data in a time no greater than drProcessingPeriod.

            DMS-REQ-0011: Produce Difference Sources

            Specification: The DMS shall produce Difference Sources from the analysis of Difference Exposures.

            DMS-REQ-0040: Enable BAO Analysis

            Specification: The DMS shall provide the data products enabling the measurement of the effects of Baryon Acoustic Oscillations (BAO) in the detected galaxies.

            DMS-REQ-0041: Measure Intrinsic Ellipticies of Small Galaxies

            Specification: The DMS shall measure the intrinsic ellipticities of small galaxies. The maximum galaxy size for this requirement is 10 arcsec. The measurement error goal for this is TBD.

            DMS-REQ-0055: Correct for Camera Bias Structure

            DMS-REQ-0056: Correct for Camera Crosstalk

            DMS-REQ-0057: Correct for Detector Fringing

            DMS-REQ-0058: Correct for Instrument Sensitivity Variation

            DMS-REQ-0066: Keep Exposure Archive

            Specification: The DMS shall provide an archive of all Raw Exposures taken by the LSST. All other exposure types produced by the DMS (Processed Science Exposures, Calibration Exposures, Coadded Exposures) shall either be archived, or a method shall be provided to recreate them on demand. The Archive shall be designed to be capable of managing the data for the full duration of the survey and associated data processing.

            DMS-REQ-0076: Keep Science Data Archive

            The DMS shall provide a science data archive containing catalogs of all detected sources and objects and associated metadata that meet data quality thresholds for retention.

            DMS-REQ-0080: Difference Sources Available within 24 hours

            Detected sources and associated metadata shall be available for public access in the DMS science data archive within 24 hours of their generation by the DMS.

            DMS-REQ-0081: Produce Object Catalog

            The LSST DMS shall produce a catalog of all objects detected by the Detection Pipeline in at least two Difference Exposures from a single Visit.

            DMS-REQ-0086: Produce Orbit Catalog

            The LSST DMS shall produce a catalog of all moving objects detected by the Moving Object Pipeline (MOP)

            DMS-REQ-0090: Generate Alerts

            DMS-REQ-0092: Alert Attributes

            For each alert, DMS shall store the pipeline parameters used to derive it, and a set of metadata attributes including at least:

            • Class of event detected
            • Confidence of detection
            • All associated information from the Object Catalog (includes Sources associated with this Object)
            • Postage stamp images centered on the Object from both difference exposures of the visit which triggered the alert, and from the template image used in image substraction.

            DMS-REQ-0104: Product Co-Added Exposures

            The DMS shall produce Co-Added Exposures combining the set of exposures taken of the same region of the sky that meet a user-specified set of quality and other selection criteria. These may include site conditions (seeing, sky brightness), telescope conditions (wavefront quality), PSF shape and spatial variability, date of exposure, or filter used.

            Each Exposure contributing to a Co-Added Exposure shall be projected onto a common reference frame using a projection selected from a set of options by a Policy. [ACTION: harmonize with co-add pipeline requirement, enumerate the types of coadds required]

            DMS-REQ-0116: Extended Object Shape Parameters

            For extended objects only, the summary metadata attributes must also include shape parameters.
            Weak lensing studies require the image moments (or equivalent) through N=2.
            For weak lensing extended objects of size greater than TBD (10 arcsec?) do not require shape parameters to be measured

            Show
            tjenness Tim Jenness added a comment - Here's the text. Some of these are empty, some are "obvious", and some are duplicates. DMS-REQ-0003: Create and Maintain Science Data Archive Specification: The LSST project shall create and manage an archive of all its public data products and the raw data necessary to reproduce them. In addition, the archive shall contain all necessary engineering and calibration data for the full understanding of the performance and operation of the Observatory. DMS-REQ-0005: Produce Data Releases Specification: All Level 2 Data Products shall be made public as part of periodic coherent Data Releases. DMS-REQ-0007: Pipeline Infrastructure Specification: The DMS shall provide Processing, Storage, and Network resources capable of executing the DMS Data Release pipelines over all pre-existing survey data in a time no greater than drProcessingPeriod. DMS-REQ-0011: Produce Difference Sources Specification: The DMS shall produce Difference Sources from the analysis of Difference Exposures. DMS-REQ-0040: Enable BAO Analysis Specification: The DMS shall provide the data products enabling the measurement of the effects of Baryon Acoustic Oscillations (BAO) in the detected galaxies. DMS-REQ-0041: Measure Intrinsic Ellipticies of Small Galaxies Specification: The DMS shall measure the intrinsic ellipticities of small galaxies. The maximum galaxy size for this requirement is 10 arcsec. The measurement error goal for this is TBD. DMS-REQ-0055: Correct for Camera Bias Structure DMS-REQ-0056: Correct for Camera Crosstalk DMS-REQ-0057: Correct for Detector Fringing DMS-REQ-0058: Correct for Instrument Sensitivity Variation DMS-REQ-0066: Keep Exposure Archive Specification: The DMS shall provide an archive of all Raw Exposures taken by the LSST. All other exposure types produced by the DMS (Processed Science Exposures, Calibration Exposures, Coadded Exposures) shall either be archived, or a method shall be provided to recreate them on demand. The Archive shall be designed to be capable of managing the data for the full duration of the survey and associated data processing. DMS-REQ-0076: Keep Science Data Archive The DMS shall provide a science data archive containing catalogs of all detected sources and objects and associated metadata that meet data quality thresholds for retention. DMS-REQ-0080: Difference Sources Available within 24 hours Detected sources and associated metadata shall be available for public access in the DMS science data archive within 24 hours of their generation by the DMS. DMS-REQ-0081: Produce Object Catalog The LSST DMS shall produce a catalog of all objects detected by the Detection Pipeline in at least two Difference Exposures from a single Visit. DMS-REQ-0086: Produce Orbit Catalog The LSST DMS shall produce a catalog of all moving objects detected by the Moving Object Pipeline (MOP) DMS-REQ-0090: Generate Alerts DMS-REQ-0092: Alert Attributes For each alert, DMS shall store the pipeline parameters used to derive it, and a set of metadata attributes including at least: Class of event detected Confidence of detection All associated information from the Object Catalog (includes Sources associated with this Object) Postage stamp images centered on the Object from both difference exposures of the visit which triggered the alert, and from the template image used in image substraction. DMS-REQ-0104: Product Co-Added Exposures The DMS shall produce Co-Added Exposures combining the set of exposures taken of the same region of the sky that meet a user-specified set of quality and other selection criteria. These may include site conditions (seeing, sky brightness), telescope conditions (wavefront quality), PSF shape and spatial variability, date of exposure, or filter used. Each Exposure contributing to a Co-Added Exposure shall be projected onto a common reference frame using a projection selected from a set of options by a Policy. [ACTION: harmonize with co-add pipeline requirement, enumerate the types of coadds required] DMS-REQ-0116: Extended Object Shape Parameters For extended objects only, the summary metadata attributes must also include shape parameters. Weak lensing studies require the image moments (or equivalent) through N=2. For weak lensing extended objects of size greater than TBD (10 arcsec?) do not require shape parameters to be measured
            Hide
            lguy Leanne Guy added a comment - - edited

            Thank you Tim Jenness The DM-SST will review these and come back with a proposal 

            Show
            lguy Leanne Guy added a comment - - edited Thank you Tim Jenness The DM-SST will review these and come back with a proposal 
            Hide
            lguy Leanne Guy added a comment -

            Tim Jenness is there any information in MD about which higher level requirements in the OSS or LSR that  these dangling requirements were derived from?

            Show
            lguy Leanne Guy added a comment - Tim Jenness is there any information in MD about which higher level requirements in the OSS or LSR that  these dangling requirements were derived from?
            Hide
            tjenness Tim Jenness added a comment -

            No. Linking to OSS (we should not be linking to LSR from LSE-61) was added by me a couple of years ago so these requirements outside the main model were never formally linked inside the model.

            Show
            tjenness Tim Jenness added a comment - No. Linking to OSS (we should not be linking to LSR from LSE-61) was added by me a couple of years ago so these requirements outside the main model were never formally linked inside the model.
            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            I think it's accurate to say that this ticket is now "In Progress", but the work is being done by Leanne Guy and myself Gregory Dubois-Felsmann at the moment.

            Show
            gpdf Gregory Dubois-Felsmann added a comment - I think it's accurate to say that this ticket is now "In Progress", but the work is being done by Leanne Guy and myself Gregory Dubois-Felsmann at the moment.

              People

              • Assignee:
                lguy Leanne Guy
                Reporter:
                swinbank John Swinbank
                Watchers:
                Gabriele Comoretto, Gregory Dubois-Felsmann, John Swinbank, Kian-Tat Lim, Leanne Guy, Simon Krughoff, Tim Jenness
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Summary Panel