-
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
Code to process phase2 version of deepTauID v2p5 [12_5_X] #40723
Code to process phase2 version of deepTauID v2p5 [12_5_X] #40723
Conversation
A new Pull Request was created by @mbluj for CMSSW_12_5_X. It involves the following packages:
@cmsbuild, @mandrenguyen, @clacaputo, @swertz, @vlimant can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
type tau |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-033c57/30503/summary.html Comparison SummarySummary:
|
+1 |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_5_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_0_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
Just a comment: to make this PR useful also cms-dist of 12_5_X should be updated to contain cms-data state with data-model of the new phase-2 integrated in, i.e. with PR cms-data/RecoTauTag-TrainingFiles#11 |
@@ -382,8 +382,8 @@ def _add_deepFlavour(process): | |||
toKeep = ['deepTau2017v2p1','deepTau2018v2p5'] | |||
) | |||
from Configuration.Eras.Modifier_phase2_common_cff import phase2_common #Phase2 Tau MVA | |||
phase2_common.toModify(tauIdEmbedder.toKeep, func=lambda t:t.append('newDMPhase2v1')) #Phase2 Tau isolation MVA | |||
phase2_common.toModify(tauIdEmbedder.toKeep, func=lambda t:t.append('againstElePhase2v1')) #Phase2 Tau anti-e MVA | |||
_tauIds_phase2 = ['newDMPhase2v1','againstElePhase2v1'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mbluj newDMPhase2v1
was not kept in the master version. Just to try to understand: why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mbluj
newDMPhase2v1
was not kept in the master version. Just to try to understand: why?
It has quite likely something to do with #40724 (comment), but I fail to find the connection (sorry...)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea is to to keep in master only phase-2 deepTauID ('deepTau2026v2p5') and remove/depreciate older, less powerful phase-2 tauIDs ('newDMPhase2v1' and 'againstElePhase2v1').
please test with cms-sw/cmsdist#8308 |
-1 Failed Tests: RelVals-INPUT RelVals-INPUTThe relvals timed out after 4 hours. Comparison SummarySummary:
|
+1 |
merge |
PR description:
This PR adds code for a phase-2 version of DeepTau discriminator; it is a backport of #40622.
The neural network structure of the new phase-2 version is identical to that of Run-2/3 DeepTau v2p5, therefore code modifications are small. The changes include:
slimmedElectrons
(gsfElectrons in EB) andslimmedElectronsHGC
(HGCal electrons in endcaps). Notes: 1. The latter collection is calledslimmedElectronsFromMultiCl
in older CMSSW release series (and samples produced with them) which can cause some problems with running on old samples; 2. The same merged electron collection is used by old-style anti-electron tau discriminant for phase-2;The performance of this new phase-2 DeepTau discriminator is documented in AN-22-090.
The new data-model was merged to cms-data in the following PR: cms-data/RecoTauTag-TrainingFiles#11
This PR allows to run the new version of DeepTau discriminator in private workflows (to analyse phase-2 samples with 12_5_X), but it does not enable the new version of DeepTau in official workflows. Therefore, differences in outputs are not expected.
To run standalone test, one can run the configuration file
RecoTauTag/RecoTau/test/runDeepTauIDsOnMiniAOD.py
after setting the flagphase2 = True
in that file.PR validation:
Validated with the standalone test mentioned above and with miniAOD workflows.
Backport PR
This is backport of #40622 to 12_5_X to facilitate tau studies for phase-2 with 12_5_X samples.