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
We could have a more descriptive naming for the flag in the config file. Do I understand correctly that this is only for the jet correction reading and has no other effect?
If so we could call it readCorrFromTxt or readCorrFromDb so that it conveys better what is happening. PAT is CMS jargon and does not tell what is the actual difference.
But correct me if I'm wrong, I did not look in details, maybe it has other effects in resulting jets.
@katilp No, it's actually doing lots more. It is running the whole PAT sequence, so we could really use pat::muons, pat::electrons, pat::taus, etc. For now we're just using the pat::jet collection it creates, but the code becomes quite different for applying the corrections and also for interacting with b-tagging.
I will go through and make significantly more comments here in the config. Perhaps we could change the flag to "makePATobjects" or "makePATjets" or something.
caredg
changed the title
doPAT flag - CMS jargon?
doPAT flag - CMS jargon? (2012 branch)
May 5, 2022
We could have a more descriptive naming for the flag in the config file. Do I understand correctly that this is only for the jet correction reading and has no other effect?
If so we could call it readCorrFromTxt or readCorrFromDb so that it conveys better what is happening. PAT is CMS jargon and does not tell what is the actual difference.
But correct me if I'm wrong, I did not look in details, maybe it has other effects in resulting jets.
@caredg @jmhogan
The text was updated successfully, but these errors were encountered: