User name paschke
Log entry time 21:52:01 on January30,2003
Entry number 93937
keyword=parity DAQ oversamplingI took a couple of oversampled runs on the parity DAQs to keep an eye on the unusual multipeaked charge asymmetry.
I set all ADCs in the high-energy DAQ to High Gain. I didn't change the injector
DAQ ADC gain, because I couldn't remember the old commands.
For both DAQs, IT = 1000, RD = 0
Runs 5201 (injector) and 1585 (high-energy) had Oversampling = 13 (setpoint=12)
Runs 5202 and 1586 had Oversampling = 12 (setpoint 11)
Runs 5203 and 1587 were made to check that I had properly reverted to
IT=13300, OS = 1 (setpoint=0), and high-energy DAQ ADCs to Low Gain, except for ADC0 and ADC4.
I couldn't get the feedback pan to work properly with oversampling, even though I
changed the /home/apar/db/control.db which is what I thought it loaded.
I've included a plot of the time structure of the charge asymmetry across the helicity
window, separated by the ordering of the pair and the previous helicity state. For
some reason, the outer peaks have moved much closer to together, and now lie
at only +/-1100 ppm (instead of 2000 ppm, as seen in previous runs with HWP out).
The charge asymmetry without oversampling (run 1576) is shown in figure 2.
FIGURE 1
FIGURE 2
