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
Fix mix-up between the physical and the trigger chamber number in upgrade CSC motherboard #27958
Fix mix-up between the physical and the trigger chamber number in upgrade CSC motherboard #27958
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27958/11824
|
A new Pull Request was created by @dildick (Sven Dildick) for master. It involves the following packages: L1Trigger/CSCTriggerPrimitives @cmsbuild, @rekovic, @benkrikler 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 Comparison Summary:
|
+1 |
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) |
Hi @dildick |
@rekovic I'll provide back-ports of all recent PRs. @fabiocos I do see a difference in the GEM copad validation plots for station 1. It's hard to judge from the GEM DQM plots since the plots are not very clear themselves. Before submitting the PR I also tested the copad production on a Phase-2 PU0 single muon gun. |
+1 |
PR description:
This PR fixes a bug in the initialization of the GEMCoPadProcessor. In the constructor of the base class
CSCGEMMotherboard
the variablechamber
is used to reset the processor. This needs to betheChamber
instead which refers to the physical chamber number, not the trigger chamber number. Without the fix the upgrade motherboards do not produce coincidence pads.PR validation:
I tested this fix with workflow 22034.0.
@tahuang1991