What happens is that I get several copies of the tree in the same file. I only want one copy of it, but it seems to duplicate itself. If the chain that I am copying is called FullRec0 I get in my new file trees called f.ex.
FullRec,21 and FullRec,22
I only want one tree called FullRec.
A short version of the code I am using is attached.
[quote]I only want one tree called FullRec. [/quote]Per se that is what you have . This is actually one backup copy and one final copy of the meta data of the TTree (and not of the data). (Those are technically called ‘cycles’ (see the user’s guide for details)).
You can callmyfile->Purge();to remove the backup copy.
Yes, maybe this is just the backup copy. What has confused me though is that the trees now how f.ex. FullRec0;21 and FullRec0;22 instead of FullRec0;1 and FullRec0;2. I have an idea that it can be because I add so many root files in the chain. But If I add f.ex. 36 root files into the chain I do not get FullRec0;36, but f.ex. FullRec0;22. It is just a little odd.
So you think my code is doing what it is supposed to do, and not duplicating things unnessecary?
[quote]So you think my code is doing what it is supposed to do, and not duplicating things unnessecary? [/quote]Indeed
[quote]I do not get FullRec0;36, but f.ex. FullRec0;22. It is just a little odd. [/quote]The number of time it is saved depends on data size and not on the number of input files (see TTree::SetAutoSave).
. This is actually one backup copy and one final copy of the meta data of the TTree (and not of the data). (Those are technically called ‘cycles’ (see the user’s guide for details)).