-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
[EGM MVA ID] xml.gz to root conversion for photons #38556
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38556/30794
|
enable profiling |
A new Pull Request was created by @swagata87 (Swagata Mukherjee) for master. It involves the following packages:
@jpata, @cmsbuild, @clacaputo can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test with cms-data/RecoEgamma-PhotonIdentification#12 |
type egamma |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2c023c/25888/summary.html The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
You can see more details here: Comparison SummarySummary:
|
Hi @swagata87 , I'm not sure what to check in the profiling but if I considered 12_5_0_pre3: 2.6 % ----> this PR: 2.37 % |
Hi @clacaputo, thanks for checking. |
+reconstruction
|
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. @perrotta, @dpiparo, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This is a follow up of #38339, which addressed xml to root conversion of electron MVA IDs, while this PR does the same for photon MVA ID. This is motivated by the noticeable improvement reported in #38339. Since the number of photon xml files are much smaller than electron, it could very well be that the improvement brought in by this PR won't be as noticeable. But I'm curious to see the effect of this PR, taking advantage of the profiling options of the bot. If the improvement is negligible, then.. oh well.
PR validation:
Tested with workflow
11834.21
.This PR is not a backport.
Backport not necessary.