-
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
Jetid muon fraction fix #27691
Jetid muon fraction fix #27691
Conversation
merge with master
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27691/11293
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
@knash , you need to apply the code-checks in order to have this PR tested, and the review can start. |
By the way, is there any intention to backport to any other release? |
The code-checks are being triggered in jenkins. |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27691/11425
|
A new Pull Request was created by @knash for master. It involves the following packages: PhysicsTools/SelectorUtils @perrotta, @cmsbuild, @santocch, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
+1
|
By the way (@fabiocos @smuzaffar): no external is really needed here. It was just added for the tests in order to allow the PR build on top of the latest IB |
@perrotta yes, it was a temporary workaround waiting for next IB, thank you anyway for reminding |
+xpog As said, this is a real bugfix. Do we have plans for backport? |
+1 |
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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
@ahinzmann Right! let me start the backport now -- 106, 102? |
@ahinzmann |
Well every NanoAOD production is affected, though the number of analyses is likely very small, and there is a way to work around it matching e.g. ak4 and ak8 jets. So this is a small improvement. Up to you what campaign shall take it into account. |
Do I understand correctly that this only affects variables stored in NanoAOD? If so, I think we should prepare the backports and hold them until we update the rest of NanoAOD code for the next round of production. It is not far away in time, in this way we can update both things at the same time and avoid inconsistencies until then. |
PR description:
Upon investigation into the issue reported here:
https://hypernews.cern.ch/HyperNews/CMS/get/physTools/3669.html
It seems that the muon fraction was not properly implemented for all jet types. This PR fixes the issue.
This affects the "lepveto" jetid value stored in NanoAOD.