Minutes FPD D0 integration Meeting
December  6th, 2002

Victor Bodyagin, Mario Vaz (VRVS), Wagner Carvalho (VRVS), Andrew Brandt (video), Ricardo Ramirez


1) Data Base

Victor has provided us with a FPD_GUI, which is a modification 
of the CFT_GUI in order to put the delay values in the sequencer.

Also, Carlos needs to provide access to his folder in the
online machine in order to keep going with the Examine
software.

2) TPP

Russ Rucinski is working in the design of the fitting tool in
order to make easier the task of attaching the cables to TPP.


3) Sequencer

Victor and Ricardo have tested the Sequencer using FPD_GUI, 
CFT_GUI, and the standard spread-sheet.

The first interaction, between FPD_GUI and Sequencer, requires
more tests. However, a first approach was tested, giving 
good results for one of the delays.

The standard spread-sheet tool was used for testing the
latest firmware modifications. The results are good for 
both delay values, and a new delays table has been generated.

More test are required. The AFE-Sequencer-VRB chain must
be evaluated using the Data Taker from CFT in CTS. It is
going to require some help from Fred.

3) DFE

Jamieson Olsen has provided us with the first DFE. He
has tested the link communication, and it seems to 
be working fine.

Andrew pointed that the second board is going to 
come by middle of January for the shutdown.

Mario and Wagner are working in the pipelined equations.
Also, the veto simulations showed that the timing is OK,
and they can fit in the DFE FPGAs.

Wagner has asked for an common web area in order to 
share the DFE projects. This area is going to be in
the FPD folder, d0server4, in the following path

http://d0server1.fnal.gov/projects/FPD/Hardware/Trigger/DFE/DWDB/www

The access to this area can be do it by FTP, through 
d0server1. For more information please go to

http://d0server1.fnal.gov/files/NT-ftp-srv.html


-----------------------------------------

	------------
	Things to Do
	------------

1. list of the involved steps in FPD DFE commisioning.
2. Testing with Veto equations in CTS
3. Testing of a dummy code with Data Pump.
4. Looking for documentation of the Trigger Manager in order
to start the brain-storm around this firmware.

-----------------------------------------