Reactivation of fat event filter for uGMT ZS online DQM - 90x v2 #18409
Conversation
…ectory names. Conflicts: DQM/Integration/python/clients/l1tstage2_dqm_sourceclient-live_cfg.py DQM/L1TMonitor/python/L1TStage2uGMT_cfi.py Conflicts: DQM/Integration/python/clients/l1tstage2_dqm_sourceclient-live_cfg.py DQM/L1TMonitor/python/L1TStage2uGMT_cfi.py
|
A new Pull Request was created by @thomreis (Thomas Reis) for CMSSW_9_0_X. It involves the following packages: DQM/Integration @cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
Why is it 2 times larger than original backport? |
|
@dmitrijus this contains also commits that are already in PR #18043 in order to resolve a conflict at P5. |
|
+1 |
cmsbuild
added
dqm-approved
fully-signed
and removed
dqm-pending
pending-signatures
labels
|
The tests are being triggered in jenkins. |
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_9_0_X IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar |
|
Comparison job queued. |
|
Comparison is ready Comparison Summary:
|
|
+1 |
Backport from PR #18395
Add the fat event filter (keeps every 107th event) again to the L1 trigger online DQM configuration.
This is needed for the uGMT zero suppression DQM module because for those events the ZS is in validation mode and does only flag and not suppress the data blocks.
In addition the "2016" string was removed from the DQM directory names and the maximum FED readout size was increased.
This PR has the same changes as #18396 and in addition also contains what is already in PR #18043 in order to resolve a conflict when merging for the deployment at P5. The 91x version of #18043 is already merged.