Fiber Tracker Meeting Minutes

talk slides
as the boards come back from being modified, they don't always come back happily
we're being hampered by calorimeter studies
53MHz readout has been successfully installed on crate 0x50

accidentally destroyed two VME backplane connectors in the process - will need to be fixed

sequencer and DFE power supplies on South and West side upgraded; still need to do North side
AFE power supply upgrade not started yet

talk slides (only pages 1 through 11)
require that, on the layer of interest, the hit has to be a singlet
page 5 - top set is an axial layer, bottom is a stereo layer
page 6 - x-axis is phi
page 7 - "Light yield for axial layers (clusters)" - each hit is plotted separately
steps in the bit processing may be producing artifacts in this data - needs to be checked

spoken status report given
used MC file produced by Mike (Z->mumu), including high occupancy events
using a sigma of 25cm
in Guennadi's code, info is provided per fiber, but the reco code used clusters - could be a mistranslation between the two
additional condition: (z of axial cluster - z of stereo cluster) < 75cm (about 2 sigma?)
results are encouraging - see a reduction in the time it takes to reco tracks
50 events, tracking only, default(AA only) took ~1200sec; modified code took ~500sec
average number of tracks reco-ed goes from 107 to 92
Alan will set up a meeting next week about how to proceed

talk slides
data is zero bias events with beam in the machine but not colliding
did not have trigger requirements other than zero-bias or min-bias fire? need to check
Greg: the L3 info includes the prescale, the AND/OR terms do not
plots show that eventually zero-bias and min-bias slopes will cross?
pages 10-11, and 13-16 : x-axis is luminosity per luminosity block
"set 1" is before timing change, "set 2" is after (really just different run ranges)
min-bias is much flatter than zero-bias, set after timing change slopes down!
Andrew: the online database stores the prescale per run
Greg: patterns could be due to the prescales beating against the accumulated luminosity (need to get instantaneous luminosity). Also, the jet95 trigger is never prescaled.

Gaston: has the ability to adjust the ADC cut separately btw axial and stereo been implimented? No. Still debating how to impliment this. No one has volunteered to do further study or re-code.
Jadzia: can have one cut level per tick, per fiber type?
The debate goes on...
Decided that right now Mike should impliment "if axial, ADC cut = 20; else ADC cut = 10" and get an expert to test the reco timing difference.