From aadae5d6881414ce337b07a3416935475e126f17 Mon Sep 17 00:00:00 2001 From: Krzysztof Findeisen Date: Mon, 26 Aug 2024 13:30:34 -0700 Subject: [PATCH] Fix incorrect metadata dimensions for *timing_loadDiaCatalogs. The loading used to be part of a visit-level task, but is now group-level. --- pipelines/_ingredients/MetricsRuntime.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/pipelines/_ingredients/MetricsRuntime.yaml b/pipelines/_ingredients/MetricsRuntime.yaml index 3e6bffb..1241a0e 100644 --- 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