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
Update of DeepTauID to ver. 2017v2 #26796
Update of DeepTauID to ver. 2017v2 #26796
Conversation
Skeleton for DeepTau v2
motifications for the TauBlockInputs
Improved CellGrid implementation.
changes in the hadronBlock
Updates in the electron block
Changes in the muon block
Modificacion to add v2 in the python config
Currently tauID in MiniAOD samples is routinely (as part of RelVal campaigns) validated with standalone (python+ROOT-based) Tau POG tools, i.e. tools not integrated with central DQM workflows. We plan to add DeepTauID to these tools which is rather trivial task. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1
|
+1 |
+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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR updates DeepTauID to version 2017v2. The new version, thanks to revised structure of used DNN, fixes issues of version 2017v1 that is a size of training files and memory consumption are greatly reduced. Possibility to run previous version is maintained.
DeepTauID (2017v2) is added to the tau sequence in the standard MiniAOD workflow.
Performance with 1k ttbar events:
pat::PackedCandidate::dzError()
method which triggers unpacking of track covariance matrix and at smaller extend from initialization of TensorFlow. Full information on memory usage from IGProf can be accessed at this link: http://mdidomen.web.cern.ch/mdidomen/cgi-bin/igprof-navigator/changes_PR_126/DeepTau_memory_usage/;In addition the new v2 training overperforms (physics-result-wise) old v1 one as well as other TauIDs, details in slides:
Note 1: this PR is meant to be backported to 10_6_X for UL processing and to 10_2_X for using with current Run-2 samples.
Note 2: this PR is completed by PR to cms-data cms-data/RecoTauTag-TrainingFiles#3 which needs to be propagated to cms-dist.
Note 3: DeepTau 2017v2 is added to MiniAOD workflow with 11_0_X and 10_6_X (UL), while not in the backport to 10_2_X.
PR validation:
Validated with matrix tests; requires cms-data/RecoTauTag-TrainingFiles#3 for unit tests
if this PR is a backport please specify the original PR:
N/A