User name Sulkosky
Log entry time 13:28:46 on July27,2003
Entry number 107419
This entry is a followup to: 107346
keyword=Charge Asymmetry Feedback
Following up on Olivier's Halog entry (107346), I decided to look into the Parity DAQ problem. I looked at the end of run files and saw that the charge asymmetry during Owl shift and the first hour or so of Day shift was fine. However Run #'s 22887 to 22898 and 2887 to 2898 had a charge asymmetry between 3000 and 4000 ppm. Eventhough the Parity DAQ was running the charge asymmetry read back was blue and not updating. I attempted to fix the problem by rebooting ROC23 and restarting the Parity DAQ. This did not fix the problem. I also quit runbird and restarted it, but that also did not fix the problem.
I paged Bryan Moffit, and he said to quit and restart runbird again. This time the problem was fixed. He also said the error message that Olivier mentioned in his Halog was not a problem.
Note: Run #'s 22890/2890 and 22895/2895 are junk runs.