Trigger Naming Conventions
These conventions are to be used when naming Level 1 and Level 2 triggers
in the trigger database.
-
Name will always have a 3 character prefix specifying the trigger level:
L1_
or L2_
-
The only characters used in trigger names will be
alph-neumeric, period (.),
underscore (_),
and ampersand (&
).
-
All characters will be upper case
-
Trigger name is based on the objects required to
satisfy the trigger.
-
Objects Name: speciified by 3 or 4 letter acronyms
listed below.
-
Thresholds for the object:
-
Given by Numeric Characters immediately following
the name acryonym
-
Given in GeV or GeV/c
-
No units are included in the name
-
A period (.) will be used to specify the decimal
place in thresholds.
-
If the threshold is a whole number, the period and
trailing zero are omitted
-
If a track is required in addition to the primary
object, it will be specified by appending an additional threshold with
a prefix _PT
(e.g.
_PT1.5 would be a 1.5 GeV/c track
requirement)
-
If two objects of the same type are required for
the trigger the Object description will be prefaced by TWO_
(e.g. L1_TWO_xxx)
-
If multiple objects of different types are required
for the trigger (e.g. Electron and Muon) the two objects will be joined
by an &.
-
Eaxmple:
L1_CMU2_PT2&CMX2_PT2
-
In the following description elements in curly
brackets
{} are required and those in square
brackets [ ] are
optional parameters
-
Calorimeter Objects (Jets, Photons, Electrons,
Tracks):
-
EM for object based
on EM energy threshold
-
JET for object based
on Total
energy
-
A prefix of a C
(Central) or P
(Plug) is used for a trigger in an exclusive detector region.
If this is absent it is valid for all detector regions.
-
At L2 options may be appended:
-
_SM
for shower max. Number following gives the threshold
-
_ISO for isolation cut on cluster
-
It is assumed that HAD/EM thresholds will not be spelled out in the trigger
name unless needed to differentiate from a similarly named trigger
-
It is also assumed that the L2 Clustering pass will not be spelled out
in the name unless needed to differentiate from a similarly named trigger
-
Form for L1: L1_[P,C]
{EM,JET}et[_PTpt]
-
et=Tower Et threshold
-
pt=track Pt threshold
-
Form for L2: L2_[P,C]
{EM,JET}et
[_PTpt][_SMss][_ISO][_CPc]
-
et=Tower Et threshold
-
pt=track Pt threshold
-
c = clustering pass
-
ss = Shower max threshold
-
Examples:
-
L1_CEM1.5_PT1.5 - Electron
with Et>1.5 GeV and Pt>1.5 GeV/c
-
L2_CEM3_PT3_SM2 - Electron
with Et>3 GeV, Pt>3 GeV/c, Shower Max Energy >2 GeV
-
Muon objects:
-
Defined by detector region of the stub:
-
CMU for CMU
-
CMUP for CMP and CMU
-
CMP for CMP in
region of CMU gaps
-
CMNP for CMU where
there is no CMP
-
CMX for CMX
-
IMUO for outer IMU (high
eta)
-
IMUI for inner IMU (low
eta)
-
TSU
-
Form for L1:
L1_{Region}{ss}[_PTpt]
(same
form for L2)
-
ss =nominal stub threshold
Pt in GeV/c
-
pt=track Pt threshold
-
Examples:
-
L1_CMU3_PT3 - CMU stub with Pt > 3 GeV/c matched to a track with Pt>3
GeV/c
-
L1_TWO_CMU1.5_PT1.5 - Two CMU stubs with Pt>1.5 GeV/c each matched to tracks
with Pt>1.5 GeV/c
-
Track Objects:
-
TRKpt[_ISO]
defines a track based trigger
-
pt=track Pt threshold
-
_ISO = Track isolation
-
At L2 can add impat parameter cut: [_Ddd]
-
dd = imapct paramter
cut in microns
-
Other Parameters and Objects:
-
MB is minimum bias
-
Append _CLC
for CLC
-
Append _BSC
for beam shower counter
-
To add a CLC requirement to another L1 Trigger just
add &CLC
-
XING
is Crossing or Zero-Bias trigger
-
SUMETet is Sum Et Trigger
with threshold of et GeV
-
METet is Missing Et
Trigger with threshold of et GeV
-
PSps: prescale is appended
at end of trigger name
-
ps is an integer from
0-999
-
if ps==0
then trigger is masked
-
if desired prescale is larger than 1000 but less
than 1000000, use form [ps/1000]K
-
if desired prescale is larger than 1000000 use form
[ps/1000000]M
-
Example: _PS500K
means
prescale by 500,000
-
AUTO is used for L2
Auto accept
-
Form of L2 auto accept trigger is: L2_AUTO_{L1
Trigger Name}
-
A L2 trigger that just consists of a prescale has
a similar form:
-
L2_PSps_{L1 Trigger Name}
-
More complex triggers can be indicated by additional
text in the name as needed to differentiate from similar triggers.
For example:
-
TWO_CMU1.5_PT1.5_JPSI
-
_MT to indicate transverse
mass cut etc