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 nanoAOD trigger bits for e+tau overlap filter #39099
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39099/31633
|
A new Pull Request was created by @adewit for master. It involves the following packages:
@cmsbuild, @mariadalfonso, @gouskos, @swertz, @vlimant 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-899932/26907/summary.html Comparison SummarySummary:
|
+xpog |
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:
Tau trigger bits for nanoAOD do not correctly store the e+tau cross trigger overlap filter, as this filter ends, e.g. in 2018, with
PFTau30
rather thanPFTau
. In the past the filter matching string correctly had*
at the end but in this update: https://github.com/cms-sw/cmssw/pull/38472/files it was removed. Adding it back here.FYI @mbluj @lwezenbe @kandrosov @danielwinterbottom (I don't have Anne-Catherine's github handle, can someone please tag her). Since nano v10 will close very soon I think we should try to get this fix in urgently which is why I went straight for the PR.
Spotted thanks to investigation by @PascalBaertschi.
PR validation:
Observed incorrect behaviour without the
*
at the end, previous runs with it included produced the correct results.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:
Not a backport.