-
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] Update muon shower data formats for 2023 running #41198
[13_0_X] Update muon shower data formats for 2023 running #41198
Conversation
Also clean up MuonShower data format a bit.
A new Pull Request was created by @dinyar (Dinyar Rabady) for CMSSW_13_0_X. It involves the following packages:
@epalencia, @cmsbuild, @cecilecaillol, @aloeliger can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
backport of #40890 |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-aa183d/31626/summary.html Comparison SummarySummary:
|
+l1 |
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 |
PR description:
Backport of the update for the muon shower data formats (RegionalMuonShower and MuonShower) containing the changes that I think are needed for 2023 running.
attn @elfontan and @eyigitba
PR validation:
Similar as for the original PR there isn't much validation that can be done yet apart from the standard tests.
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:
Backport of #40890 to CMSSW 13_0_X