From ff0b90fb31087b5ff4fd325343f0eff23a0f777b Mon Sep 17 00:00:00 2001
From: Pascal Raisig <praisig@ikf.uni-frankfurt.de>
Date: Thu, 21 Jan 2021 16:43:00 +0100
Subject: [PATCH] Fix missing cut deactivation

A small bug was introduced with MR!200,
which caused the cut on max digis to be activated instead of disabled,
 when set to -1
---
 fles/mcbm2018/tasks/CbmMcbm2019TimeWinEventBuilderAlgo.cxx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fles/mcbm2018/tasks/CbmMcbm2019TimeWinEventBuilderAlgo.cxx b/fles/mcbm2018/tasks/CbmMcbm2019TimeWinEventBuilderAlgo.cxx
index f33e5c97be..f1191e94ad 100644
--- a/fles/mcbm2018/tasks/CbmMcbm2019TimeWinEventBuilderAlgo.cxx
+++ b/fles/mcbm2018/tasks/CbmMcbm2019TimeWinEventBuilderAlgo.cxx
@@ -594,7 +594,7 @@ Bool_t CbmMcbm2019TimeWinEventBuilderAlgo::CheckTriggerConditions(
     return kFALSE;
   }  // if((-1 == iNbDigis) || (static_cast<UInt_t>(iNbDigis) < det.fuTriggerMinDigis))
   /// Check trigger rejection by maximal number
-  else if (det.fiTriggerMaxDigis < iNbDigis) {
+  else if (0 < det.fiTriggerMaxDigis && det.fiTriggerMaxDigis < iNbDigis) {
     LOG(debug2) << "Event Has too many digis: " << iNbDigis << " vs "
                 << det.fiTriggerMaxDigis << " for " << det.sName;
     return kFALSE;
-- 
GitLab