DØ Trigger Simulator Manual
Outputs

When you run the command runD0TrigSim for the first time, a new directory will be created in your working area. This new directory will have a name constructed from the options used in the runD0TrigSim command.

The first part of the created directory's name is always the name of the base executable - D0TrigSim_x. The second part is the release number under which TrigSim is running. The third segment is the operating system and if the compilation used is optimized (using "maxopt"). For most users this third piece is either Linux or maxopt-Linux. The fourth piece is the name of the filelist provided to runD0TrigSim. If the filelist given has the extension .dat, the extension is dropped. Otherwise the entire file name is kept. The fifth and final segment is the name of the trigger list being used. If no triggerlist is specified, TrigSim will use the compiled-in default triggerlist, labelled DEFLIST. As an example, if one executes runD0TrigSim under p15.05.00 with only the required command line options and an input filelist called myfiles.dat, the results will be put in the directory D0TrigSim_x-p15.05.00-Linux-myfiles-DEFLIST.

Be aware that re-executing runD0TrigSim under previously-used conditions will replace the contents of the existing directory instead of creating a new one.

In the results directory, TrigSim will place:

• a link to the physical location of the executable that was run, called D0TrigSim_x
• a file called command.txt containing a copy of the command line that was passed by d0tools to D0TrigSim_x
• a copy or link of the framework RCP file used (called framework.rcp)
• text-based output logs files from the execution, called D0TrigSim_x.log, D0TrigSim_x.out, L3_SR_stat.log, and L3_SR_tsim.log. In general, the first two are the most helpful.
• a link or copy of the tool list used for level 3 (toollist.txt).
• output files in the same format as input files with Chunks added. The file names are currently auto-generated and are outputfile_nn where nn is a number between 00 and 25. TrigSim creates one output file per input file. The 26 file limit is hard-coded into the D0TrigSimWriteEvent.rcp file and may be edited by hand. Hopefully this limitation will be removed soon. There is no limitation on the number of events written per file.
• all other files needed for calibration, etc., including files copied from the user's working area trigsim directory.

The command runTrigSimAnalyze creates an output directory in the same manner as runD0TrigSim. This directory will always start with the executable name TrigSimAna_x. The second, third, and fourth parts of the directory name are the same as for runD0TrigSim. There is no fifth segment in the name. The TrigsimAnalyze directory will contain:

• a link to the physical location of the executable that was run, called TrigSimAna_x
• a file called command.txt containing a copy of the command line that was passed by d0tools to TrigSimAna_x
• a copy or link of the framework RCP file used (called framework.rcp)
• text-based output logs files from the execution, called TrigSimAna_x.log and TrigSimAna_x.out.
• a link or copy of the tool list used for level 3 (toollist.txt).
• a ROOT-tuple output file called trigsim.root.
• a ROOT-tuple file containing information about the performance of the tools that were run, called toolstats.root.