------------------------------------------------------------
Date: Sat Dec 22 07:50:03 2001, Shift: 00:00-08:00
Supervisor: James Norris, with:
Log book#11 pages 73 - 74
Shift Summary:
------------------------------------------------------------
1. 18:15 - Beam stored and cogged since 13:14
Polarization measurement being made.
Beam dump scheduled for 20:00
STAR wants .5hrs access after beam dump
16:45 - Called for Magnet Team to fix D1 fault
They came, they saw, they fixed.
D1 and D2 are now at 1/8, D5 is at 2kG.
20:05 - Beam dumped.
21:50 - Preparing for next ramp
22:40 - Beam cogged for data
02:31 - MCR called to say they planned to dump
beam in 10min
03:00 - Preparing for next store
04:00 - Filling RHIC
04:10 - We will not keep this store. The beam will be
dumped after polarization measurement
04:20 - RHIC beam is cogged and stored
Triggers 1, 3, 4, 6, 7, 8
2. PP Data Run 6101 - 539.5K, 16.0K, 201.5K, 44.2K, 0, 5.3K
PP Data Run 6102 - 175K, 7.2K, 95.2K, 20.8K, 2.1K, 4.3K
PP Data Run 6108 - Trigger 7 scaledown=1
PP Data Run 6109 - 174.2K, 3K, 39.1K, 8.6K, 2.7K, 5.9K
3. At 0425, I tried to do a TPC Pedestal run, not thinking
that fb3 was down. This produced an IoServe error that
I could not clear. Network status is fine according to
http://pii3.brahms.bnl.gov/~daq/opus-home-daq-run/daqhealth.html
The Alarm Help Message says that an IoServ error indicates
a loss of contact with EventBuilder, and
http://pii3.brahms.bnl.gov/~daq/opus-home-daq-run/runState.html
says: "Event Builder: no connection"
but at 05:15, I haven't found any reference as to what to do to
to establish an EventBuilder connection. Cycling power on
Rack 5.1, has no effect. But lo and behold,
stopping and restarting the IoServer of the Tasks page of the
DAQ has worked so I'm back in business!
Can't print on qms_ch - it wants letter paper in any bin, but it
has paper in upper bin.
------------------------------------------------------------
This archive was generated by hypermail 2b30 : Sat Dec 22 2001 - 07:50:57 EST