26 August

14:40

Turned CARME on 

Everything started up okay, all detectors on and stable. 

Note aida16 clock and ADC are uncalibrated. Note dssd4 is on MEC

Detector 1 noisy. 

AIDA started - all okay. 

All FEEs set to LEC (0x0) and slow comparator threshold set to 300keV (0x1e). 

Currently writing to data to G22-205/R100, doing background run, ~400 kB/s. 

16:40

Checks OK. 

19:00

Checks OK

22:30

Temps OK, Rates OK

x2go window size weird on different monitor as well.

27th August

Stopped Run 100. We had accidently set the threshold to 140 keV (0xe) not 300 keV (0x1e) as intended. 

Either way we require data on the alphas for electronics testing in October and the data rate at this threshold is too high. Threshold set to 0x64 (1 MeV) to look only at the alphas. 

Run 101 started. See attached leakage currents

20:30

Checks OK

28th August

10:00

Checks OK

CARME daq crashed this afternoon. Aida14 had a disconnection error. Seemed to coincide with dssd4 tripping again. 

Rebooting FEEs. On reboot there are always some FEEs which seem to have some error. The FEE changes each time. i.e aida12 one time, aida09 next time. I will give them a little while to compose themselves before trying again. 

Unable to get the system writing data to disk again. I think the system is unhappy with the merger / tape server not being closed properly. Will have a proper look tomorrow. 

29th August

20:15

Running again R102. 0x64 slow comparator thresholds. DSSD4 off due to leakage current tripping -> MEC

30th August

Daq continues R102