PF-based b-taggers in the standard Reco

[ferencek]

This PR is the first step toward replacing the legacy with PF-based b-taggers. Here, the PF-based b-taggers are added to the standard Reco sequence alongside the legacy b-taggers. In subsequent PRs validation, PAT, etc. need to be switched to the PF-based taggers and finally the legacy taggers will be removed from the standard Reco sequence.

In the attached plots and in https://indico.cern.ch/event/359461/session/0/contribution/2/material/slides/0.pdf performance comparison between the legacy and PF-based taggers can be seen.

Legacy vs PF-based taggers from MiniAOD

[cmsbuild]

A new Pull Request was created by @ferencek (Dinko Ferencek) for CMSSW_7_4_X.

PF-based b-taggers in the standard Reco

It involves the following packages:

FastSimulation/ParticleFlow
PhysicsTools/PatAlgos
RecoBTag/Configuration
RecoBTag/ImpactParameter
RecoBTag/SecondaryVertex
RecoBTau/JetTagComputer
RecoParticleFlow/Configuration

@civanch, @nclopezo, @lveldere, @mdhildreth, @monttj, @cmsbuild, @StoyanStoynev, @slava77, @vadler can you please review it and eventually sign? Thanks.
@TaiSakuma, @imarches, @ahinzmann, @acaudron, @mmarionncern, @rappoccio, @lgray, @Martin-Grunewald, @nhanvtran, @schoef, @ferencek, @matt-komm, @mariadalfonso, @pvmulder, @bachtis this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.

[ferencek]

@cmsbuild please test

[slava77]

please test

[cmsbuild]

The tests are being triggered in jenkins.

[slava77]

I'm not sure it's particularly practical to define so many almost identical cfi files.
If you decide to add some common parameters to JetTagProducer, the maintenance will be more costly than having one default and cloning with replace from it.

[ferencek]

For the JetTagProducers cloning would not be that useful since all parameters are typically updated. So these I won't modify.

[cmsbuild]

+1
Tested at: b931dd8
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7041/1761/summary.html

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7041/1770/summary.html

[slava77]

+1

for #7041 1cd5296

tested in CMSSW_7_4_X_2015-01-07-1000 (test area sign484)

new products appear as expected from

• pfInclusiveSecondaryVertexFinderTagInfos
• inclusiveCandidateSecondaryVertices
• pfCombinedInclusiveSecondaryVertexV2BJetTags
• pfJetBProbabilityBJetTags
• pfCombinedMVABJetTags
• pfJetProbabilityBJetTags
• pfTrackCountingHighEffBJetTags
• pfTrackCountingHighPurBJetTags
• pfSimpleSecondaryVertexHighEffBJetTags
• pfSimpleSecondaryVertexHighPurBJetTags

the cost for AOD (ttbar PU35@25ns) is ~ 0.2%;
CPU additions are driven by the inclusive vertexing with candidates and takes 0.4% of RECO, which is a bit too much.
Since this is temporary, it's OK for now.

[slava77]

@monttj
TaeJeong, please check, we need your signature here.
Thank you.

[monttj]

+1
I see it is already merged. I am sorry for being late.