Fork me on GitHub

Changeset 99 in svn for trunk/paper/notes.tex


Ignore:
Timestamp:
Dec 14, 2008, 2:35:56 PM (16 years ago)
Author:
Xavier Rouby
Message:

petit update

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/paper/notes.tex

    r93 r99  
    22\usepackage[english]{babel}
    33\usepackage[ansinew]{inputenc}
    4 
    5 \usepackage[dvips]{graphicx}
    6 \graphicspath{{figures/}}
     4\usepackage{abstract}
    75
    86\usepackage{amsmath}
    97\usepackage{epic}
    10 \usepackage{wrapfig}
     8 \usepackage{wrapfig}
    119\usepackage{eepic}
    1210\usepackage{color}
     
    1715\usepackage{verbatim}
    1816\addtolength{\textwidth}{2cm} \addtolength{\hoffset}{-1cm}
     17\usepackage[colorlinks=true, pdfstartview=FitV, linkcolor=black, citecolor=black, urlcolor=black, unicode]{hyperref}
     18\usepackage{ifpdf}
     19\usepackage{cite}
     20
     21\ifpdf
     22  \usepackage[pdftex]{graphicx}
     23  \graphicspath{{all_png/}}
     24  \pdfinfo{
     25   /Author (S. Ovyn, X. Rouby)
     26   /Title  (Delphes, a framework for fast simulation of a general purpose LHC detector)
     27   /Subject ()
     28   /Keywords (Delphes, Fast simulation, LHC, FROG, Hector, Smearing, FastJet)}
     29\else
     30   \usepackage[dvips]{graphicx}
     31   \graphicspath{{figures/}}
     32\fi
     33
     34\title{\textsc{Delphes}, a framework for fast simulation \\of a general purpose LHC detector}
     35\author{S. Ovyn and X. Rouby\thanks{Now in Physikalisches Institut, Albert-Ludwigs-Universit\"at Freiburg} \\
     36        Center for Particle Physics and Phenomenology (CP3)\\ Universit\'e catholique de Louvain \\ B-1348 Louvain-la-Neuve, Belgium \\ \\
     37        \textit{severine.ovyn@uclouvain.be, xavier.rouby@cern.ch} \\
     38}
     39\date{}
     40
     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%
    1944\begin{document}
    2045
    21 \section*{Abstract}
    22 
    23 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.\\
     46
     47\twocolumn[
     48\maketitle
     49% \begin{@twocolumnfalse}
     50    \begin{onecolabstract}
     51Knowing whether theoretical predictions are visible and measurable in a high energy experiment is always delicate, due to the
     52complexity of the related detectors, data acquisition chain and software. We introduce here a new framework, \textsc{Delphes}, for fast simulation of
     53a general purpose experiment. The simulation includes a tracking system, embedded into a magnetic field, calorimetry and a muon
     54system, and possible very forward detectors arranged along the beamline.
     55The framework is interfaced to standard file format (e.g. Les Houches Event File) and outputs observable analysis data objects, like missing transverse energy and collections of electrons or jets.
     56The simulation of detector response takes into account the detector resolution, and usual reconstruction algorithms for complex objects, like 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 Hector software. Finally, the FROG 2D/3D event display is used for visualisation of the collision final states.
     57An overview of \textsc{Delphes} is given as well as a few use-cases for illustration.
     58\vspace{1cm}
     59    \end{onecolabstract}
     60% \end{@twocolumnfalse}
     61]
     62\saythanks
     63
    2464
    2565\section{Introduction}
     
    3171A fast simulation of a typical \textsc{lhc} multipurpose detector response can be used to obtain more realistic observables and fast approximate estimates of signal and background rates for specific channels. \textsc{Delphes} includes the most crucial detector apects as jet reconstruction, momentum/energy smearing for leptons, photons and hadrons and missing transverse energy. Starting from ``particle-level" information, the package provides reconstructed jets, isolated leptons, photons, reconstructed charged tracks, calorimeter towers and the expected transverse missing energy. Although this kind of approach yields much realistic results than a simple ``parton-level" analysis, a quick simulation comes at the expense of detector details. Therefore, the interactions not simulated in \textsc{Delphes} are: secondary interactions, multiple interactions, photon conversion, electron Bremsstrahlung, magnetic field effects, detector dead materials.\\
    3272
    33 The simulation package proceeds in two stages. The first part is executed on the generated events. ``Particle-level" informations are read from input files and stored in a {\it \textsc{gen}} \textsc{root} tree. Three varieties of input files can currently be used as input in \textsc{Delphes}. In order to process events from many different generators, the standard Monte Carlo event structure 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}) and \textsc{root} files obtained using the {\bf h2root} converter program. This first stage is performed using three C++ classes: {\verb HEPEVTConverter }, {\verb LHEFConverter } and {\verb STDHEPConverter }. 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. The output of the various C++ classes is stored in the {\it Analysis} tree. The program is driven by a datacard (data/DataCardDet.dat) which allow a large spectrum of running conditions by modifying basic detector parameters, including calorimeter and tracking coverage and resolution, thresholds or jet algorithm parameters.\\
     73The simulation package proceeds in two stages. The first part is executed on the generated events. ``Particle-level" informations are read from input files and stored in a {\it \textsc{gen}} \textsc{root} tree. Three varieties of input files can currently be used as input in \textsc{Delphes}. In order to process events from many different generators, the standard Monte Carlo event structure 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}) and \textsc{root} files obtained using the {\bf h2root} converter program. This first stage is performed using three C++ classes: {\verb HEPEVTConverter }, {\verb LHEFConverter } and {\verb STDHEPConverter }. 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. The output of the various C++ classes is stored in the {\it Analysis} tree. The program is driven by a datacard (data/DataCardDet.dat) which allow a large spectrum of running conditions by modifying basic detector parameters, including calorimeter and tracking coverage and resolution, thresholds or jet algorithm parameters.\\
    3474
    3575\section{Central detector simulation}
     
    3979\includegraphics[width=\columnwidth]{detectorAng.eps}
    4080\caption{\small{detectorAng.eps}}
    41 \label{fig:genDet}
     81\label{fig:GenDet}
    4282\end{center}
    4383\end{figure}
     
    120160Lepton isolation demands that there is no other charged particles with $p_T>2$~GeV within a cone of $\Delta R<0.5$ around the lepton.\\
    121161
     162\subsection{Very forward detectors simulation}
     163
     164Some subdetectors have the ability to measure the time of flight of the particle. This correspond to the delay after which the particle is observed in the detector, after the bunch crossing. The time of flight measurement of ZDC and FP420 detector is implemented here. For the ZDC, the formula is simply
     165\begin{equation}
     166 t_2 = t_1 + \frac{1}{v} \times \big( \frac{s-z}{\cos \theta}\big),
     167\end{equation}
     168where $t_2$ is the time of flight, $t_1$ is the true time coordinate of the vertex from which the particle originates, $v$ the particle velocity, $s$ is the 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 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}$.
     169The formula then reduces to
     170\begin{equation}
     171 t_2 = \frac{1}{c} \times (s-z)
     172\end{equation}
     173NB : for the moment, only neutrons and photons are assumed to be able to reach the ZDC. All other particles are neglected
     174
     175To fix the ideas, if the ZDC is located at $s=140~\textrm{m}$, neglecting $z$ and $\theta$, and assuming that $v=c$, one gets  $t=0.47~\mu\textrm{s}$.
     176
    122177\section{``High-level" objects reconstruction}
    123178
     
    181236\subsection{Transverse missing energy}
    182237
    183 \section{Very forward detectors simulation}
    184 
    185 Some subdetectors have the ability to measure the time of flight of the particle. This correspond to the delay after which the particle is observed in the detector, after the bunch crossing. The time of flight measurement of ZDC and FP420 detector is implemented here. For the ZDC, the formula is simply
    186 \begin{equation}
    187  t_2 = t_1 + \frac{1}{v} \times \big( \frac{s-z}{\cos \theta}\big),
    188 \end{equation}
    189 where $t_2$ is the time of flight, $t_1$ is the true time coordinate of the vertex from which the particle originates, $v$ the particle velocity, $s$ is the 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 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}$.
    190 The formula then reduces to
    191 \begin{equation}
    192  t_2 = \frac{1}{c} \times (s-z)
    193 \end{equation}
    194 NB : for the moment, only neutrons and photons are assumed to be able to reach the ZDC. All other particles are neglected
    195 
    196 To fix the ideas, if the ZDC is located at $s=140~\textrm{m}$, neglecting $z$ and $\theta$, and assuming that $v=c$, one gets  $t=0.47~\mu\textrm{s}$.
    197 
    198 \section{Simulation physics validation}
    199 
    200 \section{conclusion}
    201 
     238\section{Trigger emulation}
     239
     240\section{Validation}   
     241
     242\section{Visualisation}
     243
     244\section{Conclusion and perspectives}
     245
     246\begin{thebibliography}{99}
     247\bibitem{Delphes} \textsc{Delphes}, hepforge:
     248\end{thebibliography}
    202249\appendix
    203250Attention : 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 !
Note: See TracChangeset for help on using the changeset viewer.