Changeset 325 in svn
- Timestamp:
- Mar 11, 2009, 11:14:16 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/paper/notes.tex
r324 r325 29 29 \pdfinfo{ 30 30 /Author (S. Ovyn, X. Rouby, V. Lemaitre) 31 /Title (Delphes, a framework for fast simulation of a gener ic collider experiment)31 /Title (Delphes, a framework for fast simulation of a general-purpose LHC detector) 32 32 /Subject () 33 /Keywords (Delphes, Fast simulation, smearing, reconstruction, trigger, event display, LHC, Hector, FastJet, Frog)}33 /Keywords (Delphes, Fast simulation, LHC, FROG, Hector, Smearing, FastJet)} 34 34 \else 35 35 \usepackage[dvips]{graphicx} … … 60 60 \begin{abstract} 61 61 It is always delicate to know whether theoretical predictions are visible and measurable in a high energy collider experiment due to the complexity of the related detectors, data acquisition chain and software. 62 We introduce here a new \texttt{C++}-based 62 We introduce here a new \texttt{C++}-basedframework, \textsc{Delphes}, for fast simulation of 63 63 a general-purpose experiment. The simulation includes a tracking system, embedded into a magnetic field, calorimetry and a muon 64 64 system, and possible very forward detectors arranged along the beamline. … … 69 69 70 70 \noindent 71 \textit{Keywords:} \textsc{Delphes}, fast simulation, trigger, event display, \textsc{lhc}, \textsc{FastJet}, \textsc{Hector}, \textsc{Frog}\\71 \textit{Keywords:} \textsc{Delphes}, fast simulation, \textsc{lhc}, smearing, trigger, \textsc{FastJet}, \textsc{Hector}, \textsc{Frog}\\ 72 72 \href{http://www.fynu.ucl.ac.be/delphes.html}{http://www.fynu.ucl.ac.be/delphes.html}\\ 73 73 \textit{Preprint:} \texttt{CP3-09-01} … … 80 80 81 81 \section{Introduction} 82 % Motiver l'utilisation d'un simulateur rapide 83 % - 1) rapide VS lent 84 % - 2) relativement bonne prédiction en premiÚre approximation 85 % - 3) permet de comparer 82 86 83 87 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. … … 87 91 A new framework, called \textsc{Delphes}~\cite{bib:Delphes}, is introduced here, for the fast simulation of a general-purpose collider experiment. 88 92 Using the framework, observables can be estimated for specific signal and background channels, as well as their production and measurement rates. 89 Starting from the output of event generators, the simulation of the detector response takes into account the subdetector resolutions, by smearing the kinematic properties of the final-state particles\footnote{ Throughout the paper, final-state particles refer as particles considered as stable by the event generator.}. Tracks of charged particles and deposits of energy in calorimetric cells (or \textit{calotowers}) are then created.93 Starting from the output of event generators, the simulation of the detector response takes into account the subdetector resolutions, by smearing the kinematic properties of the final-state particles\footnote{throughout the paper, final-state particles refer as particles considered as stable by the event generator.}. Tracks of charged particles and deposits of energy in calorimetric cells (or \textit{calotowers}) are then created. 90 94 91 95 \textsc{Delphes} includes the most crucial experimental features, such as (Fig.~\ref{fig:FlowChart}): … … 104 108 \caption{Flow chart describing the principles behind \textsc{Delphes}. Event files coming from external Monte Carlo generators are read by a converter stage (top). 105 109 The kinematics variables of the final-state particles are then smeared according to the tunable subdetector resolutions. 106 Tracks are reconstructed in a simulated solenoidalmagnetic field and calorimetric towers sample the energy deposits. Based on these low-level objects, dedicated algorithms are applied for particle identification, isolation and reconstruction.110 Tracks are reconstructed in a simulated dipolar magnetic field and calorimetric towers sample the energy deposits. Based on these low-level objects, dedicated algorithms are applied for particle identification, isolation and reconstruction. 107 111 The transport of very forward particles to the near-beam detectors is also simulated. 108 Finally, an output file is written, including generator-level and analysis-object data. 109 If requested, a fully parametrisable trigger can be emulated. Optionally, the geometry and visualisation files for the 3D event display can also be produced. 110 All user parameters are set in the \textit{Detector/Smearing Card} and the \textit{Trigger Card}. } 112 Finally, an output file is written, including generator-level and analysis-object data. If requested, a fully parametrisable trigger can be emulated. Optionally, the geometry and visualisation files for the 3D event display can also be produced. 113 All user parameters are set in the \textit{Smearing Card} and the \textit{Trigger Card}. } 111 114 \label{fig:FlowChart} 112 115 \end{center} … … 119 122 120 123 \textsc{Delphes} uses the \texttt{ExRootAnalysis} utility~\cite{bib:ExRootAnalysis} to create output data in a \texttt{*.root} ntuple. 121 This output contains a copy of the generator-level data (\textsc{gen} tree), the analysis data objects after reconstruction (\mbox{\textsc{A}nalysis} tree), and possibly the results of the trigger emulation (\mbox{\textsc{T}rigger} tree). 122 In option\footnote{\texttt{[code]} See the \texttt{FLAG\_lhco} variable in the detector datacard. This text file format is shortly described in the user manual.}, \textsc{Delphes} can produce a reduced output file in \texttt{*.lhco} text format, which is limited to the list of the reconstructed high-level objects in the final states. 123 124 The program is driven by input cards. The detector card (\texttt{data/DetectorCard.dat}) allows a large spectrum of running conditions by modifying basic detector parameters, including calorimeter and tracking coverage and resolution, thresholds or jet algorithm parameters. The trigger card (\texttt{data/TriggerCard.dat}) lists the user algorithms for the simplified online 125 preselection. 124 This output contains a copy of the generator-level data (\textsc{gen} tree), the analysis data objects after reconstruction (\mbox{\textsc{A}nalysis} tree), and possibly the results of the trigger emulation (\mbox{\textsc{T}rigger} tree). The program is driven by input cards. The detector card (\texttt{data/DataCardDet.dat}) allows a large spectrum of running conditions by modifying basic detector parameters, including calorimeter and tracking coverage and resolution, thresholds or jet algorithm parameters. The trigger card (\texttt{data/trigger.dat}) lists the user algorithms for the simplified online preselection.\\ 126 125 127 126 … … 130 129 The overall layout of the general-purpose detector simulated by \textsc{Delphes} is shown in Fig.~\ref{fig:GenDet3}. 131 130 A central tracking system (\textsc{tracker}) is surrounded by an electromagnetic and a hadron calorimeters (\textsc{ecal} and \textsc{hcal}, resp.). Two forward calorimeters (\textsc{fcal}) ensure a larger geometric coverage for the measurement of the missing transverse energy. Finally, a muon system (\textsc{muon}) encloses the central detector volume 132 The fast simulation of the detector response takes into account geometrical acceptance of sub-detectors and their finite resolution, as defined in the detectordata card\footnote{\texttt{[code] }See the \texttt{RESOLution} class.}.133 If no such file is provided, predefined values based on ``typical'' \textsc{cms} acceptances and resolutions are used \footnote{\texttt{[code] }Detector and trigger cards for the \textsc{atlas} and \textsc{cms} experiments are also provided in \texttt{data/} directory.}. The geometrical coverage of the various subsystems used in the default configuration are summarised in Tab.~\ref{tab:defEta}.131 The fast simulation of the detector response takes into account geometrical acceptance of sub-detectors and their finite resolution, as defined in the smearing data card\footnote{\texttt{[code] }See the \texttt{RESOLution} class.}. 132 If no such file is provided, predefined values based on ``typical'' \textsc{cms} acceptances and resolutions are used. The geometrical coverage of the various subsystems used in the default configuration are summarised in Tab.~\ref{tab:defEta}. 134 133 135 134 \begin{table*}[t] … … 137 136 \caption{Default extension in pseudorapidity $\eta$ of the different subdetectors. 138 137 Full azimuthal ($\phi$) acceptance is assumed. 139 The corresponding parameter name, in the detectorcard, is given. \vspace{0.5cm}}138 The corresponding parameter name, in the smearing card, is given. \vspace{0.5cm}} 140 139 \begin{tabular}{llcc} 141 140 \hline … … 165 164 166 165 \subsubsection*{Magnetic field} 167 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.166 In addition to the subdetectors, the effects of a dipolar 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. 168 167 169 168 … … 171 170 \subsection{Tracks reconstruction} 172 171 Every stable charged particle with a transverse momentum above some threshold and lying inside the detector volume covered by the tracker provides a track. 173 By default, a track is assumed to be reconstructed with $90\%$ probability\footnote{\texttt{[code]} The reconstruction efficiency is defined in the detectordatacard by the \texttt{TRACKING\_EFF} term.} if its transverse momentum $p_T$ is higher than $0.9~\textrm{GeV}/c$ and if its pseudorapidity $|\eta| \leq 2.5$.172 By default, a track is assumed to be reconstructed with $90\%$ probability\footnote{\texttt{[code]} The reconstruction efficiency is defined in the smearing datacard by the \texttt{TRACKING\_EFF} term.} if its transverse momentum $p_T$ is higher than $0.9~\textrm{GeV}/c$ and if its pseudorapidity $|\eta| \leq 2.5$. 174 173 175 174 … … 187 186 The particle four-momentum $p^\mu$ are smeared with a parametrisation directly derived from typical detector technical designs\footnote{\texttt{[code] }~\cite{bib:cmsjetresolution,bib:ATLASresolution}. The response of the detector is applied to the electromagnetic and the hadronic particles through the \texttt{SmearElectron} and \texttt{SmearHadron} functions.}. 188 187 In the default parametrisation, the calorimeter is assumed to cover the pseudorapidity range $|\eta|<3$ and consists in an electromagnetic and hadronic parts. Coverage between pseudorapidities of $3.0$ and $5.0$ is provided by forward calorimeters, with different response to electromagnetic objects ($e^\pm, \gamma$) or hadrons. 189 Muons and neutrinos are assumed not to interact with the calorimeters\footnote{In the current \textsc{Delphes} version, particles other than delectrons ($e^\pm$), photons ($\gamma$), muons ($\mu^\pm$) and neutrinos ($\nu_e$, $\nu_\mu$ and $\nu_\tau$) are simulated as hadrons for their interactions with the calorimeters. The simulation of stable particles beyond the Standard Model should therefore be handled with care.}.188 Muons and neutrinos are assumed not to interact with the calorimeters\footnote{In the current \textsc{Delphes} version, particles other than electrons ($e^\pm$), photons ($\gamma$), muons ($\mu^\pm$) and neutrinos ($\nu_e$, $\nu_\mu$ and $\nu_\tau$) are simulated as hadrons for their interactions with the calorimeters. The simulation of stable particles beyond the Standard Model should therefore be handled with care.}. 190 189 The default values of the stochastic, noise and constant terms are given in Tab.~\ref{tab:defResol}.\\ 191 190 … … 193 192 \begin{center} 194 193 \caption{Default values for the resolution of the central and forward calorimeters. Resolution is parametrised by the \textit{stochastic} ($S$), \textit{noise} ($N$) and \textit{constant} ($C$) terms (Eq.~\ref{eq:caloresolution}). 195 The corresponding parameter name, in the detectorcard, is given. \vspace{0.5cm}}194 The corresponding parameter name, in the smearing card, is given. \vspace{0.5cm}} 196 195 \begin{tabular}[!h]{lllc} 197 196 \hline … … 230 229 \end{equation} 231 230 where $0 \leq F \leq 1$. The electromagnetic part is handled the same way for the electrons and photons. 232 The resulting calorimetry energy measurement given after the application of the smearing is then $E = E_{\textsc{hcal}} + E_{\textsc{ecal}}$. For $K_S^0$ and $\Lambda$ hadrons \footnote{\texttt{[code]} To implement different ratios for other particles, see the \texttt{BlockClasses} class.}, the energy fraction is $F$ is assumed to be $0.7$.\\231 The resulting calorimetry energy measurement given after the application of the smearing is then $E = E_{\textsc{hcal}} + E_{\textsc{ecal}}$. For $K_S^0$ and $\Lambda$ hadrons, the energy fraction is $F$ is assumed to be $0.7$.\\ 233 232 234 233 \subsection{Calorimetric towers} 235 234 236 235 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}. 237 As the detector is assumed to be cylindical (e.g. symmetric in $\phi$ and with respect to the $\eta=0$ plane), the detectorcard 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.236 As the detector is assumed to be cylindical (e.g. symmetric in $\phi$ and with respect to the $\eta=0$ plane), the smearing 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. 238 237 239 238 \begin{figure}[!h] … … 245 244 \end{figure} 246 245 247 The calorimetric towers directly enter in the calculation of the missing transverse energy (\textsc{met}), and as input for the jet reconstruction algorithms. No sharing between neighbouring towers is implemented when particles enter a tower very close to its geometrical edge. Smearing is applied directly on the accumulated electromagnetic and hadronic energies of each calorimetric tower.246 The calorimetric towers directly enter in the calculation of the missing transverse energy (\textsc{met}), and as input for the jet reconstruction algorithms. No sharing between neighbouring towers is implemented when particles enter a tower very close to its geometrical edge. 248 247 249 248 \subsection{Very forward detectors simulation} … … 307 306 \subsection{Photon and charged lepton reconstruction} 308 307 From here onwards, \textit{electrons} refer to both positrons ($e^+$) and electrons ($e^-$), and $\textit{charged leptons}$ refer to electrons and muons ($\mu^\pm$), leaving out the $\tau^\pm$ leptons as they decay before being detected. 309 310 308 \subsubsection*{Electrons and photons} 311 309 Electron ($e^\pm$) and photon candidates are reconstructed if they fall into the acceptance of the tracking system and have a transverse momentum above a threshold (default $p_T > 10~\textrm{GeV}/c$). A calorimetric tower will be seen in the detector, an electrons will leave in addition a track. Subsequently, electrons and photons create a candidate in the jet collection. 312 Assuming a good measurement of the track parameters in the real experiment, the electron energy can be reasonably recovered. In \textsc{Delphes}, electron energy is smeared according to the resolution of the calorimetric tower where it points to, but independently from any other deposited energy is this tower. This approach is still conservative as the calorimeter resolution is worse than the tracker one.313 310 314 311 \subsubsection*{Muons} 312 315 313 Generator-level muons entering the detector acceptance are considered as candidates for the analysis level. 316 314 The acceptance is defined in terms of a transverse momentum threshold to be overpassed that should be computed using the chosen geometry of the detector and the magnetic field considered (default : $p_T > 10~\textrm{GeV}/c$) and of the pseudorapidity coverage of the muon system (default: $-2.4 \leq \eta \leq 2.4$). 317 The application of the detector resolution on the muon momentum depends on a Gaussian smearing of the $p_T$ variable\footnote{\texttt{[code]} See the \texttt{SmearMuon} method.}. Neither $\eta$ nor $\phi$ variables are modified beyond the calorimeters: no additional magnetic field is applied. Multiple scattering is neglected. This implies that low energy muons have in \textsc{Delphes} a better resolution than in a real detector. Furthermore, muons leave no deposit in calorimeters.315 The application of the detector resolution on the muon momentum depends on a Gaussian smearing of the $p_T$ variable\footnote{\texttt{[code]} See the \texttt{SmearMuon} method.}. Neither $\eta$ nor $\phi$ variables are modified beyond the calorimeters: no additional magnetic field is applied. In addition, multiple scattering is also neglected. This implies that low energy muons have in \textsc{Delphes} a better resolution than in a real detector. Moreover, muons leave no deposit in calorimeters. 318 316 319 317 \subsubsection*{Charged lepton isolation} 320 318 321 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. 322 The result (i.e. \textit{isolated} or \textit{not}) is added to the charged lepton measured properties. 323 In addition, the sum $P_T$ of the transverse momenta of all tracks but the lepton one within the isolation cone is 324 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.}: 325 $$ P_T = \sum_{i \neq \mu}^\textrm{tracks} p_T(i)$$ 326 327 No calorimetric isolation is applied, but the muon collection contains also the ratio $\rho_\mu$ between (1) the sum of the transverse energies in all calotowers in a $N \times N$ grid around the muon, and (2) the muon transverse 328 momentum\footnote{\texttt{[code] }Calorimetric isolation parameters in the detector card are \texttt{ISOL\_Calo\_ET} and \texttt{ISOL\_Calo\_Grid}.}: 329 $$ \rho_\mu = \frac{\Sigma_i E_T(i)}{p_T(\mu)}~,~ i\textrm{ in }N \times N \textrm { grid centered on }\mu.$$ 319 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\footnote{\texttt{[code] }See the \texttt{IsolFlag} output of the \texttt{Electron} or \texttt{Muon} collections in the \texttt{Analysis} tree.}. No calorimetric isolation is applied. \\ 320 330 321 331 322 … … 337 328 338 329 A realistic analysis requires a correct treatment of particles which have hadronised. Therefore, the most widely currently used jet algorithms have been integrated into the \textsc{Delphes} framework using the \textsc{FastJet} tools~\cite{bib:FastJet}. 339 Six different jet reconstruction schemes are available\footnote{\texttt{[code] }The choice is done by allocating the \texttt{JET\_jetalgo } input parameter in the detectorcard.}. The first three belong to the cone algorithm class while the last three are using a sequential recombination scheme. For all of them, the towers are used as input for the jet clustering. Jet algorithms differ in their sensitivity to soft particles or collinear splittings, and in their computing speed performances.330 Six different jet reconstruction schemes are available\footnote{\texttt{[code] }The choice is done by allocating the \texttt{JET\_jetalgo } input parameter in the smearing card.}. The first three belong to the cone algorithm class while the last three are using a sequential recombination scheme. For all of them, the towers are used as input for the jet clustering. Jet algorithms differ in their sensitivity to soft particles or collinear splittings, and in their computing speed performances. 340 331 By default, reconstruction uses a cone algorithm with $\Delta R=0.7$. 341 Jets are stored if their transverse energy is higher\footnote{\texttt{[code] PTCUT\_jet }variable in the detectorcard.} than $20~\textrm{GeV}$.332 Jets are stored if their transverse energy is higher\footnote{\texttt{[code] PTCUT\_jet }variable in the smearing card.} than $20~\textrm{GeV}$. 342 333 343 334 \subsubsection*{Cone algorithms} … … 349 340 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. 350 341 The existing \textsc{FastJet} code has been modified to allow easy modification of the tower pattern in $\eta$, $\phi$ space. 351 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 detectorcard.}.342 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 smearing card.}. 352 343 353 344 \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. … … 394 385 \subsection{$b$-tagging} 395 386 396 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.}. 387 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{TAGGING\_B}, \texttt{MISTAGGING\_C} and \texttt{MISTAGGING\_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.} 388 %(Fig.~\ref{fig:btag}) 389 . 397 390 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$). 391 392 %\begin{figure}[!h] 393 %\begin{center} 394 %\includegraphics[width=0.6\columnwidth]{btag} 395 %\caption{Default efficiency of $b$-tag for jets coming from $b$ quarks, $c$ quarks and from other particles (jets from gluons or $u$, $d$ and $s$ quarks).} 396 %\label{fig:btag} 397 %\end{center} 398 %\end{figure} 399 398 400 399 401 \subsection{\texorpdfstring{$\tau$}{\texttau} identification} … … 526 528 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$. 527 529 528 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.530 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/trigger.dat} file.}. When enabled, this trigger is applied on analysis-object data. 529 531 In a real experiment, the online selection is often divided into several steps (or \textit{levels}). 530 532 This splits the overall reduction factor into a product of smaller factors, corresponding to the different trigger levels. … … 606 608 The resolution $\sigma_x$ of the horizontal component of \textsc{met} is observed to behave like 607 609 \begin{equation} 608 \sigma_x = \alpha ~\sqrt {E_T}~~~(\mathrm{GeV}^{1/2}),610 \sigma_x = \alpha ~\sqrt(E_T) ~~~(\mathrm{GeV}^{1/2}), 609 611 \end{equation} 610 612 where the $\alpha$ parameter depends on the resolution of the calorimeters. 611 613 612 The \textsc{met} resolution expected for the \textsc{cms} detector for similar events is $\sigma_x = (0.6-0.7) ~ \sqrt {E_T}~ \mathrm{GeV}^{1/2}$ with no pile-up\footnote{\textit{Pile-up} events are extra simultaneous $pp$ collision occurring at high-luminosity in the same bunch crossing.}~\cite{bib:cmsjetresolution}, which compares very well with the $\alpha = 0.68$ obtained with \textsc{Delphes}.614 The \textsc{met} resolution expected for the \textsc{cms} detector for similar events is $\sigma_x = (0.6-0.7) ~ \sqrt(E_T) ~ \mathrm{GeV}^{1/2}$ with no pile-up\footnote{\textit{Pile-up} events are extra simultaneous $pp$ collision occurring at high-luminosity in the same bunch crossing.}~\cite{bib:cmsjetresolution}, which compares very well with the $\alpha = 0.68$ obtained with \textsc{Delphes}. 613 615 614 616 \subsection{\texorpdfstring{$\tau$}{\texttau}-jet efficiency} … … 645 647 % The outer layer of the central system (red) consist of a muon system. 646 648 % In addition, two end-cap calorimeters (blue) extend the pseudorapidity coverage of the central detector. 647 % The actual detector granularity and extension is defined in the detectorcard.649 % The actual detector granularity and extension is defined in the smearing card. 648 650 % The detector is assumed to be strictly symmetric around the beam axis (black line). 649 651 % Additional forward detectors are not depicted.} … … 753 755 P. Demin, (2006), unpublished. Now part of \textsc{MadGraph/MadEvent}. 754 756 \bibitem{bib:cmsjetresolution} The CMS Collaboration, \textbf{CERN/LHCC} \\ \href{http://documents.cern.ch/cgi-bin/setlink?base=lhcc&categ=public&id=lhcc-2006-001}{2006-001}. 755 \bibitem{bib:ATLASresolution} The ATLAS Collaboration, \ textbf{CERN-OPEN} 2008-020,arXiv:\href{http://arxiv.org/abs/arxiv:0901.0512}{0901.0512v1}[hep-ex].757 \bibitem{bib:ATLASresolution} The ATLAS Collaboration, \\ arXiv:\href{http://arxiv.org/abs/arxiv:0901.0512}{0901.0512v1}[hep-ex]. 756 758 \bibitem{bib:Hector} %\textsc{Hector}, \textit{a fast simulator for the transport of particles in beamlines}, 757 759 X. Rouby, J. de Favereau, K. Piotrzkowski, \textbf{JINST} \href{http://www.iop.org/EJ/abstract/1748-0221/2/09/P09005}{2 P09005 (2007)}. … … 781 783 \bibitem{bib:papierquisortirajamais}J. de Favereau~et~al, \textbf{CP3-08-04} (2008), to be published in EPJ. 782 784 783 \bibitem{bib:papiersimon} ``Phenomenology of a twisted two-Higgs-doublet model'', Simon de Visscher, Jean-Marc Gerard, Michel Herquet, Vincent Lema\^itre, Fabio Maltoni, to be published.785 \bibitem{bib:papiersimon} "Phenomenology of a twisted two-Higgs-doublet model", Simon de Visscher, Jean-Marc Gerard, Michel Herquet, Vincent Lemaitre, Fabio Maltoni, to be published. 784 786 785 787 \bibitem{bib:mcfio} P. Lebrun, L. Garren, Copyright (c) 1994-1995 Universities Research Association, Inc. … … 793 795 \section{User manual} 794 796 795 The available \texttt{C++}-code is compressed in a zipped tar file which contains with everything needed to run the \textsc{Delphes} package, assuming a running \textsc{root} installation. 796 The package includes \texttt{ExRootAnalysis}~\cite{bib:ExRootAnalysis}, \textsc{Hector}~\cite{bib:Hector}, 797 \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}. 797 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}. 798 798 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/}. 799 799 … … 812 812 \end{verbatim} 813 813 \end{quote} 814 Due to the large number of external utilities, the number of printed lines during the compilation can be high. 815 The user should not pay attention to possible warning messages. 816 When compilation is completed, the following message is printed: 814 Due to the large number of external utilities, the number of printed lines during the compilation can be high. The user should not pay attention to possible warning messages. When compilation is completed, the following message is printed: 817 815 \begin{quote} 818 816 \begin{verbatim} … … 824 822 \subsection{Running \textsc{Delphes} on your events} 825 823 826 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 no vice 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).824 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). 827 825 828 826 \begin{quote} … … 834 832 \subsubsection{Setting up the configuration} 835 833 836 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. 837 Please note that if the user does not provide these two 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. 834 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. 838 835 839 836 \begin{enumerate} … … 841 838 \item{\bf The detector card } 842 839 843 The \textit{detector} or \textit{smearing} card is by default \texttt{data/DataCard.dat}.844 840 It contains all pieces of information needed to run \textsc{Delphes}: 845 841 \begin{itemize} 846 \item detector parameters, including calorimeter and tracking coverage and resolution , transverse energy thresholds for object reconstruction and jet algorithm parameters.847 \item four flags ({\verb FLAG_bfield }, {\verb FLAG_vfd }, {\verb FLAG_trigger } and {\verb FLAG_frog }), should be set in order to configure the magnetic field propagation, the very forward detectors simulation, the trigger selection and the preparation for \textsc{Frog} display(respectively).842 \item detector parameters, including calorimeter and tracking coverage and resolutions, transverse energy thresholds for object reconstruction and jet algorithm parameters. 843 \item six flags ({\verb FLAG_bfield }, {\verb FLAG_vfd }, {\verb FLAG_RP }, {\verb FLAG_trigger }, {\verb FLAG_frog } and {\verb FLAG_lhco }), should be set in order to configure the magnetic field propagation, the very forward detectors simulation, the use of very forward taggers, the trigger selection, the preparation for \textsc{Frog} display and the creation of an output file in *.lhco text format (respectively). 848 844 \end{itemize} 849 845 … … 859 855 # Energy resolution for electron/photon 860 856 # \sigma/E = C + N/E + S/\sqrt{E}, E in GeV 861 ELG_Scen 0.05 // S term for central ECAL862 ELG_Ncen 0.25 // N term for central ECAL863 ELG_Ccen 0.005 // C term for central ECAL864 ELG_ Cfwd 0.107// S term for FCAL865 ELG_ Sfwd 2.084 // Cterm for FCAL866 ELG_ Nfwd 0.0 // Nterm for FCAL867 857 ELG_Scen 0.05 // S term for central ECAL 858 ELG_Ncen 0.25 // N term for central ECAL 859 ELG_Ccen 0.005 // C term for central ECAL 860 ELG_Sfwd 2.084 // S term for FCAL 861 ELG_Nfwd 0.0 // N term for FCAL 862 ELG_Cfwd 0.107 // C term for FCAL 863 868 864 # Energy resolution for hadrons in ecal/hcal/hf 869 865 # \sigma/E = C + N/E + S/\sqrt{E}, E in GeV … … 906 902 ### the list ends with the phi-size of the most forward tower 907 903 ### there should be NTOWER values 908 #TOWER_dphi 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 10904 TOWER_dphi 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 10 909 905 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 20 20 910 906 … … 915 911 PTCUT_gamma 10.0 916 912 PTCUT_taujet 10.0 917 913 914 # Charged lepton isolation. Pt and Et in GeV 915 ISOL_PT 2.0 //minimal pt of tracks for isolation criteria 916 ISOL_Cone 0.5 //Cone for isolation criteria 917 ISOL_Calo_ET 2.0 //minimal tower transverse energy for isolation criteria. 1E99 means "off" 918 ISOL_Calo_Cone 0.4 //Cone for calorimetric isolation 919 ISOL_Calo_Grid 3 //Grid size (N x N) for calorimetric isolation 920 918 921 # General jet variable 919 JET_coneradius 0.7 // generic jet radius 920 JET_jetalgo 1 // Jet algorithm selection 921 JET_seed 1.0 // minimum seed to start jet reconstruction, in GeV 922 922 JET_coneradius 0.7 // generic jet radius 923 JET_jetalgo 1 // 1 for Cone algorithm, 924 // 2 for MidPoint algorithm, 925 // 3 for SIScone algorithm, 926 // 4 for kt algorithm 927 // 5 for Cambridge/Aachen algorithm 928 // 6 for anti-kt algorithm 929 JET_seed 1.0 // minimum seed to start jet reconstruction, in GeV 930 923 931 # Tagging definition 924 932 BTAG_b 40 // b-tag efficiency (%) … … 927 935 928 936 # FLAGS 929 FLAG_bfield 0 // 1 to run the bfield propagation else 0 930 FLAG_vfd 1 // 1 to run the very forward detectors else 0 931 FLAG_trigger 1 // 1 to run the trigger selection else 0 932 FLAG_frog 1 // 1 to run the FROG event display 933 937 FLAG_bfield 1 //1 to run the bfield propagation else 0 938 FLAG_vfd 1 //1 to run the very forward detectors else 0 939 FLAG_RP 1 //1 to run the very forward detectors else 0 940 FLAG_trigger 1 //1 to run the trigger selection else 0 941 FLAG_frog 1 //1 to run the FROG event display 942 FLAG_lhco 1 //1 to run the LHCO 943 934 944 # In case BField propagation allowed 935 945 TRACK_radius 129 // radius of the BField coverage, in cm … … 938 948 TRACK_bfield_y 0 // Y component of the BField, in T 939 949 TRACK_bfield_z 3.8 // Z component of the BFieldn in T 940 950 941 951 # Very forward detector extension, in pseudorapidity 942 952 # if allowed 943 VFD_min_calo_vfd 5.2 // very forward calorimeter (if any) like CASTOR953 VFD_min_calo_vfd 5.2 // very forward calorimeter (if any) like CASTOR 944 954 VFD_max_calo_vfd 6.6 945 VFD_min_zdc 8.3 // zero-degree neutral calorimeter 946 VFD_s_zdc 140 // distance of the ZDC, from the IP, in [m] 947 948 RP_220_s 220 // distance of the RP to the IP, in meters 949 RP_220_x 0.002 // distance of the RP to the beam, in meters 950 RP_420_s 420 // distance of the RP to the IP, in meters 951 RP_420_x 0.004 // distance of the RP to the beam, in meters 952 955 VFD_min_zdc 8.3 // zero-degree neutral calorimeter 956 VFD_s_zdc 140 // distance of the Zero Degree Calorimeter, from the IP, in [m] 957 958 RP_220_s 220 // distance of the RP to the IP, in meters 959 RP_220_x 0.002 // distance of the RP to the beam, in meters 960 RP_420_s 420 // distance of the RP to the IP, in meters 961 RP_420_x 0.004 // distance of the RP to the beam, in meters 962 RP_beam1Card data/LHCB1IR5_v6.500.tfs 963 RP_beam2Card data/LHCB2IR5_v6.500.tfs 964 RP_IP_name IP5 965 953 966 # In case FROG event display allowed 954 967 NEvents_Frog 100 … … 962 975 963 976 This card contains the definitions of all trigger-bits. Cuts can be applied on the transverse momentum $p_T$ of electrons, muons, jets, $\tau$-jets, photons and the missing transverse energy. The following codes should be used so that \textsc{Delphes} can correctly translate the input list of trigger-bits into selection algorithms: 964 977 965 978 \begin{quote} 966 979 \begin{tabular}{ll} 967 980 {\it Trigger code} & {\it Corresponding object}\\ 968 981 {\verb ELEC_PT } & electron \\ 982 {\verb IElec_PT } & isolated electron \\ 969 983 {\verb MUON_PT } & muon \\ 984 {\verb IMuon_PT } & isolated muon \\ 970 985 {\verb JET_PT } & jet \\ 971 {\verb TAU JET_PT } & $\tau$-jet \\986 {\verb TAU_PT } & $\tau$-jet \\ 972 987 {\verb ETMIS_PT } & missing transverse energy \\ 973 988 {\verb GAMMA_PT } & photon \\ 989 {\verb Bjet_PT } & $b$-jet \\ 974 990 \end{tabular} 975 991 \end{quote} 976 992 977 993 Each line in the trigger datacard is allocated to exactly one trigger-bit and starts with the name of the corresponding trigger. 978 Logical combination of several conditions is also possible. 979 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. 994 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. 980 995 The default trigger card can be found in the data repository of \textsc{Delphes} (\texttt{data/TriggerCard.dat}). 981 996 An example of trigger table consistent with the previous rules is given here: … … 991 1006 \subsubsection{Running the code} 992 1007 993 First, create the detector and trigger cards (\texttt{data/ mydetector.dat} and \texttt{data/myTriggerCard.dat}). \\1008 First, create the detector and trigger cards (\texttt{data/DetectorCard.dat} and \texttt{data/TriggerCard.dat}). \\ 994 1009 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}). 995 1010 To run the code, type the following command (in one line) … … 997 1012 \begin{verbatim} 998 1013 me@mylaptop:~$ ./Delphes inputlist.list OutputRootFileName.root 999 data/ mydetector.dat data/myTriggerCard.dat1014 data/DetectorCard.dat data/TriggerCard.dat 1000 1015 \end{verbatim} 1001 1016 \end{quote} … … 1024 1039 \begin{tabular}{lll} 1025 1040 {\bf GEN \textsc{tree}} & &\\ 1026 ~~~Particle & generator particles from \textsc{hepevt} & {\verb TRootGenParticle }\\1041 ~~~Particle & generator particles from \textsc{hepevt} & {\verb GenParticle }\\ 1027 1042 {\bf Trigger } & &\\ 1028 1043 ~~~TrigResult & Acceptance of different trigger-bits & {\verb TRootTrigger }\\ … … 1031 1046 \begin{quote} 1032 1047 \begin{tabular}{lll} 1048 1033 1049 {\bf Analysis \textsc{tree}} & & \\ 1034 1050 ~~~Tracks & Collection of tracks & {\verb TRootTracks }\\ … … 1037 1053 ~~~Photon & Collection of photons & {\verb TRootPhoton }\\ 1038 1054 ~~~Muon & Collection of muons & {\verb TRootMuon }\\ 1039 ~~~Jet & Collection of jets 1055 ~~~Jet & Collection of jets & {\verb TRootJet }\\ 1040 1056 ~~~TauJet & Collection of jets tagged as $\tau$-jets & {\verb TRootTauJet }\\ 1041 1057 ~~~ETmis & Transverse missing energy information & {\verb TRootETmis }\\ … … 1046 1062 \end{quote} 1047 1063 The third column shows the names of the corresponding classes to be written in a \textsc{root} tree. 1048 All classes except \texttt{TRootTr igger}, \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}):1064 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}): 1049 1065 \begin{quote} 1050 1066 \begin{tabular}{ll} … … 1076 1092 \texttt{~~~float Z; }&\texttt{ // particle vertex position (z component, in mm) }\\ 1077 1093 \texttt{~~~float M; }&\texttt{ // particle mass in GeV$/c^2$}\\ 1078 \end{tabular} 1079 \end{quote} 1080 \begin{quote} 1081 \begin{tabular}{ll} 1094 &\\ 1082 1095 \multicolumn{2}{l}{\textbf{Additional leaves in \texttt{Electron} and \texttt{Muon} branches}} \\ 1083 \texttt{~~~int Charge } &\\ 1084 \texttt{~~~bool IsolFlag } &\\ 1096 \texttt{~~~int Charge } &\texttt{ // particle Charge }\\ 1097 \texttt{~~~bool IsolFlag } &\texttt{ // stores the result of the tracking isolation test }\\ 1098 \texttt{~~~float EtaCalo } &\texttt{ // particle pseudorapidity when entering the calo }\\ 1099 \texttt{~~~float PhiCalo } &\texttt{ // particle azimuthal angle in rad when entering the calo }\\ 1100 \texttt{~~~float EHoverEE }&\texttt{ // hadronic energy over electromagnetic energy }\\ 1101 \texttt{~~~float EtRatio } &\texttt{ // calo Et in NxN-tower grid around the muon over the muon Et }\\ 1085 1102 & \\ 1086 1103 \multicolumn{2}{l}{\textbf{Additional leaf in the \texttt{Jet} branch}} \\ 1087 \texttt{~~~bool Btag } &\\ 1104 \texttt{~~~bool Btag } &\texttt{ // stores the result of the b-tagging }\\ 1105 \texttt{~~~int NTracks }&\texttt{ // number of tracks asociated to the jet }\\ 1106 \texttt{~~~float EHoverEE }&\texttt{ // hadronic energy over electromagnetic energy }\\ 1088 1107 & \\ 1089 1108 \multicolumn{2}{l}{\textbf{Additional leaves in the \texttt{ZDChits} branch}}\\ 1090 \texttt{~~~float T; }&\texttt{ // time of flight in s }\\ 1091 \texttt{~~~int side; }&\texttt{ // -1 or +1 }\\ 1109 \texttt{~~~float T } &\texttt{ // time of flight in s }\\ 1110 \texttt{~~~int side }&\texttt{ // -1 or +1 }\\ 1111 \end{tabular} 1112 \end{quote} 1113 \begin{quote} 1114 \begin{tabular}{ll} 1115 \multicolumn{2}{l}{\textbf{Leaves in the \texttt{Tracks} branch}}\\ 1116 \texttt{~~~float Eta } &\texttt{ // pseudorapidity at the beginning of the track }\\ 1117 \texttt{~~~float Phi } &\texttt{ // azimuthal angle at the beginning of the track }\\ 1118 \texttt{~~~float EtaOuter }&\texttt{ // pseudorapidity at the end of the track }\\ 1119 \texttt{~~~float PhiOuter }&\texttt{ // azimuthal angle at the end of the track }\\ 1120 \texttt{~~~float PT } &\texttt{ // track transverse momentum in GeV$/c$ }\\ 1121 \texttt{~~~float E } &\texttt{ // track energy in GeV }\\ 1122 \texttt{~~~float Px } &\texttt{ // track momentum vector (x component) in GeV$/c$ }\\ 1123 \texttt{~~~float Py } &\texttt{ // track momentum vector (x component) in GeV$/c$ }\\ 1124 \texttt{~~~float Pz } &\texttt{ // track momentum vector (x component) in GeV$/c$ }\\ 1125 \texttt{~~~float Charge } &\texttt{ // track charge }\\ 1126 & \\ 1127 \multicolumn{2}{l}{\textbf{Leaves in the \texttt{CaloTower} branch}}\\ 1128 \texttt{~~~float Eta } &\texttt{ // pseudorapidity of the tower }\\ 1129 \texttt{~~~float Phi } &\texttt{ // azimuthal angle of the tower in rad }\\ 1130 \texttt{~~~float E } &\texttt{ // tower energy in GeV }\\ 1131 \texttt{~~~float E\_em } &\texttt{ // electromagnetic component of the tower energy in GeV}\\ 1132 \texttt{~~~float E\_had } &\texttt{ // hadronic component of the tower energy in GeV}\\ 1133 \texttt{~~~float ET } &\texttt{ // tower transverse energy in GeV }\\ 1134 & \\ 1135 \multicolumn{2}{l}{\textbf{Leaves in the \texttt{ETmis} branch}}\\ 1136 \texttt{~~~float Phi } &\texttt{ // azimuthal angle of the transverse missing energy in rad }\\ 1137 \texttt{~~~float ET } &\texttt{ // transverse missing energy in GeV }\\ 1138 \texttt{~~~float Px } &\texttt{ // x component of the transverse missing energy in GeV }\\ 1139 \texttt{~~~float Py } &\texttt{ // y vomponent of the transverse missing energy in GeV }\\ 1092 1140 \end{tabular} 1093 1141 \end{quote} … … 1171 1219 1172 1220 \subsubsection{Adding the trigger information} 1173 The \texttt{Examples/Trigger\_Only.cpp} code permits to run the trigger selection separately from the general detector simulation on output \textsc{Delphes} root files. 1174 A \textsc{Delphes} root file is mandatory as an input argument for the \texttt{Trigger\_Only} routine. 1175 The new \textit{tree} containing the trigger result data will be appended to this file. 1221 The \texttt{Examples/Trigger\_Only.cpp} code permits to run the trigger selection separately from the general detector simulation on output \textsc{Delphes} root files. A \textsc{Delphes} root file is mandatory as an input argument for the \texttt{Trigger\_Only} routine. The new \textit{tree} containing the trigger result data will be appended to this file. 1176 1222 The trigger datacard is also necessary. To run the code: 1177 1223 \begin{quote} … … 1184 1230 1185 1231 \begin{itemize} 1186 \item If the { \verb FLAG_frog } was switched on in the detectorcard, 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}.1232 \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}. 1187 1233 \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). 1188 1234 \item Go back into the main directory and type
Note:
See TracChangeset
for help on using the changeset viewer.