DØ Trigger Simulator Manual
Inputs and configuration

TrigSim can take many command line options, but currently requires only two inputs: the event file to run over ( -filelist or -defname ), and the format of the events ( -format ). The event file can be either data or MC, but it must contain a Raw Data Chunk (RDC). The RDC is present by default in MC files from the farms which have been run through D0Sim, and in any raw data file. Files that have been run through reco can be used if reco was configured to keep the RDC in the output (this is not the default when you run it yourself!). For the data that comes directly from online, the default is to not keep the RDC. The format of the events in the event file is specified with the -format option. Therefore, the simplest command to run TrigSim would be:

      runD0TrigSim -filelist=<mylistfile> -format=<format>

where <format> is either mc or data.

In older releases of TrigSim, both the trigger simulation and summarization of the results were done in a single executable that was run by calling runD0TrigSim. As of production release number 15 (p15), all the "analyze" portions of TrigSim were split off into their own executable called TrigAnalyze. This was done to facilitate code debugging, and in case the analyze portions did not build properly in a release at least the simulation portion had a chance to build successfully and be used. TrigAnalyze takes the output files from TrigSim as input files and produces a .root file. The simplest command to run TrigAnalyze is similar to that for TrigSim:

      runTrigAnalyze -filelist=<mylistfile> -format=<format>

where <format> is the same arguement given to runD0TrigSim for the simulation (either mc or data), and <mylistfile> is a text file of the outputfile_*(s) in the D0TrigSim_x-... directory. With this new split-executable method (p15 releases and newer), additional command line options given to TrigSim should be the same as those given to TrigAnalyze. Options like -l1l2only and -l3only, if given to runD0TrigSim command must be given to the runTrigAnalyze command or TrigAnalyze will crash.
Next section: Trigger lists and sim files Previous section: Getting Started Back to Table of contents
Updated: Dec 2, 2002
bellavan@fnal.gov