A. Dainese:
When creating the friend chain with the delta files (either by replacing the
file name or by relying on the path), one has to check that both AOD and deltaAOD files
exist in the catalogue, and only then add both to the respective chains.Otherwise you loose the correspondence. In principle this should granted by the validation, but may be not the case if the deltas are produced at a second stage.
At the moment, for vertexingHF, we use the macro $ALICE_ROOT/PWG3/vertexingHF/MakeAODInputChain.C to create the two chains, checking the file existence in the catalogue.
It would be very useful to have this check built in the framework(InputHandlers?).
A. Morsch:
If we have 2 chains A and B, and B is friend of A the two
chains can get out of synch if one of the friend files is missing.
The behavior is like in the following example
fileA1 fileB1 events 0 - 199
fileA2 fileB2 events 200 - 399
fileA3 fileB3 events 400 - 599
Let's assume fileB2 cannot be opened.
chainA->GetEntry(200)
gives a message
Error in <TFile::TFile>: file fileB2 does not exist
and gives you back entry 400
as chainA->GetEntry(400) does
The second time you call chainA->GetEntry(200) there is no error message
at all.
I wonder whether this is a bug or a feature. In any case this seems to be
rather unsafe in the grid world.
Decision:
AM contacts Rene to find a solution for the TChain implementation or usage.
Submitted as Savannah bug #53978