Support multiple output TTrees
Analyses may wish to write multiple TTrees to optimise the content for different selections, e.g. lep/had vs had/had ditau decays.
The existing tree_cfg
function should already provide enough flexibility to specify:
- Different branch lists
- Different tree names
For this use case, the higher level
minituple_cfg
might not be used, as it would mandate the standard branch list.
Practically speaking, it is probably outside the scope of the central framework to fit the TTree scheduling together with analysis-specific selections, so this part calls for more bespoke configuration within the custom executables/analysis configuration.
That said, we should identify any other features that would make multiple TTree output simpler, e.g.:
- Restructuring the placement of the
THistSvc
configuration of the file name?- If we put this in the
tree_cfg
and add a file name argument, multiple calls would just merge duplicate output files, but also support multiple file output (could allow running a common ntuple production for several teams if at all desirable)
- If we put this in the
- Adding the capability to provide multiple output configurations in yaml that could handle the content specification, even if the user would have to call the output scheduling themselves