UV power was not stable but dropping from ~18 mW to 13 mW after opening COBRA shutters.
New calibration of frequency conversion unit:

Wavelength/nm       Position/Steps
554,0001            383029
553,0000            386604
552,0001            390229
551,0000            393954
550,0001            397679
549,0001            401404
548,0001            405104
547,0001            408829

now stable at ~19-20 mJ depending on wavelength

Table of dataset: Attachement 1
Plot of dataset: Attachement 2

The data of DAQ1 are stored in the following directory and with the following filenames

open file /data.local2/2025_229Th/2025_229ThDAQ1_ -auto -rfio 
(from @openfile)

The usual @connectdisk, @openfile @closefile are adapted and can be used.

The WDBook RAID0 disk is attached for backup of the data

/media/atplaser/WDBook2/2025E0052daq1

We checked the timing (before the start of the measurement cycle documented below).
Timing and measurement window are attached.

We cross-checked the timing. Laser pulse is detected at bins 136 (PD-North) and 171 (PD-south), respectively. Therefore, the laser puls is in the electron cooler at 153.5. The revolution period corresponds to 3e8Hz / 1.54315MHz = 194. 
The ion bunch must travel 2.5m more than the half of the circumference (108.3m). Taking this into account, the ion bunch must be detected (0.5 + 2.5 / 108.3) * 194 = 101.5 bins later (meaning less) than 153.5.
Finally, we are happy that the timing is still perfect, since the ion bunch arrives at 52. 

Test scan to see whether laser spot is moving while scanning

Aborted accumulation because SIS stopped. 12.9k counts
saved as /data.local2/2025_229Th/2025_229ThDAQ1_0103.lmd using DAC1 only

We filmed it and will try to attach it later
1. After resetting to high wavelength, the MRC stabilization takes a bit longer to adjust, beam not centered for the first 1-2s
2. During the scan the beam does not seem to jump around more than usual, but there might be a minimal wavelength dependent drift (maybe 1/3 of laser beam diameter towards bottom right over entire scan range)

• ECEDS1VU: Verriegelt mit ECEDS1HA. Der Antrieb kann nur fahren
  wenn der Antrieb ECEDS1HA in Position -4,0 steht.
  
  
• ECEDS1HA: Verriegelt mit ECEDS1VU. Der Antrieb kann nur fahren
  wenn der Antrieb ECEDS1VU in Stellung EI steht.
  
  
• ECEDS2VU: Verriegelt mit ECEDS2HA. Der Antrieb kann nur fahren
  wenn der Antrieb ECEDS2HA in Position 0,0 steht.
  
  
• ECEDS2HA: Verriegelt mit ECEDS2VU. Der Antrieb kann nur fahren
  wenn der Antrieb ECEDS2VU in Stellung EI steht.
  

• Very long cooling times are needed after deceleration to cool the decelerated beam.
  
• Electron energy and decelerated beam are not well matched.
  
• 229Th is cooled even later after the other ions
  
• Even after scraping some contaminats remained that were either rebunched and show side bands. or move around as a "cloud".
  
• This can be seen on the detectors (e.g. particle dector, but also PMTS) as a flat bump in the folded "accu" spectra. the signal decreases with time. I.e., It moves around the ring with a frequency matching the one of the wanted species but with some "phase offset" of about half a ESR revolution. The signal is ratger stron but vanishes ("decays") after some time. Probably finally scraped og
  
• It is very tigth to set the scrapers correctly (and the particke detector).
  
• Fortunately the ion beam optical setting is such that the scraper in the south is in optimal position just at its "Endlage inne" (values see below)
  
• SIS intensiteis have increased but are still on average a factor 3-4 lower than one year ago.
  
• As a sidenode: For optimal scraping, the beam decelerated, debunched, cooled, scraped and rebunhced. Thus, one can see if there are contaminants, and, in consequence clean the beam better from unwanted species.
  
• The bunches are still quite long given the number of ions, increasing of the bucket fill from 1.0 to values large than 1.4 gives problems such as phase shifts , ande changes even inbetween a waiting/measurement time. to be discussed with the specialists on monday
  

• The cooling energy is set 100V higher - which also matches better to a recalculated scanning range; ( PTB 104513 V, Ohmlabs 1040509 V). This better matching improves cooling times but is till not optimal. It is noted, tha tthe cooling times are long since a broad cloud of ions is decelerated, and the electron current is low (was 50 mA, now 60 mA).
  
• Electron current increased 50 mA -> 60 mA.
  
• Scrapers are moved in in two steps with an intermediate posiions to mitigate the problem of overshoots when driving. Before rebunching they are slightly moved out to make room for the slightly larger
  bunched beam.
  
• Due to the change of the voltage the bunching frequency has changed (see post of the start of the test measurements); electron cooled DC beam and bunched beam are (alomost) matched using the RSA in 100kHz scale. The new reference frequency on the RSA are (old: 243.750625MHz, rev. frequency 1.542728 MHz, 158 harm - new: 243.815 MHz, 1.54313 MHz).
  [New settings for timing and scraper position will be attached as fotos; an emergency backup of the settings are stored in an earlier post).
  
• The cooler actually drags the ion very slowly to its final position after ~30 s just before rebunichng (visible by the shift of the peak relative to the marker just before rebunching). This is interpreted as and effet of the power supplies only very slowly reaching a final value to within a few kHz.
  

[1] 242.27986 MHz
[2] 242.82623 MHz + 27.5 kHz
[3] 242.853 MHz + 54.375 kHz 229Th
[4] 242.878 MHz + 79.375 kHz
[5] 242.936 MHz + 137.5 kHz
[6] 242.959 MHz + 160 kHz
[7] 242.982 MHz + 183.75 kHz

[1] 243.6925 MHz
[2] 243.72213 MHz + 29.6 kHz
[3] 243.750 MHz + 57.375 kHz 229Th --- Reference on Schottky scope
[4] 243.7768 MHz + 84. kHz
[5] 243.8376 MHz + 145 kHz
[6] 243.863 MHz + 170.6 kHz
[7] 243.687 MHz + 194.625 kHz

1. UNILAC running again, so we resumed the beam tuning wherre we stopped yesterday at 14:00

2. Goals: Reduce intensity and lifetime of "antibunch" contamination while maximising intensity for main bunch/on PD
   Adjusted bucketsize, el. cooler current, cooling times,.. 
   Managed to get bunch width to 6-8 bins and get 10k counts in 15 mins with only 20 injections
   but el. cooling still takes long and sometimes bunch phase jumps by 90° in "measurement manipulation"

4. Checked scan range again and found small discrepancy

3. Decided to switch el. cooler voltage (1st cooling) by +100V, 
   ion beam position in el. cooler should not be afected by this too much, at the scrapers at which the dispersion is maximal it shifted the beam by 5mm

new revolution frequency: 1.54315 GHz
new electron cooler voltage: 104506 V(+95 V; slightly adjusted to match revolution frequency   
"antibunch" vanishes within first 10s
bunch on PD wider, but might be missmatch of HF and cooler voltage

1. Open additional views, options are "Display" (figure of recent values), "MBS Messenger" (connection status with MBS, lower part of Attachment 2), "Devices View" (most recent values of different devices, right part of Attachment 2)
   
2. Make sure that "Make Data Available to MBS" is selected
   
3. Definition of laser scan Parameters. The laser will perform an automated scan between the selected wavelengths. It's possible to define an increment or a number of laser steps as scan parameter. After the laser has received the specified number of rising edges on Trigger port #1 (Do not change the port number, since this corresponds to the Hardware setting!) the laser advances to the next frequency until the number of steps and scan repetitions is completed. There is an option to start the laser scan automatically, when a trigger was received on port #3 (The cabling is done. However, the pulse generation must be provided from SCU sddsc221 channel IO1 of timing receiver tr1 whenever needed).
   
4. The button can be used to start and stop a scan. In some cases there might occur an USB communication error with the laser, which can also be reset by this button.
   
5. IMPORTANT NOTE: Make sure that the FCU is enabled, since otherwise the BBO of the FCU does not follow the wavelength of the laser, which results in NO UV output power.
   
6. After "Make Data Available to MBS" option (see 2.) has been selected, Medusa is awaiting the MBS client to connect.
   
7. View of most recent parameter settings.
   

1. Start medusa as described above
   
2. Connect to "r4l-41":
   atplaser@lxg1297:~$ ssh atplaser@r4l-41
   
3. Change to the directory of the Th-MBS version:
   R4L-41 > cd mbsrun/E0052/DAQ1
   
4. Make a reset (optional):
   R4L-41 > resl
   
5. Start mbs:
   R4L-41 > mbs
   
6. Once you are in the mbs environment start the acquisition:
   mbs > @startup
   
7. Connect to the file server:
   mbs > @connectdisk
   
8. Start acquisition:
   mbs > sta ac
   With this command, the connection to the Medusa server should be established. This can be verified by the line
   -R4L-41 :read_meb :connected succesfully to LabView Server.
   of the MBS output, and in the MBS Messenger View of Medusa stating
   Connected! Established connection to ...
   
   
9. Open file:
   mbs > @openfile
   
10. Press Run-button in the Go4 analysis (must be started beforehand)
    
11. Start laser scan in medusa
    
12. Press Stop-button in the Go4 analysis
    
13. Close file:
    mbs > @closefile