At 23:22 we started recording data under the new conditions.

Merger, Tape server (WS3): 1408 kB/s writing ok

Leakage current (WS4): 3.27 uA

DAQ (WS2): temperature checked, clock status:ok, adc calibration:ok, white rabbit check:failed

Online monitoring (WS 5): done

In this last hour we have been playing with the cryostat temperature as dictated by Nikos, in order to have the target working properly. For this, we have increased from 80K to 140K the cryostat temperature then we saw again target until we didn't. Then we went down again to 80K. After a few minutes, with a really nice target again was gone, so we increased the temperature to 120K at 00:19. At 00:27 decrease from 120K to 80K.

Ring current 8e7 particles/s

Merger, Tape server (WS3): 1580 kB/s writing ok

Leakage current (WS4): 3.27 uA

DAQ (WS2): temperature checked, clock status: ok, adc calibration: ok, white rabbit check: failed

Online monitoring (WS 5): done

At 00:37 we lost the beam due to a high pressure burst in the tarjet which resulted in a valve closed at YR09VV...

On-call service technicians are coming to solve the problem.

We have recovered the beam at 01:49, after such a long time we had no target so we increased from 80K to 120K at 01:52. 02:01 update 120K-->95K as we have observed around that temperature always fluctuations and is safer.

Ring current 7.74e7 particles/s

Merger, Tape server (WS3): 1619 kB/s writing ok

Leakage current (WS4): 3.26 uA

DAQ (WS2): temperature checked, clock status: ok, adc calibration: ok, white rabbit check: failed

Online monitoring (WS 5): done

So far looks like with a temperature of 95K the target is maintained with a reasonable density throughout long periods of time.

Ring current 6.41e7 particles/s

Merger, Tape server (WS3): 1472 kB/s writing fine

Leakage current (WS4): 3.26 uA

DAQ (WS2): temperature checked, clock status: ok, adc calibration: ok, white rabbit check: failed

Online monitoring (WS 5): everything fine

We have decreased the temperatur> 95K --> 90K. At 95K the target was stable, but let's try to increase the density a bit.

Edit 03:54 : 90K --> 85K

Merger, Tape server (WS3): 1300 kB/s writing ok

Leakage current (WS4): 3.27 uA

DAQ (WS2): temperature checked, clock status: ok, adc calibration: ok, white rabbit check: failed

Online monitoring (WS 5): done

04:06 85K -->120K : 04:13 120K -->95K

current ring 8e7 p/s

Merger, Tape server (WS3): 1600 kB/s, writing/refreshing ok

Leakage current (WS4): 3.26 uA

DAQ (WS2): temperature checked, clock status: ok, adc calibration: ok, white rabbit check: failed

Online monitoring (WS 5): done

Ring current 8e7 particles/s

Merger, Tape server (WS3): 1664 kB/s writing ok

Leakage current (WS4): 3.26 uA

DAQ (WS2): temperature checked, clock status: ok, adc calibration: ok, white rabbit check: failed

Online monitoring (WS 5): done

6:05: 95K-->120K

6:12: 120K --> 95K

Ring current 8e7 particles/s

Merger, Tape server (WS3): 1414 kB/s writing ok

Leakage current (WS4): 3.25 uA

DAQ (WS2): temperature checked, clock status: ok, adc calibration: ok, white rabbit check: failed

Online monitoring (WS 5): done

Ring current 6.67e7 particles/s

pressure at S1: 2.3-2.8e-8

Merger, Tape server (WS3): 1574 kB/s, writing ok

Leakage current (WS4): 3.20 uA

DAQ (WS2): temperature checked, clock status: ok, adc calibration: ok, white rabbit check: failed

Online monitoring (WS 5): done

00:30
Pressure in S1 slightly decreased from before but still high enough to measure data.
One new count at 20MeV

Target density at S1: 2e-8 - 2.7e-8
Pressures OK (one small spike just before 00:00 in YR08)
System Checks OK
White rabbit fail diff: 49
Data write speed: ~1.4Mb/s
Beam intensity at injection: ~7.7e7
Cryo Temp Setpoint: 110K

(Beam intensity in ring dropped as I was writing which is why there is no rutherford peak on exRate image)
 

00:38
Intensity in the ring dropped by 2 orders of magnitude to 5e5 on injection

Lost rutherford rate (as seen in last e-log post)
All pressures seem fine

00:48
Called main control room, said they will take a look

00:59
Servo motor control restarted and homed

01:11
Ion source is confirmed to be off
Zoran will try and fix it, should take 1hr or so and not guaranteed to work.

02:25
Zoran was unable to ignite the ion source.

He has given some parameters to the control room so they can wiggle stuff around and try and ignite it.
He also said it may at some point ignite itself.
In worse case scenario, the person who usually manages the ion source will come in from 7am-8am, read Zoran's notes and try and get it working again.

Also target density seems a little worse but still hanging above 2e-8 to 2e-4

04:40
Target density is hovering between 2.0e-8 and 2.3e-8, sometimes dipping below 2.0e-8

We will conduct a temperature walkthrough while there is no beam,
04:40: setpoint 125K
04:46 setpoint 95K
04:56 setpoint 108K
04:59 setpoint 110K
05:00 setpoint 112K (here improved from 110K)
05:03 setpoint 114K
05:08 setpoint 113K

05:11
113K seems good, fluctuating between 2.3e-8 and 3.1e-8
will leave temperature here

Michael is modifying the settings of the electron cooler --> changed beam from bunched to coasting

Merger, Tape server (WS3) checks: DONE, writing ~1036 kB/s, refreshing is fine

Leakage current (WS4): 3.46 uA , stable current

DAQ (WS2): temperature checked,

     - clock status:

Clock status test result: Passed 5, Failed 0

Understand status as follows
Status bit 3 : firmware PLL that creates clocks from external clock not locked
Status bit 2 : always logic '1'
Status bit 1 : LMK3200(2) PLL and clock distribution chip not locked to external clock
Status bit 0 : LMK3200(1) PLL and clock distribution chip not locked to external clock
If all these bits are not set then the operation of the firmware is unreliable

     -  adc calibration:

Calibration test result: Passed 5, Failed 0

If any modules fail calibration , check the clock status and open the FADC Align and Control browser page to rerun calibration for that module

   - white rabbit check:

     Base         Current     Difference
aida01 fault      0xc228 :      0xc274 :      76  
aida02 fault      0x5e98 :      0x5ee0 :      72  
aida03 fault      0x92d3 :      0x931f :      76  
aida04 fault      0x7a92 :      0x7ade :      76  
aida05 fault      0xedc0 :      0xedcc :      12  
White Rabbit error counter test result: Passed 0, Failed 5

Understand the status reports as follows:-
Status bit 3 : White Rabbit decoder detected an error in the received data
Status bit 2 : Firmware registered WR error, no reload of Timestamp
Status bit 0 : White Rabbit decoder reports uncertain of Timestamp information from WR

DAQ (WS2): everything ok

Online monitoring (WS 5): done;

Still trying to recover previous pressures, more details in the next entry.

Merger, Tape server (WS3) checks: DONE, writing ~1030 kB/s, refreshing is fine

Leakage current (WS4): 3.46 uA , stable current

DAQ (WS2): temperature checked,

DAQ (WS2): everything ok

Online monitoring (WS 5): done;

Beam energy = 3 MeV

Horizontal beam position = 4.0 mm, vertical beam position = 0.0 mm.

Beam intensity at inj ~ 2.5e7

Detectors are positioned IN. Left arm = 36.54, right arm =  64.60 mm

Cycle time ~ 6 minutes

01:05

Target density still very unstable

02:45

Target density has dropped to ~1e9 and has been at that level for 30 minutes. We will try to move the target a bit and see if we can get an increase. Target position is currently x=-12400, y=2900

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

04:15

We were able to recover some target, but it is still very unstable. The new position is x=-12800, y=2000

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

06:15

Target still unstable, fluctuating around the 5e10 region

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

06:45

All system checks OK

Target density 3.4e11

11:50

System checks OK.

No beam in the ring yet. Althoug some injection may be taking place at low intensities

Target density appears much more stable than before.

Density currently just above 1e11 at/cm2

Note maintanace is required to appc025 so anydesk is currently down.

13:13

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

Attachments 1-5 (also waveforms)

15:00

Merger OK, Tape server OK

ADC data item statistics DO NOT looks as before. NOT OK

FEE temperatures look OK

System checks OK

Leakage current stable

Attachments 6-8

15:16

Notice the statistics for aida01-aida04 (DDSD 0, top left) were counting extremely high in the previous check (attachment 6). Previous rate was 0-1 counts.

We tried ASIC check load three times but not effect on the rate.

We then tried 'shaking the detectors' by moving the left pneumatic in and out again.

Rates go back to normal levels (0-1 counts)

8:13

Since 6:40 the target density dramatically dropped to 10^9 since then it has been unstable and did not recover. Currently it is around 8e8.

09:00

Target density has been increased to the high -10, very low -11 region. We will keep this run going unless the density is increased further.

10:21

Beam energy = 3 MeV.

Horizontal beam position = 4.0 mm, vertical beam position = 0.0 mm.

Target density ~ 1e9 at/cm2 (no target, get lost quite quckly)

Beam intensity at inj ~ 1.7e7

Detectors are positioned IN. Left arm = 36.54, right arm =  64.60 mm

Histograms and stats zero'd, monitoring code restarted.

Beam in the ring ~ 6 minutes.

Pressure in YR09 E target ~ 4.36e-11 mbar.

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

target density has been fluctuating between E9 to E12. We can very clearly see the increase in elastic counts on our detector during high density periods.

Attachment 1 - rate plots at 1E12 at/cm2

Attachment 2 - rate plots at 1E9 at/cm2

12:26

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

After reaching a density of > 10^12 a bit before 11:00, the valve got closed. When a valve is closed, can be observed a dramatic change in the plot and one of the three green ligths of atps7vaccrz1 (0,2,4) is turned off. Nikos opened it, and now it seems stable again around 1e11.

14:07

Merger OK, Tape server OK

ADC data item statistics looks as before. OK

FEE temperatures look OK

System checks OK

Leakage current stable

15:05

Run stopped as target density is rubbish. Might as well get beam background

- Motor checked , OK

SW3

- Merger OK

- Screenshot uploaded

- Data rate : 755 kbytes/s

SW4

- current plot uploaded

SW2

- T OK

- system wide check OK

- Statistics ok

- Spectra ok

SW5

4 plots uploaded