New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New feature in GEM simulation: GEMPadDigiCluster #15001
New feature in GEM simulation: GEMPadDigiCluster #15001
Conversation
A new Pull Request was created by @dildick (Sven Dildick) for CMSSW_8_1_X. It involves the following packages: DataFormats/GEMDigi @cmsbuild, @civanch, @mdhildreth, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Comparison looks good. There should not be (and there aren't) any changes with respect to the baseline. |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar |
+1 |
A GEMPadDigiCluster is a set of adjacent GEMPadDigis in a single GEM chamber. Currently we send all trigger pads from the GEM chamber to the CSC chamber. In the hardware each GEM chamber optohybrid will send at most 8 clusters of at most 8 adjacent trigger pads to the nearby CSC optical trigger mother board. The effects are expected to be very small (<1%) on the local GEM-CSC trigger performance.
Still needs to be done: use GEMPadDigiClusters instead of GEMPadDigis in CSC trigger emulator.