Log entry time 11:14:20 on November 2,2009

Entry number 297163

Followups:

• 297165 11/02/09 11:49 R. Michaels ovs=9 results seem ok

HAPPEX / PVDIS DAQ.

Here are some short runs to check oversampling.  

We'll check the rate(deadtime) and that the pedestals scale like 
1/N where N=oversample factor.  The GreenMonster is used to adjust
the timing board between runs.  Ovs = 0 means no oversampling
and Ovs=3 means oversampling-by-4, for example.  Selected pedestals
are shown on the 1st chan of two (roc,slot) combinations:

Run .... Ovs .... Integ .... Rate ... Roc23, slot0 ... Roc26, slot2

13697 ... 0 ...... 13200 .... 30 ..... 600.8 ......... 2157

13698 ... 3 ...... 3200 ..... 120 .... 137.3 ......... 514.6

13699 ... 9 ...... 1300 ..... 300 .... 48.92 ......... 201.6

but a  small fraction of the data are "glitchy" ... will follow-up
shortly on this.

Set BAD18DATA = -999 (minus) in happex3_ts.crl

13700 ... downloaded.  This reset the timing board to ovs=0.

I was going to do more, but it seems MPS is missing now.
(The ACC is replacing helicity board today ... I guess that's it.)