DØ Trigger Simulator Manual
Command Line Options

TrigSim will list the command line options if you type:

      runD0TrigSim -h

• D0TrigSim-Specific options

-format=<format>

- tell TrigSim or TrigAnalyze if the events you are processing are data or Monte Carlo. This command line parameter must always be supplied for TrigSim and TrigAnalyze. The <format> argument choices are "mc" and "data".

-l1l2only

- run only the L1/L2 simulation. NB: As of release p15, the "analysis" part of TrigSim was split into its own executable. If you use the -l1l2only option with the runD0TrigSim command, you must also use it with the runTrigAnalyze command. If you don't TrigAnalyze will crash.

-l3only

- run only the L3 simulation. NB: As of release p15, the "analysis" part of TrigSim was split into its own executable. If you use the -l3only option with the runD0TrigSim command, you must also use it with the runTrigAnalyze command. If you don't TrigAnalyze will crash.

-l3reprocess

- drop a pre-existing L3Chunk. This option is intended to be run only on input files that have already been run through TrigSim and have an offline L3Chunk in them (mainly MC from the farms). It causes any L3Chunk already existing in the input file to be ignored in favor of TrigSim writing a new L3Chunk in the output file. Caution: If TrigSim is run over a file already containing an offline L3Chunk and that chunk is not dropped, you will not see new offline L3Chunk results in your output file. Another Caution: If you use this option on a real data input file, then the online L3Chunk information will be lost.

-l3toollist=<filename>.txt

- provide a filename containing a list of tools for the l3fanalyze package to run. If this option is not given, TrigSim looks in the default trigsim directory for a file called toollist.txt and uses it if found. If this option is not specified and there is no toollist.txt file in the trigsim directory, TrigSim will generate a default toollist.txt in the D0TrigSim_x-* directory. NB: As of release p15, the "analysis" part of TrigSim was split into its own executable. If you use the -l3toollist option with the runD0TrigSim command, you should also use it with the runTrigAnalyze command.

-trglst=<filename>.xml

- the name of trigger list xml file to use, for example global_CMT-9.01.xml.

-trglstpath=<pathname>

- path to the trigger list xml file. Not needed if the xml file is in the working area directory.

• General

-h

- prints out the online help information.

• Global parameters

-exe=<filename>.exe

- name of executable to run. TrigSim default is rund0exe.

-initscript=<scriptname>.sh

- initialization script to use for the executable. TrigSim default is ???.sh.

-localbuild

- use local build of runD0TrigSim or runTrigAnalyze instead of the official release version.

-localfwkrcp

- use a local version of the main framework rcp instead of the official release version.

-localrcp

- use local rcp's in addition to the official release ones.

-name=<jobname>

- override the machine-produced default job name. WARNING! Because of the way in which d0tools is configured, TrigSim looks for the trigsim directory one level up from its output directory. If you used the -name option to redirect the output, TrigSim may not find the trigsim directory you wanted it to use. The way to get around this is, before you run the executable, put the trigsim directory in the same directory you want your output directory to appear in. For example, if you use -name=/rooms/attic/joeschmo/trigsim_stuff/job_01, and you do not want to use the default .sim files, you must have the .sim files you want to use in the directory /rooms/attic/joeschmo/trigsim_stuff/trigsim

-rcp=<filename>.rcp

- name of framework rcp script to use. TrigSim default depends on the other command line options used.

-rcppkg=<packagename>

- name of the framework rcp package to use. TrigSim default depends on the other command line options used.

-userscript=<scriptname>.sh

- user provided initialization script for executable. TrigSim default depends on the other command line options used.

• Run Time Environment (rte) options

-rtepath=<pathname>

- the path from current working directory to rte directory.

-rtepkg=<filename>.exe

- the name of the executable (yes, the executable) within the rte directory to be invoked. This option will changed to rteexe in a future release.

-userte

- use the run time environment (rte) directory.

• Running mode (default mode is interactive)

-batch

- use the batch queues. If a queue is not specified, the "short" queue is used.

-debug

- use the totalview interactive debugger. Totalview must be set up before this option is used (type setup totalview).

-jobname=<jobname>

- specify the batch job name. If this option is not given, the default batch job name is "rund0exe".

-maxopt

- use the optimized build. TrigSim default is to use the build containing debugging information.

-profile

- use ssrun to profile the job. This option works on d0mino only. You may find some useful information on how to analyze the results of profiling at this  web site.

-purify

- use Purify. This option will not work with TrigSim because the program is too large.

• d0mino (LSF) batch system switches:

-mem=<maxmemory>

- specify the maximum amount of memory to use (in bytes). TrigSim default is 500Mb ( -mem=500000 ).

-q=<queuename>

- specify the batch queue to run on. TrigSim default is "short".

Note: The above d0mino switches are ignored if SAM is being used because SAM picks the queue.

• clued0 (PBS) batch system switches:

-cput=<time>

- specify the maximum CPU time the job is allowed to run for. The TrigSim default is three hours ( -cput=3:00:00 ).

-mem=<maxmemory>

- specify the maximum amount of memory to use (in bytes). TrigSim default is 500Mb ( -mem=500000 ).

-node=<nodename>

- specify the node where job should be run. If this option is not specified, the system choses a node.

-thisnode

- run the job on the current node.

• Options controlling input / output

-defname=<defname>

- process the files in the SAM project definition named <defname>. The dataset / project definition must first be created using SAM before TrigSim can use it. For convenience, instead of using -defname users may create a text file containing the string "SAMDEFNAME:<defname>", and then use the -filelist option.

-filelist=<filename>

- process the files/datasets listed in the file <filename>. This file should be a text file, with one full path and file name per line. There are no restrictions on the name of <filename>.

-out=<filename>.raw

- write the processed events to the file <filename>.raw.

• Options to control processing of specific events

-eventlist=<eventlistfile>.dat

- process only the specific collision IDs listed in <eventlistfile>.dat, where <eventlistfile>.dat is a text file containing a list of <run> <event> collision IDs. List one <run> <event> entry per line, with white space separating the two numbers.

-num=<integer>

- specify the number of events to process. TrigSim default is all events ( -num=0 ).

-skip=<integer>

- specify the number of events to skip. TrigSim default is none ( -skip=0 ).

-skipevents=<badeventlist>.dat

- skip the specific collision IDs listed in <badeventlist>.dat, which is a text file containing a list of <run> <event> collision IDs. List one <run> <event> entry per line, with white space separating the two numbers.

-skipruns=<badrunlist>.dat

- skip the runs listed in <badrunlist>.dat, which is a text file containing a list of run numbers, one run number per line.

• Other framework options

-memreport

- enable framework memory leak checking, which consists of turning on the framework switches -memusage and -memreport.

-suppress

- disable the printing of individual error messages in log file. Instead, a summary is printed at the end of the job.

• SAM options

-group=<groupname>

- specify the SAM group to use. The TrigSim default is "dzero".

• Special options

-fpe

- turn on the floating point exception handling on Linux. The exception handling is on by default on d0mino.

-fwkparams

- pass any set of parameters to a framework executable. This option should be the last one on the command line, followed by the actual parameters you want to pass to the framework. For example:
       rund0exe ... -fwkparams -<option1> <xxx> -<option2> <yyy>

-runscript=<scriptname>.sh

- specify a custom script to run. The specified script will be run before actually running the executable. Note that this script will only work reliably if it contains command line commands. This option is intended for advanced users.

To process files within SAM, first use SAM to create a dataset definition, and then use the -defname option. For convenience, users may optionally place the SAM dataset definition name into an ASCII file, prefacing it with the string "SAMDEFNAME:", and then use the -filelist option.

When -userte is specified, the framework rcp's for the executable (!) specified by -rtepkg are required to be within the runtime environment directory at runtime/framework_rcps/<executable>. In other words, for D0reco_x, you would have -rtepkg=d0reco_x and the rcp's would be at runtime/framework_rcps/d0reco_x

In order to override a framework rcp, you must checkout the package and make a local build of the executable, and then use the -localbuild switch.