2005/06/10 16:30 16:30;;2005/06/10;;+25;;LCChain
2005-6-10 18:00;;Hagar;;
2005-6-10 18:30;;Success.
Connection between hub was not tested.
hub2-hub1-hub5
The hubs connection was tested succesfuly
setup here:
fathub1 fathub2
fathub5
;;one doms (700) was not communicating. It was replaced by fat 6 dom Leprechaun (620)
2005/06/10 16:50 16:50;;2005/06/10;;+25;;STF
2005-6-11 18:49;;hagar;;- fathub2 : ok
- 3 doms failed flasher clock. after fb update passed. fathub1, fathub5: stoppetd before flasher-width. many flasher clock failures.all passed after fb update.
2005-6-12 15:33;;problem running flasher-width on hub1 and hub2
1 failure: flasher bright on 13215a559856;;
2005/06/10 18:20 18:20;;2005/06/10;;+25;;DOMCal
2005-6-10 22:40;;hagar;;Updated domcal on all doms.
7b0de8658562 LeukoPhobia Failed to calibrate. It is on fathub1 111U. updated domcal (again) but still no HV info while updating HV2DB
2005-6-10 23:40;;~/domcal/domcal+25/
1 dom failed
histos here.
;;
2005/06/10 19:20 19:20;;2005/06/10;;+25;;Lux
2005-6-11 10:40;;hagar/kael;;error: connection refused from lightsource.py.
Rates very high 20k-30k
one dom readouts=0, the same one who did not calibrate
Chris killed a python light control script, and now ok.
2005-6-11 18:47;;11.lux
;;
2005/06/11 08:00 08:00;;2005/06/11;;+25;;TestDAQ
2005-6-12 16:2;;hagar and later mark;;run 6585-6588 LC-darknoise - ok
run 6589-6598 : darknoise and gainHV runs. failed on multiplexer.
=================
from now running on hub1 and hub2 (no hub5) 62+64:
run 6599-6600 : gps problem in card 1,3 on hub2. reloaded.
6601 - 6606 dark noise - ok for atwd0, multiplexer-wisdom error for atwd1
6607-6614.. gain vs. HV many multiplexer for both atwd. few runs are ok, even for the dead dom Leukophobia: 6610, 6609,6613
=================
from now running on hub5 and hub2 (no hub1): 20+62
6615 - gps problem fathub5, card2...reloaded
runs 6616 - 6621 ok for all doms. still running
some multiplexer failures, for a single doms (but for most of the runs stable)
=================
from now running on hub5 and hub2 and hub1: 20+62+64
starting at run 6652
gps on hub2, card3 and hub5 card2...reloaded
run 6653....
started up run 6653 - idea is to check for socket errors and correlate the symptoms.
The GainVsHV runs tend to have lots of socket errors, as well as some of the Linearity runs.
Others are OK, except that some DOMs have socket errors - WisDOM and RanDOM seem to be more likely to generate this type of error, implying that the error may be related to the trigger rate...
2005-6-13 0:9;; ;;
2005/06/11 16:30 16:30;;2005/06/11;;+25;;Soaking / stability
2005-6-12 18:52;;kael;;see lux run above
2005-6-12 18:52;;;;
7; 2005/06/11 17:30 ; +25; Cooldown
8; 2005/06/12 08:30 ; -20; Defrost
9; 2005/06/12 09:15 ; -20; Cooldown
10; 2005/06/12 22:00; -45; STF
11; 2005/06/13 09:00; -45; DOMCal
12; 2005/06/13 10:00; -45; TestDAQ
13; 2005/06/13 17:00; -45; LUX
14; 2005/06/13 19:00; -45; Soaking / stability
15; 2005/06/14 19:00; -45; Cooldown
16; 2005/06/15 08:30; -55; STF
17; 2005/06/15 10:00; -55; DOMCal
18; 2005/06/15 11:00; -55; Lux
19; 2005/06/15 13:00; -55; TestDAQ
20; 2005/06/15 21:00; -55; Soaking / stability
21; 2005/06/17 08:00; -55; Warmup
22; 2005/06/17 11:30; -20; STF
23; 2005/06/17 13:00; -20; DOMCal
24; 2005/06/17 14:00; -20; Lux
25; 2005/06/17 16:00; -20; TestDAQ
26; 2005/06/18 08:30; -20; Soaking / stability
27; 2005/06/19 08:30; -20; Defrost
28; 2005/06/19 09:15; -14; Warmup1
29; 2005/06/19 14:15; +15; Warmup2
30; 2005/06/20 09:15; +25; LCChain
31; 2005/06/20 10:00; +25; STF
32; 2005/06/20 11:05; +25; DOMCal
33; 2005/06/20 12:05; +25; TestDAQ
34; 2005/06/20 19:05; +25; Lux
35; 2005/06/20 21:05; +25; Soaking / stability
36; 2005/06/21 16:30; +25; Cooldown
37; 2005/06/22 08:30; -20; Defrost
38; 2005/06/22 09:15; -20; Cooldown
39; 2005/06/22 19:15; -45; STF
40; 2005/06/23 08:00; -45; DOMCal
41; 2005/06/23 09:00; -45; Lux
42; 2005/06/23 11:00; -45; TestDAQ
43; 2005/06/23 19:30; -45; Soaking / stability