We have switched off all 3 PMTs  !

Since yesterday, channel 0 of the CAEN PS is dead (no voltage even without cable).
Changed detector south to channel 3.

We tested the PMTs again, this time with an UV LED that is mounted at a window close to the XUV detector.
PMT south showed a very clear increase in count rate from about 1 to 50 Hz.
PMT mid also showed a small increase by a few Hz.
For PMT north there was no great change between LED off and on, but we think that the count rate also very slightly increased. Note, that PMT north is also the furthest away from the LED.

Also we saw a difference between single- and multi-photon events at PMT south.

current settings of PMT voltages and thresholds at the CAEN CFD:

PMT South   [HV ch2: 2700V]  [CFD ch0: 8]

PMT Middle  [HV ch1: 2850V]  [CFD ch1: 8]

PMT Nord    [HV ch3: 2850V]  [CFD ch2: 9]

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

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

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
    

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

In the SetParameters.C file is a parameter called fPar->piPhaseOffset. It was shifted from 100 to 50 in order to see ion bunches in the pmt signal and laser pulses in the photodiode signal during the same revolution in the TDC spectrum. Note that this parameter must be taken 
into account when setting the window conditions of the arrival time in the SetConditions.C file. 

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. 

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

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