Index: /trunk/paper/CommPhysComp/notes.tex
===================================================================
--- /trunk/paper/CommPhysComp/notes.tex	(revision 440)
+++ /trunk/paper/CommPhysComp/notes.tex	(revision 441)
@@ -274,5 +274,5 @@
 %\includegraphics[width=\columnwidth]{calosegmentation}
 \includegraphics[width=\columnwidth]{fig4}
-\caption{Default segmentation of the calorimeters in the $(\eta,\phi)$ plane. Only the central detectors (\textsc{ecal}, \textsc{hcal}) and \textsc{fcal} are considered. $\phi$ angles are expressend in radians.}
+\caption{Default segmentation of the calorimeters in the $(\eta,\phi)$ plane. Only the central detectors (\textsc{ecal}, \textsc{hcal}) and \textsc{fcal} are considered. $\phi$ angles are expressed in radians.}
 \label{fig:calosegmentation}
 \end{center}
@@ -1070,4 +1070,6 @@
 # In case FROG event display allowed
 NEvents_Frog      100
+# Number of events to process
+NEvents           -1                    // -1 means 'all'
 
 # input PDG tables
@@ -1077,5 +1079,5 @@
 
 In general, energies, momenta and masses are expressed in GeV, GeV$/c$, GeV$/c^2$ respectively, and  magnetic fields in T.
-Geometrical extension are often referred in terms of pseudorapidity $\eta$, as the detectors are supposed to be symmetric in $\phi$. From version 1.8 onwards, the number of events to run will also be included in the detector card (\texttt{NEvents}).
+Geometrical extension are often referred in terms of pseudorapidity $\eta$, as the detectors are supposed to be symmetric in $\phi$. The number of events to run is also included in the detector card (\texttt{NEvents}).
  
 \item{\bf The trigger card }
Index: /trunk/paper/notes.tex
===================================================================
--- /trunk/paper/notes.tex	(revision 440)
+++ /trunk/paper/notes.tex	(revision 441)
@@ -63,5 +63,5 @@
 a general-purpose experiment. The simulation includes a tracking system, embedded into a magnetic field, calorimetry and a muon
 system, and possible very forward detectors arranged along the beamline.
-The framework is interfaced to standard file formats (e.g. Les Houches Event File) and outputs observable objects for analysis, like missing transverse energy and collections of electrons or jets.
+The framework is interfaced to standard file formats (e.g.\ Les Houches Event File  or \texttt{HepMC}) and outputs observable objects for analysis, like missing transverse energy and collections of electrons or jets.
 The simulation of detector response takes into account the detector resolution, and usual reconstruction algorithms, such as \textsc{FastJet}. A simplified preselection can also be applied on processed data for trigger emulation. Detection of very forward scattered particles relies on the transport in beamlines with the \textsc{Hector} software. Finally, the \textsc{Frog} 2D/3D event display is used for visualisation of the collision final states.
 An overview of \textsc{Delphes} is given as well as a few \textsc{lhc} use-cases for illustration.
@@ -81,5 +81,5 @@
 \section{Introduction}
 
-Experiments at high energy colliders are very complex systems for several reasons. Firstly, in terms of the various detector subsystems, including tracking, central calorimetry, forward calorimetry, and muon chambers. Such apparatus differ in their detection principles, technologies, geometrical acceptances, resolutions and sensitivities. Secondly, due to the requirement of a highly effective online selection (i.e. a \textit{trigger}), subdivided into several levels for an optimal reduction factor of ``uninteresting'' events, but based only on partially processed data. Finally, in terms of the experiment software, with different data formats (like \textit{raw} or \textit{reconstructed} data), many reconstruction algorithms and particle identification approaches.
+Experiments at high energy colliders are very complex systems for several reasons. Firstly, in terms of the various detector subsystems, including tracking, central calorimetry, forward calorimetry, and muon chambers. Such apparatus differ in their detection principles, technologies, geometrical acceptances, resolutions and sensitivities. Secondly, due to the requirement of a highly effective online selection (i.e.\ a \textit{trigger}), subdivided into several levels for an optimal reduction factor of ``uninteresting'' events, but based only on partially processed data. Finally, in terms of the experiment software, with different data formats (like \textit{raw} or \textit{reconstructed} data), many reconstruction algorithms and particle identification approaches.
 
 This complexity is handled by large collaborations of thousands of people, but the data and the expertise are only available to their members. Real data analyses require a full detector simulation, including transport of the primary and secondary particles through the detector material accounting for the various detector inefficiencies, the dead material, the imperfections and the geometrical details. Moreover, control of the detector calibration and alignment are crucial. Such simulation is very complicated, technical and requires a large \texttt{CPU} power. On the other hand, phenomenological studies, looking for the observability of given signals, may require only fast but realistic estimates of the expected signals and associated backgrounds.
@@ -115,5 +115,5 @@
 Although this kind of approach yields much realistic results than a simple ``parton-level" analysis, a fast simulation comes with some limitations. Detector geometry is idealised, being uniform, symmetric around the beam axis, and having no cracks nor dead material. Secondary interactions, multiple scatterings, photon conversion and bremsstrahlung are also neglected.
 
-Three dataformat files can be used as input in \textsc{Delphes}\footnote{\texttt{[code] }See the \texttt{HEPEVTConverter}, \texttt{LHEFConverter} and \texttt{STDHEPConverter} classes.}. In order to process events from many different generators, the standard Monte Carlo event structure \texttt{StdHEP}~\cite{bib:stdhep} can be used as an input. Besides, \textsc{Delphes} can also provide detector response for events read in ``Les Houches Event Format'' (\textsc{lhef}~\cite{bib:lhe}) and \textsc{root} files obtained from \textsc{.hbook} using the \texttt{h2root} utility from the \textsc{root} framework~\cite{bib:Root}. 
+Four datafile formats can be used as input in \textsc{Delphes}\footnote{\texttt{[code] }See the \texttt{HEPEVTConverter}, \texttt{HepMCConverter}, \texttt{LHEFConverter} and \texttt{STDHEPConverter} classes.}. In order to process events from many different generators, the standard Monte Carlo event structure \texttt{StdHEP}~\cite{bib:stdhep} can be used as an input. Besides, \textsc{Delphes} can also provide detector response for events read in ``Les Houches Event Format'' (\textsc{lhef}~\cite{bib:lhe}) and \textsc{root} files obtained from \textsc{.hbook} using the \texttt{h2root} utility from the \textsc{root} framework~\cite{bib:Root}. 
 %Afterwards, \textsc{Delphes} performs a simple trigger simulation and reconstruct "high-level objects". These informations are organised in classes and each objects are ordered with respect to the transverse momentum. 
 
@@ -143,5 +143,5 @@
 \textsc{tracker} 	& {\verb CEN_max_tracker } 	& $[-2.5; 2.5]$ 	& $[-\pi ; \pi]$\\
 \textsc{ecal}, \textsc{hcal} & {\verb CEN_max_calo_cen }& $[-3.0 ; 3.0]$	& $[-\pi ; \pi]$\\
-\textsc{fcal} 		& {\verb CEN_max_calo_fwd } 	& $[-5 ; 3]$ \& $[3 ;5]$     & $[-\pi ; \pi]$\\
+\textsc{fcal} 		& {\verb CEN_max_calo_fwd } 	& $[-5 ; -3]$ \& $[3 ;5]$     & $[-\pi ; \pi]$\\
 \textsc{muon} 		& {\verb CEN_max_mu } 		& $[-2.4 ; 2.4]$        & $[-\pi ; \pi]$\\ \hline
 \end{tabular}
@@ -165,5 +165,5 @@
 
 \subsubsection*{Magnetic field}
-In addition to the subdetectors, the effects of a solenoidal magnetic field is simulated for the charged particles\footnote{\texttt{[code] }See the \texttt{TrackPropagation} class.}. This affects the position at which charged particles enter the calorimeters and their corresponding tracks.
+In addition to the subdetectors, the effects of a solenoidal magnetic field are simulated for the charged particles\footnote{\texttt{[code] }See the \texttt{TrackPropagation} class.}. This affects the position at which charged particles enter the calorimeters and their corresponding tracks.
 
 
@@ -174,5 +174,5 @@
 
 
-\subsection{Simulation of calorimeters}
+\subsection{Simulation of central calorimeters}
 
 The energy of each particle considered as stable in the generator particle list is smeared, with a Gaussian distribution depending on the calorimeter resolution. This resolution varies with the sub-calorimeter (\textsc{ecal}, \textsc{hcal}, \textsc{fcal}) measuring the particle.
@@ -211,5 +211,5 @@
  \multicolumn{4}{l}{\textsc{fcal}, hadronic part} \\
         & $S$ (GeV$^{1/2}$)& {\verb HAD_Shf }   & $2.7$\\
-        & $N$ (GeV)& {\verb HAD_Nhf }   & $0$. \\
+        & $N$ (GeV)& {\verb HAD_Nhf }   & $0$ \\
         & $C$ & {\verb HAD_Chf }   & $0.13$\\
 \hline
@@ -235,10 +235,10 @@
 
 The smallest unit for geometrical sampling of the calorimeters is a \textit{tower}; it segments the $(\eta,\phi)$ plane for the energy measurement. No longitudinal segmentation is available in the simulated calorimeters. All undecayed particles, except muons and neutrinos deposit energy in a calorimetric tower, either in \textsc{ecal}, in \textsc{hcal} or \textsc{fcal}. 
-As the detector is assumed to be cylindrical (e.g. symmetric in $\phi$ and with respect to the $\eta=0$ plane), the detector card stores the number of calorimetric towers with $\phi=0$ and $\eta>0$ (default: $40$ towers). For a given $\eta$, the size of the $\phi$ segmentation is also specified. Fig.~\ref{fig:calosegmentation} illustrates the default segmentation of the $(\eta,\phi)$ plane.
+As the detector is assumed to be cylindrical (e.g.\ symmetric in $\phi$ and with respect to the $\eta=0$ plane), the detector card stores the number of calorimetric towers with $\phi=0$ and $\eta>0$ (default: $40$ towers). For a given $\eta$, the size of the $\phi$ segmentation is also specified. Fig.~\ref{fig:calosegmentation} illustrates the default segmentation of the $(\eta,\phi)$ plane.
 
 \begin{figure}[!h]
 \begin{center}
 \includegraphics[width=\columnwidth]{calosegmentation}
-\caption{Default segmentation of the calorimeters in the $(\eta,\phi)$ plane. Only the central detectors (\textsc{ecal}, \textsc{hcal}) and \textsc{fcal} are considered.}
+\caption{Default segmentation of the calorimeters in the $(\eta,\phi)$ plane. Only the central detectors (\textsc{ecal}, \textsc{hcal}) and \textsc{fcal} are considered. $\phi$ angles are expressed in radians.}
 \label{fig:calosegmentation}
 \end{center}
@@ -250,5 +250,5 @@
 
 Most of the recent experiments in beam colliders have additional instrumentation along the beamline. These extend the $\eta$ coverage to higher values, for the detection of very forward final-state particles. 
-Zero Degree Calorimeters (\textsc{zdc}) are located at zero angle, i.e. are aligned with the beamline axis at the interaction point, and placed beyond the point where the paths of incoming and outgoing beams separate (Fig.~\ref{fig:fdets}). These allow the measurement of stable neutral particles ($\gamma$ and $n$) coming from the interaction point, with large pseudorapidities (e.g. $|\eta_{\textrm{n,}\gamma}| > 8.3$ in \textsc{atlas} and \textsc{cms}).
+Zero Degree Calorimeters (\textsc{zdc}) are located at zero angle, i.e.\ are aligned with the beamline axis at the interaction point, and placed beyond the point where the paths of incoming and outgoing beams separate (Fig.~\ref{fig:fdets}). These allow the measurement of stable neutral particles ($\gamma$ and $n$) coming from the interaction point, with large pseudorapidities (e.g.\ $|\eta_{\textrm{n,}\gamma}| > 8.3$ in \textsc{atlas} and \textsc{cms}).
 Forward taggers (called here \textsc{rp220}, for ``roman pots at $220~\textrm{m}$'' and \textsc{fp420} ``for forward proton taggers at $420~\textrm{m}$'', as at the \textsc{lhc}) are meant for the measurement of particles following very closely the beam path. To be able to reach these detectors, such particles must have a charge identical to the beam particles, and a momentum very close to the nominal value for the beam. These taggers are near-beam detectors located a few millimetres from the true beam trajectory and this distance defines their acceptance (Tab.~\ref{tab:fdetacceptance}).
 
@@ -288,10 +288,32 @@
  t = t_0 + \frac{1}{v} \times \Big( \frac{s-z}{\cos \theta}\Big),
 \end{equation}
-where $t$ is the time of flight, $t_0$ is the true time coordinate of the vertex from which the particle originates, $v$ the particle velocity, $s$ is the \textsc{zdc} distance to the interaction point, $z$ is the longitudinal coordinate of the vertex from which the particle comes from, $\theta$ is the particle emission angle. This assumes that the neutral particle observed in the \textsc{zdc} is highly relativistic, i.e. travelling at the speed of light $c$. We also assume that $\cos \theta = 1$, i.e. $\theta \approx 0$ or equivalently $\eta$ is large. As an example, $\eta = 5$ leads to $\theta = 0.013$ and $1 - \cos \theta < 10^{-4}$.
+where $t$ is the time of flight, $t_0$ is the true time coordinate of the vertex from which the particle originates, $v$ the particle velocity, $s$ is the \textsc{zdc} distance to the interaction point, $z$ is the longitudinal coordinate of the vertex from which the particle comes from, $\theta$ is the particle emission angle. This assumes that the neutral particle observed in the \textsc{zdc} is highly relativistic, i.e.\ travelling at the speed of light $c$. We also assume that $\cos \theta = 1$, i.e.\ $\theta \approx 0$ or equivalently $\eta$ is large. As an example, $\eta = 5$ leads to $\theta = 0.013$ and $1 - \cos \theta < 10^{-4}$.
 The formula then reduces to
 \begin{equation}
  t = \frac{1}{c} \times (s-z)
 \end{equation}
-For example, a photon takes $0.47~\mu\textrm{s}$ to reach a \textsc{zdc} located at $s=140~\textrm{m}$, neglecting $z$ and $\theta$, and assuming that $v=c$. Only neutrons and photons are currently assumed to be able to reach the \textsc{zdc}. All other particles are neglected in the \textsc{zdc}.
+For example, a photon takes $0.47~\mu\textrm{s}$ to reach a \textsc{zdc} located at $s=140~\textrm{m}$, neglecting $z$ and $\theta$, and assuming that $v=c$. Only neutrons and photons are currently assumed to be able to reach the \textsc{zdc}. All other particles are neglected in the \textsc{zdc}. The \textsc{zdc}s are composed of an electromagnetic and a hadronic sections, for the measurement of photons and neutrons, respectively. The energy of the observed neutral is smeared according to Eq.~\ref{eq:caloresolution} and the section resolutions (Tab.~\ref{tab:defResolZdc}). The \textsc{zdc} hits do not enter in the calorimeter tower list used for reconstruction of jets and missing transverse energy.
+
+\begin{table}[!h]
+\begin{center}
+\caption{Default values for the resolution of the zero degree calorimeters. Resolution is parametrised by the \textit{stochastic} ($S$), \textit{noise} ($N$) and \textit{constant} ($C$) terms (Eq.~\ref{eq:caloresolution}).
+ The corresponding parameter name, in the detector card, is given. \vspace{0.5cm}}
+\begin{tabular}[!h]{lllc}
+ \hline
+ \multicolumn{2}{c}{Resolution Term}   & Card flag & Value\\\hline
+ \multicolumn{4}{l}{\textsc{zdc}, electromagnetic part} \\
+         & $S$ (GeV$^{1/2}$)& {\verb ELG_Szdc }  & $0.7$ \\
+         & $N$ (GeV)& {\verb ELG_Nzdc }  & $0.0$ \\
+         & $C$ & {\verb ELG_Czdc }  & $0.08$ \\
+ \multicolumn{4}{l}{\textsc{zdc}, hadronic part} \\
+         & $S$ (GeV$^{1/2}$)& {\verb HAD_Szdc }   & $1.38$\\
+         & $N$ (GeV)& {\verb HAD_Nzdc }   & $0$ \\
+         & $C$ & {\verb HAD_Czdc }   & $0.13$\\
+ \hline
+\end{tabular}
+\label{tab:defResolZdc}
+\end{center}
+\end{table}
+
 
 \section{High-level object reconstruction}
@@ -321,5 +343,5 @@
 
 To improve the quality of the contents of the charged lepton collections, additional criteria can be applied such as isolation. This requires that electron or muon candidates are isolated in the detector from any other particle, within a small cone. In \textsc{Delphes}, charged lepton isolation demands that there is no other charged particle with $p_T>2~\textrm{GeV}/c$ within a cone of $\Delta R = \sqrt{\Delta \eta^2 + \Delta \phi^2} <0.5$ around the lepton. 
-The result (i.e. \textit{isolated} or \textit{not}) is added to the charged lepton measured properties.
+The result (i.e.\ \textit{isolated} or \textit{not}) is added to the charged lepton measured properties.
 In addition, the sum $P_T$ of the transverse momenta of all tracks but the lepton one within the isolation cone is 
 provided\footnote{\texttt{[code] }See the \texttt{IsolFlag} and \texttt{IsolPt} values in the \texttt{Electron} or \texttt{Muon} collections in the \texttt{Analysis} tree, as well as the \texttt{ISOL\_PT} and \texttt{ISOL\_Cone} variables in the detector card.}:
@@ -330,7 +352,7 @@
 $$ \rho_\mu = \frac{\Sigma_i E_T(i)}{p_T(\mu)}~,~ i\textrm{ in }N \times N \textrm { grid centred on }\mu.$$
 
-
-
-
+\subsubsection*{Forward neutrals}
+
+The zero degree calorimeter hits correspond to neutral particles with a lifetime long enough to reach these detectors (default: $c \tau \geq 140~\textrm{m}$) and very large pseudorapidities (default: $|\eta|>8.3$). In current versions of \textsc{Delphes}, only photons and neutrons are considered. Photons are identified thanks to the electromagnetic section of the calorimeter, and if their energy overpasses a given threshold (def. $20$~GeV). Similarly, neutrons are reconstructed according to the resolution of the hadronic section, if their energy exceeds a threshold\footnote{\texttt{[code]} These thresholds are defined by the \texttt{ZDC\_gamma\_E} and \texttt{ZDC\_n\_E} variables in the detector card.} (def. $50$~GeV).
 
 
@@ -349,8 +371,8 @@
 This so-called \textsc{Jetclu} cone jet algorithm is used by the \textsc{cdf} experiment in Run II. 
 All towers with a transverse energy $E_T$ higher than a given threshold (default: $E_T > 1~\textrm{GeV}$) are used to seed the jet candidates. 
-The existing \textsc{FastJet} code has been modified to allow easy modification of the tower pattern in $\eta$, $\phi$ space. 
-In the following versions of \textsc{Delphes}, a new dedicated plug-in will be created on this purpose\footnote{\texttt{[code] }\texttt{JET\_coneradius} and \texttt{JET\_seed} variables in the detector card.}.
- 
-\item {\it CDF MidPoint}~\cite{bib:midpoint}: Algorithm developed for the \textsc{cdf} Run II to reduce infrared and collinear sensitivity compared to purely seed-based cone by adding `midpoints' (energy barycentres) in the list of cone seeds.
+The existing \textsc{FastJet} code has been modified to allow easy modification of the tower pattern in ($\eta$, $\phi$) space. 
+In following versions of \textsc{Delphes}, a new dedicated plug-in will be created on this purpose\footnote{\texttt{[code] }\texttt{JET\_coneradius} and \texttt{JET\_seed} variables in the detector card.}.
+ 
+\item {\it CDF MidPoint}~\cite{bib:midpoint}: Algorithm developed for the \textsc{cdf} Run II to reduce infrared and collinear sensitivities compared to purely seed-based cone by adding `midpoints' (energy barycentres) in the list of cone seeds.
  
 \item {\it Seedless Infrared Safe Cone}~\cite{bib:SIScone}: The \textsc{SISCone} algorithm is simultaneously insensitive to additional soft particles and collinear splittings, and fast enough to be used in experimental analysis.
@@ -391,14 +413,16 @@
 \end{enumerate}
  
-
+\subsubsection*{Energy flow}
+
+In jets, several particle can leave their energy into a given calorimetric tower, which broadens the jet energy resolution. However, the energy of charged particles associated to jets can be deduced from their reconstructed track, thus providing a way to identify some of the components of towers with multiple hits. When the \textit{energy flow} is switched on in \textsc{Delphes}\footnote{\texttt{[code]} Set \texttt{JET\_Eflow} to $1$ or $0$ in the detector card in order to switch on or off the energy flow for jet reconstruction.}, the energy of tracks pointing to calotowers is extracted and smeared separately, before running the chosen jet reconstruction algorithm. This option allows a better jet $E$ reconstruction.
  
 \subsection{$b$-tagging}
 
-A jet is tagged as $b$-jets if its direction lies in the acceptance of the tracker and if it is associated to a parent $b$-quark. By default, a $b$-tagging efficiency of $40\%$ is assumed if the jet has a parent $b$ quark. For $c$-jets and light jets (i.e. originating in $u$,$d$,$s$ quarks or in gluons), a fake $b$-tagging efficiency of $10 \%$ and $1 \%$ respectively is assumed\footnote{\texttt{[code] }Corresponding to the \texttt{BTAG\_b}, \texttt{BTAG\_mistag\_c} and \texttt{BTAG\_mistag\_l} constants, for (respectively) the efficiency of tagging of a $b$-jet, the efficiency of mistagging a $c$-jet as a $b$-jet, and the efficiency of mistagging a light jet ($u$,$d$,$s$,$g$) as a $b$-jet.}.
-The (mis)tagging relies on the true particle identity (\textsc{pid}) of the most energetic particle within a cone around the observed $(\eta,\phi)$ region, with a radius equal to the one used to reconstruct the jet (default: $\Delta R$ of $0.7$).
+A jet is tagged as $b$-jets if its direction lies in the acceptance of the tracker and if it is associated to a parent $b$-quark. By default, a $b$-tagging efficiency of $40\%$ is assumed if the jet has a parent $b$ quark. For $c$-jets and light jets (i.e.\ originating in $u$, $d$, $s$ quarks or in gluons), a fake $b$-tagging efficiency of $10 \%$ and $1 \%$ respectively is assumed\footnote{\texttt{[code] }Corresponding to the \texttt{BTAG\_b}, \texttt{BTAG\_mistag\_c} and \texttt{BTAG\_mistag\_l} constants, for (respectively) the efficiency of tagging of a $b$-jet, the efficiency of mistagging a $c$-jet as a $b$-jet, and the efficiency of mistagging a light jet ($u$,$d$,$s$,$g$) as a $b$-jet.}.
+The (mis)tagging relies on the true particle identity (\textsc{pid}) of the most energetic particle within a cone around the observed $(\eta,\phi)$ region, with a radius equal to the one used to reconstruct the jet (default: $\Delta R$ of $0.7$).  In current version of \textsc{Delphes}, the displacement of secondary vertices is not simulated.
 
 \subsection{\texorpdfstring{$\tau$}{\texttau} identification}
 
-Jets originating from $\tau$-decays are identified using an identification procedure consistent with the one applied in a full detector simulation~\cite{bib:cmsjetresolution}. 
+Jets originating from $\tau$-decays are identified using a procedure consistent with the one applied in a full detector simulation~\cite{bib:cmsjetresolution}. 
 The tagging relies on two properties of the $\tau$ lepton. First, $77\%$ of the $\tau$ hadronic decays contain only one charged hadron associated to a few neutrals (Tab.~\ref{tab:taudecay}). Tracks are useful for this criterion. Secondly, the particles arisen from the $\tau$ lepton produce narrow jets in the calorimeter (this is defined as the jet \textit{collimation}). 
 
@@ -406,5 +430,5 @@
 \begin{table}[!h]
 \begin{center}
-\caption{ Branching rations for $\tau^-$ lepton~\cite{bib:pdg}. $h^\pm$ and $h^0$ refer to charged and neutral hadrons, respectively. $n \geq 0$ and $m \geq 0$ are integers.
+\caption{ Branching ratios for $\tau^-$ lepton~\cite{bib:pdg}. $h^\pm$ and $h^0$ refer to charged and neutral hadrons, respectively. $n \geq 0$ and $m \geq 0$ are integers.
 \vspace{0.5cm}  }
 \begin{tabular}[!h]{ll}
@@ -426,5 +450,5 @@
 \begin{center}
 \includegraphics[width=0.6\columnwidth]{Tau}
-\caption{Illustration of the identification of $\tau$-jets. The jet cone is narrow and contains only one track. The small cone shown as the red one is used for the \textit{electromagnetic collimation}, while the green cone is the cone radius used to reconstruct the jet originating from the $\tau$-decay.}
+\caption{Illustration of the identification of $\tau$-jets ($1-$prong). The jet cone is narrow and contains only one track. The small cone shown as the red one is used for the \textit{electromagnetic collimation}, while the green cone is the cone radius used to reconstruct the jet originating from the $\tau$-decay.}
 \label{h_WW_ss_cut1}
 \end{center}
@@ -445,5 +469,5 @@
 \multicolumn{3}{l}{\textbf{Tracking isolation}} \\
 $R^\textrm{tracks}$ & \texttt{TAU\_track\_scone} & $0.4$\\
-min $p_T^{tracks}$      & \texttt{PTAU\_track\_pt } & $2$ GeV$/c$\\
+min $p_T^\textrm{tracks}$      & \texttt{PTAU\_track\_pt } & $2$ GeV$/c$\\
 \multicolumn{3}{l}{\textbf{$\tau$-jet candidate}} \\
 $\min p_T$ & \texttt{TAUJET\_pt} & $10$ GeV$/c$\\
@@ -457,7 +481,7 @@
 \subsubsection*{Electromagnetic collimation}
 
-To use the narrowness of the $\tau$-jet, the \textit{electromagnetic collimation} $C_{\tau}^{em}$ is defined as the sum of the energy of towers in a small cone of radius $R^\textrm{em}$ around the jet axis, divided by the energy of the reconstructed jet. 
+To use the narrowness of the $\tau$-jet, the \textit{electromagnetic collimation} $C_{\tau}$ is defined as the sum of the energy of towers in a small cone of radius $R^\textrm{em}$ around the jet axis, divided by the energy of the reconstructed jet. 
 To be taken into account, a calorimeter tower should have a transverse energy $E_T^\textrm{tower}$ above a given threshold. 
-A large fraction of the jet energy is expected in this small cone. This fraction, or collimation factor, is represented in Fig.~\ref{fig:tau2} for the default values (see Tab.~\ref{tab:tauRef}).
+A large fraction of the jet energy is expected in this small cone. This fraction, or \textit{collimation factor}, is represented in Fig.~\ref{fig:tau2} for the default values (see Tab.~\ref{tab:tauRef}).
 
 \begin{figure}[!h]
@@ -474,5 +498,5 @@
 \subsubsection*{Tracking isolation}
 
-The tracking isolation for the $\tau$ identification requires that the number of tracks associated to a particle with a significant transverse momentum is one and only one in a cone of radius $R^\textrm{tracks}$ (3-prong $\tau$s are dropped). 
+The tracking isolation for the $\tau$ identification requires that the number of tracks associated to particles with significant transverse momenta is one and only one in a cone of radius $R^\textrm{tracks}$ (3-prong $\tau$s are dropped). 
 This cone should be entirely incorporated into the tracker to be taken into account. Default values of these parameters are given in Tab.~\ref{tab:tauRef}.
 
@@ -509,6 +533,6 @@
 \right.
 \end{equation}
-The \textit{true} missing transverse energy, i.e. at generator-level, is calculated as the opposite of the vector sum of the transverse momenta of all visible particles -- or equivalently, to the vector sum of invisible particle transverse momenta. 
-In a real experiment, calorimeters measure energy and not momentum. Any problem affecting the detector (dead channels, misalignment, noisy towers, cracks) worsens directly the measured missing transverse energy $\overrightarrow {E_T}^\textrm{miss}$. In this document, \textsc{met} is based on the calorimetric towers and only muons and neutrinos are not taken into account for its evaluation:
+The \textit{true} missing transverse energy, i.e.\ at generator-level, is calculated as the opposite of the vector sum of the transverse momenta of all visible particles -- or equivalently, to the vector sum of invisible particle transverse momenta. 
+In a real experiment, calorimeters measure energy and not momentum. Any problem affecting the detector (dead channels, misalignment, noisy towers, cracks) worsens directly the measured missing transverse energy $\overrightarrow {E_T}^\textrm{miss}$. In this document, \textsc{met} is based on the calorimetric towers and only muons and neutrinos are not taken into account for its evaluation\footnote{However, as tracks and calorimetric towers are available in the output file, the missing transverse energy can always be reprocessed a posteriori }:
 \begin{equation}
 \overrightarrow{E_T}^\textrm{miss} = - \sum^\textrm{towers}_i \overrightarrow{E_T}(i)
@@ -520,10 +544,10 @@
 New physics in collider experiment are often characterised in phenomenology by low cross-section values, compared to the Standard Model (\textsc{sm}) processes. %For instance at the \textsc{lhc} ($\sqrt{s}=14~\textrm{TeV}$), the cross-section of inclusive production of $b \bar b$ pairs is expected to be $10^7~\textrm{nb}$, or inclusive jets at $100~\textrm{nb}$ ($p_T > 200~\textrm{GeV}/c$), while Higgs boson cross-section within the \textsc{sm} can be as small as $2 \times 10^{-3}~\textrm{nb}$ ($pp \rightarrow WH$, $m_H=115~\textrm{GeV}/c^2$). 
 
-%High statistics are required for data analyses, consequently imposing high luminosity, i.e. a high collision rate.
+%High statistics are required for data analyses, consequently imposing high luminosity, i.e.\ a high collision rate.
 As only a tiny fraction of the observed events can be stored for subsequent \textit{offline} analyses, a very large data rejection factor should be applied directly as the events are produced.
 This data selection is supposed to reject only well-known \textsc{sm} events\footnote{However, some bandwidth is allocated to minimum-bias and/or zero-bias (``random'') triggers that stores a small fraction of the events without any selection criteria.}.
 Dedicated algorithms of this \textit{online} selection, or \textit{trigger}, should be fast and very efficient for data rejection, in order to preserve the experiment output bandwidth. They must also be as inclusive as possible to avoid loosing interesting events.
 
-Most of the usual trigger algorithms select events containing objects (i.e. jets, particles, \textsc{met}) with an energy scale above some threshold. This is often expressed in terms of a cut on the transverse momentum of one or several objects of the measured event. Logical combinations of several conditions are also possible. For instance, a trigger path could select events containing at least one jet and one electron such as $p_T^\textrm{jet} > 100~\textrm{GeV}/c$ and $p_T^e > 50~\textrm{GeV}/c$.
+Most of the usual trigger algorithms select events containing objects (i.e.\ jets, particles, \textsc{met}) with an energy scale above some threshold. This is often expressed in terms of a cut on the transverse momentum of one or several objects of the measured event. Logical combinations of several conditions are also possible. For instance, a trigger path could select events containing at least one jet and one electron such as $p_T^\textrm{jet} > 100~\textrm{GeV}/c$ and $p_T^e > 50~\textrm{GeV}/c$.
 
 A trigger emulation is included in \textsc{Delphes}, using a fully parametrisable \textit{trigger table}\footnote{\texttt{[code] }The trigger card is the \texttt{data/TriggerCard.dat} file.}. When enabled, this trigger is applied on analysis-object data. 
@@ -739,5 +763,5 @@
 \section*{Acknowledgements}
 \addcontentsline{toc}{section}{Acknowledgements}
-The authors would like to thank Jer\^ome de Favereau, Christophe Delaere, Muriel Vander Donckt and David d'Enterria for useful discussions and comments, and Loic Quertenmont for support in interfacing \textsc{Frog}. We are also really grateful to Alice Dechambre and Simon de Visscher for being beta testers of the complete package. 
+The authors would like to thank very warmly Vincent LemaÃ®tre for the interesting suggestions during the development of the software, as well as Jer\^ome de Favereau, Christophe Delaere, Muriel Vander Donckt and David d'Enterria for useful discussions and comments, and Loic Quertenmont for support in interfacing \textsc{Frog}. We are also really grateful to Alice Dechambre and Simon de Visscher for being beta testers of the complete package. 
 Part of this work was supported by the Belgian Federal Office for Scientific, Technical and Cultural Affairs through the Interuniversity Attraction Pole P6/11. 
 
@@ -749,4 +773,5 @@
 %hepforge:
 \bibitem{bib:stdhep} L.A. Garren, M. Fischler, \\ \href{http://cepa.fnal.gov/psm/stdhep/c++}{cepa.fnal.gov/psm/stdhep/c++}
+\bibitem{bib:hepmc} M. Dobbs and J.B. Hansen, \textbf{Comput. Phys. Commun.} \href{http://dx.doi.org/10.1016/S0010-4655(00)00189-2}{134 (2001) 41}.
 \bibitem{bib:lhe} J. Alwall, et al., \textbf{Comput. Phys. Commun.} \href{http://dx.doi.org/10.1016/j.cpc.2006.11.010}{176:300-304,2007}.
 \bibitem{bib:Root} %\textsc{Root}, \textit{An Object Oriented Data Analysis Framework}, 
@@ -796,5 +821,5 @@
 \section{User manual}
  
-The available \texttt{C++}-code is compressed in a zipped tar file which contains everything needed to run the \textsc{Delphes} package, assuming a running \textsc{root} installation. The package includes \texttt{ExRootAnalysis}~\cite{bib:ExRootAnalysis}, \textsc{Hector}~\cite{bib:Hector}, \textsc{FastJet}~\cite{bib:FastJet}, and \textsc{Frog}~\cite{bib:Frog}, as well as the conversion codes to read standard \mbox{\textsc{s}td\textsc{hep}} input files (\texttt{mcfio} and \texttt{stdhep})~\cite{bib:mcfio}.
+The available \texttt{C++}-code is compressed in a zipped tar file which contains everything needed to run the \textsc{Delphes} package, assuming a running \textsc{root} installation. The package includes \texttt{ExRootAnalysis}~\cite{bib:ExRootAnalysis}, \textsc{Hector}~\cite{bib:Hector}, \textsc{FastJet}~\cite{bib:FastJet}, and \textsc{Frog}~\cite{bib:Frog}, as well as the conversion codes to read standard \mbox{\textsc{s}td\textsc{hep}} input files (\texttt{mcfio} and \texttt{stdhep})~\cite{bib:mcfio} and \textsc{HepMC}~\cite{bib:hepmc}.
 In order to visualise the events with the \textsc{Frog} software, a few additional external libraries may be required, as explained in \href{http://projects.hepforge.org/frog/}{http://projects.hepforge.org/frog/}.
  
@@ -803,5 +828,5 @@
 In order to run \textsc{Delphes} on your system, first download its sources and compile them:\\
 \texttt{wget http://www.fynu.ucl.ac.be/users/s.ovyn/Delphes/files/Delphes\_V\_*.tar.gz}\\
-Replace the \texttt{*} symbol by the proper version number\footnote{Refer to the download page on the \textsc{Delphes} website \href{http://www.fynu.ucl.ac.be/users/s.ovyn/Delphes/download.html}{http://www.fynu.ucl.ac.be/users/s.ovyn/Delphes/download.html}.}.
+Replace the \texttt{*} symbol by the proper version number\footnote{Refer to the download page on the \textsc{Delphes} website \href{http://www.fynu.ucl.ac.be/users/s.ovyn/Delphes/download.html}{http://www.fynu.ucl.ac.be/users/s.ovyn/Delphes/download.html}. Current version of \textsc{Delphes} for this manual is V 1.7 (May 2009)}.
 
 \begin{quote}
@@ -823,5 +848,5 @@
 \subsection{Running \textsc{Delphes} on your events}
  
-In this sub-appendix, we will explain how to use \textsc{Delphes} to perform a fast simulation of a general-purpose detector on your event files. The first step to use \textsc{Delphes} is to create the list of input event files (e.g. {\verb inputlist.list }). It is important to notice that all the files comprised in the list file should have the same of extension (\texttt{*.hep}, \texttt{*.lhe} or \texttt{*.root}). In the simplest way to run \textsc{Delphes}, you need this input file and you need to specify the name of the output file that will contain the generator-level data (\texttt{GEN} tree), the analysis data objects after reconstruction (\texttt{Analysis} tree), and the results of the trigger emulation (\texttt{Trigger} tree).
+In this sub-appendix, we will explain how to use \textsc{Delphes} to perform a fast simulation of a general-purpose detector on your event files. The first step to use \textsc{Delphes} is to create the list of input event files (e.g.\ {\verb inputlist.list }). It is important to notice that all the files comprised in the list file should have the same of extension (\texttt{*.hep}, \texttt{*.lhe}, \texttt{*.hepmc} or \texttt{*.root}). In the simplest way to run \textsc{Delphes}, you need this input file and you need to specify the name of the output file that will contain the generator-level data (\texttt{GEN} tree), the analysis data objects after reconstruction (\texttt{Analysis} tree), and the results of the trigger emulation (\texttt{Trigger} tree).
  
 \begin{quote}
@@ -833,5 +858,5 @@
 \subsubsection{Setting up the configuration}
  
-The program is driven by two datacards (default cards are {\verb data/DetectorCard.dat } and {\verb data/TriggerCard.dat }) which allow the user to choose among a large spectrum of running conditions. Please note that if the user does not provide these datacards, the running will be done using the default parameters defined in the constructor of the class \texttt{RESOLution} (see next). If you choose a different detector or running configuration, you will need to edit the datacards accordingly.
+The program is driven by two datacards (default cards are {\verb data/DetectorCard.dat } and {\verb data/TriggerCard.dat }) which allow the user to choose among a large spectrum of running conditions. Please note that if the user does not provide these datacards, the running will be done using the default parameters defined in the constructor of the class \texttt{RESOLution} (see next). If you choose a different detector or running configuration, you will need to edit the datacards accordingly. Detector and trigger cards are provided in the \texttt{data/} subdirectory for the \textsc{cms} and \textsc{atlas} experiments.
  
 \begin{enumerate}
@@ -858,6 +883,10 @@
 ELG_Ccen          0.005    // C term for central ECAL
 ELG_Sfwd          2.084    // S term for FCAL
-ELG_Nfwd          0.0      // N term for FCAL
+ELG_Nfwd          0.       // N term for FCAL
 ELG_Cfwd          0.107    // C term for FCAL
+ELG_Szdc          0.70     // S term for ZDC
+ELG_Nzdc          0.       // N term for ZDC
+ELG_Czdc          0.08     // C term for ZDC
+
 
 # Energy resolution for hadrons in ecal/hcal/hf
@@ -869,4 +898,13 @@
 HAD_Nhf           0.       // N term for FCAL
 HAD_Chf           0.13     // C term for FCAL
+HAD_Szdc          1.38     // S term for ZDC
+HAD_Nzdc          0.       // N term for ZDC
+HAD_Czdc          0.13     // C term for ZDC
+
+# Time resolution for ZDC/RP220/RP420
+ZDC_T_resolution   0       // in s
+RP220_T_resolution 0       // in s
+RP420_T_resolution 0       // in s
+
  
 # Muon smearing
@@ -888,5 +926,5 @@
 ### the list ends with the higher edged of the most forward tower
 ### there should be NTOWER+1 values
-TOWER_eta_edges 0.    0.087 0.174 0.261 0.348 0.435 0.522 0.609 0.696 0.783
+TOWER_eta_edges 0. 0.087 0.174 0.261 0.348 0.435 0.522 0.609 0.696 0.783
                0.870 0.957 1.044 1.131 1.218 1.305 1.392 1.479 1.566 1.653
                1.740 1.830 1.930 2.043 2.172 2.322 2.500 2.650 2.868 2.950
@@ -909,9 +947,12 @@
 PTCUT_taujet     10.0
 
+# Thresholds for reconstructed objects in ZDC, E in GeV
+ZDC_gamma_E      20
+ZDC_n_E          50
+
 # Charged lepton isolation. Pt and Et in GeV
 ISOL_PT          2.0  //minimal pt of tracks for isolation criteria
 ISOL_Cone        0.5  //Cone  for isolation criteria
 ISOL_Calo_ET     2.0  //minimal tower E_T for isolation criteria. 1E99 means "off"
-ISOL_Calo_Cone   0.4  //Cone for calorimetric isolation
 ISOL_Calo_Grid   3    //Grid size (N x N) for calorimetric isolation
 
@@ -925,4 +966,6 @@
                         // 6 for anti-kt algorithm
 JET_seed         1.0    // minimum seed to start jet reconstruction, in GeV
+JET_Eflow        1      // Energy flow: perfect energy assumed in the tracker coverage.
+                        // 1 is 'on' ; 0 is 'off'
 \end{verbatim}
 \end{quote}
@@ -952,6 +995,4 @@
 # Very forward detector extension, in pseudorapidity
 # if allowed
-VFD_min_calo_vfd  5.2     // very forward calorimeter (if any) like CASTOR
-VFD_max_calo_vfd  6.6
 VFD_min_zdc       8.3     // Zero-Degree neutral Calorimeter
 VFD_s_zdc         140     // distance of the ZDC, from the IP, in [m]
@@ -965,12 +1006,24 @@
 RP_beam2Card      data/LHCB2IR5_v6.500.tfs // beam optics file, beam 2
 RP_IP_name        IP5     // tag for IP in Hector ; 'IP1' for ATLAS
+RP_offsetEl_x     0.097   // horizontal separation between both beam, in meters
+RP_offsetEl_y     0       // vertical separation between both beam, in meters
+RP_offsetEl_s     120     // distance of beam separation point, from IP
+RP_cross_x        -500    // IP offset in horizontal plane, in micrometers
+RP_cross_y        0       // IP offset in vertical plane, in micrometers
+RP_cross_ang_x    142.5   // half-crossing angle in horizontal plane, in microrad
+RP_cross_ang_y    0       // half-crossing angle in vertical plane, in microrad
+
 
 # In case FROG event display allowed
 NEvents_Frog      100
- 
+# Number of events to process
+NEvents           -1                    // -1 means 'all'
+
+# input PDG tables
+PdgTableFilename  data/particle.tbl     // table with particle pid,mass,charge,... 
 \end{verbatim}
 \end{quote}
 In general, energies, momenta and masses are expressed in GeV, GeV$/c$, GeV$/c^2$ respectively, and  magnetic fields in T.
-Geometrical extension are often referred in terms of pseudorapidity $\eta$, as the detectors are supposed to be symmetric in $\phi$.
+Geometrical extension are often referred in terms of pseudorapidity $\eta$, as the detectors are supposed to be symmetric in $\phi$. The number of events to run is also included in the detector card (\texttt{NEvents}).
  
 \item{\bf The trigger card }
@@ -994,6 +1047,6 @@
  
 Each line in the trigger datacard is allocated to exactly one trigger-bit and starts with the name of the corresponding trigger. 
-Logical combination of several conditions is also possible. If the trigger-bit requires the presence of multiple identical objects, the order of their $p_T$ thresholds is very important: they must be defined in \textit{decreasing} order. Finally, the different requirements on the objects must be separated by a {\verb && } flag. 
-The default trigger card can be found in the data repository of \textsc{Delphes} (\texttt{data/TriggerCard.dat}). 
+Logical combination of several conditions is also possible. If the trigger-bit requires the presence of multiple identical objects, the order of their $p_T$ thresholds is very important: they must be defined in \textit{decreasing} order. The transverse momentum $p_T$ is expressed in \mbox{GeV/$c$}. Finally, the different requirements on the objects must be separated by a {\verb && } flag. 
+The default trigger card can be found in the data repository of \textsc{Delphes} (\texttt{data/TriggerCard.dat}), as well as for both \textsc{cms} and \textsc{atlas} experiments at the \textsc{lhc}. 
 An example of trigger table consistent with the previous rules is given here:
 \begin{quote}
@@ -1009,5 +1062,5 @@
  
 First, create the detector and trigger cards (\texttt{data/DetectorCard.dat} and \texttt{data/TriggerCard.dat}). \\
-Then, create a text file containing the list of input files that will be used by \textsc{Delphes} (with extension \texttt{*.lhe}, \texttt{*.root} or \texttt{*.hep}).
+Then, create a text file containing the list of input files that will be used by \textsc{Delphes} (with extension \texttt{*.lhe}, \texttt{*.hepmc}, \texttt{*.root} or \texttt{*.hep}).
 To run the code, type the following command (in one line)
 \begin{quote}
@@ -1023,5 +1076,5 @@
 me@mylaptop:~$ ./Delphes
  Usage: ./Delphes input_file output_file [detector_card] [trigger_card]
- input_list - list of files in Ntpl, StdHep of LHEF format,
+ input_list - list of files in Ntpl, StdHep, HepMC or LHEF format,
  output_file - output file.
  detector_card - Card containing resolution variables for detector simulation (optional)
@@ -1037,5 +1090,5 @@
 The \textsc{Delphes} output file (\texttt{*.root}) is subdivided into three \textit{trees}, corresponding to generator-level data, analysis-object data and trigger output. These \textit{trees} are structures that organise the output data into \textit{branches} containing data (or \textit{leaves}) related with each others, like the kinematics properties ($E$, $p_x$, $\eta$, $\ldots$) of a given particle.
 
-Here is the exhaustive list of \textit{branches} availables in these \textit{trees}, together with their corresponding physical objet and \texttt{ExRootAnalysis} class:
+Here is the exhaustive list of \textit{branches} availables in these \textit{trees}, together with their corresponding physical objet and \texttt{ExRootAnalysis} C++ class name:
 \begin{quote}
 \begin{tabular}{lll}
@@ -1043,5 +1096,5 @@
 ~~~Particle & generator particles from \textsc{hepevt}     & {\verb GenParticle }\\
 \multicolumn{3}{l}{}\\
-{\bf Trigger  } & &\\
+{\bf Trigger tree } & &\\
 ~~~TrigResult & Acceptance of different trigger-bits       & {\verb TRootTrigger }\\
 \multicolumn{3}{l}{}\\
@@ -1061,5 +1114,6 @@
 \end{quote}
 The third column shows the names of the corresponding classes to be written in a \textsc{root} tree. 
-All classes except \texttt{TRootTracks}, \texttt{TRootCalo}, \texttt{TRootTrigger}, \texttt{TRootETmis} and \texttt{TRootRomanPotHits} inherit from the class \texttt{TRootParticle} which includes the following data members (stored as \textit{leaves} in \textit{branches} of the \textit{trees}):
+The bin number in the unique leaf in the \texttt{trigger} tree (namely, \texttt{TrigResult.Accepted}) corresponds to the trigger number in the provided list. In addition, the result of the global trigger decision upon each event (i.e.\ the logical \texttt{OR} of all trigger conditions) is stored in the first bin (number 0) of this leaf.
+In \texttt{Analysis} tree, all classes except \texttt{TRootTracks}, \texttt{TRootCalo}, \texttt{TRootTrigger}, \texttt{TRootETmis} and \texttt{TRootRomanPotHits} inherit from the class \texttt{TRootParticle} which includes the following data members (stored as \textit{leaves} in \textit{branches} of the \textit{trees}):
 \begin{quote}
 \begin{tabular}{ll}
@@ -1078,5 +1132,5 @@
 \begin{quote}
 \begin{tabular}{ll}
-\multicolumn{2}{l}{{\bf Leaves in the \texttt{Particle} branch}} \\    
+\multicolumn{2}{l}{{\bf Leaves in the \texttt{Particle} branch (\texttt{GEN} tree)}} \\    
    \texttt{~~~int PID;      }&\texttt{ // particle HEP ID number }\\
    \texttt{~~~int Status;   }&\texttt{ // particle status }\\
@@ -1095,5 +1149,5 @@
 \begin{quote}
 \begin{tabular}{ll}
-\multicolumn{2}{l}{\textbf{Additional leaves in \texttt{Electron} and \texttt{Muon} branches}} \\
+\multicolumn{2}{l}{\textbf{Additional leaves in \texttt{Electron} and \texttt{Muon} branches (\texttt{Analysis} tree)}} \\
    \texttt{~~~int Charge }    &\texttt{ // particle Charge }\\
    \texttt{~~~bool IsolFlag } &\texttt{ // stores the result of the tracking isolation test }\\
@@ -1102,9 +1156,10 @@
    \texttt{~~~float EHoverEE }&\texttt{ // hadronic energy over electromagnetic energy }\\
    \texttt{~~~float EtRatio } &\texttt{ // calo Et in NxN-tower grid around the muon over the muon Et }\\
+   \texttt{~~~float IsolPt } &\texttt{  // sum of all track pt in isolation cone (GeV/c) }\\
 \end{tabular}
 \end{quote}
 \begin{quote}
 \begin{tabular}{ll}
-\multicolumn{2}{l}{\textbf{Additional leaf in the \texttt{Jet} branch}}  \\
+\multicolumn{2}{l}{\textbf{Additional leaf in the \texttt{Jet} branch (\texttt{Analysis} tree)}}  \\
    \texttt{~~~bool Btag }  &\texttt{ // stores the result of the b-tagging }\\
    \texttt{~~~int NTracks }&\texttt{ // number of tracks associated to the jet }\\
@@ -1114,12 +1169,5 @@
 \begin{quote}
 \begin{tabular}{ll}
-\multicolumn{2}{l}{\textbf{Additional leaves in the \texttt{ZDChits} branch}}\\
-   \texttt{~~~float T } &\texttt{ // time of flight  in s }\\
-   \texttt{~~~int side }&\texttt{ // -1 or +1 }
-\end{tabular}
-\end{quote}
-\begin{quote}
-\begin{tabular}{ll}
-\multicolumn{2}{l}{\textbf{Leaves in the \texttt{Tracks} branch}}\\
+\multicolumn{2}{l}{\textbf{Leaves in the \texttt{Tracks} branch (\texttt{Analysis} tree)}}\\
     \texttt{~~~float Eta }     &\texttt{ // pseudorapidity at the beginning of the track }\\
     \texttt{~~~float Phi }     &\texttt{ // azimuthal angle at the beginning of the track }\\
@@ -1131,10 +1179,10 @@
     \texttt{~~~float Py }      &\texttt{ // track momentum vector (x component) in GeV$/c$ }\\
     \texttt{~~~float Pz }      &\texttt{ // track momentum vector (x component) in GeV$/c$ }\\
-    \texttt{~~~float Charge }  &\texttt{ // track charge }\\
+    \texttt{~~~float Charge }  &\texttt{ // track charge in units of $e$ }\\
 \end{tabular}
 \end{quote}
 \begin{quote}
 \begin{tabular}{ll}
-\multicolumn{2}{l}{\textbf{Leaves in the \texttt{CaloTower} branch}}\\
+\multicolumn{2}{l}{\textbf{Leaves in the \texttt{CaloTower} branch (\texttt{Analysis} tree)}}\\
     \texttt{~~~float Eta }     &\texttt{ // pseudorapidity of the tower }\\
     \texttt{~~~float Phi }     &\texttt{ // azimuthal angle of the tower in rad }\\
@@ -1144,5 +1192,5 @@
     \texttt{~~~float ET }      &\texttt{ // tower transverse energy in GeV }\\
 & \\
-\multicolumn{2}{l}{\textbf{Leaves in the \texttt{ETmis} branch}}\\
+\multicolumn{2}{l}{\textbf{Leaves in the \texttt{ETmis} branch (\texttt{Analysis} tree)}}\\
     \texttt{~~~float Phi }     &\texttt{ // azimuthal angle of the transverse missing energy in rad }\\
     \texttt{~~~float ET }      &\texttt{ // transverse missing energy in GeV }\\
@@ -1151,4 +1199,44 @@
 \end{tabular}
 \end{quote}
+
+The hits in very forward detector (\textsc{zdc, rp220, fp420}) have some common data. In particular, the \texttt{side} variable tells in which detector (left:-1 or right:+1 of the interaction point) the hit has been seen. Moreover, some generator level data is provided for information, as the correspondance with the contents of the \texttt{GEN} tree is not possible. These generator-level data correspond to the particle kinematics (energy, momentum, angle) and identification (pid).
+
+\begin{quote}
+\begin{tabular}{ll}
+\multicolumn{2}{l}{\textbf{Common leaves for ZDC, RP220, FP420}}\\
+   \texttt{~~~float T } &\texttt{ // time of flight  in s }\\
+   \texttt{~~~float E } &\texttt{ // measured/smeared energy in GeV }\\
+   \texttt{~~~int side }&\texttt{ // -1 or +1 }\\
+\multicolumn{2}{l}{Generator level data}\\
+   \texttt{~~~int pid;     }&\texttt{ // particle ID }\\
+   \texttt{~~~float genPx;    }&\texttt{ // particle momentum vector (x component) in GeV$/c$ }\\
+   \texttt{~~~float genPy;    }&\texttt{ // particle momentum vector (y component) in GeV$/c$ }\\
+   \texttt{~~~float genPz;    }&\texttt{ // particle momentum vector (z component) in GeV$/c$ }\\
+   \texttt{~~~float genPT;    }&\texttt{ // particle transverse momentum in GeV$/c$ }\\
+   \texttt{~~~float genEta;   }&\texttt{ // particle pseudorapidity   }\\
+   \texttt{~~~float genPhi;   }&\texttt{ // particle azimuthal angle in rad }\\
+\end{tabular}
+\end{quote}
+
+\begin{quote}
+\begin{tabular}{ll}
+\multicolumn{2}{l}{\textbf{Additional leaves in the \texttt{ZDChits} branch (\texttt{Analysis} tree)}}\\
+   \texttt{~~~int hadronic\_hit } &\texttt{ // 0(is not hadronic) or 1(is hadronic) }
+\end{tabular}
+\end{quote}
+
+\begin{quote}
+\begin{tabular}{ll}
+\multicolumn{2}{l}{\textbf{Additional leaves in the \texttt{RP220hits} and \texttt{FP420hits} branches (\texttt{Analysis} tree)}}\\
+   \texttt{~~~flaot S } &\texttt{ // detector position from IP in m } \\
+   \texttt{~~~float X } &\texttt{ // hit horizontal position in m } \\
+   \texttt{~~~float Y } &\texttt{ // hit vertical position in m }   \\
+   \texttt{~~~float TX } &\texttt{ // hit horizontal angle in rad } \\
+   \texttt{~~~float TY } &\texttt{ // hit vertical angle in rad } \\
+   \texttt{~~~float q2 } &\texttt{ // reconstructed momentum transfer in GeV$^2$ }
+\end{tabular}
+\end{quote}
+The hit position is computed from the center of the beam position, not from the edge of the detector.
+
  
 \subsection{Running an analysis on your \textsc{Delphes} events}
@@ -1206,5 +1294,5 @@
 \end{verbatim}
 \end{quote}
-Mathematical operations on several \textit{leaves} are possible within a given \textit{tree}:
+Mathematical operations on several \textit{leaves} are possible within a given \textit{tree}, following the C++ syntax:
 \begin{quote}
 \begin{verbatim}
@@ -1213,5 +1301,5 @@
 \end{verbatim}
 \end{quote}
-Finally, to prepare an deeper analysis, the \texttt{MakeClass} method is useful:
+Finally, to prepare an deeper analysis, the \texttt{MakeClass} method is useful. It creates two files (\texttt{*.h} and \texttt{*.C}) with automatically generated code that allows the access to all branches and leaves of the corresponding tree:
 \begin{quote}
 \begin{verbatim}
@@ -1221,4 +1309,5 @@
 \end{verbatim}
 \end{quote}
+For more information, refer to ROOT documentation. Moreover, an example of code (based on the output of \begin{verbatim}MakeClass\end{verbatim}) is provided in the \texttt{Examples/} directory.
 
 To run the \texttt{Examples/Analysis\_Ex.cpp} code, the two following arguments are required: a text file containing the input \textsc{Delphes} \textsc{root} files to run, and the name of the output \textsc{root} file. 
@@ -1228,4 +1317,5 @@
 \end{verbatim}
  \end{quote}
+One can easily edit, modify and compile (\begin{verbatim}make\end{verbatim}) changes in this file.
  
 \subsubsection{Adding the trigger information}
@@ -1242,5 +1332,5 @@
 \begin{itemize}
 \item If the { \verb FLAG_frog } was switched on in the smearing card, two files have been created during the running of \textsc{Delphes}: {\verb DelphesToFrog.vis } and {\verb DelphesToFrog.geom }. They contain all the needed pieces of information to run \textsc{frog}.
-\item To display the events and the geometry, you first need to compile \textsc{Frog}. Go to the {\verb Utilities/FROG } and type {\verb make }. This compilation is done once for all, with this geometry (i.e. as long as the \texttt{*vis} and \texttt{*geom} files do not change).
+\item To display the events and the geometry, you first need to compile \textsc{Frog}. Go to the {\verb Utilities/FROG } and type {\verb make }. This compilation is done once for all, with this geometry (i.e.\ as long as the \texttt{*vis} and \texttt{*geom} files do not change).
 \item Go back into the main directory and type 
 \begin{quote}
@@ -1264,5 +1354,5 @@
   7   6   0.000   0.845  62.574   0.000   0.000   0.000   0.000   0.000  0.000
 \end{verbatim}
-Each row in an event starts with a unique number (i.e. in first column). 
+Each row in an event starts with a unique number (i.e.\ in first column). 
 Row \texttt{0} contains the event number (here: \texttt{57}) and some trigger information (here: \texttt{0}. This very particular trigger encoding is not implemented in \textsc{Delphes}.). 
 Subsequent rows list the reconstructed high-level objects. 
