A modification was recently introduced in ANALYSIS trunk that automatically creates...
authorfca <fca@f7af4fe6-9843-0410-8265-dc069ae4e863>
Wed, 18 Feb 2009 11:24:35 +0000 (11:24 +0000)
committerfca <fca@f7af4fe6-9843-0410-8265-dc069ae4e863>
Wed, 18 Feb 2009 11:24:35 +0000 (11:24 +0000)
commit861795a81f8c4b101265ca2640e88f2dfdb4e4c0
tree67db167915834cc6e01ce5919bfb3e9e82497633
parent3635f34f7e01909b0dc493f23966a4c9a6f11068
A modification was recently introduced in ANALYSIS trunk that automatically creates input and output containers when connecting and input/output event handlers to the analysis manager. Users using the trunk should not create these containers themselves like:

cin = mgr->CreateContainer("cInput", TChain::Class(), AliAnalysisManager::kInputContainer);
mgr->ConnectInput(myTask, 0, cin);

But rather:

mgr->ConnectInput(myTask, 0, mgr->GetCommonInputContainer());

The same applies for the common output AOD container. The reason for this is that user tasks will be able to connect to an analysis manager and data containers created in a different steering macro (train).
16 files changed:
FMD/analysis/RunAliEnFMDAnalysisSE.C
FMD/analysis/RunLocalFMDAnalysisSE.C
HMPID/AliHMPIDAnalysisTask.C
JETAN/JetAnalysisManagerCAF.C
JETAN/JetAnalysisManagerLoc.C
PWG0/dNdEta/run.C
PWG0/esdTrackCuts/run.C
PWG0/multiplicity/run.C
PWG1/Macros/taskComp.C
PWG1/comparison/runProofCheckESD.C
PWG1/comparison/runProofITSComparison.C
PWG1/comparison/runProofTOFComparison.C
PWG1/comparison/runProofTPCComparison.C
PWG1/comparison/runProofTRDComparison.C
TPC/macros/CalibrateTPC.C
TPC/macros/TestV0.C