-
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
[13.0.X] Modernize / optimize DisappearingMuonsSkimming
#41311
[13.0.X] Modernize / optimize DisappearingMuonsSkimming
#41311
Conversation
A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_13_0_X. It involves the following packages:
@cmsbuild, @bbilin, @sunilUIET, @kskovpen can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-90a94d/31902/summary.html Comparison SummarySummary:
|
@kskovpen, could you please sign? |
+pdmv |
This pull request is fully signed and it will be integrated in one of the next CMSSW_13_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
backport of #41225
PR description:
I noticed that the code introduced in #40666 could be optimized in a few places, mostly:
deltaR2
in lieu ofdeltaR
I propose these optimizations here, as well as a test configuration that I have been using to make sure the update code results in exactly the same output as the old one.
PR validation:
Run the
Configuration/Skimming/test/test_DisMuon_cfg.py
file introduced here in a vanillaCMSSW_13_1_X_2023-03-27-1100
release and in this branch and checked that the exact same events are selected.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:
Verbatim backport of #41225, as request in #41225 (comment)