cms-jet / pfnano Goto Github PK

https://github.com/cms-jet/NanoAODJMAR/blob/bede8ed60911be15808d82c44781d2338cb05306/python/addBTV.py#L34

Updated b tag discriminators are not stored for AK8 (fat jet) although the function calls the correct models. At the same time, it works perfectly well for AK4 and AK8 Sub jets.

@alefisico
@andrzejnovak

Tracking issue

In medium-term horizon we should be able to run on 2015 Open Data - Open Data Portal

Initial work in #46

The XPOG conveners are now in favor of integrating into CMSSW to include the AK8 candidates in the default nano. Since this will be the primary use case, we propose the following naming:

AK8 PF Jets:

• FatJet: AK8 PFJets
• FatJetPFCand : Candidates associated to FatJets
• FatJetPFCandAssoc: Association between FatJetPFCands and FatJet.

AK8 Gen Jets:

• GenFatJet: AK8 GenJets
• GenFatJetCand : Candidates associated to FatJets
• GenFatJetCandAssoc: Association between FatJetPFCands and FatJet.

I wrote a validation script to check the associations in https://gist.github.com/nsmith-/b29c4f4a13214ed65b93bf2d5a65f955
But I notice a few branches are unavailable, or the association is buggy. This is an issue to track fixes.

I'm submitting crab jobs using the handler script, I have appropriately modified card_example.yml, but the --lumiMask argument does not work. I've tried placing it in different orders w.r.t --make and --submit but all attempts end in the same error.
I'm using the instructions here: https://github.com/cms-jet/PFNano#processing-data

$ python crabby.py -c card_example.yml --make --lumiMask jsons/Cert_314472-325175_13TeV_Legacy2018_Collisions18_JSON.txt --submit
usage: crabby.py [-h] [-c CARD] [--make] [--submit] [--status]
                 [--test {False,True}]
crabby.py: error: unrecognized arguments: --lumiMask jsons/Cert_314472-325175_13TeV_Legacy2018_Collisions18_JSON.txt

nB/C hadrons duplicate (probably after it was added in stock nano)

Taking a glance it looks some variables come associated from the baseline, but we're missing quite a few for BTV studies.

What we have:

• Jet <- Muons
• Jet <- Electrons
• Fatjet <- Muons
• Fatjet <- Electron
• Fatjet <- Subjets

What's missing:

• Jet <- Secondary Vertices
• FatJet <- Secondary Vertices
• SubJet <- Secondary Vertices
• SubJet <- Muons
• (SubJet <- Muons)

@XavierAtCERN

In general, I'm interested in using this format as a standard for training/re-training deep jet taggers. So it'd be nice to have a complete set of inputs (enabled with some flag).

• For DeepDoubleX, we're missing the 27 "jet-level" inputs that are the same as the ones used for the original double-b tagger. For example, they're listed here: https://github.com/cms-sw/cmssw/blob/CMSSW_10_6_X/DataFormats/BTauReco/interface/BoostedDoubleSVTagInfoFeatures.h (except one of them is not used).
• For DeepAK8, we're missing the track covariance matrix entries (possibly among a few others): https://github.com/cms-sw/cmssw/blob/CMSSW_10_6_X/RecoBTag/FeatureTools/plugins/DeepBoostedJetTagInfoProducer.cc#L76-L88)

I can try to help add these in a pull request, although I think I'll need some guidance. In particular, how can we add variables to the jet table?

@andrzejnovak