Changeset 144 in svn

Timestamp:

Jan 7, 2009, 12:49:33 AM (16 years ago)

Author:

Xavier Rouby

Message:

on avance dans le manuel

Location:

trunk/paper

Files:

• notes.pdf (modified) ( previous)
• notes.tex (modified) (2 diffs)

trunk/paper/notes.tex

@@ -941 +941 @@
 \item{\bf The trigger card }
  
-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 bit into selection algorithms:
+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:
  
 \begin{quote}
@@ -955 +955 @@
 \end{quote}
  
-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/trigger.dat}). An example of trigger table consistent with the previous rules is given here:
+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/trigger.dat}). 
+An example of trigger table consistent with the previous rules is given here:
 \begin{quote}
 \begin{verbatim}   
+SingleJet                   >> JET_PT: '200'
 DoubleElec                  >> ELEC_PT: '20' && ELEC_PT: '10'   
 SingleElec and Single Muon  >> ELEC_PT: '20' && MUON_PT: '15'
 \end{verbatim}
 \end{quote}
- 
-An example (the default trigger card) can be found in {\verb files/trigger.dat }.
- 
 \end{enumerate}
  
 \subsubsection{Running the code}
  
-Create the above cards (data/mydetector.dat and data/mytrigger.dat). Create a text file containing the list of input files that will be used by \textsc{Delphes} (with extension *.lhe, *.root or *.hep)
-To run the code, type the following
+First, create the smearing and trigger cards (\texttt{data/mydetector.dat} and \texttt{data/mytrigger.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}).
+To run the code, type the following command (in one line)
 \begin{quote}
 \begin{verbatim}
-me@mylaptop:~$ ./Delphes inputlist.list OutputRootFileName.root data/mydetector.dat data/mytrigger.dat
+me@mylaptop:~$ ./Delphes inputlist.list OutputRootFileName.root 
+                         data/mydetector.dat data/mytrigger.dat
+\end{verbatim}
+\end{quote}
+As a reminder, typing the \texttt{./Delphes} command simply display the correct usage:
+
+\begin{quote}
+\begin{verbatim}
+me@mylaptop:~$ ./Delphes
+ Usage: ./Delphes input_file output_file [detector_card] [trigger_card]
+ input_list - list of files in Ntpl, StdHep of LHEF format,
+ output_file - output file.
+ detector_card - Card containing resolution variables for detector simulation (optional)
+ trigger_card - Card containing the trigger algorithms (optional)
 \end{verbatim}
 \end{quote}