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

Support job metadata in verify_ap

    XMLWordPrintable

Details

    • 6
    • Alert Production F17 - 8, Alert Production F17 - 9
    • Alert Production

    Description

      When we begin analyzing metrics for verify_ap, those metrics will need to have metadata on the job being run. This could include the dataset/camera/filter IDs (see SQR-019), provenance and pipeline version (see Community post), and information about the server running the pipeline (requested on #dm-squash to control for environmental effects on performance metrics).

      This ticket is to decide a coherent strategy for delivering metadata to verify_ap's verify.Job object, and then adding the necessary infrastructure to verify.ap.metrics. We may need multiple sources of information; for example, reporting camera IDs could naturally be a feature of the verify.ap.Dataset class, and ultimately read from config files, while server information should be foolproof to keep arbitrary users from masquerading as official trial runs.

      Attachments

        Issue Links

          Activity

            No work has yet been logged on this issue.

            People

              krzys Krzysztof Findeisen
              krzys Krzysztof Findeisen
              Angelo Fausti, Eric Bellm, Joshua Hoblitt, Krzysztof Findeisen, Meredith Rawls, Simon Krughoff (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jenkins

                  No builds found.