AliAODEvent::GetHeader now return AliVHeader This required patching the base classes in a few places and moving some of the NanoAOD to STEER/AOD and checking which actual header is contained in the AODEvent class in a few places. This commit does not compile (analysis tasks which use AliAODEvent::GetHeader still need to be patched)
ESD and AOD tracks contain a transient pointer to the event to which they belong (if not detached). Event pointer gets connected automatically if using event handlers, otherwise the user has to call event->ConnectTracks() AFTER reading the tracks branch for the current event. Individual event setters per track will be overwritten when the track will be added to some event, so their direct usage is not reccommended. To get the event pointer use AliVTrack::GetEvent. The implementation followed the discussion on http://savannah.cern.ch/bugs/?93685
Patch allowing to run analysis on a chain with file names different than AliESDs.root of AliAOD.root. The input file name is detected from the chain. If this is needed earlier than AliAnalysisManager::StartAnalysis() it has to be explicitely set by hand via mgr->GetInputEventHandler()->SetInputFileName()
From Pietro: Added AliInputEventHandler::GetUserInfo to get the user info in ESD and AOD analysis. Added AliProdInfo class to parse the user info to decode production metadata. To use: in myTask::Notify() one has to get the pointer to the input handler (mgr->GetInputEventHandler() and: AliProdInfo pi(handler->GetUserInfo()), then use the getters to retrieve the metadata