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

Add new option --metrics-package in dispatch_verify.py to specify the package that hosts metrics and specifications definitions

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Invalid
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: verify
    • Labels:
      None

      Description

      dispatch_verify.py loads metrics and specifications from the verify_metrics package by default and add that information to the verification job.

      For some verification framework use cases, like in System Verification, metrics and specifications might be defined in different packages. For that, we need a new command line option --metrics-package in dispatch_verify.py to specify the package that hosts metrics and specifications definitions.

      If it is not an EUPS package a path to the directory that hosts metrics and specifications definitions also should work.

        Attachments

          Issue Links

            Activity

            Hide
            afausti Angelo Fausti added a comment -

            All lsst.verify metrics are defined in the verify_metrics repo, the full qualified metric name is prefixed by the metrics package and this is how we currently obtain the metrics package name in SQuaSH. If a better mechanism is needed we can open another ticket to implement this.

            Show
            afausti Angelo Fausti added a comment - All lsst.verify metrics are defined in the verify_metrics repo, the full qualified metric name is prefixed by the metrics package and this is how we currently obtain the metrics package name in SQuaSH. If a better mechanism is needed we can open another ticket to implement this.

              People

              Assignee:
              afausti Angelo Fausti
              Reporter:
              afausti Angelo Fausti
              Watchers:
              Angelo Fausti
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.