[L1T] Adding a reduced data format: phase2_l1scout for use in the Spring24 MC Campaign (Phase 2)#51330
Conversation
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-51330/49955
|
|
A new Pull Request was created by @eyigitba for master. It involves the following packages:
@BenjaminRS, @cmsbuild, @davidlange6, @fabiocos, @ftenchini, @mandrenguyen, @quinnanm can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
please test |
|
+1 Size: This PR adds an extra 36KB to repository Comparison SummarySummary:
|
|
+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, @ftenchini, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
|
@mandrenguyen @BenjaminRS thanks for the quick review. should I submit backports to other releases in addition to 140X? |
PR description:
Adding in new configuration options providing a reduced data format: phase2_l1scout for use in the Spring24 MC Campaign. Previously disucssed a bit in #51259 and in #51319
I modified @BenjaminRS's PR based on @mmusich suggestion.
The idea behind this is to reduce the event size by a factor of ~50 to be able to request more MC statistics for Phase-2 L1 Scouting use.
PR validation:
Ran the code locally over ~50 events using Phase2Spring24 MC campaign setup commands. It produces the expected result without crashing. File size goes from ~3 GB to ~100 MB.
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:
Related to #51319
Please let me know which other releases should get a backport of this PR