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 was debugging differences in UL re-miniAOD between 106X and 112X, and was puzzled by the somewhat small but numerous changes in slimmedMETsNoHF UnclusteredEnUp/Down.
If I understood correctly (although I did not add any debug printouts to confirm), the problem is that the "NoHF" is based on noHFCands, which are copies (not Ptrs) of the original PF cands
So, the CandPtrProjector can not match the vetoing electron's sourceCandidatePtr (the original particleFlow) to the noHFCands (another check by the cand's sourceCandidatePtr may suffice though).
So, either we
need an extension in CandPtrProjector to also check for the main collection sourceCandidatePtr
or instead have useDeltaRforFootprint = True for all MET variants with copied candidates;
I was debugging differences in UL re-miniAOD between 106X and 112X, and was puzzled by the somewhat small but numerous changes in slimmedMETsNoHF UnclusteredEnUp/Down.
If I understood correctly (although I did not add any debug printouts to confirm), the problem is that the "NoHF" is based on
noHFCands
, which are copies (not Ptrs) of the original PF candscmssw/CommonTools/ParticleFlow/interface/GenericPFCandidateSelectorDefinition.h
Lines 31 to 34 in 3402e09
So, the CandPtrProjector can not match the vetoing electron's sourceCandidatePtr (the original particleFlow) to the
noHFCands
(another check by the cand's sourceCandidatePtr may suffice though).So, either we
useDeltaRforFootprint = True
for all MET variants with copied candidates;@ahinzmann @camclean @alefisico
The text was updated successfully, but these errors were encountered: