Updated draft specification of the Run2B L1 Calorimeter Trigger Resource Programming by COOR

This document is based on the original draft specification prepared by P. Laurens, H. Evans and M. Mulhearn (dated 4-Oct-2005).
This document has been prepared by M. Verzocchi and includes comments by H. Evans, S. Lammers and P. Laurens (dated 01-May-2006).
Original set of proposed changes (Marco, 24-Apr-2006)
Comments from Hal (26-Apr-2006)
Reply to Hal (Marco, 01-May-2006)
Comments from Philippe (26-Apr-2006)
Reply to Philippe (Marco, 01-May-2006)

Changes and additions relative to the original are highlighted in bold.
Obsoleted sections are underlined.
COOR messages to the Trigger Control Computer are indicated in blue.
Area where additional specifications are needed are highlighted in red.


0) General

The new syntax for Run IIb follows and adapts the Run IIa syntax.

All keywords are not case-sensitive with respect to TCC, and capitalization is used and encouraged to help the human reader.

The Run IIb L1Cal will be controlled via a new computer called L1CAL TCC (d0tcc3.fnal.gov) which presents an ITC server port #52345 for COOR. L1CAL TCC will accept and acknowledge but ignore all the standard run control messages that COOR sends but are not relevant to L1Cal operation (e.g. Begin Store, Start Run, etc).

The resources have been organized below around which card type they come from. 

There are 3 types of cards in the data path of the L1Cal system.  The Analog and Digital Filter cards version 2 (ADF-2 or simply ADF) receive the BLS Energy signals, and compute for each beam crossing an EM and an HD Et value for each of the 1280 Trigger Towers (TT) in the L1 Cal coverage.

The Trigger Algorithm Boards (TAB) apply the L1CAL algorithms locally and construct physics objects (e.g. jet energies).
  
The Global Algorithm Board (GAB)  puts it all together to perform final sums, counts, and topological cuts to produce And/Or Terms to be sent to the L1FW.

1) Initialization

"L1CAL_Initialize"
alias: "INIT"

Initialize the L1CAL system.  The goal is to write to all internal registers, and program all resources such that:
 (The default state after initialization will be defined more specifically.)

2) ADF-2 resources

There are no truly run-dependent resources on the ADF-2 for  COOR to program.

2.1) Excluding trigger towers

This is probably part of initialization, like for IIa, but managed by the trigger experts, not by COOR .

"L1CAL_Exclude  EM_Tower TT_Eta(20) TT_Phi(23)"
"L1CAL_Exclude  HD_Tower TT_Eta(20) TT_Phi(23)"

These commands are used to suppress the contribution of one or more Trigger Tower.  The specified EM or HD Trigger Tower will be programmed so that it will always report 0 GeV of energy. 0 GeV is represented by a non zero value, defined as 8 ADC counts, which is called the zero energy response, and which is constan over all EM and HD Trigger Towers.

TCC implements a related command for special tests requiring that the fixed value coming out of a tower be different than the standard zero energy response of 8 counts:

"L1Cal_Simu_ADC  EM_Tower TT_Eta(20) TT_Phi(23)  Value 20"
"L1Cal_Simu_ADC  HD_Tower TT_Eta(20) TT_Phi(23)  Value 20"

3) TAB resources

NB In all the following examples the maximum eta range has been changed from (-20:20) to (-16:16) to reflect firmware changes. The maximum allowed rapidity for trigger objects has been change from 20 to 16 in the firmware. COOR should enforce a check on the maximum value of the rapidity requested in the triggerlist.

All the resources in this section are programmable per TAB chip i.e. per 4x4 in eta,phi

There are 7 ET Reference Sets available for each object type (7 ET thresholds for EM and Jet) that we can number in the conventional zero-based way, i.e. #0:6.
There are 6 tau ratio Reference Sets available for Taus, that we number starting from one, i.e. #1:6.

The result of these comparisons on the TAB is passed to the GAB and used to create And/Or Terms.  However only the upper 6 ET thresholds (#1:6) are passed and the existence of the lowest threshold is only meaningful to the Cal-Track matching Trigger and readout to L2 and L3.

For each Threshold Reference Set there is one value downloaded per TAB chip which corresponds to a range of 4x TT_Eta values and 4x TT_Phi values. Normal operation will probably desire constant values over the whole coverage, but special studies, special cases, or commissioning could make use of non-uniform thresholds. TCC already knows how to parse per-TT syntax, and TCC has to program the TAB chips one at a time anyway.

The details of the TT_Eta/TT_Phi specifications is identical to Run IIa, and is repeated here.

Trigger Tower Ranges:

Example :
"L1CAL_Ref_Set <RS_Type> <RS_Number> TT_Eta(-16:16) TT_Phi(1:32) Energy_Threshold <Et in GeV> "

The first keyword, "L1CAL_Ref_Set", introduces all Reference Set definitions.
The second keyword, "<RS_Type>", specifies the type of Reference Set.
The "<RS_Number>" is the ID number of the Reference Set. cf. 3.1.

A set of magnitudes of eta is specified by the keyword "TT_Eta"followed by a pair of parenthesis delimiting any combination of individual eta Trigger Tower indices and/or ranges of eta indices.

TT_Eta values are the Trigger Tower pseudo-rapidity indices. TT_Eta values are signed integers between -20 and -1 and +1 and +20. The plus sign ("+") is NOT necessary but accepted.

A range is specified by its upper and lower bounds separated by a colon character (":"). The lower (respectively upper) bound is the number appearing before (respectively after) the colon character. Extra space characters may appear before and after the colon character. When two eta magnitudes are separated by a colon to form a range, they are understood as representing the complete set of all integer values between and including the upper and lower bounds.

There is no requirement in the order of upper and lower range bounds with respect to their sign or magnitude: (-4:+4), (+4:-4), (4:8), (8:4) are all legal range definitions.

When an eta index is not separated by a colon character from either of its surrounding index values it will be understood as one more discrete values to be included in a set of magnitudes defined inside the parenthesis (note: this is not very useful for run IIb).

Multiple ranges and/or multiple discrete values may be specified within the same set of parenthesis, each separated by at least one space character.

The specification of the eta indices may be omitted when all existing magnitudes are to be treated identically; it is equivalent to TT_Eta(-20:20). A pair of empty parenthesis following "TT_Eta" is equivalent to omitting the eta indices.

The keyword "TT_Eta" must always be followed (after optional space characters) by a set of parenthesis including the Eta indices.

A set of phi values is specified by the keyword "TT_Phi" followed by a pair of parenthesis including any combination of individual phi values and phi ranges.

TT_Phi values are the Trigger Tower azimuthal indices. TT_Phi values are unsigned integers between 1 and 32. A plus sign ("+") is NOT necessary but accepted.

The syntax rules for specifying TT_Phi values are identical to the syntax rules for the TT_Eta defined above.

The specification of the phi values may be omitted when all existing phi values are to be treated identically; it is equivalent to TT_Phi(1:32). A pair of empty parenthesis following "TT_Phi" is equivalent to omitting the Phi indices. The keyword "TT_Phi" must always be followed (after optional space characters) by a set of parenthesis including the Phi indices.

When both the Eta and Phi indices are omitted the Reference Set is programmed uniformly over all Trigger Tower.

The Keyword "Energy_Threshold" must appear after the Trigger Tower specification.  The Keyword "Energy_Threshold" is followed by the Energy Threshold Value specified as a floating point number in units of GeV of z-corrected Transverse Energies.   The decimal point is not required in the specification of the Threshold Value. For thresholds below 1 GeV, a leading 0 must be explicitly specified before the decimal point.

The Trigger Control Computer will perform the translation to the nearest quantified threshold value that will be inclusive of the requested value, as defined earlier.

Only one Threshold value may be defined within a single message.

Whenever a range of Trigger Tower appears in a message, the following threshold value is applied to the specified Reference Set and to all the Trigger Towers specified in the range. Trigger Towers outside of the specified range are not affected.

When successive Trigger Tower ranges overlap for the same reference set the threshold value programmed for the overlapping tower(s) is the one specified for the last occurrence.  This may be useful to first define a uniform reference set and subsequently modify it by adding singularities.

The Keywords must always be specified in the order described except for the "TT_Eta" and "TT_Phi keywords which may be reversed. These two keywords may
also appear zero or multiple times.

Examples of range specification:

"L1CAL_Ref_Set <RS_Type> <RS_Number> TT_Eta(-16:16) TT_Phi(1:32) Energy_Threshold 10.0"
"L1CAL_Ref_Set <RS_Type> <RS_Number> TT_Eta(-16:16) Energy_Threshold 10.0"
"L1CAL_Ref_Set <RS_Type> <RS_Number> Energy_Threshold 10.0"

Either of these three messages specifies a uniform threshold of 10.0 GeV over all Trigger Tower eta indices within [-16,-1] and [1,16] and phi indices within [1,32]

"L1CAL_Ref_Set <RS_Type> <RS_Number> TT_Eta(-16:-13 13:16) Energy_Threshold 20"
"L1CAL_Ref_Set <RS_Type> <RS_Number> TT_Eta(-12:12) Energy_Threshold 10"

These three messages taken together specify a Reference Set of 10.0 GeV over all Trigger Tower eta indices within [-12,-1] and [1,12], 20.0 GeV over all Trigger Tower eta indices within [-20,-13] and [13,20]. This Reference Set is uniform with respect to the phi index for all values [1,32].

"L1CAL_Ref_Set <RS_Type> <RS_Number> TT_Eta(-1:-4) TT_Phi(5:8) Energy_Threshold 1000.0"

This message specifies or modifies the Threshold value for the Trigger Towers with eta index [-1,-4] and phi index [5:8] to effectively exclude these Trigger Towers from contributing to the Reference Set.

Reference Set Boundaries

The eta,phi boundaries specified by COOR always need to follow the TAB chip granularity.  These boundaries cannot cut accross the following ranges:
-20:-17, -16:-13, -12:-9, -8:5, -4:1, 1:4, 5:8, 9:12, 13:16, 17:20 in eta 1:4, 5:8, 9:12, 13:16, 17:20, 21:24, 25:28, 29:32 in phi

3.1 Threshold Reference Sets

3.1.a. Jet Reference Sets
3.1.b. EM  Reference Sets
3.1.c. Tau Reference Sets  (currently hardcoded) (REMOVED Tau ET Reference Sets are NOT downloaded to the TABs)

"L1CAL_Ref_Set Jet_Et_Ref_Set <T=0:6> TT_Eta(-16:16) TT_Phi(1:32) Energy_Threshold <Et in GeV, e.g. 10.0>"
"L1CAL_Ref_Set EM_Et_Ref_Set  <T=0:6> TT_Eta(-16:16) TT_Phi(1:32) Energy_Threshold <Et in GeV, e.g. 10.0>"
"L1CAL_Ref_Set Tau_Et_Ref_Set <T=0:6> TT_Eta(-20:20) TT_Phi(1:32) Energy_Threshold <Et in GeV, e.g. 10.0>" (REMOVED)

This message programs the Jet_Et (or EM_Et) Reference Set #T to require that the Energy of the Jet (or electron) object found within the specified TT_Eta x TT_Phi coverage are reconstructed to have an energy equal to or greater than the specified Et value.  

The TABs don't have transverse energy reference sets used for Taus. In the TABs Tau finding is limited to the calculation of the ratio of energies in 2x2 and 4x4 trigger towers matrices, and the count of objects found in different bins of this tau ratio is the only tau specific information sent to the GAB. For the transverse energy cut the GAB uses the transverse energy of jets found within the same phi-slice as the objects used for the calculation of the tau ratio. The tau ratio thresholds are not downloadable parameters and are instead fixed in firmware.

Any message defining part of, or all of, a given Reference Set will implicitely also mean that COOR has allocated the Reference Set and is now controlling its Threshold Value(s).  cf below for Deallocation, and behavior of unallocated Reference Sets.

Like in Run IIa, the Energy threshold value is inclusive, meaning that an object must have a reconstructed energy value equal to or greater than the specified threshold to be accepted.   Since the comparators on the TABs operate as "strictly greater", TCC will simply subtract one ADC count during translation from GeVs to ADC counts.

For every Trigger Tower the energy threshold must be monotonically increasing with the Reference Set Number.  This is not a temporary limitation, but is required by the design of the system.  TCC can verify the thresold values as they are being specified by COOR.  COOR will still need to manage this intrinsic limitation as well, in particular when it receives a new request after some of the resources have already been allocated.

The energy threshold programmed into the TABs is a 12 bit number in units of ADC counts, i.e. the value specified by COOR has a granularity of 0.25 GeV (other values will be rounded down), a minimum value of 0.25 GeV  (0.0 GeV is not allowed) and a maximum value of 1024.0 GeV.

Setting the Reference Set thresholds is independent from the programming of the global thresholds acting on the total count carried over the whole detector for the number of objects found exceeding their individual threshold. The global thresholds are programmed with separate messages. cf. section 4.

Default programming after initialization: All Thresholds are initialized to a safe don't pass value defined as 1024 GeV everywhere.

Initial limitations: Tau references are hardcoded, with values to be determined. (REMOVED: Tau ET Reference Sets are NOT downloaded to the TABs)

3.1.d. Deallocate Jet Reference Sets
3.1.e. Deallocate EM  Reference Sets
3.1.f. Deallocate Tau Reference Sets
(REMOVED Tau ET Reference Sets are NOT downloaded to the TABs)

"L1CAL_Ref_Set Jet_Et_Ref_Set <T=0:6> Deallocate"
"L1CAL_Ref_Set EM_Et_Ref_Set  <T=0:6> Deallocate"
cL1CAL_Ref_Set Tau_Et_Ref_Set <T=0:6> Deallocate"  (REMOVED)

This message deallocates the Jet_Et (or EM_Et) Reference Set #T.

The Reference Set will then be implicitely managed by TCC to maintain proper operation of the other allocated reference sets (cf below)

Default programming after initialization: All Reference Sets are un-allocated after an initialization message.

3.1.g. Reference Set Management

COOR is required to comply with the monotonicity requirement so that all Reference Sets always be specified with energy thresholds monotonically increasing with Reference Set Index number for all allocated Reference Sets of each type.

For each reference set message that it receives, TCC will verify that the monotonicity rule is always satisfied, and TCC will respond to the request with a "BAD" acknowledgement when an inconsistency is detected within the currently allocated Reference Sets.

COOR does not need to always allocate and specify all 7 Reference Sets of each type.  COOR may allocate and program any subset of zero, one or more Reference Set(s) at any given time.

However COOR should always allocate the lowest reference set (#0) both for Jet and EM. According to the old specification this reference set could not be allocated by COOR because it does not correspond to one of the thresholds used by the triggers (the GAB sees only the object count for thresholds #1-6).

The 0-th reference threshold needs to be downloaded all the time because it may be used for other purposes (transferring object masks to Level2, it can be used for selecting the EM objects for which the EM isolation and EM/HAD fraction ratio are calculated, it can be used for the threshold veto in the new versions of the acoplanar jet trigger).

The definition of the value of the 0-th Reference Set does not require any change in the TCC-TAB communication. However it does require a change in the message
sent from COOR to TCC and a corresponding change in the XML syntax, or alternatively it requires that this threshold is defined by the TCC initialization procedure.

TCC will implicitely manage all un-allocated Reference Sets to maintain proper operation of the system at all times.  At any given time, all Reference Sets of each type are maintained to follow the following rules:
  1. If the lowest Reference Set allocated by COOR is #N, with N>0, TCC will program all Reference Set #M, with 0 < M < N to the same threshold as the one COOR defined for Reference Set #N.
  2. If COOR defines two reference Sets #P and #R while leaving some Reference Set(s) #Q un-allocated, with P < Q < R, TCC will program #Q to the same threshold has the one COOR defined for Reference Set #R.
  3. If the highest Reference Set allocated by COOR is #S, with S!=6, TCC will program all Reference Set #T, with S < T <= 6 to the default initial "don't pass threshold", i.e. 1000 GeV.
  4. When all reference Sets are unallocated, they are all programmed by TCC to the default initial "don't pass threshold", i.e. 1000 GeV.
Any time COOR allocates and programs (or modifies) a Reference Set, TCC will reprogram any unallocated Reference Set of lower index to satisfy the above rules, if necessary.

3.2 Algorithms Parameters

3.2.a. EM Isolation Ratio and
EM/HD Fraction (was 2 separate messages before)

"L1CAL_Ref_Set EM_Isolation_Et TT_Eta(-16:16) TT_Phi(1:32) EM_Et_Ref_Set <RS_Number>"
(replaces the two messages "L1CAL_Ref_Set EM_Isolation TT_Eta(-16:16) TT_Phi(1:32) Ratio <X=Power of 2>"
and
"L1CAL_Ref_Set EM_HD_Fraction TT_Eta(-20:20) TT_Phi(1:32) Ratio <X=Power of 2>")

In the initial implementation of the COOR-TCC protocol it was thought that COOR would program the a value for the EM Isolation ratio of X, meaning that an electron object will be tagged as Isolated if the ratio of the EM Et energy sum in the corresponding 1x2 (or 2x1) TT_Eta x TT_Phi cell over the EM Et energy sum in the two neighboring 1x2 (or 2x1) cell is greater or equal to the value X and similarly it would also set
a value for the EM/HD fraction of X, meaning that an electron object will be tagged as passing the EM/HD fraction cut if the ratio of the EM Et energy sum in the corresponding 1x2 (or 2x1) TT_Eta x TT_Phi cell over the HD Et energy sum in the same 1x2 (or 2x1) cells is greater or equal to the value X.

In the current implementation of the firmware the Ratio cut done in the TABs will not be programmable via the TCC, but fixed in firmware. Therefore the Ratio part of the message has been removed from the definition of the COOR-TCC message.

The current firmware however allows (and requests) that a value is downloaded for the minimum threshold which an EM object should pass in order to be considered for setting the EM Isolation flag and EMfraction flag within one phi-slice in the TAB (The isolated EM object trigger is formed in the GAB requiring that in a given phi-slice there is an EM object passing the transverse energy cut and that the isolation and EMfraction flag is set in that phi-slice. The isolated EM object trigger may fire because there are two separate EM objects within the same phi-slice, one of which passed the isolation/EMfraction cut and one which passes the transverse energy requirement).

The value of the minimum threshold which an EM object should pass needs to be downloaded from the TCC to the TABs. By default (at initialization) this parameter will be set to the lowest EM Et Reference Set (#0).

The EM Isolation Ratio is only used for the computation of the EM Isolated Object Counts in the GAB and related And/Or Term (cf. 4.4)

The Ratio X needs to be a power of 2. The ratio values allowed are 1, 2, 4, 8. (REMOVED Does not apply any longer, the Ratio X is fixed in firmware)

This feature can be enabled or disabled. The value 0 will be used to request that the feature be disabled. (REMOVED: does not apply any longer, the flag for isolated EM objects is always set in the algorithm running in the TABs).

3.2.b Tau Ratio (New requirement)

The new TAB/GAB firmware contains a new version of the tau triggers which requires a new configuration message sent from COOR to TCC.

The basic feature of the new Tau triggers are the following:
  1. Inside the TAB a set of 6 flags are set for each phi-slice whenever a local maximum found by the jet algorithm satisfies the requirement that the ratio of the transverse energies in a 2x2 area divided by the ratio of the transverse energies in a 4x4 area is larger than a fixed value. Only the local maxima with a total energy larger than a given threshold are considered for the calculation of the Tau ratios.
  2. Inside the GAB a Tau trigger is formed when within a same phi-slice we find a Jet object passing a given transverse energy threshold and the flag indicating that one of the jets found in that phi-slice satisfied the Tau ratio requirement. As in the case of the isolated EM object trigger the object which satisfy the transverse energy requirement and the object which satisfy the Tau ratio requirements may be two distinct objects within the same phi-slice.
  3. The values of the Tau ratio thresholds are fixed in firmware and cannot be downloaded from TCC.
Therefore the TCC needs to download to each TAB the value of the transverse energy threshold which is used to select the local maxima considered for the calculation of the Tau ratios. This requires a message:Re

"L1CAL_Ref_Set Min_Tau_Et_Ref_Set TT_Eta(-16:16) TT_Phi(1:32) Energy_Threshold <Et in GeV, e.g. 10.0>"

(Note that there is only one reference value, not 7 as in the case of the EM and Jet reference sets).

The energy threshold programmed into the TABs is a 12 bit number in units of ADC counts, i.e. the value specified by COOR has a granularity of 0.25 GeV (other values will be rounded down), a minimum value of 0.25 GeV  (0.0 GeV is not allowed) and a maximum value of 1024.0 GeV.

Default programming after initialization: this threshold is initialized to a safe don't pass value defined as 1024 GeV everywhere.



3.2.c Minimum ET in a trigger tower for the inclusion in the missing Et/global Et sums. (New requirement)

The new TAB firmware contains a new downloadable parameter which sets a threshold in ADC counts for the inclusion of
a trigger tower (the same threshold is applied separately to the EM and HD trigger towers after adding in the energy from the
ICR trigger towers). This threshold in ADC counts must be transferred from TCC to each TAB (this threshold is a X bit integer).

A value of the threshold of 0 ADC counts means that all trigger towers (including those below the pedestal value) will be included in the missing Et/global Et sums. If a threshold of 8 ADC counts is used all towers with negative energies will be ignored in the sums.  Any threshold value larger than 8 ADC counts can be used to suppress trigger towers with small energies (negative energies will be suppressed as well).

This requires a new message sent from COOR to TCC (see 3.2.g for additional parameter in this message):

"L1CAL_Global_Sums Min_Tower_Et TT_Eta(-20:20) TT_Phi(1:32) Energy_Threshold <E in GeV, e.g. 1.0>"

Please note that in this case the threshold needs to be downloaded also to trigger towers at |eta|>3.2 as those are included in the missing Et/ global Et sums. Negative values of the Energy_Thresholds are allowed: any value smaller or equal to -2.0 GeV will be converted to a threshold of 0 ADC counts, effectively turning off the suppression of trigger towers in the missing Et/global Et sums.

This parameter will be downloaded only once when configuring the trigger.

Default programming after initialization: the threshold is set to 0 ADC counts (no suppression of trigger towers in the missing Et/global Et sums.


3.2.d Switching on/off the use of ICR trigger towers in the Jet sums and in the missing Et/global Et sums. (New requirement)

The new TAB firmware is configured to ignore the ICR trigger towers when forming EM triggers and it has the possibility of using them when forming Jet triggers and when calculating the missing Et/global Et sums. Two separate downloadable parameters are available for the Jet triggers and for the missing Et/global Et sums.

This requires a new message sent from COOR to TCC (0 means don't use the ICR towers, 1 means use the ICR towers):

"L1CAL_Ref_Set Jet_Use_ICR <0/1>"

and an addition to the the message which passes the trigger towers threshold for the missing Et/global Et calculation:

"
L1CAL_Global_Sums Min_Tower_Et TT_Eta(-20:20) TT_Phi(1:32) Energy_Threshold <E in GeV, e.g. 1.0> Global_Sums_Use_ICR <0/1>"

These parameters will be downloaded only once when configuring the trigger.

Default programming after initialization: the ICR towers are not used for the Jet triggers and are not used for the missing Et/global Et sums.

3.2.e Transferring trigger masks to L2.

We use the lowthresh parameter defined both for Jets and EM objects for sending masks to L2. Therefore we do not define specific parameters
for this purpose.

3.3 L1 CalTrack Match

The TAB cards will send L1Cal information to the L1 Cal-Track system, which is a new system for Run IIb.

No special resource needs to be programmed by COOR. L1CAL sends information about all the jets and EM objects found.


4 GAB Resources

NB Please note that the definition of central region for the calorimeter trigger has been changed !!!!

These resources control the overall Thresholds affecting the terms sent to the L1 Framework as And/Or Input Terms.

Note that the GAB only sees the result of the upper 6 of the 7 Reference Sets defined in the TABs.

The definition of "Central Calorimeter Coverage" used in the definitions below currently corresponds to the central trigger towers with |eta| <= 2.4, (changed from the old definition of 1.0) which corresponds to |TT_eta| <= 12, or |ieta|<=24.  This definition is implemented in firmware on the TAB card, and may be changed in the future.


4.1. Jet Object Count

4.1.a. Jet Count over the Full Calorimeter Coverage (|eta|<3.2)

"L1CAL_to_L1FW Jet_All_Term <P=0:15> Use_Ref_Set <T=1:6> Count_Threshold <N=1:4>"

This message programs the Jet_All Term #P to require N or more Jet objects having passed Jet Et Threshold Reference Set #T with no restriction on Eta,Phi.

This corresponds to And/Or Term CSWJT(n,t,ALL). There are 16 such terms (TO BE CONFIRMED).

Default programming after initialization: To be defined.

Firmware limitations expected initially:  (NEED TO FINALIZE THIS QUICKLY !!!!!)
The count thresholds for P=0:3 are fixed at N=1, P=4:7 at N=2, P=8:11 at N=3, and P=12:15 at N=4.
We could either ask COOR to re-specify such fixed values, or make these the default values and ask COOR to ommit the Count_Threshold keyword/Value for now.

4.1.b. Jet Count over the Central Calorimeter Coverage (|eta|<2.4)

"L1CAL_to_L1FW Jet_Central_Term <P=0:3> Use_Ref_Set <T=1:6> Count_Threshold <N=1:4>"

This message programs the Jet_Central Term #P to require N or more Jet objects having passed Jet Et Threshold Reference Set #T while only counting objects in the Eta range corresponding to the Central Calorimeter.

This corresponds to And/Or Term CSWJT(n,t,C). There are 4 such terms available to COOR (TO BE CONFIRMED).

Default programming after initialization: To be defined.

Firmware limitations expected initially:  (NEED TO FINALIZE THIS QUICKLY !!!!!)
Only the first two Terms P=0:1 are implemented.
The count thresholds for P=0 is fixed at N=1, P=1 at N=2

4.2. EM Object Count

4.2.a. EM Count over the Full Calorimeter Coverage

"L1CAL_to_L1FW EM_All_Term <P=0:11> Use_Ref_Set <T=1:6> Count_Threshold <N= 1:4>"

This message programs the EM_All Term #P to require N or more EM Electron objects having passed Tau Et Threshold Reference Set #T with no restriction on Eta,Phi.

This corresponds to And/Or Term CSWEM(n,t,ALL). There are 12 such terms available to COOR (TO BE CONFIRMED).

Default programming after initialization: To be defined.

Firmware limitations expected initially:   (NEED TO FINALIZE THIS QUICKLY !!!!!)
Only the first 8 Terms P=0:7 are implemented.
The count thresholds for P=0:3 are fixed at N=1, P=4:7 at N=2

4.2.b. EM Count over the the Central Calorimeter Coverage

"L1CAL_to_L1FW EM_Central_Term <P=0:3> Use_Ref_Set  <T=1:6> Count_Threshold <N=1:4>"

This message programs the EM_Central Term #P to require N or more EM Electron objects having passed EM Et Threshold Reference Set #T while only counting objects in the Eta range corresponding to the Central Calorimeter.

This corresponds to And/Or Term CSWEM(n,t,C). There are 4 such terms available to COOR (TO BE CONFIRMED).

Default programming after initialization: To be defined.

Firmware limitations expected initially:   (NEED TO FINALIZE THIS QUICKLY !!!!!)
Only the first 2 Terms P=0:1 are implemented.
The count Threshold for P=0 is fixed at N=1, P=1 at N=2

4.3. Tau Object Count

4.3.a. Tau Count over the Full Calorimeter Coverage

"L1CAL_to_L1FW Tau_All_Term  <P=0:3> Use_Ref_Set  <T=1:6> Use_Tau_Ratio_Set <R=1:6> Count_Threshold <N=1:2>"

This message programs the Tau_All Term #P to require N or more Tau objects having passed Jet Et Threshold Reference Set #T and the Tau Ratio Threshold Set #R with no restriction on Eta,Phi.

This corresponds to And/Or Term CSWTA(n,t,ratio,ALL).  There are 4 such terms available to COOR (TO BE CONFIRMED).

Default programming after initialization: To be defined.

Firmware limitations expected initially: (NEED TO FINALIZE THIS QUICKLY !!!!!)
The count thresholds for P=0:1 are fixed at N=1, P=2:3 at N=2

4.2.c. Tau Count over the the Central Calorimeter Coverage

"L1CAL_to_L1FW Tau_Central_Term <P=0:3> Use_Ref_Set  <T=1:6> Use_Tau_Ratio_Set <R=1:6> Count_Threshold <N=1:2>"

This message programs the Tau_Central Term #P to require N or more Tau objects having passed Jet Et Threshold Reference Set #T and the Tau Ratio Threshold Set #R while only counting objects in the Eta range corresponding to the Central Calorimeter.

This corresponds to And/Or Term CSWTA(n,t,ratio,C). There are 4 such terms available to COOR (TO BE CONFIRMED).

Default programming after initialization: To be defined.

Firmware limitations expected initially:   (NEED TO FINALIZE THIS QUICKLY !!!!!)
Only the first 2 Terms P=0:1 are implemented.
The count Threshold for P=0 is fixed at N=1, P=1 at N=2


4.4. EM Isolated Object Count

4.4.a. EM Isolated Count over the Full Calorimeter Coverage

"L1CAL_to_L1FW Isolated_EM_All_Term  <P=0:1> Use_Ref_Set  <T=1:6> Count_Threshold <N=1:2>"

This message programs the Isolated_EM_All Term #P to require at least N Electron objects having passed EM Et Threshold Reference Set #T and having been tagged as Isolated with no restriction on Eta,Phi.

This corresponds to And/Or Term CSWEI(n,t, ALL). There are 2 such terms available to COOR (TO BE CONFIRMED).
The reference to the actual values of the isolation and EMfraction cuts have been removed from the AOTerm name, since they are NOT programmable from COOR.

Default programming after initialization: To be defined.

Firmware limitations expected initially: none

4.4.b. EM Isolated Count over the Central Calorimeter Coverage

"L1CAL_to_L1FW Isolated_EM_Central_Term  <P=0:1> Use_Ref_Set  <T=1:6> Count_Threshold <N=1:2>"

This message programs the Isolated_EM_Central Term #P to require at least N Electron objects having passed EM Et Threshold Reference Set #T and having been tagged as Isolated while only counting objects in the Eta range corresponding to the Central Calorimeter.

This corresponds to And/Or Term CSWEI(n,t, C). There are 2 such terms available to COOR (TO BE CONFIRMED).
The reference to the actual values of the isolation and EMfraction cuts have been removed from the AOTerm name, since they are NOT programmable from COOR.

Default programming after initialization: To be defined.

Firmware limitations expected initially: none


4.5. Missing Et Energy Cut

"L1CAL_to_L1FW Missing_Et_Term <P=0:3>  Energy_Threshold <E in GeV, e.g. 10.0>"

This message programs the Missing_Et Term #P to require a Missing Et Energy Sum greater or equal to E GeV, with no restriction on Eta,Phi (while this may change in the future, it is not clear whether this will be under COOR control).

This corresponds to And/Or Term CSWMET(cut,eta_sum,icr). There are 4 such terms available to COOR (TO BE CONFIRMED).
The reference to the threshold on the square of the ADC counts is removed from the AOTerm name. The reference to the rapidity region used for the global sum is kept for possible future extensions (by default there is no rapidity cut in the sum used for the missing ET calculation).

What actually gets programmed is the square of the threshold as a 14-bit number and in units of ADC counts. This translates to a 7-bit Missing Et from 0 to about 64 GeV (to be verified and specified with more precision).

Default programming after initialization: To be defined.

Firmware limitations expected initially: none


4.6. Total Et Energy Cut

"L1CAL_to_L1FW Total_Et_Term   <P=0:3>  Energy_Threshold <E in GeV, e.g. 10.0>"

This message programs the Total_Et Term #P to require a total Et Energy Sum greater or equal to E GeV, with no restriction on Eta,Phi (while this may change in the future, it is not clear whether this will be under COOR control).

This corresponds to And/Or Term CSWTET(cut, eta_sum,icr). There are 4 such terms available to COOR (TO BE CONFIRMED).

What actually gets programmed is the square of the threshold as a 14-bit number and in units of ADC counts. This translates to a 7-bit Missing Et from 0 to about 64 GeV (to be verified and specified with more precision).

Default programming after initialization: To be defined.

Firmware limitations expected initially: none


4.6. Topological Acoplanar Jet Requirement (1st version) (IT IS UNCLEAR TO ME THAT THIS WILL BE USED)

"L1CAL_to_L1FW Acoplanar_Jet_Term <P=0:1>  Use_Ref_Set1 <T_1=1:6> Use_Ref_Set2 <T_2=1:6> Min_Delta_phi <K=0:X>"

This command programs the Acoplanar_Jet Term #P to require that at least one pair of Jet objects (one with a transverse energy in excess of Reference Threshold #T_1, the second with a transverse energy in excess of Reference  Threshold #T_2) also  pass the Acoplanar topological requirement (a separation of at least #K phi-slices). (There is a maximum value for K in firmware, what is it ? Is K programmable ?)

This corresponds to Andor Term CSWAJT(t_1,t_2, contig). There are 2 such terms available to COOR (TO BE CONFIRMED).

This resource is not meant to be used alone in a Specific Trigger programming, but in addition to a requirement for 2 or more Jet Objects above the same threshold.

Default programming after initialization: To be defined.

Current firmware limitation: Reference Set indices T_1 and T_2 must be identical

4.7. Topological Acoplanar Jet Requirement (2nd version)

"L1CAL_to_L1FW NonCollinear_LowEt_Jet_Term <P=0:1>  Use_Ref_Set1 <T_1=1:6> Use_Ref_Set2 <T_2=1:6>  Use_Ref_Set_Veto <T_v=0:6> Min_Delta_phi <K=0:X>"

This command programs the NonCollinear_LowEt_Jet Term #P to fire provided there are not two jets with a transverse energy in the
range specified by the Reference sets #T_v and #T_1 (first jet) and
by the Reference sets #T_v and #T_2 (second jet) which
are collinear (i.e. their angular separation is less than #K phi-slices). 
(There is a maximum value for K in firmware, what is it ?)

This corresponds to Andor Term CSWAKL(t_1,t_2,t_v,contig)
. There are 2 such terms available to COOR (TO BE CONFIRMED).

This resource is not meant to be used alone in a Specific Trigger programming, but in addition to a requirement for 2 or more Jet Objects above the same threshold.

Default programming after initialization: To be defined.

Current firmware limitation: Reference Set indices T_1 and T_2 must be identical. Is this implemented as described ?


4.8. Topological Acoplanar MonoJet Requirement

"L1CAL_to_L1FW NonCollinear_Mono_Jet_Term <P=0:1>  Use_Ref_Set1 <T_1=1:6> Use_Ref_Set2 <T_2=1:6>  Use_Ref_Set_Veto <T_v=0:6> Min_Delta_phi <K=0:X>"

This command programs the NonCollinear_Mono_Jet Term #P to fire if there is at least one jet with transverse energy in excess of Reference  Set #T_1, provided there are not two jets with a transverse energy in the range specified by the Reference sets #T_v and #T_1 (first jet) and by the Reference sets #T_v and #T_2 (second jet) which are collinear (i.e. their angular separation is less than #K phi-slices). (There is a maximum value for K in firmware, what is it ?)

This corresponds to Andor Term CSWAKM(t_1,t_2,t_v,contig)
. There are 2 such terms available to COOR (TO BE CONFIRMED).

Default programming after initialization: To be defined.

Current firmware limitation: Is this implemented as described ?


4.9. Topological Back-to-Back EM Requirement

"L1CAL_to_L1FW Back_To_Back_EM_Term <P=0:1>   Use_Ref_Set <T=1:6> Min_Delta_phi <K=0:X>"

This command programs Back_To_Back_EM Term #P to require that at least one pair of electron objects passing Threshold #T also pass the Back-to-Back topological requirement (the two EM objects are required to be back to back within a window of #K phi-slices).

This corresponds to Andor Term CSWBBEM(t, contig).There are 2 such terms available to COOR (TO BE CONFIRMED).

This resource is not meant to be used alone in a Specific Trigger programming, but in addition to a requirement for 2 or more EM Objects above the same threshold.

 Default programming after initialization: To be defined.

 Current firmware limitation: Is this implemented as described ? 

4.10. Jet free region trigger.

"L1CAL_to_L1FW Jet_Free_Term <P=0:1>   Use_Ref_Set <T=1:6> Use_Ref_Set_Veto <T_v=0:6> Min_Delta_phi <K=0:X>"

This command programs the Jet_Free_Term #P to require that there is a region of the calorimeter of #K phi-slices which is free of jets with a transverse energy in the range specified by the Reference Set #T_v and #T.

This corresponds to Andor Term CSWJFRE(t, contig).There are 2 such terms available to COOR (TO BE CONFIRMED).

 Default programming after initialization: To be defined.


5  XML Syntax

The changes made to the protocol for the communication between COOR and TCC are reflected in the following changes to the syntax of the triggers terms in the XML file containing the triggerlist. The original list from Scott (E-mail from 12 Oct 2005) :
The X's below represent required attributes, the O's optional ones.
In addition to the attributes below, all terms take the optional
attributes `number', to explicitly specify which term to allocate,
`ownmode', to specify the coor ownership mode, and `require',
to specify the require/veto sense of the term in a term list.


<run2b.l1jet thresh="X" count="X" maxeta="O" rsnumber="O"/>
<run2b.l1tau thresh="X" count="X" maxeta="O" rsnumber="O"/>
<run2b.l1em thresh="X" count="X" maxeta="O" rsnumber="O"/>
<run2b.l1iso_em thresh="X" count="X" maxeta="O" rsnumber="O" emf="O" iso="O"/>
<run2b.l1miss_et thresh="X"/>
<run2b.l1tot_et thresh="X"/>
<run2b.l1bb_em thresh="X" maxeta="O" rsnumber="O"/>
<run2b.l1aco_jet thresh="X" maxeta="O" rsnumber="O"
thresh_v="O" maxeta_v="O" rsnumber_v="O"/>


Some notes. Coor parameterizes reference sets in terms of a threshold
and a maximum eta (defaulting to the full calorimeter). Outside the specified
eta range, the refset threshold will be set to the maximum. Due to the
sorting requirement, not all combinations of threshold/maxeta will
be possible. However, if the maxeta specified matches the hardwired
cutoff for a `central' term, that `central' term will be used,
with the refset itself including the full eta coverage.

The rsnumber attribute can be used to force allocation of a specific
reference set; otherwise, coor will choose.

For l1iso_em, the emfraction and isolation ratios may be specified.
If defaulted, they are taken as `0' (no requirement).
These settings must be the same for all l1iso_em terms used
at any one time.

l1aco_jet has two associated reference sets; the second (veto) is specified
via the attributes ending in `_v'. If they are all defaulted, then
the two reference sets used will be identical. (This is the only
configuration that's allowed by the current firmware, anyway.)



The changes made to the protocol for the communication between COOR and TCC are reflected in the following changes to the syntax of the triggers terms in the XML file containing the triggerlist. The original list from Scott (E-mail from 12 Oct 2005) :

1) change  
<run2b.l1jet          thresh="X" count="X" maxeta="O" rsnumber="O">  
   to
<run2b.l1jet          thresh="X" count="X" maxeta="O" rsnumber="O" lowthresh="X" useICR="O">
    where lowthresh is the value of reference set 0 for jets, it defaults to 5 GeV and it has to be unique among all L1 jet triggers, useICR is the flag which controls the use of the ICR towers in the jet triggers and it defaults to 0 (not used). The default value for maxeta is 3.2. A value of 2.4 for maxeta corresponds to central trigger terms.

This message in the XML files triggers the following messages sent from COOR to TCC for configuring the TAB:
and it triggers the following messages for configuring the GAB:

2) change
<run2b.l1em           thresh="X" count="X" maxeta="O" rsnumber="O">  
   to
<run2b.l1em           thresh="X" count="X" maxeta="O" rsnumber="O" lowthresh="X">
   where  lowthresh is the value of reference set 0 for EM objects, it defaults to 3 GeV and it has to be unique among all L1 EM triggers. The default value for maxeta is 3.2. A value of 2.4 for maxeta corresponds to central trigger terms.

This message in the XML files triggers the following messages sent from COOR to TCC for configuring the TAB:
and it triggers the following messages for configuring the GAB:

3) change
<run2b.l1iso_em        thresh="X" count="X" maxeta="O" rsnumber="O" emf="O" iso="O">
   to
<run2b.l1iso_em        thresh="X" count="X" maxeta="O" rsnumber="O" lowthresh="X" isothresh="X" >
   where lowthresh is the value of reference set 0 for EM objects, it defaults to 3 GeV and it has to be unique among all L1 EM triggers, isothres is the value of the reference set to be used for selecting EM objects which are checked for the isolation and EMfraction criteria. It has to be one of the reference sets used for the EM triggers and it defaults to 3 GeV (the same value used for the lowthresh parameter in the run2b.l1em term). The default value for maxeta is 3.2. A value of 2.4 for maxeta corresponds to central trigger terms.

This message in the XML files triggers the following messages sent from COOR to TCC for configuring the TAB:
and it triggers the following messages for configuring the GAB:

4) change
<run2b.l1tau          thresh="X" count="X" maxeta="O" rsnumber="O">  
   to
<run2b.l1tau          thresh="X" count="X" maxeta="O" rsnumber="O" lowthresh="O" useICR="O" objthresh="X" rsratio="X">  
  where lowthresh is the value of reference set 0 for jets, it defaults to 5 GeV and it has to be unique among all L1 jet triggers, useICR is the flag which controls the use of the ICR towers in the jet triggers and it defaults to 0 (not used), objthresh is the threshold to be used for selecting the 2x2 regions which are checked for the tau ratio and rsratio is the value of the tau ratio cut to be applied (this is passed to TCC as a number between 1 and 6, the values of the thresholds is fixed in firmware) The default value for maxeta is 3.2. A value of 2.4 for maxeta corresponds to central trigger terms.

This message in the XML files triggers the following messages sent from COOR to TCC for configuring the TAB (please note that it is NOT a mistake, these are the jets reference sets !!!):
and it triggers the following messages for configuring the GAB:

5) change
<run2b.l1miss_et     thresh="X">  
   
to
<run2b.l1miss_et     thresh="X" useICR="O" minTowerEt="O" maxeta="O">  
   where useICR is the parameter which controls the use of ICR trigger towers (this is different from the ones used for jets and it's the same as the one used for the l1tot_et trigger) and it defaults to 0 (not used), minTowerEt is the threshold for inclusion of a trigger tower in the missing Et sum (default 1 GeV, corresponding to 12 ADC counts, which means 4 ADC counts above pedestal) and maxeta is a parameter which could be used in the future to specify a maximum limit for the rapidity range of the trigger towers to be included in the missing Et sum (this parameter will be ignored by TCC).

This message in the XML files triggers the following message sent from COOR to TCC for configuring the TAB:
and it triggers the following message for configuring the GAB:

6) change
<run2b.l1tot_et     thresh="X">  
   
to
<run2b.l1tot_et     thresh="X" useICR="O" minTowerEt="O" maxeta="O">  
   where useICR is the parameter which controls the use of ICR trigger towers (this is different from the ones used for jets and it's the same as the one used for the l1tot_et trigger) and it defaults to 0 (not used), minTowerEt is the threshold for inclusion of a trigger tower in the missing Et sum (default 1 GeV, corresponding to 12 ADC counts, which means 4 ADC counts above pedestal) and maxeta is a parameter which could be used in the future to specify a maximum limit for the rapidity range of the trigger towers to be included in the missing Et sum (this parameter will be ignored by TCC).

This message in the XML files triggers the following message sent from COOR to TCC for configuring the TAB:
and it triggers the following message for configuring the GAB:

7) change
<run2b.l1aco_jet     thresh="X" maxeta="O" rsnumber="O"  thresh_v="X"   maxeta_v="O"  rsnumber_v="O">
to
<run2b.l1aco_jet     thresh_1="X" maxeta_1="O" rsnumber_1="O"  thresh_2="X" maxeta_2="O"  rsnumber_2="O" contig="X" useICR="O">
where contig is the minimum number of phi-slices separating the directions of the two calorimeter objects (modulo 180 degrees) and useICR is the flag which controls the use of the ICR towers in the jet triggers and it defaults to 0 (not used).

This message in the XML files triggers the following messages sent from COOR to TCC for configuring the TAB:
and it triggers the following message for configuring the GAB:

8) introduce the new XML element:
<run2b.l1ncol_jet     thresh_1="X" maxeta_1="O" rsnumber_1="O"  thresh_2="X" maxeta_2="O"  rsnumber_2="O" lowthresh="O" contig="X" useICR="O">
   
where lowthresh is the value of reference set 0 for jets, it defaults to 5 GeV and it has to be unique among all L1 jet triggers, contig is the minimum number of phi-slices separating the directions of the two calorimeter objects (modulo 180 degrees) and useICR is the flag which controls the use of the ICR towers in the jet triggers and it defaults to 0 (not used).

This message in the XML files triggers the following messages sent from COOR to TCC for configuring the TAB:
and it triggers the following message for configuring the GAB:
9) introduce the new XML element:
<run2b.l1ncol_monojet     thresh_1="X" maxeta_1="O" rsnumber_1="O"  thresh_2="X" maxeta_2="O"  rsnumber_2="O" lowthresh="O" contig="X" useICR="O">
   
where lowthresh is the value of reference set 0 for jets, it defaults to 5 GeV and it has to be unique among all L1 jet triggers, contig is the minimum number of phi-slices separating the directions of the two calorimeter objects (modulo 180 degrees) and useICR is the flag which controls the use of the ICR towers in the jet triggers and it defaults to 0 (not used).

This message in the XML files triggers the following messages sent from COOR to TCC for configuring the TAB:
and it triggers the following message for configuring the GAB:
10) change
<run2b.l1bb_em    thresh="X" maxeta="O"  rsnumber="O">
    to
<run2b.l1bb_em    thresh="X" maxeta="O"  rsnumber="O" contig="X">
where contig is the maximum number of phi-slices separating the directions of the two calorimeter objects (modulo 180 degrees).

This message in the XML files triggers the following mesage sent from COOR to TCC for configuring the TAB:
and it triggers the following message for configuring the GAB:
11) introduce the new message:
<run2b.l1jet_free    thresh="X"  maxeta="O"  rsnumber="O"   contig="X" lowthresh="O">
where contig is the minimum number of phi-slices in the calorimeter without any jet in the transverse energy range below the Et corresponding to the threshold thresh, and lowthresh is the value of reference set 0 for jets, it defaults to 5 GeV and it has to be unique among all L1 jet triggers.

This message in the XML files triggers the following mesage sent from COOR to TCC for configuring the TAB:
and it triggers the following message for configuring the GAB:

6  And Or Terms


The following AndOr terms should be recognized by the XML generator and trigger the generation of the appropriate XML code when found in the triggerlist.

CSWJT(n,Et,maxeta) or CSWJET(n,Et,maxeta,lowthresh,useICR)
<run2b.l1jet          thresh="X" count="X" maxeta="O" rsnumber="O" lowthresh="X" useICR="O">


CSWEM(n,Et,maxeta) or CSWEM(n,Et,maxeta,lowthresh)
<run2b.l1em           thresh="X" count="X" maxeta="O" rsnumber="O" lowthresh="X">

CSWEI(n,Et,maxeta,isothresh) or CSWEI(n,Et,maxeta,isothresh,lowthresh)
<run2b.l1iso_em       thresh="X" count="X" maxeta="O" rsnumber="O" lowthresh="X" isothresh="X">

CSWTA(n,Et,maxeta,objthresh,rsratio) or
CSWTA(n,Et,maxeta,objthresh,rsratio,lowthresh,useICR)
<run2b.l1tau          thresh="X" count="X" maxeta="O" rsnumber="O" lowthresh="O" useICR="O" objthresh="O" rsratio="X">

CSWMET(Et) or CSWMET(Et,useICR,minTowerEt) or CSWMET(Et,useICR,minTowerEt,maxeta)
<run2b.l1miss_et      thresh="X" useICR="O" minTowerEt="O" maxeta="O">  

CSWTET(Et) or CSWTET(Et,useICR,minTowerEt) or CSWTET(Et,useICR,minTowerEt,maxeta)
<run2b.l1tot_et       thresh="X" useICR="O" minTowerEt="O" maxeta="O">

CSWAJT(Et1,Et2,contig) or CSWAJT(Et1,Et2,contig,maxeta1,maxeta2,useICR)
<run2b.l1aco_jet      thresh_1="X" maxeta_1="O" rsnumber_1="O"  thresh_2="X" maxeta_2="O"  rsnumber_2="O" contig="X" useICR="O">

CSWNCO(Et1,Et2,contig) or CSWNCO(Et1,Et2,contig,maxeta1,maxeta2,lowthresh,useICR)
<run2b.l1ncol_jet     thresh_1="X" maxeta_1="O" rsnumber_1="O"  thresh_2="X" maxeta_2="O"  rsnumber_2="O" lowthresh="O" contig="X" useICR="O">

CSWNCMONO(Et1,Et2,contig) or CSWNCMONO(Et1,Et2,contig,maxeta1,maxeta2,lowthresh,useICR)

<run2b.l1ncol_monojet thresh_1="X" maxeta_1="O" rsnumber_1="O"  thresh_2="X" maxeta_2="O"  rsnumber_2="O" lowthresh="O" contig="X" useICR="O">

CSWBBEM(Et,contig) or CSWBBEM(Et,contig,maxeta)
<run2b.l1bb_em        thresh="X" maxeta="O"  rsnumber="O" contig="X">

CSWJFREE(Et,contig) or CSWJFREE(Et,contig,maxeta,lowthresh)
<run2b.l1jet_free     thresh="X"  maxeta="O"  rsnumber="O"   contig="X" lowthresh="O"
>

7  And Or Terms bits for the trigger framework

The following AndOr terms should be recognized by the XML generator and trigger the generation of the appropriate XML code when found in the triggerlist.