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;

Merger, Tape server (WS3) checks: DONE, writing ~1 1273kB/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 :      0xc272 :      74  
aida02 fault      0x5e98 :      0x5edf :      71  
aida03 fault      0x92d3 :      0x931d :      74  
aida04 fault      0x7a92 :      0x7adc :      74  
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

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

Leakage current (WS4): 3.48 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 :      0xc272 :      74  
aida02 fault      0x5e98 :      0x5edf :      71  
aida03 fault      0x92d3 :      0x931d :      74  
aida04 fault      0x7a92 :      0x7adc :      74  
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; first shots with something?

13:20 Stopped run.

Slow comp thresh 0x64 -> 0x32 on all FEEs

Checkload x2

New run - R55

Restarted Data Spy code

Zerod histograms

Data rate acceptable.

Dead channels seem to come back online

Please check for deadtime/idle time once we collect enough stats.

01:00

Beam optimisation since 09:25.

Target ON and open to the ring

YR09xxx ETarget ~1.9e-10 (saturated)

Target E4 inlet pressure ~8.8E-9 mbar

Dump S3 ~ 6.8E-10 mbar

Nozzle temperature 150 K

Run 54 started, monitoring code restarted.

Beam optimization will be done until 3 pm and will be then give for the experiment.

11:30

Beam optimisation. No beam since 09:25.

Target ON and open to the ring

YR09xxx ETarget ~1.9e-10 (saturated)

Target E4 inlet pressure ~8.8E-9 mbar

Dump S3 ~ 6.8E-10 mbar

Nozzle temperature 150 K

Run 54 started, monitoring code restarted.

Beam optimization will be done until 3 pm and will be then give for the experiment.

YR00DA1ZB is the channel for PMT rate.

Results of the fortran analyser programs for R54_14

No timewarps observed in the data
No dead time observed either.
Lots of idle time but expected with high thresholds and low noise

09:30

Beam optimisation. No beam since 09:25.

Target ON and open to the ring

YR09xxx ETarget ~1.9e-10 (saturated)

Target E4 inlet pressure ~8.8E-9 mbar

Dump S3 ~ 6.8E-10 mbar

Nozzle temperature 150 K

Run 54 started, monitoring code restarted.

FH and ML are optimising the beam.

08:30

Beam ON ~1.0E7 pps

Target ON and open to the ring

YR09xxx ETarget ~1.9e-10 (saturated)

Target E4 inlet pressure ~8.8E-9 mbar

Dump S3 ~ 6.8E-10 mbar

Nozzle temperature 150 K

Run 54 started, monitoring code restarted.

FH and ML are optimising the beam.

07:30

Beam ON ~8.0E6 pps

Target ON and open to the ring

YR09xxx ETarget ~1.9e-10 (saturated)

Target E4 inlet pressure ~8.8E-9 mbar

Dump S3 ~ 6.8E-10 mbar

Nozzle temperature 150 K

Run 54 started, monitoring code restarted.

08:00 The beam is electron cooled by FH and the orbit of the beam is slighty changed.

06:47

Beam ON ~2.0E6 pps, still fluctates between 1e6 and 6e6 (like a step function)

Target ON and open to the ring

YR09xxx ETarget ~1.8e-10 (saturated)

Target E4 inlet pressure 8.0E-9 mbar

Dump S3 ~ 6.6E-10 mbar

Nozzle temperature 150 K

Run 54 started, monitoring code restarted.

06:00

Beam ON ~1.5E6 pps, still fluctates between 1e6 and 6e6 (like a step function)

Target ON and open to the ring

YR09xxx ETarget ~1.8e-10

Target E4 inlet pressure 8.2E-9 mbar

Dump S3 ~ 6.5E-10 mbar

Nozzle temperature 150 K

Run 54 started, monitoring code restarted.

05:00

Beam ON ~2E6 pps, still fluctates between 2e6 and 6e6 (like a step function)

Target ON and open to the ring

YR09xxx ETarget ~1.8e-10

Target E4 inlet pressure 8.3E-9 mbar

Dump S3 ~ 6.8E-10 mbar

Nozzle temperature 150 K

Run 54 started, monitoring code restarted.

04:00

Beam ON ~5.5E6 pps, but it fluctates between 2e6 and 6e6 (like a step function) in about each 5-10min

Target ON and open to the ring

YR09xxx ETarget ~1.8e-10

Target E4 inlet pressure 8.4E-9 mbar

Dump S3 ~ 7.0E-10 mbar

Nozzle temperature 150 K

Run 54 started, monitoring code restarted.

03:00

Beam ON ~7E6 pps

Target ON and open to the ring

Target E4 inlet pressure 8.5E-9 mbar

Dump S3 ~ 7.3E-10 mbar

Nozzle temperature 150 K

Run 54 started, monitoring code restarted.

01:30

Beam ON ~6E6 pps

Target ON and open to the ring

Target E4 inlet pressure 8.12E-9 mbar

Dump S3 ~ 7E-10 mbar

Nozzle temperature 150 K

1:40

Run 54 started, monitoring code restarted.

signals from ICT and CRYRADIO are now connected to AIDA2 and AIDA5 respectively. ICT is set to factor 200 and CRYRADIO to 40 for now.

(AIDA3 --> electron cooler)

Currently 4 possibilities to have a look at the beam, all of them are OK to check whether there is beam or not, but some of them are better for checking absolute values.
- Schottky RF signal
- Schottky zero span signal
- CRYRING Radio (signal from BPM) --> YR12DA1R
- ICT (integrated current transformer) --> YR12DT1C

absolute measurements:

- currently the beam is at 5.5 MeV/u calibrated on the flat top. The signal of ICT before is noisy but on the flat top it is well calibrated.

relative measurements:

- The signal from CRYRING radio, has a good amplifier and is frequency independent with a nice log signal. it can be used for relative measurements

- The zero span signal of Schottky can be used, but it is not reliable for measuring the number of ions since change in the control room may change the signal level.

- Schottky RF signal can be viewed by running Launcher-App using the button "VNC Tektronix RSA". The only problem is that only one instance can run, so if in the control room someone needs it, in the container it will disappear.