Log entry time 23:58:59 on April 06, 2011

Entry number 354636

Crew:
Ole Hansen (SL)
Nuruzzaman (TO)
Carlos Munoz Camacho (3rd)

Summary:
Mostly smooth production data taking on 4He. Beam instability during
first half of shift might affect data quality.

Events:
16:00 Start shift with production in progress. 4uA on 20cm 4He.
16:10 BigBite scaler display shows large dead areas. Rebooting bbts1
brings them back alive.
17:49 MCC calls to inform us of an unstable box power supply that causes
our beam position to fluctuate by a few 1/10th of a mm. We continue to
take beam even if the data might be affected.
19:33 MCC takes beam away for experts to look at the beam instability
problem.
20:44 Beam delivery resumes. Beam positions stable now.
21:20 spot++ for the first run after the downtime, 3328, shows a
mysteriously offset beam position. The BPM readings on the Tools screen
are perfect, though, so we doubt that this a real. We start a new run,
and the problem is gone. BPM data in run 3328 are suspect. DAQ glitch?
24:00 End shift with production in progress

Run summary:
3324 production 165k. Stopped to reboot BB TS
3325 production 1M
3326 production 1M
3327 production 300k
3328 production 538k. BPM data might be bad. DAQ glitch?
3329 production 1M
3330 production in progress at end of shift