We believe to have identified the 237U92+ and the 229Th89+ peaks. 

Using the Schottky resonator at about 244 MHz and taking the 123rd harmonic: 
The Schottky peak of 237U92+ should be at 242.7975 MHz and the one of 229Th89+ at 242.8494 MHz. 
The peaks should be ~52 kHz apart.

We have used:  
gamma_t	= 2.355 
alpha_p = 0.18 

For PID with rionid we used: 
- LISE file from last year (attached.
- .npz file from 410 RSA (attached).

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

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

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

We recognized that the output power of the pump laser was instable when externally triggered with 200kHz (stand-bye frequency of ESR). Therefore, we changed the coarse timing offset of the pockels cell trigger compared to the flash lamp pulse from 215µs to 219.9µs. 
Thereby, the output power increased from ~600mJ to 620mJ, and the PTP stability improved from 15% to 10%. The RMS stability improved from 2% to 1.2 %. With these settings we had UV pulse energies of 20mJ.

• 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.
  

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

The metadata provided by Medusa (Labview channels in former times) are now labelled correctly in Go4. 
Most important data are "Cobra Set WL", "WS7 Meas WL", "PTB U scal", "Ohmlabs U scal", which correspond to the set wavelength, measured wavelength, voltage measured at the PTB divider, and voltage measured at the Ohmlabs divider.
Other channels are mostly for debugging purposes.

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
    

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

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