Re: TChain of bad files

Dear Rene,
thanks for your answer. If this is not a big deal I would ask for such an option.
Just an example when it might be usefull: in some applications root file may contain
working material + some debug information (histos, etc). If the file was not closed
(the process was killed because of time exceeded for example) then root tries
to recovery not only those usefull material but also the debugging information. When
one tries to make a chain of many files root consumes a lot of time in attempts to recover
all these things releasing also a lot of warning messages. It might be usefull if root
instead could label such files as suspicious which eventually must be reprocessed.

This is just a naive opinion, I do not insist on this option... Dmitry

Rene Brun wrote:

> Hi Dmitry,
>
> There are two kinds of "bad" files: recoverable or not recoverable.
> The recoverable files are typically files that have not been closed by
> the application, but the material written to this file is usable
> if the autoupdate mechanism of Trees had been used.
>
> When you call TChain::Add(filename,nentries), you can specify
> nentries<=0 (see doc). In this case, a non recoverable file will
> not be added to the chain definition.
> Currently the files that are recoverable are always recovered.
> One could add an option to not recover these files.
>
> Rene brun
>
> On Wed, 22 Jun 2005, Dmitry Naumov wrote:
>
>> Dear ROOTers,
>>
>> is there a simple solution to the following problem:
>> I have a list of root files which I chain together. Some of these
>> files might be corrupted and I do not want to use root
>> recovering mechanism for them - I better ignore these files.
>> Is is possible to automatically disable (not connect to the chain) these
>> bad files ?
>>
>> Thank you in advance,
>> Dmitry
>>
Received on Fri Jun 24 2005 - 19:24:46 MEST