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

validateDrp arguments (including brightSnr) not passed/parsed correctly

    Details

    • Type: Bug
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Templates:
    • Story Points:
      2
    • Sprint:
      DRP F19-6 (Nov), DRP S20-2 (Jan), DRP S20-3 (Feb)
    • Team:
      Data Release Production
    • Urgent?:
      No

      Description

      There are a few problems in how validateDrp.py calls run() in validate.py:

      • The brightSnr input argument gets passed to runOneFilter explicitly but also isn't used. Therefore the brightSnr config settings in the various yaml files in validate_drp and lsst_ci have no effect, and in effect the actual S/N limit applied in the metrics is currently the default safeSnr in matchreduce.py, which is 50 rather than the override of 100 in most of the configs.

        Attachments

          Activity

            People

            • Assignee:
              dtaranu Dan Taranu
              Reporter:
              dtaranu Dan Taranu
              Reviewers:
              Jeffrey Carlin
              Watchers:
              Dan Taranu, Jeffrey Carlin, Michael Wood-Vasey, Sophie Reed
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Summary Panel