- Timestamp:
- Jan 8, 2009, 12:20:52 AM (16 years ago)
- Location:
- trunk/paper
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/paper/notes.tex
r161 r167 92 92 A new framework, called \textsc{Delphes}~\cite{bib:Delphes}, is introduced here, for the fast simulation of a general purpose collider experiment. 93 93 Using the framework, observables can be estimated for specific signal and background channels, as well as their production and measurement rates, under a set of assumptions. 94 Starting from the output of event generators, the simulation of the detector response takes into account the subdetector resolutions, by smearing the kinematics properties of the visible final particles. Tracks of charged particles and calorimetric towers (or \textit{calotowers} are then created.94 Starting from the output of event generators, the simulation of the detector response takes into account the subdetector resolutions, by smearing the kinematics properties of the visible final particles. Tracks of charged particles and calorimetric towers (or \textit{calotowers}) are then created. 95 95 96 96 \textsc{Delphes} includes the most crucial experimental features, like (1) the geometry of both central or forward detectors; (2) lepton isolation; (3) reconstruction of photons, leptons, jets, $b$-jets, $\tau$-jets and missing transverse energy; (4) trigger emulation and (5) an event display (Fig.~\ref{fig:FlowChart}). … … 117 117 %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. 118 118 119 \textsc{Delphes} uses the \texttt{ExRootAnalysis} utility~\cite{bib:ExRootAnalysis} to create output data in a \texttt{*.root} file format.119 \textsc{Delphes} uses the \texttt{ExRootAnalysis} utility~\cite{bib:ExRootAnalysis} to create output data in a \texttt{*.root} ntuple. 120 120 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.\\ 121 121 … … 251 251 \caption{Default location of the very forward detectors, including \textsc{zdc}, \textsc{rp220} and \textsc{fp420} in the \textsc{lhc} beamline. 252 252 Incoming (red) and outgoing (black) beams on one side of the interaction point ($s=0~\textrm{m}$). 253 The Zero Degree Calorimeter is located in perfect alignment with the beamline axis at the interaction point, at $140~\textrm{m}$, where the beam paths are separated. The forward taggers are near-beam detectors located at $220~\textrm{m}$ and $420~\textrm{m}$. }253 The Zero Degree Calorimeter is located in perfect alignment with the beamline axis at the interaction point, at $140~\textrm{m}$, where the beam paths are separated. The forward taggers are near-beam detectors located at $220~\textrm{m}$ and $420~\textrm{m}$. Beamline simulation with \textsc{Hector}~\cite{bib:Hector}.} 254 254 \label{fig:fdets} 255 255 \end{center} … … 987 987 \end{verbatim} 988 988 \end{quote} 989 As a reminder, typing the \texttt{./Delphes} command simply display the correct usage:989 As a reminder, typing the \texttt{./Delphes} command simply displays the correct usage: 990 990 991 991 \begin{quote} … … 1005 1005 \subsubsection{Contents of the \textsc{Delphes} ROOT trees} 1006 1006 1007 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 \text sc{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.1007 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. 1008 1008 1009 1009 Here is the exhaustive list of \textit{branches} availables in these \textit{trees}, together with their corresponding physical objet and \texttt{ExRootAnalysis} class: … … 1171 1171 1172 1172 \begin{itemize} 1173 \item If the { \verb FLAG_frog } was switched on in the smearing card, two files has been created during the run of \textsc{Delphes}: {\verb DelphesToFrog.vis } and {\verb DelphesToFrog.geom }. They contain all the needed information to run \textsc{frog}. 1174 \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) 1175 \item Go back into the main directory and type \texttt{me@mylaptop:~\$ ./Utilities/FROG/frog}. 1173 \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}. 1174 \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). 1175 \item Go back into the main directory and type 1176 \begin{quote} 1177 \texttt{me@mylaptop:~\$ ./Utilities/FROG/frog}. 1178 \end{quote} 1176 1179 \end{itemize} 1177 1180
Note:
See TracChangeset
for help on using the changeset viewer.