-
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
Update on the muon shower trigger for startup Run-3 (HadronicShowerTrigger-7) #35886
Update on the muon shower trigger for startup Run-3 (HadronicShowerTrigger-7) #35886
Conversation
…move out-of-time triggers for startup Run-3. Add anode AND cathode case
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35886/26283
|
A new Pull Request was created by @dildick (Sven Dildick) for master. It involves the following packages:
@cmsbuild, @rekovic, @cecilecaillol can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Interesting WF 11634.0 fails in CMSSW_12_1_X_2021-10-27-2300 with
|
WF 11634.0 seems to work in CMSSW_12_2_X_2021-11-02-1100 |
Can someone initiate the tests, please? |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b544f6/20210/summary.html Comparison SummarySummary:
|
+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. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
@dildick , even if it is not in the part of the code that you modified, since it is in one file that you modified, could you please take care of the static analyzer warning which points out to an uncorrect usage of variable The same static analyzer report also points out a few other rather obvious mistakes/bugs in the code that should be better addressed, in a different PR but possibly rather soon. For example: |
@perrotta For the static analyzer, do you have an example solution that would not throw static warnings? I suppose I could just remove the |
The |
Yes, I would do exactly the same (possibly for both files here, since you are there) . By the way, having hardcoded the value of |
... and this is a good reason to remove/fix obvious flaws since now (not in this PR, though) |
@perrotta I'll open up a separate PR for the static warnings. For the |
+1
|
PR description:
For startup Run-3 we aim to have 2 trigger modes for muon shower: (1) >=1 nominal shower (main trigger for physics analysis) and (2) >=1 tight shower (backup trigger for physics analysis).
Relevant presentation here: https://indico.cern.ch/event/1090753/contributions/4585330/attachments/2335554/3980792/CSCShower_SD_20211027.pdf
PR validation:
Code compiles. Tested with Run-2 ZeroBias and Run-3 MC samples.
if this PR is a backport please specify the original PR and why you need to backport that PR:
N/A
@tahuang1991 @Nik-Menendez