DØ Trigger Simulator Manual
Glossary

The terms defined here are as they pertain to TrigSim.

CVS: "CVS" is short for "Concurrent Versions System" and is the method used by DZero to keep track of all code intended for general use by DZero collaborators. Different versions of code with the same name are referenced by their tag. More information about CVS is available on the CVS homepage. TrigSim is set up such that there is a development "trunk" and production release "branches". Once a branch is created, or "cut", it becomes independent of any farther changes made to the development trunk. The "pnn.00.00" version of a branch is usually just a copy of the then-current trunk code.
d0setwa: The d0setwa command is a DZero environment script that sets certain environment names, including a pointer to the directory within which the command was issued. It is not necessary to issue the d0setwa command before running TrigSim if you are using it through d0tools. Part of the d0tools initialization is to run d0setwa for you on the directory that runD0TrigSim was issued from. TrigSim will then search the directory pointed to by d0setwa for a directory called trigsim to see if there are any user parameters that should override the default parameters.
framework .rcp files: These files end with the .rcp extension, but they do not contain run-time parameters. Instead "framework" rcp files tell TrigSim how the program flow control should be set up.
level1 (L1): The hardware-based first level of the DZero trigger is called "level1", or simply "L1". It is simulated within TrigSim.
level2 (L2): The second level of the DZero trigger is called "level2", or simply "L2". It is mostly software based. The TrigSim program is used to test L2 code before it is run online.
level3 (L3): The third and final level of the DZero trigger is called "level3", or simply "L3". It is entirely software based. The TrigSim program is used to test L3 code before it is run online.
.rcp files: Files with the extension "rcp" come in two kinds. Some rcp files are "framework" rcp files, which are defined seperately. Regular rcp files contain run-time parameters that are used by TrigSim. This includes things such as the value at which to place a cut, or how many cells to use in a clustering routine. Information in rcp files is stored in the rcp database. Users can copy these files, make changes, and place the edited file in their working area. For TrigSim to pick up the user's .rcp file, the -localrcp command line option must be given.
release version number: The "release version number", usually just called the "release", is a way to reference a specific version of the bundle of programs that includes TrigSim. Production releases will always have a tag that starts with "p". Test releases are meant for use by developers only and begin with "t". In general, the higher the release number, the more functionality the code contains. When large changes take place, the number immediately following the "p" is incremented and the rest of the digits are reset to zeros. This is also called "cutting the release". Other release numbers that start with the same "pnn" are subsequent builds that were done to correct errors and make minor improvements. It is generally a good idea to always use the latest release available, i.e., the one with the largest release version number.
release working area: The "release working area" is the directory you have set up within which to run TrigSim. It is usually created using the newrel command. From within it you should issue the d0setwa command before running TrigSim. You should be within this directory when you issue the runD0TrigSim command, and if you are using your own sim files, the trigsim directory that they reside in should a subdirectory of your working area.
runD0TrigSim: duh.
setup D0RunII <releasenumber>: necessary evil.
.sim files: Files whose extension includes "sim" are used by TrigSim to configure itself when running. They include epics.sim, level1.sim, level2.sim-stripped, and level3.sim. When runD0TrigSim is called, the versions of sim files used by the program are placed in the appropriate D0TrigSim_x-... directory. Usually these are soft links to the sim files contained in the release area. For a sim file to be overridden, one must put a replacement file of the same name in a directory called trigsim within your release working area. TrigSim will replace its default sim files with a copy of any sim files found in the trigsim directory. Sometimes you may find other sim files in the trigsim directory, namely calib.sim, level2.sim, logger.sim, and sdaq.sim. These files are not used by TrigSim so it does not matter if they are present or not.
tag: A "tag" is the identifying version name for software that resides in CVS. The general format for a tag is one letter, followed by two digits, a dash, two more digits, a dash, and two more digits. For example, packages that were used in the release p13.03.00 build have a "p13-03-00" tag. So, for most users the tag digits will be the same as the release name. Production releases will always have a tag that begins with the letter "p". A tag that loks like "pnn-br-nn", where the "n"s are digits, are packages which were modified after the first "pnn" of that branch was cut. A tag that starts with "v" is generally a work-in-progress or test version.