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
Protect L1T producers against ME0 hits #29369
Protect L1T producers against ME0 hits #29369
Conversation
The code-checks are being triggered in jenkins. |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29369/14472
|
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 |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29369/14473
|
Kind reminder @rekovic (this change is rather small) |
+1 |
The tests are being triggered in jenkins. |
This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
Comparison job queued. |
@dildick protecting for the 16 eta partitions would be handy too |
@jshlee Idd. But I would put that in a different PR. |
Comparison is ready Comparison Summary:
|
+1 |
PR description:
Coincidence pads nor pad clusters will be built for ME0. This PR prevents two L1T producers from using ME0 digis. This is done in preparation of the merger of GEM and ME0.
PR validation:
I ran WF 22034.0 successfully.
if this PR is a backport please specify the original PR and why you need to backport that PR:
N/A
@watson-ij @jshlee