I think that TTree::Branch(“foldername”) is an interesting feature but wonder if it can be inverted such that when a tree created in that fashion is read in from disk the folder heirarchy is restored. The motivation is to allow for rather free-form DSTs which can also be filtered down by simply removing some of the heirarchy before writing to disk again (e.g. mini DST -> micro DST).
Also I find that if a flolder is included as a class variable:
class my_record : public our_records {
private:
TFolder* folder;
};
then folder branch is not split up like TTree:Branch(“foldername”). Is there anyway to change that behaviour? The questions above could also be applied to TTree::Branch(TCollection").
I agree with this and about to implement this feature 3 years ago
when I realized that it is more difficult than at a first glance.
[quote]Also I find that if a flolder is included as a class variable:
class my_record : public our_records {
private:
TFolder* folder;
};
then folder branch is not split up like TTree:Branch(“foldername”). Is there anyway to change that behaviour? The questions above could also be applied to TTree::Branch(TCollection"). [/quote]
In this example TFolder* folder is considered like a normal class.
You have to go via the TTree::Branch function accepting a folder as input.
Although this could be supported by the split algorithm, we have no plans
to implement it in the foreseable future.