From fdfaa4ac7f73d360d8ae5c2fe48e732bf176ed6b Mon Sep 17 00:00:00 2001
From: shahoian <ruben.shahoyan@cern.ch>
Date: Mon, 23 Mar 2026 17:24:44 +0100
Subject: [PATCH] Fix using MeanVertex in the residuals monitoring workflow

---
 Detectors/GlobalTrackingWorkflow/study/src/CheckResid.cxx | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Detectors/GlobalTrackingWorkflow/study/src/CheckResid.cxx b/Detectors/GlobalTrackingWorkflow/study/src/CheckResid.cxx
index e6584a7055446..063edc65d7486 100644
--- a/Detectors/GlobalTrackingWorkflow/study/src/CheckResid.cxx
+++ b/Detectors/GlobalTrackingWorkflow/study/src/CheckResid.cxx
@@ -44,7 +44,7 @@
 
 // Attention: in case the residuals are checked with geometry different from the one used for initial reconstruction,
 // pass a --configKeyValues option for vertex refit as:
-// ;pvertexer.useMeanVertexConstraint=false;pvertexer.iniScale2=100;pvertexer.acceptableScale2=10.;
+// ;pvertexer.useMeanVertexConstraint=false;pvertexer.meanVertexExtraErrSelection=0.2;pvertexer.iniScale2=100;pvertexer.acceptableScale2=10.;
 // In any case, it is better to pass ;pvertexer.useMeanVertexConstraint=false;
 
 namespace o2::checkresid
@@ -152,6 +152,7 @@ void CheckResidSpec::updateTimeDependentParams(ProcessingContext& pc)
   }
   if (mMeanVertexUpdated) {
     mMeanVertexUpdated = false;
+    mVertexer.setMeanVertex(&mMeanVtx);
     mVertexer.initMeanVertexConstraint();
   }
   bool updateMaps = false;