Switching off reconstruction of so called "NullTaus" #17706
Conversation
…ect on losely seleced taus
Add an additional requirement that PFChargedHardon exists. It protects against poor taus build around RecoTauChargedHadron candidates with a poor track which usually have null or very small momentum.
…pog-removeNullTaus
|
A new Pull Request was created by @cmsbuild for master. It involves the following packages: RecoTauTag/Configuration @cmsbuild, @cvuosalo, @slava77, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here #13028 |
|
@cmsbuild please test |
|
The tests are being triggered in jenkins. |
|
@mbluj |
|
Yes, sorry, I pushed to incorrect repository. It will be solved tomorrow as I have to leave now. Anyway, it is not urgent as this goes to 91X anyway. |
|
-1 You can see the log for git cms-merge-topic here: |
|
Closing as mentioned in #17767 Michał |
|
-1 |
Hi all,
this is a simple configuration switch to remove the so called "null-taus" from the tau reconstruction. Null taus are jets seeding tau candidates, which actually do not fulfil any good tau reconstruction criterion. In the past these had been kept in the reconstruction for debugging purposes, since it allows a 1:1 correspondence of reconstructed tau candidates with seeding jets. In the meantime this should be switched to False when running in standard reconstruction. For more details refer to @mbluj.
NB:
we have split this change off from #17620 for clarity reasons. See also discussion in the conversation there.
Cheers,
Roger
Automatically ported from CMSSW_9_0_X #17643 (original by @cms-tau-pog).
Please wait for a new IB (12 to 24H) before requesting to test this PR.