Hi Robert,
Hum ! It seems that you have a funny logic.
You can always do something like:
for (i=0;i<nentries;i++) {
mytree.SetBranchStatus("*",1);
mytree->GetEntry(i);
mytree->SetBranchStatus("*",0);
call_analysis_code();
}
Rene Brun
Robert Zitoun wrote:
>
> Hi Rooters
>
> I have very big rootuples which I cannot reprocess. In order to save time
> in macros, we load only specified branches whereever we need them with
> "branch->GetEntry(ientry);"
>
> Once many method have been written, we have discovered that, from time to
> time, one of the variables in branch "branch" is wrong. It is easy to
> write a new method which modifies it. However, some already written
> methods reopen "branch" with a new "branch->GetEntry(ientry);" so that the
> modified variable is replaced by the wrong one.
>
> Is there a way after the correction has been made to prevent reloading the
> branch later on?
>
> Or, is there a more clever way to avoid the problem without changing the
> already written methods?
>
> Robert.
This archive was generated by hypermail 2b29 : Sat Jan 04 2003 - 23:50:49 MET