Main INDEX,
Monthly INDEX,
PREV,
NEXT
Make New Entry,
Make Followup Entry
User name lgan
Log entry time 00:08:01 on August 8,2005
Entry number 102908
keyword=shift summary
16:32, we had network communication problem and all ROCs can not be accessed.
We eventually fixed the problem following the procedure described in the
previous entry.
17:08, start run #58089
17:18, start run #58090
17:29, start run #58091, end run failed due to ROC13.
17:42, ROC13 is down, try to reboot all ROCs. ROC11 is rebooted very slowly.
17:49, start run #58092
17:53, ROC12 failed, reboot all.
17:58, start run #58093
18:09, start run #58094
18:21, start run #58095
18:32, start run #59096
18:38, Enge hodoscope histograms are bad, reboot ROC11 and ROC12. Run #59096 is junk
18:48, start run #59098, ROC11 is still not working. Reboot network server. No
data in this run.
18:58, start run #59099
19:07, start run #59100
19:16, ROC12 is down, reboot
19:17, start run #59101
19:28, start run #59102
19:37, start run #59103
19:48, beam is off due to ion chamber tripped. MCC informed us that reboot ion
chamber failed. Expert has been paged.
22:30, IOC expert arrived. He need a controlled access to the hall to fix the ion chamber problem.
22:48, IOC is fixed and the hall is in beam permit.
22:54, rebooted ROC13 and ROC14; we requested 5uA and have the raster set to 2x2 to warm up the target
23:04 requested 12 uA and to take off raster
23:05, start run #58104
23:16, start run #58105, ROC 12 crashed rebooted
23:18, start run #58106
23:30, start run #58107
23:40, start run #58108
23:44, ROC12 crashed and rebooted
23:46, start run #58109.
23:49, ROC11 crashed, all ROCs are rebooted
23:53, start run #58110