Dependence of AliHMPIDCluster objects on geometry.root file eliminated

[u/mrichter/AliRoot.git] / EMCAL / doc / reconstruction.tex

\r
\r
\section{Reconstruction code}\r
\r
\r
The energy deposited by the particles in the towers produces scintillating light that is propagated with optic fibers through the different layers to APD placed at the base of the cells. The APDs amplify the signal and generate an electronic pulse shape that is stored in the raw data format. From this pulse shape, we extract the signal amplitude and the arrival time. The pulse shape is fitted during the reconstruction via a parametrized function and TMinuit, and those 2 values are extracted.\r
\r
A particle produces signals in different towers (electromagnetic shower expands more than its Moli\`ere radius which is a cell size). The next step is the formation of clusters of cells that belong to the same particle, although depending on the energy, granularity, clusterization algorithm or event type, those clusters might have contributions from different particles. The default algorithm in pp collisions is a simple aggregation of neighboring cells until there is no more cells above a certain energy threshold (named {\it clusterizer V1}). In case of Pb-Pb collisions environment, where particle showers merge quite often, we apply another algorithm that aggregates cells to the clusters until reaching a cell with more energy than the precedent (named {\it clusterizer V2}). Depending on the analysis type, one might want to use one or the other clusterization type. For this reason, a re-clusterization is also possible at the analysis level. A last clusterizer is implemented, which makes 3x3 clusters. It has been used in jet analysis for instance in order to avoid biasing jet reconstruction where one is interested in the energy flow over a large area without explicit reconstruction of photon showers and where the driving consideration is that the wide clusterizer does not interfere with the jet finder. For $\pi^{0}$, $\eta$, and direct $\gamma$ analyses, {\it V2} is most likely preferable).\r
\r
Once the cluster is defined, we calculate cluster parameters, shower shape parameters, that will help at the analysis level to identify each cluster as one particle type. Also, we compare the cluster position information with the propagation of tracks measured in the central barrel to the EMCAL surface, to identify the clusters generated by charged particles.\r
\r
The final analysis objects, ESDs and AODs, contain all the cluster and cell basic informations allowing to redo the clusterization if needed at the analysis level.\r
\r
%The class AliReconstruction manages this part. This step can\r
%begin either from the Digits or from the Raw data. We can distinguish\r
%different steps described in the following sections. \r
\r
\r
\subsection{Offline data base access}\r
\r
How to create explained OCDB/OADB section.\r
\r
\subsubsection{Energy calibration}\r
\r
\subsubsection{Bad channels - Marie, Alexis}\r
\r
\subsubsection{Alignment - Marco}\r
\r
\subsection{Raw data fitting: from ADC sample to digits - David}\r
\r
\begin{lstlisting}\r
AliEMCALRawUtils, AliCaloRawAnalyzer*, AliCalo*, AliEMCALDigit.\r
\end{lstlisting}\r
\r
\subsection{Clusterization: From digits to clusters - Constantin, Adam}\r
\r
\begin{lstlisting}\r
AliEMCALClusterizer*, AliEMCALRecPoint\r
\end{lstlisting}\r
\r
\subsection{Cluster-Track matching - Rongrong, Shingo, Michael}\r
\r
Even though EMCal is intended to measure the energy of particles that interact with EMCal via electromagnetic showering, e.g. photons and electrons, charged hadrons can also deposit energy in EMCal, most commonly via minimum ionization, but also via nuclear interactions generating hadronic showers. In the analysis where the distinction between hadroic and electromagnetic showers is necessary, cluster-track matching is often used to meet this requirement. \r
\r
The main method used to extrapolate tracks in the ALICE software framework is:\r
\r
\begin{DDbox}{\linewidth}\r
\begin{lstlisting}\r
 static Bool_t PropagateTrackToBxByBz(AliExternalTrackParam *track, Double_t x, Double_t m,Double_t maxStep, Bool_t rotateTo=kTRUE, Double_t maxSnp=0.8,Int_t sign=0, Bool_t addTimeStep=kFALSE); \r
\end{lstlisting}\r
\end{DDbox}\r
which takes the following arguments: {\it ``track''} stores all the information of the starting point for the extrapolation; {\it ``x''} is the coordinate of the destination plane in the local coordinate system; {\it ``m''} is the mass assumption for the track; {\it ``maxStep''} is the step size used in the extrapolation. This method extrapolates the track trajectory to a destination plane in a magnetic field, taking into account the energy loss of the tracks when going through detector materials. However, the energy loss model is tuned for charged hadrons, so it does not work very well for electrons or positions whose primary energy loss process is bremsstrahlung.\r
\r
For EMCal, the track-cluster matching is done by default in the reconstruction chain and the code is implemented in:\r
\r
\begin{DDbox}{\linewidth}\r
\begin{lstlisting}\r
 AliEMCALTracker::PropagateBack(AliESDEvent* esd)\r
\end{lstlisting}\r
\end{DDbox}\r
\r
The logic of the matching procedure is the following:\r
\begin{itemize}\r
\item Check wheter TPC is available in DAQ/reco. See AliEMCALTracker::LoadClusters(). In case there is no TPC, ITS specific extrapolation will be used.\r
\item Find all the EMCal clusters in the event. See AliEMCALTracker::LoadClusters().\r
\item Find all the good tracks in the event. See AliEMCALTracker:: LoadTracks(). Several cuts are applied to select good tracks\r
	\begin{itemize}\r
	\item Minimum $p_{\rm{T}}$ cut, which can be set during the reconstruction.\r
	\item Cut on number of TPC clusters, which can be set during the reconstruction. This specific cut is avoided in case there is only ITS available in reconstruction. 	\r
	\item $|\eta|<0.8$ and $20^{\circ} < \varphi < 120^{\circ} $. These fiducial cuts are hard coded since tracks out of this range should never make it to EMCal. \r
	\end{itemize}\r
\item For each good track, find the nearest cluster as matched if their residuals fall within the cuts. See AliEMCALTracker::FindMatchedCluster(), which follows the following steps:\r
	\begin{itemize}\r
	\item Get the starting point: if the {\it friendTrack} is available, use the last point on the TPC. Otherwise, use the point at the inner wall of the TPC.\r
	\item If only ITS tracks are available in reconstruction, the propagation will use the track information from the vertex.  	   \r
	\item Extrapolate tracks to the EMCal surface at 430 cm, and apply fiducial cuts on the extrapolated points: $|\eta|<0.75$ and $70^{\circ} < \varphi < 190^{\circ} $. The step size in the extrapolation can be set in the reconstruction, and the default value is 20 cm.\r
	\item Extrapolate tracks further, with 5 cm step size, to the positions of all the EMCal clusters which are in the vicinity of the extrapolated points from last step. Then the distance between extrapolated tracks to the clusters are calculated, and the nearest cluster is assigned as matched if the residuals fall within cuts. By fitting the distributions of the residuals using Gaussian functions, we can choose to cut on $N\sigma$ of the residuals.To further improve the matching performance, $p_{\rm{T}}$ and charge dependent cuts can be used. \r
	\end{itemize}\r
\end{itemize}\r
\r
\r
\r
\subsection{How to execute the reconstruction}\r
\r
Executing the reconstruction is very similar to the simulation case, see the macro TestEMCALReconstruction.C (a bit more detailed than the one in \$ALICE\_ROOT/EMCAL/macros) :\r
\r
\begin{DDbox}{\linewidth}\r
\begin{lstlisting}\r
void TestEMCALReconstruction() {\r
\r
TString detector=``EMCAL TPC'';//Same function as in Simulation.C  \r
// TString detector=``EMCAL ITS''; if user wants ITS tracking to be used.\r
\r
AliReconstruction rec; //Create reconstruction object \r
\r
//Making Tracking \r
rec.SetRunTracking(detector) ;\r
\r
//Particle Reconstruction. Make Rec Points \r
rec.SetRunReconstruction(detector); \r
\r
//read RAW data. Give directory where raw data is stored\r
//rec.SetInput(``RawDataDirectory/raw.root");\r
\r
//Make vertex finder \r
rec.SetRunVertexFinder(kFALSE) ; // false only if the tracking detectors are not included.\r
\r
//Fill ESD file with RecPoints information. \r
rec.SetFillESD(detector) ; \r
\r
//Run Reconstruction \r
rec.Run() ;\r
}\r
\end{lstlisting}\r
\end{DDbox}\r
\r
\r