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
Fix uppermost bin edge handling in non-linear lookup of JEC bins #34382
Conversation
…CorrectorParameters::binIndex()
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-34382/23770
|
A new Pull Request was created by @kirschen (Henning Kirschenmann) for master. It involves the following packages: CondFormats/JetMETObjects @ggovi, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c67dc9/16731/summary.html Comparison SummarySummary:
|
+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. @silviodonato, @dpiparo, @qliphy, @perrotta (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Addresses the issue raised in
#34381
Expected change:
only affects the uppermost bin edge (e.g. often 5.191 in eta-binned JEC), now excluding it from the evaluation instead of including it. Should restore the previous behavior of the linear look-up and aligns with the correctionlib lookup used in
https://github.com/cms-jet/JECDatabase/tree/master/scripts/JEC2JSON
PR validation:
Ran local tests on consistency between new "JSON corrections" and cmssw. Now get full consistency over a scan of input parameters including bin-boundaries, out-of-range, etc. cases.