You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't see that jets are skipped if they have an EM fraction above a threshold, as is done in CMSSW here, where the threshold is defined here to be 0.9.
Is this intentional, or something that needs to be implemented? In principle, this is already doable with the nominal jet collection since there are Jet_chEmEF and Jet_neEmEF branches, but this information is not available for the low pT jets in the CorrT1METJet collection.
Checking on some 2018 data events with a different framework for correction, I find that 0.7% of events will have a MET value that differs by >0.1GeV between applying this EM veto and not applying it.
The text was updated successfully, but these errors were encountered:
ifnot ( self.metBranchName=='METFixEE2017'and2.65<abs(jet.eta)<3.14andjet.pt*(1-jet.rawFactor)<50 ): # do not re-correct for jets that aren't included in METv2 recipe
When recalculating Type-1 corrected MET in this loop:
nanoAOD-tools/python/postprocessing/modules/jme/jetmetUncertainties.py
Line 256 in 6b4870f
I don't see that jets are skipped if they have an EM fraction above a threshold, as is done in CMSSW here, where the threshold is defined here to be 0.9.
Is this intentional, or something that needs to be implemented? In principle, this is already doable with the nominal jet collection since there are
Jet_chEmEF
andJet_neEmEF
branches, but this information is not available for the low pT jets in theCorrT1METJet
collection.Checking on some 2018 data events with a different framework for correction, I find that 0.7% of events will have a MET value that differs by >0.1GeV between applying this EM veto and not applying it.
The text was updated successfully, but these errors were encountered: