NEXT
Make New Entry,
Make Followup Entry
User name R. Michaels
Log entry time 06:48:42 on November 04, 2010
Entry number 338420
This entry is a followup to: 338410
keyword=auto BANU fixed now, I think
Because of the rearrangement of scalers before DVCS and that I forgot
to update the BANU script, it was looking at the accepted-trigger counts
for a helicity scaler. This would actually be ok for the purpose of
BANU, except that sometimes the helicity scalers stop counting (a
separate problem).
Just now I've repointed the calculation to the ungated scaler to find out
if the DAQ is in use. This should fix the automated BANU numbers.
Now we have to fix the helicity problems. I think I'm supposed to go in
today and look on a scope. It's a known problem that for 5% of the time
(with tails up to 60% in a given run) the helicity in this part of
the electronics makes no sense, hence the helicity-gated scaler stops
counting -- which affected this auto BANU calc.