Use ConfigBlocks to automatically keep track of output branches
Once the CP lags are migrated to ConfigBlocks
via !257 (closed) we should use their ability to keep track of the core output branches rather than keeping track of your own list. The variables stored can be seen at
https://acode-browser.usatlas.bnl.gov/lxr/search?%21v=head&_filestring=.py&_string=addOutputVar
and these can be retrieved from the ConfigAccumulator
via getOutputVars
like so
This list should be passed to the BranchManager
, which should take care of constructing the output string after any further manipulation needed. The BranchManager
will still deal with additional branches, though could do this internally by carrying them around on a ConfigAccumulator
.
Note: by default the ConfigBlocks
only treat pT (not eta, phi, charge) as systematic-dependent.