-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
L1 Scouting Online Selection modules #45350
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45350/40769
|
A new Pull Request was created by @Mmiglio for master. It involves the following packages:
The following packages do not have a category, yet: L1TriggerScouting/OnlineProcessing @cmsbuild, @emeschi, @smorovic can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
cms-sw/cms-bot#2278 adds new package to cms-bot |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-329d42/40169/summary.html
Comparison SummarySummary:
|
+daq |
cms-sw/cms-bot#2276 assigns this new package to |
Pull request #45350 was updated. @aloeliger, @epalencia can you please check and sign again. |
+l1 |
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. @sextonkennedy, @rappoccio, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR introduces the modules used for the L1 Scouting Online selection, which will complement the "Zero bias" stream.
The selection stream was discussed during L1 Trigger DPG meetings (e.g. link)
Related to this PR, a new category is introduced with cms-sw/cms-bot#2276.
PR validation:
The PR has been validate using files collected in the "Zero Bias" stream, e.g.
In parallel, it was successfully tested in the Scouting system at P5.
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
We would like this PR to be backported in a data-taking release (14_0_X) in order to collect data from pp collisions during 2024.