-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Check valid pads and clusters in GEM trigger primitive producers #30624
Check valid pads and clusters in GEM trigger primitive producers #30624
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30624/16887
|
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 |
@rekovic do you have any comments? |
please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@rekovic If you could wait with signing this. I'll amend this pull requests with log warnings in the pad and cluster producer is invalid primitives are produced. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+upgrade |
+1 |
+1 |
@rekovic Could you sign, please? |
kind reminder @cms-sw/l1-l2 |
+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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
I added a few statements to ignore invalid pads and clusters in the GEM-CSC trigger. I also added checks (LogWarnings, not selections) in the GEM trigger primitive producers.
PR validation:
Tested with 23234.0 in 11_2_X.
if this PR is a backport please specify the original PR and why you need to backport that PR:
N/A