Fix incorrect metadata dimensions for *timing_loadDiaCatalogs.

The loading used to be part of a visit-level task, but is now group-level.
lsst · Aug 26, 2024 · aadae5d · aadae5d
1 parent c270027
commit aadae5d
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/pipelines/_ingredients/MetricsRuntime.yaml b/pipelines/_ingredients/MetricsRuntime.yaml
@@ -96,6 +96,7 @@ tasks:
       connections.package: ap_association
       connections.metric: LoadDiaCatalogsTime
       connections.labelName: loadDiaCatalogs
+      metadataDimensions: [instrument, group, detector]  # TimingMetricTask assumes visit
       target: loadDiaCatalogs.run
   timing_diaPipe_associator:
     class: lsst.verify.tasks.commonMetrics.TimingMetricTask
@@ -217,6 +218,7 @@ tasks:
       connections.package: ap_association
       connections.metric: LoadDiaCatalogsCpuTime
       connections.labelName: loadDiaCatalogs
+      metadataDimensions: [instrument, group, detector]  # CpuTimingMetricTask assumes visit
       target: loadDiaCatalogs.run
   cputiming_diaPipe_associator:
     class: lsst.verify.tasks.commonMetrics.CpuTimingMetricTask