Proposal for Level 1 Track Trigger Implementation in Trigger DB
---------------------------------------------------------------
Version 1.0 5 Dec 2001 - revised to include decisions from 4 Dec Trigger DB 
			meeting

There are nine cuts and parameters that will be passed from the
Trigger DB to the Two track boards for each One track or Two track
trigger.  Not all will be defined in the database or appear in the
options.

1. XFT_PT - Track Pt 
2. XFT_PT2 - Track Pt for second track 
	- hardcoded to 0 for single track option 
3. XFT_REQUIRE_ISO - Do we use Track Isolation (from XFT)
	- assumed to be the same for both tracks
	- Not currently implemented so will not appear in the options or cuts
	- hard coded to 0
4. XFT_SPARE 
	- assumed to be the same for both tracks
	- Not currently implemented so will not appear in the options
	- hard coded to 0
5. XFT number of layers (3, 4 or 0) 
	- assumed the same cut for both tracks
6. q1*q2 - hard coded to 0 for single track
7. pt1+pt2 or sumpt - hard coded to 0 for single track
8. delta_phi_min (degrees) - hard coded to 0 for single track
9. delta_phi_max (degrees) - hard coded to 180 for single track

There will be three options to choose from: ONE_TRACK, TWO_TRACK and 
SEVEN_TRACK (not yet documented) as detailed in:
http://www-cdf.fnal.gov/trigger_database/Level_1_Options.ps
If there are any ONE_TRACK or TWO_TRACK specific options in a PHYSICS Table 
there must be one and only one SEVEN_TRACK specific option.

The following PreFRED bits will be assigned in order 44-50 and 52-55.
PreFRED bit 51 will ALWAYS be assigned to the SEVEN_TRACK trigger.  It
would be nice if the assignment followed some logical order of the
options.  For example: all single track triggers followed by two track
triggers.

Trigger Table Validation Code:
-----------------------------
Some requirements that must be tested in validation (action if not satisfied):

1. If there are any Track triggers in the Physics table there must be one 
and ONLY one SEVEN_TRACK trigger  (Fail validation).

2. The Seven Track pt threshold determines the pt of tracks passed to
the two track trigger board.  Therefore: the threshold of all ONE and
TRACK track triggers must be greater than or equal to the SEVEN_TRACK
trigger (Fail Validation).  If all ONE_TRACK and TWO_TRACK thresholds
are greater than the SEVEN_TRACK threshold (Warning).  In either case
error message should list all thresholds.

3. Check number of Track triggers.  This should be handled by the FRED 
validation.  In current FRED configuration allow only 12 (PreFREDbits 44-55).  
But should be capable of up to 16 if the FRED configuration is changed.  The 
test on the number of bits should be driven off the FRED configuration.

Downloading:
-----------

The One_Track option will only have 3 of the possible 9 parameters
and the Two_Track option will only have 7 of the 9.  The ones for which a 
cut or parameter is not specified will have hard coded values passed as 
specified above.  

The download will always have:
- One Seven track trigger with one parameter (PT)
- Fifteen Two track or One track triggers with the nine parameters specified 
above.  If there are fewer than 15, the extras will be filled out with 0s for
each of the parameters. 

Notes:
-----

The ISO and number XFT layers are handled in a simpler fashion than Kevin's
proposal  of 24 May 2001.  Here we would treat the tracks independently and 
require or not require isolation and short or long tracks.  If we want to 
implement Kevin's more complicated scheme but it does not seem necessary.  

We do not have a mechanism for arbitrary functions built in.  We only include 
delta_phi and  sum_pt at this time.  If we want others we can create another 
cut and a new option.