From 24a1a0dbd2afe4e0a899b2c3300602aae5261090 Mon Sep 17 00:00:00 2001
From: shahoian <ruben.shahoyan@cern.ch>
Date: Wed, 11 Nov 2026 21:34:24 +0100
Subject: [PATCH] Clear mTriggeredBCFT0 container at TF start

Accumulation of FT0 triggers over processed TFs lead to linear increase of processing time per TF,
but did not affect pile-up assignment or matching rate
---
 Detectors/TRD/workflow/src/TRDGlobalTrackingSpec.cxx | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Detectors/TRD/workflow/src/TRDGlobalTrackingSpec.cxx b/Detectors/TRD/workflow/src/TRDGlobalTrackingSpec.cxx
index 4cbe5ca7a3609..cd6c981926a67 100644
--- a/Detectors/TRD/workflow/src/TRDGlobalTrackingSpec.cxx
+++ b/Detectors/TRD/workflow/src/TRDGlobalTrackingSpec.cxx
@@ -316,6 +316,7 @@ void TRDGlobalTracking::run(ProcessingContext& pc)
   inputTracks.collectData(pc, *mDataRequest);
   updateTimeDependentParams(pc);
   storeConfigs(pc);
+  mTriggeredBCFT0.clear();
   mChainTracking->ClearIOPointers();
 
   mTPCClusterIdxStruct = &inputTracks.inputsTPCclusters->clusterIndex;