1) AliAnalysisTaskESDMuonFilter.h --> analysis task to copy the muon information from the ESD to the standard AOD
2) AliAnalysisTaskESDMuonFilter.cxx --> analysis task to copy the muon information from the ESD to the standard AOD
-In order to test locally the analysis train from the ESD to the Standard AOD production, the following macro is provided
-
-1) AnalysisTrainMuonLocal.C
- - The input file is the ESD
- - The outputs are the standard AOD and the AOD tag file
+In order to test the analysis train from the ESD to the Standard AOD production, the following macro is provided:
+
+ AnalysisTrainFromESDToAOD.C
+
+Input file: ESD
+Output files: standard AOD (+AOD tags)
+
+Two wagons are attached to the analysis train:
+ 1) $ALICE_ROOT/ANALYSIS/macros/AddTaskESDFilter.C
+ 2) $ALICE_ROOT/PWG3/muon/AddTaskTagCreation.C
+
+Several flags can be activated:
+ 1) iESDfilter: to activate, using AddTaskESDFilter.C, the copy of the ESD information into the AOD.
+ In AddTaskESDFilter.C there is the possibility to apply cuts on the tracks and muon tracks in order
+ to reject them before filling the AOD.
+ 2) iAODAddMCBranch: to activate the inclusion of the MC branch (containing Kinematics info) into a branch of the AOD
+ 3) iAODTagCreation: to activate, using AddTaskTagCreation.C, the AOD tag creation
+
+Runninng options tested:
+ 1) GRID (with/without AliEn plugin)
+ 2) LOCAL
+
+If the AliEn plugin is required, the macro
+ CreateAlienHandler_FromESDToAOD.C
+can be used, in order to configure the jdl.
+
+AnalysisTrainFromESDToAOD.C is an updated version of the macro AnalysisTrainMuonLocal.C
+(input file: ESD, output files standard AOD and the AOD tag file)
+The main differences are related to implementations to be compliant with the analysis framework,
+possibility to run on the grid with/without the Alien Plugin and possibility of adding the MC truth in a branch of the AOD.
+
+The macro ReadAOD_MCBranch.C is an example on how to access MC information stored in the AOD.
===================================================
Creation of the MUON-AOD from the standard AOD
corresponding field map is selected by looking at the value of the L3 current
stored in the GRP database which was used for the reconstruction.
+===================================================
+ Analysis task to correlate ESD tracks to their corresponding Monte Carlo data.
+ Artur Szostak, INFN
+---------------------------------------------------------------
+
+The AliAnalysisTaskLinkToMC analysis task is used to correlate reconstructed tracks
+found in ESDs to their corresponding MC track information found in the kinematics
+tree. The the same algorithm is used as in MUON/AliMUONRecoCheck but without any
+dependancy on MUON library code. This analysis task will copy out ESD MUON track
+information into the AOD like AliAnalysisTaskESDMuonFilter does, however the MC
+track label in the AOD track class is filled with the label of the corresponding
+MC track. Thus, subsequent analysis tasks can easily find the correct MC track from
+the label.
+
+Files:
+
+AliAnalysisTaskLinkToMC.h - The header file for the analysis task code.
+AliAnalysisTaskLinkToMC.cxx - The source file for the analysis task code.
+
+RunLinkToMCAnalysisExample.C - An example macro for running the analysis task in
+ local mode over simulated data. The macro takes one argument which is the name
+ of the ESD file to process. By default it uses AliESDs.root in the current working
+ directory.
+
+PlotEfficiency.C - This macro can be used to quickly check the control histograms
+ which are generated by RunLinkToMCAnalysisExample.C by default. The macro simply
+ calculates the reconstruction efficiency from the found and findable track histograms
+ that are filled by the analysis task.
+
+How to run:
+
+To run the analysis task in local mode with the example macro simply run the command
+ $ root RunLinkToMCAnalysisExample.C\(\"AliESDs.root\"\)
+where AliESDs.root can be replaced with the full path and name of the appropriate ESD
+file you wish to process. This command can also be run via AliRoot.
+
+
+===================================================
+ Analysis task to create mixed AOD events, containing a
+ pair of muon tracks coming from two different real AOD events.
+ Alessandro De Falco and Antonio Uras, INFN Cagliari
+---------------------------------------------------------------
+
+IMPORTANT: The AliAnalysisTaskCreateMixedDimuons analysis task needs
+ the class AliEventPoolMuon.
+
+In class AliEventPoolMuon the definition of the pools to be used
+in the mixing is implemented. Up to now, it is possible to create
+pools diving events by:
+ - total multiplicity
+ - forward muons multiplicity
+ - z-position of the primary vertex
+
+In class AliAnalysisTaskCreateMixedDimuons the mixing is performed between
+each pair of events which can be built up picking events from the internal
+buffer: if the buffer contains n events, n(n-1)/2 mixed events are created
+within the same call of the task.
+
+Some more details:
+ - the mixing task asks a completely fresh buffer for each call
+ - the mixing task creates output events from scratch
+ - output events are filled with two muon tracks (picked randomly
+ from the events being mixed and a vertex having its z-position in the middle
+ of the z-vertex bin defining the pool. Due to technical reasons,
+ the tracks are NOT connected with the vertex
+ - standard AOD are created as output, nearly completely empty
+
+Files:
+
+AliAnalysisTaskCreateMixedDimuons.(h,cxx) - The analysis task class.
+AliEventPoolMuon.(h,cxx) - The class implementing the pool.
+
+AnalysisTrainCreateMixedDimuons.C - An example macro enabling connections between
+the pool manager, the input event handler, the input and output containers,
+via the Analysis Manager. Input arguments: - directory containing AOD tag file
+ - name of the output file
+ - number of events to be loaded
+ in the internal buffer
+
+How to run:
+
+To run the analysis task in local mode with the example macro, simply run
+the AnalysisTrainCreateMixedDimuons.C macro (without compiling it) with
+appropriate arguments.
+