-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Add EW skim for 2025 PbPb #49227
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 EW skim for 2025 PbPb #49227
Conversation
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-49227/46564 |
|
A new Pull Request was created by @stahlleiton for master. It involves the following packages:
@AdrianoDee, @DickyChant, @antoniovagnerini, @cmsbuild, @miquork can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
please test workflow 143.203 |
|
+1 Size: This PR adds an extra 16KB to repository Comparison SummarySummary:
|
|
urgent |
|
+pdmv |
|
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. @mandrenguyen, @ftenchini, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
PR description:
This PR replaces the previous muon and electron PbPb skims (PbPbEMu, PbPbZEE and PbPbZMu) with one new skim that requires the presence of a high pT (> 15 GeV) electron or muon, labelled as EW skim. The content of this new skim is stored in MiniAOD. After testing on ~5000 minbias events from 2024 PbPb data, the size of the old skims (PbPbEMu + PbPbZEE + PbPbZMu) is about 3% of 2024 RawPrime PDs while the new EW skim is only 1%, reducing the skim PD size by a factor of 3 in 2025 PbPb while enhancing the physics potential (looser selection). The relval 143.203 is added to test the new skim.
@flodamas @mandrenguyen
PR validation:
Tested with relval 143.203
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:
To be backported to 15_1_X for PbPb data taking