The b-tagging algorithms store some intermediate dynamic variables in the EDM. In general these have a form like
ALGORITHM is a group like
VARIABLE is some discriminant that algorithm adds.
This merge moves few variables that should be considered part of
JetFitterSecondaryVertex into that group. Moving them isn't strictly necessary but should avoid confusion in the future. Specifically the following variables are changed:
minimumTrackRelativeEta -> JetFitterSecondaryVertex_minimumAllJetTrackRelativeEta maximumTrackRelativeEta -> JetFitterSecondaryVertex_maximumAllJetTrackRelativeEta averageTrackRelativeEta -> JetFitterSecondaryVertex_averageAllJetTrackRelativeEta
I think @jshlomi originally came up with these variables, maybe he has a better suggestion for what to call them.
As far as I know these variables are only used in two places:
- monitoring (@cmilke take note, I touched some of your code)
- training high level taggers like DL1 (should be easy to accommodate in the downstream code)
This is also a minor bugfix: there were some extra variables stored in the trigger outputs that we no longer fill.