From a49c1dcb346a492cedc6c8590af55756fcbb0efe Mon Sep 17 00:00:00 2001
From: Andreas Stefl <stefl.andreas@gmail.com>
Date: Fri, 23 Feb 2024 11:23:01 +0100
Subject: [PATCH] revert tracksMaxSignificance change

---
 .../Vertexing/src/AdaptiveMultiVertexFinderAlgorithm.cpp      | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Examples/Algorithms/Vertexing/src/AdaptiveMultiVertexFinderAlgorithm.cpp b/Examples/Algorithms/Vertexing/src/AdaptiveMultiVertexFinderAlgorithm.cpp
index e75caa6ec51..655d8792424 100644
--- a/Examples/Algorithms/Vertexing/src/AdaptiveMultiVertexFinderAlgorithm.cpp
+++ b/Examples/Algorithms/Vertexing/src/AdaptiveMultiVertexFinderAlgorithm.cpp
@@ -134,6 +134,10 @@ auto ActsExamples::AdaptiveMultiVertexFinderAlgorithm::makeVertexFinder() const
   finderConfig.maxIterations = 200;
   finderConfig.useTime = m_cfg.useTime;
   if (m_cfg.useTime) {
+    // When using time, we have an extra contribution to the chi2 by the time
+    // coordinate. We thus need to increase tracksMaxSignificance (i.e., the
+    // maximum chi2 that a track can have to be associated with a vertex).
+    finderConfig.tracksMaxSignificance = 7.5;
     // Check if vertices are merged in space and time
     // TODO rename do3dSplitting -> doFullSplitting
     finderConfig.do3dSplitting = true;