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
Modification of configuration for boostedTau creation #15996
Modification of configuration for boostedTau creation #15996
Conversation
…RECO requiring muon used in the discriminator to be in the boosted tau area
…RECO added dump boosted taus
…au-RECO Conflicts: RecoTauTag/Configuration/test/QCD-validation.txt
A new Pull Request was created by @roger-wolf (Roger Wolf) for CMSSW_8_1_X. It involves the following packages: RecoTauTag/Configuration @cmsbuild, @cvuosalo, @slava77, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
@cmsbuild please test |
The tests are being triggered in jenkins. |
@cmsbuild please test |
The tests are being triggered in jenkins. |
+1 Small configuration change to improve boosted tau ID efficiency. The code changes are satisfactory, and Jenkins tests against baseline CMSSW_8_1_X_2016-09-28-1100 show no significant differences. A test of workflow 25202.0_TTbar_13 with 100 events against baseline CMSSW_8_1_X_2016-09-27-1100 also shows no significant differences. CPU time (without DQM or Validation) for the affected module appears to improve by almost 10%:
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar |
On 9/29/16 3:14 PM, Carl Vuosalo wrote:
Looks like the boosted taus are not monitored in miniAOD DQM.
this must be random the modified modules
|
+1 |
Dear all,
this is a PR with a minor modification of the configuration for the creation of boostedTaus. The only file that really has anything to do with the modification as such is
RecoTauTag/Configuration/python/boostedHPSPFTaus_cfi.py (lines 22 & 23)
The other files are part of a infrastructure that we use for our internal testing and validation (e.g. of this change), which has been extended to be able also to validate boostedTaus now.
The modification as such loosens the anti-muon discriminator requirement to be more efficient for the identification of boostedTaus. It has been verified that this increases the efficiency of the identification of boostedTaus in the relevant kinematic regimes, where two taus might be very close to each other. For non-boosted taus the expected behaviour is:
Usual tests have been made w/o notice of any problems.
Cheers,
Roger