15:30

Waiting for the target to cool down. ETA is 16:30 for cooling to be finished and then we need to try and make target.

While waiting we havve been running a background (R3). I noticed the rates on aida10 had increased (300k) and aida09 were slowlly creeping up too. Check load and shaking the detectors did not work. These FEEs correspond to the high leakage current detectors and showed similar rates to aida03 and aida04 which were turned to MEC.

Tried some tests. Lowered bias voltage to 50V. Rates increased on aida09 and aida10. Increased voltage to 110V and rates dropped to approx zero. Checked 105V and we get the same effect as at 110V. 

Then decided to try to increase the bias on DSSD1 as well. 110V no ffect but at 115V we see the rates drop to zero.

Data rates of ~300 kB/sec writing to disk.

Some increases in rates on aida12 have also been noticed. We have turned the fast discrimtor off for this FEE which has resolved the issue. We should keep an eye on the rates as we hope this is stable but may not be.

 Attachment 1 - current ADC data items rate with new settings. (still 0x32 slow comparator, all channels LEC)

Attachment 2 - aida12 discriminator settings.

Attachment 3 - current bias/leakage current values.

Started R4 - background we expect beam in the ring soon.

16:00

Beam is in the ring - we see the beam stripe on DSSD1

No change on data rate writing to disk or in ADC statistics rate.

Motors fully out. Left potentiometer = 18.86 mm, Right potentiometer = 19.80 mm

Beam energy = 2 MeV/u - 6Li1+

Cycle time is 25 seconds

Attachment 4 - CARME detectors xy plot

Attachment 5 - Total energy histograms (Ex)

17:56

Nikos requires access to the cave so beam is stopped and background run is going.

R5 started. Same settings as previous run.

21:45

All system checks OK - except white rabbit decoder and FPGA timestamps see attachments 6,7

Data rate had gone high again ~2 MB/sec. No difference on ADC data items. Large increase on aida06 for aida disc info #6.

Checked hit rate for aida06 and see ASIC 2 was misbehaving. ASIC check load on asic 2 -> problem sorted. This is not first time this has happened. We should keep an eye on the data rate.