-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Updated way to store DeepTau WPs in nanoAOD #38776
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
Updated way to store DeepTau WPs in nanoAOD #38776
Conversation
…WPs-nano-dev Test PR with DeepTau v2p5 WPs
…5-WPs-nano DeepTau v2p5 WPs @nanoAOD
…-tau-pog with cms-merge-topic
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38776/31114
|
|
A new Pull Request was created by @kandrosov (Konstantin Androsov) for master. It involves the following packages:
@gouskos, @clacaputo, @cmsbuild, @fgolf, @jpata, @mariadalfonso 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-c956ff/26309/summary.html Comparison SummarySummary:
|
|
@kandrosov we can close this PR, as is clear what the int vs bit mask does. (we cannot merge like this because the history will add the new ID, then remove them re-add again) |


PR description:
Splitting DM storage format related modifications into a separate PR. See #38726 and #38751 for details.
Following modifications are introduced:
_tauIdWPMask();from_rawargument in_tauIdWPMask()) given the threshold values, instead of reading them directly from MINIAOD;Change of the format of storing WPs affects all present tauIDs and thus is not backward compatible. For instance if old versions of nano (with old eras) were produced with this PR integrated they would have format which is not backward compatible with the same versions without this PR. We think, however, that there is not realistic use-case, i.e. old versions of nano are not produced with new releases. Keeping backward compatibility is possible, but implementation will be painful. Comments from experts are welcome.
Backport to 12_4_X foreseen.
PR validation: