trt.html

trigger_rate_tool

The trigger_rate_tool is a D0 framework package used to estimate trigger rates in data. It allows the computation of the rates and overlaps of individual as well as sets of triggers. It can predict trigger rates at all levels (L1,L2,L3) for large and complicated global trigger lists.

The tool consists of two parts. The first one (built using the instructions in the bin directory) is a framework executable which uses the information contained in the TMBTriggerChunk (the L1/L2/L3 trigger names/bits and the AndOr mask) and in the L1L2Chunk (the detailed readout of the L1 and L2 trigger information) to emulate different L1 and L2 triggers (L3Chunk for L3 triggers). It produces in output a simple ASCII file which for each event contains the list of triggers. The second part consists of the standalone Rates executable.

Here is the cookbook (always being updated) for checking out trigger_rate_tool:

setup D0RunII p17.09.00 -O SRT_QUAL=maxopt
setenv LINK_SHARED yes
setup d0cvs
newrel -t p17.09.00 TRT
cd TRT
addpkg trigger_rate_tool v00-03-06
addpkg l1cal2b_sliding_windows v00-01-00
gmake all

You can use this script to find L1/L2 rates from the enhanced bias run 203351, which generates a file l1l2l3trigger.dat in the GenerateTriggerTable_x-p17.08.00-maxopt-Linux-run203351 directory which contains the list of triggers that fired for every event. Then you need to run trigger_rate_tool/scripts/convertTriggerDump.py (in a new area which also contains l1l2l3trigger.dat) which generates two additional files you need: l1l2l3trigger.dump and l1l2l3trigger.dict . These are the files you need for simulating the trigger rates with the Rates program (available in the shbin directory). To run this program on the triggers you are interested in, copy the executable to your working directory, create a trigger list file (example), then you obtain an output ascii file with the rates using the following command:

Rates trigger_list > Trigger_Rates.txt

Here are the L1/L2 trigger names for enhanced bias run 203551.
If you are only interested in running Rates with the v13 triggers, you can take the l1l2l3trigger.dat file from Marco's area /work/cole-clued0/mverzocc/TRTPUBLIC
Here is the full list of v13.51 EM triggers in trigger_list format (from Carsten M.).
Here is a partial list of v13.51 muon, trilepton, and test triggers in trigger_list format (from Carsten M.).
If you want to run with RunIIb triggers, set the rcp parameter Emulate_Run2BL1Cal in trigger_rate_tool/rcp/GenerateTriggerTable.rcp to "true". This README may also be helpful in designing RunIIb triggers.

***************************************************************************************************

Run 204974 can be used for L3 trigger studies. The data have been reconstructed using p17.03.03 d0reco and are available on disk:

raw data: /prj_root/1161/l3_write/mverzocc/RAW/all_0000204974_0**.raw
DST: /prj_root/1161/l3_write/mverzocc/DST/reco_all_0000204974_0**.raw_p17.03.03
TMB: /prj_root/1161/l3_write/mverzocc/TMB/recoT_all_0000204974_0**.raw_p17.03.03
trigsimmed thumbnails: /prj_root/1161/l3_write/jonsson/p17-new/D0TrigSim_x-p17.05.00-maxopt-Linux-run204974_XX-DEFLIST XX=01,40

Tips:

Sample triggerlist and some associated comments
Here are the triggers that were used (in triggerlist format) to collect these data
set Required_L3Chunk in rcp/GenerateTriggerTable.rcp to "offline" for trigsimmed data or MC
use "//" to put comments into the trigger list
you can find the current input to Rates for run 204974 in:

/work/cole-clued0/mverzocc/TRTL3/l1l2l3trigger.dat
/work/cole-clued0/mverzocc/TRTL3/l1l2l3trigger.dump
/work/cole-clued0/mverzocc/TRTL3/l1l2l3trigger.dict

use normalization factor = 960 in bin2/Rates.cpp to extrapolate to L=100E30
Level3.README which documents all rewritten L3 filters

****************************************************************************************************