Changeset 100 in svn for trunk/paper/notes.tex
- Timestamp:
- Dec 18, 2008, 2:39:26 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/paper/notes.tex
r99 r100 1 \documentclass[a4paper,11pt,oneside, twocolumn]{article}1 \documentclass[a4paper,11pt,oneside,onecolumn]{article} 2 2 \usepackage[english]{babel} 3 3 \usepackage[ansinew]{inputenc} … … 11 11 \usepackage{latexsym} 12 12 \usepackage{array} 13 \usepackage{multicol} 13 14 14 15 \usepackage{fancyhdr} … … 18 19 \usepackage{ifpdf} 19 20 \usepackage{cite} 21 22 \newcommand{\dollar}{\$} 20 23 21 24 \ifpdf … … 39 42 \date{} 40 43 41 42 % The \textsc{Delphes} software provides a framework for fast simulation of particle interactions in a generic high-energy physics collider detector containing a tracking system, electromagnetic and hadronic calorimeters, and a muon system. It is an object-oriented system writen using the C++ programming language. Using input files originating from a Monte-Carlo event generator such as \textsc{pythia} and \textsc{herwig}, \textsc{Delphes} creates ``high-level" analysis objects.\\43 %44 44 \begin{document} 45 45 46 46 47 \twocolumn[48 47 \maketitle 49 % \begin{@twocolumnfalse} 50 \begin{onecolabstract} 48 51 49 Knowing whether theoretical predictions are visible and measurable in a high energy experiment is always delicate, due to the 52 50 complexity of the related detectors, data acquisition chain and software. We introduce here a new framework, \textsc{Delphes}, for fast simulation of … … 57 55 An overview of \textsc{Delphes} is given as well as a few use-cases for illustration. 58 56 \vspace{1cm} 59 \end{onecolabstract} 60 % \end{@twocolumnfalse} 61 ] 57 62 58 \saythanks 63 64 59 65 60 \section{Introduction} … … 91 86 \begin{tabular}[!h]{lll} 92 87 \hline 93 Sub-system & Card flag & $|\eta|^{max}$\\\hline 94 Tracking & {\verb MAX_TRACKER } & 2.5\\ 95 Calorimeters & {\verb MAX_CALO_CEN } & 3.0\\ 96 & {\verb MAX_CALO_FWD } & 5.0\\ 97 Muon & {\verb MAX_MU } & 2.4\\\hline 88 Tracking & {\verb CEN_max_tracker } & 2.5\\ 89 Calorimeters & {\verb CEN_max_calo_cen } & 3.0\\ 90 & {\verb CEN_max_calo_fwd } & 5.0\\ 91 Muon & {\verb CEN_max_mu } & 2.4\\\hline 98 92 \end{tabular} 99 93 \label{tab:defEta} … … 187 181 \subsection{Tau identification} 188 182 189 \begin{wrapfigure}{l}{0. 5\columnwidth}190 \includegraphics[width=0. 5\columnwidth]{Tau.eps}183 \begin{wrapfigure}{l}{0.3\columnwidth} 184 \includegraphics[width=0.3\columnwidth]{Tau.eps} 191 185 \caption{\small{detectorAng.eps}} 192 186 \label{h_WW_ss_cut1} … … 197 191 \subsubsection*{Electromagnetic collimation} 198 192 199 To use the narrowness of the $\tau$-jet, the \textit{electromagnetic collimation} ($C_{\tau}^{em}$) is defined as the sum of the energy in a cone with $\Delta R = ${\verb TAU_ CONE_ENERGIE } around the jet axis divided by the energy of the reconstructed jet. The energy in the small cone is calculated using the towers objects. To be taken into account a calorimeter tower should have a transverse energy above a given threshold {\verb M_SEEDTHRESHOLD}. A large fraction of the jet energy, denominated here with {\verb TAU_EM_COLLIMATION } is expected in this small cone. The quantity is represented in figure \ref{fig:tau1} for the default values (see table \ref{tab:tauRef})193 To use the narrowness of the $\tau$-jet, the \textit{electromagnetic collimation} ($C_{\tau}^{em}$) is defined as the sum of the energy in a cone with $\Delta R = ${\verb TAU_energy_scone } around the jet axis divided by the energy of the reconstructed jet. The energy in the small cone is calculated using the towers objects. To be taken into account a calorimeter tower should have a transverse energy above a given threshold {\verb JET_M_seed }. A large fraction of the jet energy, denominated here with {\verb TAU_energy_frac } is expected in this small cone. The quantity is represented in figure \ref{fig:tau1} for the default values (see table \ref{tab:tauRef}). 200 194 201 195 \begin{figure}[!h] 202 196 \begin{center} 203 \includegraphics[width=0.8\columnwidth]{figures/Taujets1.eps}197 %\includegraphics[width=0.8\columnwidth]{figures/Taujets1.eps} 204 198 \caption{\small{}} 205 199 \label{fig:tau1} … … 211 205 \begin{figure}[!h] 212 206 \begin{center} 213 \includegraphics[width=0.8\columnwidth]{figures/Taujets2.eps}207 %\includegraphics[width=0.8\columnwidth]{figures/Taujets2.eps} 214 208 \caption{\small{}} 215 209 \label{h_WW_ss_cut1} … … 217 211 \end{figure} 218 212 219 The tracking isolation for the $\tau$ identification requires that the number of tracks associated to a particle with $p_T >$ {\verb PT_TRACK_TAU } is one and only one in a cone with $\Delta R =$ {\verb TAU_CONE_TRACKS}. This cone should be entirely included in the tracker to be taken into account. This procedure selects taus decaying hadronically with a typical efficiency of $60\%$. Moreover, the minimal $p_T$ of the $\tau$-jet is required to be {\verb TAUJET_pt }(default value: 10~GeV).\\213 The tracking isolation for the $\tau$ identification requires that the number of tracks associated to a particle with $p_T >$ {\verb TAU_track_pt } is one and only one in a cone with $\Delta R =$ {\verb TAU_track_scone }. This cone should be entirely included in the tracker to be taken into account. This procedure selects taus decaying hadronically with a typical efficiency of $60\%$. Moreover, the minimal $p_T$ of the $\tau$-jet is required to be {\verb TAUJET_pt }(default value: 10~GeV).\\ 220 214 221 215 \begin{table}[!h] … … 224 218 \hline 225 219 Tau definition & Card flag & Value\\\hline 226 $\Delta R^{for~em}$ & {\verb TAU_ CONE_ENERGIE} & 0.15\\227 min $E_{T}^{tower}$ & {\verb M_SEEDTHRESHOLD} & 1.0~GeV\\228 $C_{\tau}^{em}$ & {\verb TAU_ EM_COLLIMATION} & 0.95.\\229 $\Delta R^{for~tracks}$ & {\verb TAU_ CONE_TRACKS} & 0.4\\230 min $p_T^{tracks}$ & {\verb PT _TRACK_TAU} & 2 GeV\\\hline220 $\Delta R^{for~em}$ & {\verb TAU_energy_scone } & 0.15\\ 221 min $E_{T}^{tower}$ & {\verb JET_M_seed } & 1.0~GeV\\ 222 $C_{\tau}^{em}$ & {\verb TAU_energy_frac } & 0.95.\\ 223 $\Delta R^{for~tracks}$ & {\verb TAU_track_scone } & 0.4\\ 224 min $p_T^{tracks}$ & {\verb PTAU_track_pt } & 2 GeV\\\hline 231 225 \end{tabular} 232 226 \label{tab:tauRef} … … 244 238 \section{Conclusion and perspectives} 245 239 240 241 \newpage 242 243 \appendix 244 245 \section{User manual} 246 247 The available code is a tar file which comes with everything you need to run the DELPHES package. Nevertheless in order to visualise the events with the FROG program, you need to install libraries as explained in {\it href="http://projects.hepforge.org/frog/} 248 249 \subsection{Getting started} 250 251 In order to run DELPHES on your system, first download is sources and compile it:\\ 252 \begin{quote} 253 \begin{verbatim} 254 me@mylaptop:~$ wget http://www.fynu.ucl.ac.be/users/s.ovyn/files/Delphes_V_*.*.tar 255 me@mylaptop:~$ tar -xvf Delphes_V_*.*. tar 256 me@mylaptop:~$ cd Delphes_V_*.* 257 me@mylaptop:~$ ./genMakefile.tcl >; Makefile 258 me@mylaptop:~$ make 259 \end{verbatim} 260 \end{quote} 261 262 263 \subsection{Running Delphes on your events} 264 265 \subsubsection{Setting the run configuration} 266 267 The program is driven by two datacards (default cards are data/DataCardDet.dat and data/trigger.dat) which allow a large spectrum of running conditions. 268 {\b The run card }\\ 269 270 Contains all needed information to run DELPHES 271 \begin{itemize} 272 273 \item The following parameters are available: detector parameters, including calorimeter and tracking coverage and resolution, transverse energy thresholds allowed for reconstructed objects, jet algorithm to use as well as jet parameters. 274 275 \item Four flags, {\verb FLAG_bfield }, {\verb FLAG_vfd }, {\verb FLAG_trigger } and {\verb FLAG_frog } should be assigned to decide if the magnetic field propagation, the very forward detectors acceptance, the trigger selection and the preparation for FROG display respectively are running by DELPHES. 276 277 \item An example (the default detector card) can be found in {\verb files/DataCardDet.dat } 278 \end{itemize} 279 280 {\b The trigger card }\\ 281 Contains the definition of all trigger bits 282 \begin{itemize} 283 284 \item Cuts can be applied on the transverse momentum of electrons, muons, jets, tau-jets, photons and transverse missing energy. 285 \item Be careful that the following structured should be used: 286 \begin{enumerate} 287 \item One trigger bit per line, the first entry in the line is the name of the trigger bit 288 \item If the trigger bit uses the presence of multiple identical objects, their transverse momentum thresholds must be defined in decreasing order 289 \item The different object requirements must be separated by a {\verb && } flag 290 \item Example of a trigger bit line:\\ 291 \begin{quote} 292 \begin{verbatim} 293 DoubleElec >> ELEC1_PT: '20' && ELEC2_PT: '10' 294 \end{verbatim} 295 \end{quote} 296 \end{enumerate} 297 \item An example (the default trigger card) can be found <a href="files/trigger.dat" title="Home">here</a></li> 298 \end{itemize} 299 300 \subsubsection{Running the code} 301 Create the above cards (data/mydetector.dat and data/mytrigger.dat) 302 Create a text file containing the list of input files that will be used by DELPHES (with extension *.lhe, *.root or *.hep) 303 To run the code, type the following 304 \begin{quote} 305 \begin{verbatim} 306 me@mylaptop:~$ ./Delphes inputlist.list OutputRootFileName.root data/mydetector.dat data/mytrigger.dat 307 \end{verbatim} 308 \end{quote} 309 310 311 \subsection{Running an analysis on your Delphes events} 312 313 Two examples of codes running on the output root file of DELPHES are coming with the package 314 \begin{enumerate} 315 \item The {\verb Examples/Analysis_Ex.cpp } code shows how to access the available reconstructed objects and the trigger information The two following arguments are required: a text file containing the input DELPHES root files to run, and the name of the output root file. To run the code: 316 \begin{quote} 317 \begin{verbatim} 318 ./Analysis_Ex input_file.list output_file.root 319 \end{verbatim} 320 \end{quote} 321 322 \item The {\verb Examples/Trigger_Only.cpp } code permits to run the trigger selection separately from the general detector simulation on output DELPHES root files. An input DELPHES root file is mandatory as argument. The new tree containing the trigger information will be added in these file. The trigger datacard is also necessary. To run the code: 323 \begin{quote} 324 \begin{verbatim} 325 ./Trigger_Only input_file.root data/trigger.dat 326 \end{verbatim} 327 \end{quote} 328 329 \end{enumerate} 330 331 \subsection{Running the FROG event display} 332 333 \begin{itemize} 334 \item If the { \verb FLAG_frog } was switched on, two files were created during the run of DELPHES: {\verb DelphesToFrog.vis } and {\verb DelphesToFrog.geom }. They contain all the needed information to run frog. 335 \item To display the events and the geometry, you first need to compile FROG. Go to the {\verb Utilities/FROG } and type {\verb make }. 336 \item Go back into the main directory and type {\verb ./Utilities/FROG/frog }. 337 \end{itemize} 338 246 339 \begin{thebibliography}{99} 340 247 341 \bibitem{Delphes} \textsc{Delphes}, hepforge: 248 342 \end{thebibliography} 249 \appendix 343 250 344 Attention : in SmearUtil::NumTracks, the function arguments 'Eta' and 'Phi' have been switched. Previously, 'Phi' was before 'Eta', now 'Eta' comes in front. This is for consistency with the other functions in SmearUtil. Check your routines, when using NumTracks ! 251 345
Note:
See TracChangeset
for help on using the changeset viewer.