NEXT
Make New Entry,
Make Followup Entry
User name miham
Log entry time 08:10:20 on November23,2010
Entry number 341383
keyword=Owl Shift Summary (11/23/10)
Swing shift summary: Miha Mihovilovic (SL), Lamiaa El Fassi (TO)
===================================================================
EVENTS
------
00:00 Shift started normally. We inherited run #8970 from swing
shift. We are taking production data on LH2 target.
01:26 During run #8971 Roc 17 crashed. We stopped run and
restarted CODA. Restart did not help, becase ROC 17
still did not respond. Therefore we rebooted ROC17 and
start CODA again. It worked. Next production run is #8972.
03:15 Current suddenly increased from 3.0uA to 3.4uA. I called
MCC and asked them, to lower current back to 3.0uA. First
current dropped to 2.8uA. After a short trip beam current
changed to 3.1uA. I believe this is acceptable and will
leave it like this.
04:11 We noticed another jump in current. It first dropped to
2.8, but then increased to 3.4uA. I called MCC once more
and they have kindly adjusted current back to 3.0uA
04:30 MCC called and let us know, that one of their arcs tripped
off and that it will take few minutes to solve the problem
and recover the beam. Therefore we stopped run #8974,
which is almost an hour long.
05:10 Called MCC and asked them for an update. They told me, that
it will take them another 20min to recover beam.
05:18 Moved target to EMPTY for beam recovery procedure, since
there is no beam for more than 1hour and because problem
was in accelerator.
06:25 At 05:55 MCC called and told us, that they are ready to
send beam. We asked for 1ouA for the beam recovery
procedure. However, there is still no beam at the moment.
06:30 Beam seem to be back. Right now doing beam recovery
procedure.
06:32 Beam position monitors seem to be within the limits:
0.0 p/m 0.2. Moving forward to do harp scans.
07:11 Here are the results of a harp scan for 4A and 4B:
4A: sigma x/y = 0.11 / 0.148
4B: sigma x/y = ???? / 0.1493
MCC called me back and explained that they have problem
reading 4B in x direction. He believes that peak
is so thin, that he can not see it. He also believes
that beam should be fine. Therfore I decided to
accept it, since all other values are within the
limits.
07:13 We noticed that BPMs moved after HARP scan. We asked
MCC to adjust them once more.
07:15 We are back in production. Run number of the first run,
after the down time is #8975.
08:00 Shift ended in production mode. We passed following runs
to next shift: #8975 and #24210.
RUN LIST
===================================================================
Run Events BCM U3 D3 (C) Time Avg Curr Deadtime
-------------------------------------------------------------------
8970 295 k 0.00978 0.01078 61.3 mins 2.7954 uA 6.34%
8971* ROC-17 crased during this run. No end-of-run file.
8972 278 k 0.00910 0.01007 59.2 mins 2.7008 uA 6.51%
8973 297 k 0.00995 0.01095 59.2 mins 2.9442 uA 6.36%
8974* 265 k 0.00876 0.00967 55.8 mins 2.7521 uA 6.62%
8975* Run passed to next shift.
-------------------------------------------------------------------
* Look for notes abouts these runs in the time table.
COMPTON RUN LIST
===================================================================
Run Events START STOP
-------------------------------------------------------------------
24201 2.5M 23:41 00:17
24202 2.2M 00:18 00:57
24203 2.4M 00:58 01:39
24204 2.2M 01:41 02:19
24205 1.9M 02:20 02:53
24206 1.7M 02:55 03:25
24207 2.0M 03:26 04:01
24208 1.7M 04:01 04:31
24209 2.8M 07:14 08:03
24210 Run passed to next shift.