From 2331017b3de4b04df1742416bf5cdb6b973b6349 Mon Sep 17 00:00:00 2001
From: aferrero2707 <aferrero1975@gmail.com>
Date: Tue, 23 Jun 2026 08:45:46 +0200
Subject: [PATCH] [PWGDQ]fixed collision index for matching candidates in
 derived tables

The collision index was wrongly forced to -1 in the FwdTracksReAlign tables
for the case of matching candidates with no associated collision.
Now the collision index is correctly set to htat of the original track.
---
 PWGDQ/Tasks/global-muon-matcher.cxx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/PWGDQ/Tasks/global-muon-matcher.cxx b/PWGDQ/Tasks/global-muon-matcher.cxx
index 99873fd115a..3818f98a3af 100644
--- a/PWGDQ/Tasks/global-muon-matcher.cxx
+++ b/PWGDQ/Tasks/global-muon-matcher.cxx
@@ -953,7 +953,7 @@ struct GlobalMuonMatching {
     const auto nClusters = static_cast<int8_t>(std::min(127, mchPar.getNClusters() + mftPar.getNClusters()));
 
     const float chi2 = static_cast<float>(mchTrack.chi2());
-    const int32_t collisionId = mchTrack.has_collision() ? mchTrack.collisionId() : -1;
+    const int32_t collisionId = mchTrack.collisionId();
     bool hasBcSlice = false;
     std::array<int32_t, 2> bcSlice{};
     if (collisionId < 0) {