Main INDEX
Monthly INDEX
PREV
NEXT
User name gilman
Log entry time 15:54:25 on June 9,2000
Entry number 43249
keyword=day shift summary for June 9, 2000
start shift waiting for beam.
Make controlled access to reset hadron spectrometer polarity,
let Compton people work on Compton, and let in some physical
plane people for 15 minutes.
10:20 Moller starts taking data.
12:15 end Moller, start 15 minture MCC no-beam reproducibility test,
originally scheduled for 9 AM this morning.
Notice forgot to turn regulation on when turning hadron dipole
back on. Turn it on and now the field is settling much more quickly.
How soon they forget.
12:40 move target
12:43 ask for 5 uA unrastered for Harp scan, pointing test, ...
First HARP scan looks okay, but ROC14 (beamline) looks dead -> reboot
run 1830 coda, scan 927, see separate HARP
run 1831: carbon pointing test
run 1832: 4-cm dummy pointing test
run 1833: 15-cm dummy pointing test
run 1834: 10-cm dummy pointing test
Riad downloads the trigger, just to be sure for coincidences in the future...
run 1835: spot check - it looks to be 1 by 1 rather than 4 by 4.
run 1836: spot check - 300 k events taken at 5 uA taken with 4x4 raster
run 1837: luminosity scan - 20 uA, ps1 = 30, took ~300k
We observe that with 1 kHz of T1's only reading in, datamon shows
deadtime=0%, which must be wrong, for events randomly distributed in time.
run 1838: luminosity scan - 40 uA, ps1 = 30 -> redo (and beam tripped)
run 1839: luminosity scan - 40 uA, ps1 = 60 -> run tripped at end, took ~300k
run 1840: luminosity scan - 60 uA, ps1 = 90 -> beam trips at 80 k
run 1841: " " " " took 270 k, beam tripped for ~20 s about 1 minute before end of run
run 1842: " " 70 uA, ps1 = 100, took ~310 k
run 1843: " " 80 uA, ps1 = 115, took 17 k before trip...
run 1844:" " " " " , took 300 k, ended just before beam trip
- start production data -
beam is tripping often
run 1845: 1.25 M events
start run 1846
appear to have had ~12 trips this past hour