L1TGlobalProducer: fix prescale index counting #17497
Conversation
The L1 prescale index should consistently count from 0 - this is the convention used by the L1 uGT, the monitoring code (e.g. WBM), etc. The previous version of the code was internally inconsistent: the value `m_prescaleSet-1` was being used to determine the prescales, but the value `m_prescaleSet` was set in the uGT payload.
|
Please test |
|
A new Pull Request was created by @rekovic for CMSSW_8_0_X. It involves the following packages: L1Trigger/L1TGlobal @cmsbuild, @rekovic, @mulhearn, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here #13028 |
|
The tests are being triggered in jenkins. |
|
Comparison job queued. |
|
+1 |
cmsbuild
added
fully-signed
l1-approved
and removed
l1-pending
pending-signatures
labels
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar |
|
backport |
|
+1 |
80x backport of 90x PR #17496.
The L1 prescale index should consistently count from 0 - this is the
convention used by the L1 uGT, the monitoring code (e.g. WBM), etc.
The previous version of the code was internally inconsistent: the value
m_prescaleSet-1was being used to determine the prescales, but thevalue
m_prescaleSetwas set in the uGT payload.