|
This page is intended to keep the FPD L1 Trigger files, including segments definitions for single detectors, tracking and VHDL equations. The downloadable files are written in conformity with VHDL format standards so they can be promptly used at the trigger firmware simulation/implementation stages. |
The files contained in this page may quickly
evolve since this work is still under way. |
Page Contents:
1.1. General Detector Equations
1.2. Validation
and Tracking Equations
3. Test Vectors
4. Compilation Results
1.1. General Detector Equations
u_seg(5) <= ( not u(1) and not u(2) and up(2) ); .
These are the finer segments possible to be defined and correspond
to 1/3 of a detector fiber, what is approximately 1/3*0.80 mm = 0.27
mm. This fine segmentation is needed to resolve proton/antiproton
relative momentum loss (dp/p) at the order of ~ 0.005. Equations
for the fine segments are given in the table below.
We can also define coarser segments by logically adding fine segments. A wide segment 4 times wider (4*1/3 of fiber) than the fine segments is defined and used to implement triggers for high transferred momentum (|t |>1 GeV/c) events, where dp/p resolution at the first level trigger is not a must. An excerpt is shown below:
v_wide_seg(9) <= ( ( v(9) or vp(9) )
and not v(10) ); .
In this example, the wide segment is defined in terms of fibers, but
it could be done from the fine segments, as well. The files
defining wide segments are included in the table below.
|
Detector View
|
Fine Segments
|
Wide Segments
|
|
U
|
||
|
X
|
||
|
V
|
These equations apply to all FPD detectors, as the geometry is the
same for all of them.
1.2. Validation and Tracking Equations
|
Set of equations
|
PU
|
PI
|
DI
|
| U-view
segment validation |
|||
| V-view
segment validation |
|||
| Low t
and low xsi (|t| < 1 GeV , xsi < 0.01) |
|||
| Low t
and high xsi (|t| < 1 GeV , xsi > 0.01) |
|||
| U-view
wide-segment validation |
|||
| V-view
wide-segment validation |
|||
| High t
(| t| > 1 GeV) |
|||
| All wide-segments
|
The files needed to implement each of the three flavors (PU, PI and
DI) are given in the following table. (by the
time being, there are links only to DI files).
| Spectrometer Flavor |
Spectrometers |
Segments Files |
Trigger Files |
||||||||||||
| DI |
DI |
|
|
||||||||||||
| PI |
PI,PO,AU,AD |
|
|
||||||||||||
| PU |
PU,PD,AI,AO |
|
|
| Segment Validation |
|
|---|---|
| U segment |
Test vector for validated
U segment |
| V segment |
Test vector for validated
U segment |
| Tracking Equations |
|
|
Single hits
|
|
|
PU low t and low xsi |
Test vector for low t
and low xsi tracking trigger equations in PU spectrometer. Prescale=100 , what means only 1 out of each
100 equations was used to make the vector. |
|
PU low t and high xsi |
Test vector for low t
and high xsi tracking trigger equations in PU spectrometer. Prescale=100 . |
|
PU high t |
Test vector for high t
(and all xsi) tracking trigger equations in PU spectrometer. Prescale=1000 . |
|
PI low t and low xsi |
Test vector for low t
and low xsi tracking trigger equations in PI spectrometer. Prescale=50. |
|
PI low t and high xsi |
Test vector for low t
and high xsi tracking trigger equations in PI spectrometer. Prescale=50 . |
|
PI high t |
Test vector for high t
(and all xsi) tracking trigger equations in PI spectrometer. Prescale=2000 . |
|
DI low t and low xsi |
Test vector for low t
and low xsi tracking trigger equations in DI spectrometer. Prescale=50 . |
|
DI low t and high xsi |
Test vector for low t
and high xsi tracking trigger equations in DI spectrometer. Prescale=500 . |
|
DI high t |
Test vector for high t
(and all xsi) tracking trigger equations in DI spectrometer. Prescale=1200 . |
|
DI (wide segments) |
Test vector for
all-wide-segments tracking trigger equations in DI spectrometer. Prescale=24. |
|
Multiple hits
|
|
|
DI high t double hit |
Test vector for double
hits in DI spectrometer: two high t (and all xsi) tracking
trigger equations logically added. |
|
DI log file |
||
|
PI log file |
||
|
PU log file |
||
|
DI wideSeg log file - Adopt an all wide segments logic (for
testing purposes) |
||