Fix - clean (remove) run's reconstructed directory after reco/viz


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57790 f7af4fe6-9843-0410-8265-dc069ae4e863
changes from fzhou


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57791 f7af4fe6-9843-0410-8265-dc069ae4e863
test


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57792 f7af4fe6-9843-0410-8265-dc069ae4e863
test if I have commit rights


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57793 f7af4fe6-9843-0410-8265-dc069ae4e863
geometry for 2010/11


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57794 f7af4fe6-9843-0410-8265-dc069ae4e863
Updates: store track filter bit and charge, event pool for K0 and K, new featured in D* correlation task (Sandro)


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57795 f7af4fe6-9843-0410-8265-dc069ae4e863
added efficiency task for Balance Function (ESD-MC analyis), added V0 analysis for triggered Balance Function task


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57796 f7af4fe6-9843-0410-8265-dc069ae4e863
changes from saiola


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57797 f7af4fe6-9843-0410-8265-dc069ae4e863
changes from mconnors


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57798 f7af4fe6-9843-0410-8265-dc069ae4e863
Possibility to select positive and negatiev eta regions for D+


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57799 f7af4fe6-9843-0410-8265-dc069ae4e863
Fix when called from CINT


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57800 f7af4fe6-9843-0410-8265-dc069ae4e863
The train setup can now find the available packages
(ROOT,AliROOT) by it self.  Passing the value 
"last" to the options --aliroot and --root will
select the last possible version(s).  If the value
"list" is passed, then a list of available packages
will be displayed and the execution stopped. 

Also set default values on options in case of 
--help is passed.


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57801 f7af4fe6-9843-0410-8265-dc069ae4e863
changes from fzhou


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57802 f7af4fe6-9843-0410-8265-dc069ae4e863
Multiple fixes: 

- Use TParameter<T> for storing parameters of the 
  analysis rather than TNamed.  TNamed cannot be 
  merged which results in a huge overhead of 
  objects and time when merging containers with
  objects of that class.  TParameter<T> can be 
  merged and should not imply this overhead. 
- Fix memory leak and very inefficient and wrong code when
  inspecting the trigger words in AliFMDEventInspector.
  - The previous code (by Alexander) tokenized every 
    defined trigger class (from the physiscs selection)
    on every event, but the returned TObjArray was never
    free'd - which causes a memory leak. 
  - The code was wrong, because the trigger classes
    where only tokenized to get the positive and 
    negative parts, and then the found trigger word
    was compared the positive part.  However, the 
    positive part can consist of many words 
    (separated by commas) and so the comparison 
    would always fail.  
  - The code was inefficient, since the classes 
    where inspected on each event.  Since the 
    trigger classes are constant over a run, 
    it is much more efficient to cache the 
    positive words up front (on the first event
    say). 
  The new implementation caches the positive 
  words for both collision and background triggers
  on the first event.  For each event, we then 
  loop over these cached words and compare those
  to the found trigger word of the event.  In this
  way, we only tokenize the trigger classes once
  (actually, twice per class - one to get the 
  positive list, one to get the individual words)
  and we make sure we clean up the memory.  In each
  event we can do simple comparisons (using the 
  AliESDEvent supplied methods), and thereby 
  speed up the code.  We also avoid hidden memory
  leaks and overly many allocations this way. 
- Other clean up in the event inspector, so that all
  MC specific stuff is done in the derived class 
  AliFMDMCEventInspector. 
- Code in the event inspector has been re-factored 
  into separate member functions for clear structure
  and easier maintaince. 
- Debug statements added in various places to help
  identify problems (conditional on verbosity level
  of AliAnalysisManager)
- AliDisplacedVertexSelection had duplicate code
  in the member functions for the vertex and 
  centrality.  This has been unified into a 
  single member function Process that should be 
  called early in each event.  This will set 
  internal member variables which can be retrieved
  using GetVertexZ and GetCentralityPercentile. 

IMPORTANT CHANGE FOR SATELITTE EVENT ANALYSIS: 

  The AliFMDEventInspector when run over MC no 
  longer tries to subsitute the IP z coordinate 
  and centrality with information directly from
  the simulation.  Instead, this information is 
  available from the 
  AliFMDMCEventInspector::ProcessMC member function.


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57803 f7af4fe6-9843-0410-8265-dc069ae4e863
support for central and semicentral triggers


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57804 f7af4fe6-9843-0410-8265-dc069ae4e863
version for PWGLF approval


git-svn-id: https://alisoft.cern.ch/AliRoot/trunk@57805 f7af4fe6-9843-0410-8265-dc069ae4e863