Global variables for each selection #285
Conversation
|
@kreczko, thanks for your PR! By analyzing the history of the files in this pull request, we identified @jjacob, @EmyrClement and @senkin to be potential reviewers. |
| *m_bl = utils::m_bl(bjets, lepton); | ||
| *angle_bl = utils::angle_bl(bjets, lepton); | ||
| } | ||
| *st = utils::st(jets, met, lepton); |
There was a problem hiding this comment.
Technically ST is defined if there are no leptons (or more than one lepton). However I guess our lowest baseline selection is at least one lepton, so I don't mind is this isn't changed.
There was a problem hiding this comment.
I went with the definition in our slides which always includes the lepton pT. I understand that there are more than one :).
|
Yeah, on second thought, that line is not clear. What I mean by object family is a set of jet, bjet, electron & muon inputs which is currently tied to the selections. However, you can also change the inputs to create the variables for JEC up/down! |
As part of the efforts to replace AS, I've added the global variabels to the ntuples.
This is done per 'object family' such that we have the variables per selection.
Of course, the global vars are only valid if you also check if the event passes the appropriate selection (e.g. HT is well defined for 1 jet).
Test ntuple can be found on soolin in
/storage/phxlk/eventUserData.root