-
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
Add L1 objects into Run3Scouting Nano #44642
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44642/39838
|
A new Pull Request was created by @artlbv for master. It involves the following packages:
@vlimant, @hqucms, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
enable nano |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9a7da8/38663/summary.html Comparison SummarySummary:
NANO Comparison SummarySummary:
Nano size 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. @rappoccio, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
[14_0_X] Backport of: #44642 Add L1 objects into Run3Scouting Nano
PR description:
This PR adds the L1 trigger objects to the Run3 scouting NanoAOD.
This proposal was presented and approved by the scouting group on the 5th of April: https://indico.cern.ch/event/1399442/#6-l1-objects-in-scouting-event
It follows the approach of the main Nano except it takes the L1 objects from the unpacked uGT data record, and not the L1 Muon and Calo systems themselves, since only the uGT FED is stored in the scouting RAW.
PR validation:
Tested by producing scouting NanoAOD from a 2023 scouting RAW file as shown in the linked slides.
The scouting nano size increase is 5%.
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:
Not a backport, but will likely need one for this to have an effect for the upcoming data taking in 140x.
FY @elfontan @kelmorab @eyigitba @slaurila @aloeliger @epalencia