Hi, Peter,
I have implemented a simple EH-EH trigger in the Berkeley analysis software.
I masked anode 48 (the "hot spot") but otherwise left things as naive
as possible, projecting onto the time axis (only) and looking for two EH
hits separated by at least one TDC400 tick. The rates were then as follows:
Run Condition trigger rate [Hz]
muSC PP muSC+muPC PP
23433 mu+ unkicked 220 88
22941 mu- unkicked 192 69
26434 mu+ unkicked 84 35
26769 mu- kicked 527 199
27733 natural H2 kicked 133 52
It is extremely important to have the best possible pileup protection
for this analysis. I think that you will have to include the muPC in
the trigger.
Once muPC1 has been included, the rate is dominated by events like the
one I've attached, where there is a blue pixel along the green track.
The probability of such events is strongly dependent on exactly how
the E_high threshold is set relative to the gas gain, which explains the
large changes between runs.
However, we are not talking about an unworkable rate for the (mythical)
new FADC hardware. With appropriate tuning of the thresholds, we should be
able to get 50-100 Hz, which should not be too much of a problem to read out
and store, assuming some compression.
Thanks,
-- Fred
-- Fred Gray / Visiting Postdoctoral Researcher --
-- Department of Physics / University of California, Berkeley --
-- fegray@berkeley.edu / phone 510-642-2438 / fax 510-642-9811 --
Attachment:
cMuEventDisplay_1.ps
Description: PostScript document