correcting valOmtfDigis in the L1TStage2Emulator_cff.py

in the L1Trigger/L1TMuonOverlapPhase1/python/simOmtfDigis_cfi.py: adding bxMin and bxMx as cms.int32 (with defoult values i.e. 0) in the DQM/L1TMonitor/python/L1TStage2Emulator_cff.py not using cms.int32 for simOmtfDigis.bxMin and bxMax, but ordinary numbers
cms-sw · Sep 24, 2021 · b8d8a96 · b8d8a96
1 parent a8d4e08
commit b8d8a96
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/DQM/L1TMonitor/python/L1TStage2Emulator_cff.py b/DQM/L1TMonitor/python/L1TStage2Emulator_cff.py
@@ -48,8 +48,8 @@
     srcDTTh = "omtfStage2Digis",
     srcCSC = "omtfStage2Digis",
     srcRPC = "omtfStage2Digis",
-    bxMin = cms.int32(-3),
-    bxMax = cms.int32(4)
+	bxMin = -3,
+    bxMax = 4
 )
 
 # GEM TPG

diff --git a/L1Trigger/L1TMuonOverlapPhase1/python/simOmtfDigis_cfi.py b/L1Trigger/L1TMuonOverlapPhase1/python/simOmtfDigis_cfi.py
@@ -27,7 +27,7 @@
 
   #if commented the default values are 0-0
   #-3 to 4 is the range of the OMTF DAQ readout, so should be used e.g. in the DQM data to emulator comparison
-  #bxMin = cms.int32(-3),
-  #bxMax = cms.int32(4)
+  bxMin = cms.int32(0),
+  bxMax = cms.int32(0)
 )