-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[14.0.X] Fix Phase2 ditau HLT path (with DeepTau Isolation) #43912
Conversation
A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_14_0_X. It involves the following packages:
@mandrenguyen, @mmusich, @Martin-Grunewald, @jfernan2, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
cms-bot internal usage |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-e4b495/37301/summary.html Comparison SummarySummary:
|
+hlt
|
type tau |
ping @cms-sw/reconstruction-l2 |
type bug-fix |
backport of #43855 |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @antoniovilela, @sextonkennedy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
backport of #43855
PR description:
This PR implements the usage of Phase2 DeepTau training for ditau Phase 2 trigger, which was integrated with #42562. In the integrated version, Run2 training files were used. The problem with this implementation has been fixed and this PR proposes this fix and necessary changes.
Hopefully it will fix the issue mentioned here: #42862
The related JIRA ticket is CMSHLT-3010
PR validation:
The basic tests has been performed, suggested in the CMSSW PR instructions.
There was no failed tests.
See also #43855 (comment).
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:
verbatim backport of #43855