class AliReconstruction: public TSelector

 create reconstruction object with default parameters

 copy constructor

 clean up

Initialize the QA and start of cycle

Initialize the QA and start of cycle

 activate a default CDB storage
 First check if we have any CDB storage set, because it is used
 to retrieve the calibration and alignment constants

 Store the desired default CDB storage location
 Activate it later within the Run() method

 Store the desired default CDB storage location
 Activate it later within the Run() method

 Store a detector-specific CDB storage location
 Activate it later within the Run() method

 require the cdb item to be the same in the rec as in the sim
 Activate it later within the Run() method

 require the cdb item to be the same in the rec as in the sim
 Activate it later within the Run() method

 The method is called in Run() in order
 to set a correct run number.
 In case of raw data reconstruction the
 run number is taken from the raw data header

 Set CDB lock: from now on it is forbidden to reset the run number
 or the default storage or to activate any further storage!

 Translates detector name in a boolean.
 The boolean is used in GetReconstructor to load the
 upgrade reconstructor instead of the standard one.

 Read the alignment objects from CDB.
 Each detector is supposed to have the
 alignment objects in DET/Align/Data CDB path.
 All the detector objects are then collected,
 sorted by geometry level (starting from ALIC) and
 then applied to the TGeo geometry.
 Finally an overlaps check is performed.

 set the name of the galice file

 In case the input string starts with 'mem://', we run in an online mode
 and AliRawReaderDateOnline object is created. In all other cases a raw-data
 file is assumed. One can give as an input:
 mem://: - events taken from DAQ monitoring libs online
  or
 mem://<filename> - emulation of the above mode (via DATE monitoring libs)

 Set the output ESD filename
 'output' is a normalt ROOT url
 The method is used in case of raw-data reco with PROOF

 set options for the reconstruction of a detector

 Set custom reconstruction parameters for a given detector
 Single set of parameters for all the events

 Initialization of the GRP entry

 Load CDB entries for all active detectors.
 By default we load all the entries in <det>/Calib
 folder.

 Load CTP scalers from OCDB.
 The scalers are checked for consistency.

 Load CTP timing information (alignment)
 from OCDB.

 Load LHC DIP data

 Run Run Run

 Init raw-reader and
 set the input in case of raw data

 Initialization of raw-reader,
 run number, CDB etc.

 Initialize AlReconstruction before
 going into the event loop
 Should follow the TSelector convention
 i.e. initialize only the object on the client side

 Initialization related to run-loader,
 vertexer, trackers, recontructors
 In proof mode it is executed on the slave

 run the reconstruction over a single entry
 from the chain with raw data

 Implementation of TSelector::Init()
 method

 run the reconstruction over a single event
 The event loop is steered in Run method

 Finalize the run on the slave side
 Called after the exit
 from the event loop

 Create tags for the events in the ESD tree (the ESD tree is always present)
 In case of empty events the tags will contain dummy values

 run the local reconstruction

 run the SPD trackleting (for SPD efficiency purpouses)

 run the barrel tracking

 run the trackleter for multiplicity study

 run the muon spectrometer tracking

 run the barrel tracking

 Remove the data which are not needed for the physics analysis.

 fill the event summary data

 Reads the trigger decision which is
 stored in Trigger.root file and fills
 the corresponding esd entries

Scalers
fRunScalers->Print();

 Filling information from RawReader Header

 check whether detName is contained in detectors
 if yes, it is removed from detectors

 get or create the run loader

 get the reconstructor object and the loader for a detector

 create the vertexer
 Please note that the caller is the owner of the
 vertexer

 create the ITS trackleter for mult. estimation
 Please note that the caller is the owner of the
 trackleter

 create the trackers

 delete trackers and the run loader and close and delete the file

 Write space-points which are then used in the alignment procedures
 For the moment only ITS, TPC, TRD and TOF

 The method reads the raw-data error log
 accumulated within the rawReader.
 It extracts the raw-data errors related to
 the current event and stores them into
 a TClonesArray inside the esd object.

 return the detector index corresponding to detector

 Here execute all the necessary operationis, at the end of the tracking phase,
 in case that evaluation of PlaneEfficiencies was required for some detector.
 E.g., write into a DataBase file the PlaneEfficiency which have been evaluated.

 This Preliminary version works only FOR ITS !!!!!
 other detectors (TOF,TRD, etc. have to develop their specific codes)

  Input: none
  Return: kTRUE if all operations have been done properly, kFALSE otherwise

 Here execute all the necessary operations, before of the tracking phase,
 for the evaluation of PlaneEfficiencies, in case required for some detectors.
 E.g., read from a DataBase file a first evaluation of the PlaneEfficiency
 which should be updated/recalculated.

 This Preliminary version will work only FOR ITS !!!!!
 other detectors (TOF,TRD, etc. have to develop their specific codes)

  Input: none
  Return: kTRUE if all operations have been done properly, kFALSE otherwise

 This method should be called only in case
 AliReconstruction is run
 within the alieve environment.
 It will initialize AliEVE in a way
 so that it can visualize event processed
 by AliReconstruction.
 The return flag shows whenever the
 AliEVE initialization was successful or not.

 Runs AliEVE visualisation of
 the current event.
 Should be executed only after
 successful initialization of AliEVE.

 Allows to run QA for a selected set of detectors
 and a selected set of tasks among RAWS, DIGITSR, RECPOINTS and ESDS
 all selected detectors run the same selected tasks

 The method accesses OCDB and retrieves all
 the available reco-param objects from there.

 Fill the event info object

 Match the detector list found in the rec.C or the default 'ALL'
 to the list found in the GRP (stored there by the shuttle PP which
 gets the information from ECS)

 Abort processing. If what = kAbortProcess, the Process() loop will be
 aborted. If what = kAbortFile, the current file in a chain will be
 aborted and the processing will continue with the next file, if there
 is no next file then Process() will be aborted. Abort() can also  be
 called from Begin(), SlaveBegin(), Init() and Notify(). After abort
 the SlaveTerminate() and Terminate() are always called. The abort flag
 can be checked in these methods using GetAbort().

 The method is overwritten in AliReconstruction for better handling of
 reco specific errors

 Method that is used in case the event loop
 is steered from outside, for example by AMORE
 'event' is a pointer to the DATE event in the memory

 The method parses the output file
 location string in order to steer
 properly the selector

 Selection of events containing "high" pT tracks
 If at least one track is found within 1.5 and 100 GeV (pT)
 that was reconstructed by both ITS and TPC, the event is accepted

 Select cosmic or calibration events

 Fill the ESD friend in the tree. The required fraction of ESD friends is stored
 in fFractionFriends. We select events where we store the ESD friends according
 to the following algorithm:
 1. Store all Cosmic or Calibration events within the required fraction
 2. Sample "high Pt" events within the remaining fraction after step 1.
 3. Sample randomly events if we still have remaining slot

 delete requested digit files produced at current event

 delete requested recpoint files produced at current event

 require checking the resources left and stopping on excess
 if 0  : no check is done
 if >0 : stop reconstruction if exceeds this value
 if <0 : use as margin to system limits

 check if process consumed more than allowed resources

 if some CDB entries must be the same in the simulation
 and reconstruction, check here

 TBD RS
 remove everything but the url

*** Global reconstruction flag setters

 Trackers

 Quality Assurance

 Plane Efficiency Evaluation

 Upgrade

 Connection to analysis manager.
 If a macro is set it should contain a function returning an analysis
 manager object. The macro is ignored in case the analysis manager is
 set via SetAnalysisManager

 A method to declare defined trigger classes even if they are not
 present in the run, needed for proper event selection based on trigger