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
[HCAL] Make sure that trigger towers with abs(ieta)=16 are processed with QIE8 settings in 2018. #22077
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-22077/3204 |
A new Pull Request was created by @matz-e (Matthias Wolf) for master. It involves the following packages: SimCalorimetry/HcalTrigPrimAlgos @nsmith-, @cmsbuild, @thomreis, @rekovic can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
Hi @matz-e |
in principle, I think, yes. But I also think that the likelihood of triggering the bug being fixed is quite small. The bug requires energy deposits/data frames in depth 4 of tower 16 and no energy/data frames for depths 1-3. My guess is that this would mainly occur (with a very small probability — basically energy leaking from 17 -> 16) when using the emulation from RAW with zero-suppression, and as such the the regular simulation chain should not really be impacted. Do you want me to file a backport PR for 10_0_X? |
Hi, to be on the safe side I would backport to 10_0_X. we don't want to have unexpected crashes when the MC is submitted. thanks, |
@deguio Another motivation for the backport is the online and offline DQM. The crash could be triggered by tests in which the laser is fired into the HEM or HEP megatiles in a global run. Such tests are often done to validate the latency of TPs sent to L1. |
IMHO these packages could be under HCAL signature and not L1: the interface between calorimeter and trigger responsibility is at the trigger primitive level, both in hardware and software. This change won't affect that interface. As the expert on the downstream consumer of these trigger primitives, |
+1 The right way around. |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
Fixes a crash when only the last depth of tower 16 is present.