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
Updates towards enabling deepTauID at HLT #35619
Updates towards enabling deepTauID at HLT #35619
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35619/25891
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
198cbe8
to
3a1f7a2
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35619/25892 |
A new Pull Request was created by @mbluj for master. It involves the following packages:
@jpata, @missirol, @cmsbuild, @Martin-Grunewald, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
@mbluj I left a couple of style suggestions inline. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d694b0/19562/summary.html Comparison SummarySummary:
|
@missirol - thank you for comments - I plan to work on them today. Concerning squashing the commits into one - I am not fan of this as tidying history means losing history. I can try to clear the history a bit, but I do not see big advantage of it. |
44d0e5c
to
b13a1b3
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35619/26022
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d694b0/19708/summary.html Comparison SummarySummary:
|
+hlt |
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 (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR contains a set of changes needed to enable deepTauID at HLT:
L1THLTTauMatching
) updated to produce (depending on a python configuration argument) either PFTaus with all data members filled for further processing or "empty" PFTaus with only p4 and vertex information filled which is minimal information needed for filtering;deepTauBase
;deepTauAtHLT.py
customisation file updated to simulate a full di-tau paths with deepTauID for measurements needed before integration with an actual HLT menu. Module names in the customisation file adapted to not cause unwanted overlap with other paths/sequences; Implemented proper deepTauID working points for HLT which are a function of tau pt.The PR is targeting 12_1_0 to allow tests and then integration with HLT for Run3.
PR validation:
The PR has been validated on top of 12_1_0_pre4:
DeepTauID modules have been run both for offline and online (with the two customisation functions) and run smoothly without unexpected surprises in the output. Results with standard workflows containing deepTauID (miniAOD) are expected to not change.
The following command has been run to perform tests, which all succeeded:
if this PR is a backport please specify the original PR and why you need to backport that PR:
N/A