Hi Daniele,

> > I tried to look into this a bit closer and I found out that the loss of so
> > many events is due to a stupid mistake by myself. Sorry in case I caused
> > confusion with this.
> > This does not explain the "Error in <TTree::Write>: No file open" and I
> > still do not understand where this comes from, but I do not see any harm
> > that is caused so far.
> >
> > Still it would be nice if those three reduced ntuples could find some
> > space at the AWG disk since then reading them with the VirVubFitter will
> > probably be smoother and not affected by the problem described in the last
> > mail.
>
> those files seem to be already in the AWG space (/AWG18/ISL/tmpa).

Ok, I see Alessio's file there. Can we put the other two signal MC files
there as well (1.1G together)?

> Probably you run too many fit jobs at the same time. This can cause the
> problem you mentioned.
> Did you try again? It is good to run 10-20 jobs maximum on the same files.

Today I ran two jobs at the same time and I see this, and I saw it earlier
when I ran only a few (below 10) as well.

> Another point. In order to avoid chaining the root files and double the
> required disk space, it would be nice to implement the possibility to read
> chain files (as for anaQA). I already implemented that for the exclusive
> fit (ExclFit and exclfitNtp). You could just cut and paste that in VirFit

To be honest I do not exactly know what you mean. I will need time for
writing up things now because my deadline is coming close. I will have a
look afterwards into that if that is ok.

Kerstin