Eric James' Advanced L1 muon ten step plan (1/19/03)
Comments in red
Hi All - At last Friday's trigger hardware meeting, I
agreed to write up a short summary on my understanding
of the steps required to implement the enhanced L1 muon
capabilities. Please feel free to comment if it turns
out that I'm confused about some of these steps.
Step #1 :
Tom needs to upgrade the trigger database to allow
for proper handling of the track parameters for the muon triggers.
Presently, the XTRP muon map parameters (Pt thresholds, # of layer
requirements) are hardwired. We discussed a plan where we would have
valid Pt ranges for low, medium, and high muon triggers to simplify
Tom's job. Done as of 1/23 (Tom).
Step #2 :
Bill needs to update software in the fer
package to pull the new XTRP muon map parameters
from the trigger database and pass them to the XTRP
crate during coldstart. Done as of 1/23 by
Bill.
Step #3 :
We discussed two tests once these two steps
are completed. The first would be to re-create the
present trigger table with the improved trigger database
software, and then download this table to confirm that
Nate still sees the same muon map parameters arrive at
his crate during coldstart. The 2nd would be to make a
new trigger table with different thresholds to check
that different thresholds can be properly loaded.
Done. Two
test tables, MUON_TEST v23 and v24, made with previous configuration
and new, three-threshold configuration(1/28, PW), were tested
on 1/29 and saw that data was getting to XTRP (PW, Nathan)..
Step #4 :
Jonathan provides Tom and Nate with the
complete set of XTRP muon map parameters required for
enhanced L1. Done as of 1/21 by Jonathan (linked).
Step #5 :
Tom makes changes to the trigger database software
to provide the additional parameters and Bill makes changes to the fer
software to pass these new parameters to the XTRP crate on coldstart.
Nate changes the front-end code for his crate to recognize these new
parameters and print them out on receipt. Build and test a new
trigger table to confirm that these new parameters can be successfully
extracted from trigger table and passed to XTRP crate. Done (above and 1/24) by Tom, Bill and Nate, except
for a few parameters that need clarifying and non-trivial trigger
table needed (see Bill's email).
Step #6 :
Eric provides new definitions for 20 muon
Pre-FRED bits to Tom. In order to get to this point,
the new muon trigger FPGA designs must be finalized.
New FPGA design needs to be put into Hardware DB and
loaded into Matchbox Card to test reliability.
Step #7 :
Tom and Jonathan develop new test trigger
table based on enhanced L1 muon options. Will most
likely require additional coding on Tom's part for
new types of triggers (TOF, gap, etc...)
Step #8 :
Meanwhile, Nate will need to gather all the
information he needs to create the new muon maps for
enhanced L1 (TOF extrapolation, crack extrapolation,
definition of crack bits in phi, etc...) Then, he
can finalize his front-end code for loading the muon
maps for enhanced L1.
Step #9 :
After completing these last three steps, we
can have a complete system test and begin to debug
whatever problems we run into.
Step #10 :
Before we can think about using this for
real data-taking, there will need to be a number of
modifications to TrigMon. Part of this is creating
new XTRP maps for the simulation including retrieval
of new parameters from the trigger Database. Another
part is modifying diagnostic plots based on the new
definitions of bits in the trigger banks. Hopefully,
Kevin and Eric can spend some time working on this
part.
In any case, I hope this summary is useful. Let me
know if there are any comments/questions.
Trigger SPL's
Last modified: Tue Jan 28 18:52:39 CST 2003