With add friend the name of the TTree is implicit part of the branch name, so no need to change the actual branch names.
Yes, that is characteristic to both between friends in a tree containing samely-named objects and between branches in a tree containing samely-named objects. But this seems to again highlight the philosophy “you have the file as it is now, so whether or not it should been structured that way to begin with, just use friends”. I am trying to broaden my toolkit of methods to use with ROOT data management. Is this not enough of a reason as to why I would like see this particular method? In terms of long term concerns, does it help to know that this file will be standalone and not part of a larger framework?
It is used in the implementation of TBranchClones to implement split of objects.
I have found little in the way of how to implement TBranchClones, although your response here seems to suggest it relates to my problem at hand. Has progress been made in implementing the related topic of “merging laterally two files”, or is the method still to use GetEntry and Fill?
Best,
John