Details
-
Type:
Improvement
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: verify
-
Labels:None
-
Story Points:4
-
Epic Link:
-
Sprint:AP S19-5, AP S19-6
-
Team:Alert Production
Description
As originally designed, lsst.verify.compatibility.MetricsControllerTask can store only metadata that is required (e.g., by SQuaSH) for all metrics. However, applications like ap_verify, validate_drp, etc. may wish to store information that's specific to their workflow.
Design and implement a system for passing generic Job-level metadata to MetricsControllerTask.
Attachments
Issue Links
- relates to
-
DM-16642 Generalize job metadata code
- Done
Proposed API: add an optional argument to MetricsControllerTask.runDataRef that takes a dictionary of metadata keys and values. This is more work for the client than registering metadata once with the class, but it's more flexible. Given that the SQuaSH-required metadata (specifically, the data ID) is already different for different runs, it's reasonable to support run-specific values for application-specific metadata as well.