[TABLE border="1"]
Time | Part. Det. Int | SIS-intensity| accumulations in ESR |  cooler-HV PTB K250 |  cooler-HV PTB red | cooler-HV orange | LMD-DAQ1 Files | LMD-DAQ2 Files | scan range(nm) | number of positions | dwell time (laser shots) | n loops | checked laser position | comments |-
22:16 | 4800 | 2e9 | 30 | 104525 | - | - | 300 | 327 | 548.51 - 548.01 | 201 | 15 | 2 | yes | only few ions, did not start Go4 |-
22:28 | 9000 | 2e9 | 15 | 104525 | - | - | 301 | 328 | 548.51 - 548.01 | 201 | 15 | 2 | yes | After this run: Shaky SIS intensity, cathode is being changed |-
22:53 | 7000 | 2e9 | 35 | 104525 | - | - | 302 | 329 | 548.51 - 548.01 | 201 | 15 | 2 | yes |-|-
[/TABLE] 
23:20 Failure of GE01KP04, GE01KP05, GE01KP22 (or GE01KP24) devices in the ESR.
Problems with gtemu3-hick (??) , take injections since 
01:49 Bernd tried to make things work by switching off and on some of the dipole correction coils. He was even able to get a quite good intensity by leaving one of the coils switched off (although with a slight shift of frequencies visible in Schottky spectrum) but then the ESR electron cooler has failed probably due to problems with the cooling water. So, the decision was taken to stop the measurement at this point. The laser was switched off.

On the NTCAP the directory is changed to 
Q:/E0052

With reference to entry 37 Laser timing:

- at last 30 injections accumulation: 10k counts on particle detector (accumulated during manipulation until it saturates, e.g. no more Th in ESR)
- at first 70 injections accumulation: 7.6k counts
- at second 70 injections accumulation: 2.8k counts

did another 2 30 injections accumulations to confirm lower yield: 
- at first 30 injections accumulation: 3.7k counts
  SIS intensities look fine, around 1.2e9
- at second 30 injections accumulation:  6.9k counts
  saved to /data.local2/2025_229Th/2025_229ThDAQ1_0101.lmd with DAQ1
  SIS intensities look fine, around 1.2e9, only users during injection
  "late" contaminants on PD seem to quickly disappear after start of modulation 3 
  (attachment 1: full timing spectrum, attachment 2: timing spectrum at the end of the modulation)
- at second 60 injections accumulation:  0 counts, maybe scrapers overshot,did another one, still not accumulating

     -------------------   Some issue on accelerator side   -------------------
        FSR people had to go into cave, that's why we were the only users, 
        but since nothing got into ESR
        Connection to scrapers was lost, on call service had to do a reset

- at second 60 injections accumulation:  11.9k counts
  saved to /data.local2/2025_229Th/2025_229ThDAQ1_0102.lmd with DAQ1
  again observed that the late contaminant om the particle detector (see attachment 3) is more prominent in at the beginning.
  This also manifests in an early steep fall off on the counts/s, see attachment 4

• 3 Loops
  
• 501 Steps
  
• 15 Shots / Step
  
• From 550.4 nm to 547.9 nm. In total 2.5 nm @ 0.005 nm
  

We roughly adjusted the timing based on attachment 1, for ions to be in center of electron cooler (east arc), corrected for PMTs being 2.5m closer to the north on the west arc
then did a new 30 injection accumulation (10.8k counts on particle detector) and readjusted the timing to fine tune this
(attachment 2, first settings right peaks, adjusted towards left)

Then we did a 60 injection accumulation (only 7.6k counts?) to check the settings and shift the timing by half a revolution (324 ns = 98 bins)
(attachment 3, data saved in /data.local2/2025_229Th/2025_229ThDAQ1_0099.lmd with DAQ1).

Checked these settings and particle counts with another injection (2.8k counts)
(attachment 4, data saved in /data.local2/2025_229Th/2025_229ThDAQ1_0100.lmd with DAQ1)


Estimated bunch width: 20bins = 67ns;corresponds to 20/200 of 1 evolution, so about 12m
                                     assuming v+0.5c0: 11m

Pulses on photodiodes in entry 20 

1. seem wide, so we also looked at qswitch signal; also seemes wide.
2. Have a tail

1.:

We investigated this and came to the conclusion, that the CFD is the issue:
- On an oscilloscope, when looking at both HF signal (CFD input) and CFD output, there is a 2ns jitter.
- The same jitter is visible when looking at the CFD output when triggering on a freq. generator signal with same frequency and amplitude as HF signal (1.54263 MHz; 1V peak to peak).
- There is not significant jitter when comparing the CFD output and the qswitch signal

We tried differents CFD (also a leading edge CFD / different thresholds), but this did not significantly improve what we saw on the oscilloscope.
Applying a 10MHz filter to the HF signal only made the jitter worse.
There might be an option to get a logic (NIM) signal from ESR instead of the sin-signal
Alternatively, one could think about using a PLL.
Note: the 2ns might also be limited by the trigger of the oscilloscope. We saw that if the trigger of the oscilloscope is not on the steepest part of the HF signal, the jitter "gets worse".

2.:

We saw on the qswtich signal, that there are instances, when  the q-switch signal is too early; 
Ww will try to find out which NIM module between the CFD and the final qswitch signal causes this
Preliminary: It's coincidance crate

Apparentlty did not work yesterday evening (no signal), but looks fine now (see attachment)

The gate generator of the Q-switch signal for the Vuprom TDC was set to 10ms.

We exchanged the old BBO of the Cobra's FCU with a new one. The output power of the Cobra was around 120mJ. In the end, we achieved a UV power of about 21mJ. In addition, we optimized the fiber-coupling to the wavemeter.