From b215850f036265114194201bc7ea75938d1d2ba8 Mon Sep 17 00:00:00 2001
From: Michal Bluj <michal.bluj@cern.ch>
Date: Thu, 23 May 2024 17:50:24 +0200
Subject: [PATCH] Set 3 instead of 4 OMTF track sub-address as expected by uGMT

---
 L1Trigger/L1TMuonOverlapPhase1/src/Omtf/OMTFProcessor.cc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/L1Trigger/L1TMuonOverlapPhase1/src/Omtf/OMTFProcessor.cc b/L1Trigger/L1TMuonOverlapPhase1/src/Omtf/OMTFProcessor.cc
index 7a8b0545d3c69..530cdb876d66a 100644
--- a/L1Trigger/L1TMuonOverlapPhase1/src/Omtf/OMTFProcessor.cc
+++ b/L1Trigger/L1TMuonOverlapPhase1/src/Omtf/OMTFProcessor.cc
@@ -294,7 +294,8 @@ std::vector<l1t::RegionalMuonCand> OMTFProcessor<GoldenPatternType>::getFinalcan
     //check if it matters if it needs to be here as well
     trackAddr[1] = myCand->getRefLayer();
     trackAddr[2] = myCand->getDisc();
-    trackAddr[3] = myCand->getGpResultUnconstr().getPdfSumUnconstr();
+    //TODO: uGMT expects only 3 sub-addresses, so not set 4th. This is anyway currently not used.
+    //trackAddr[3] = myCand->getGpResultUnconstr().getPdfSumUnconstr();
     if (candidate.hwPt() > 0 || candidate.hwPtUnconstrained() > 0) {
       candidate.setTrackAddress(trackAddr);
       candidate.setTFIdentifiers(iProcessor, mtfType);