changed 410 resonance frequency back to 213th harmonic
plunger 20

center freq:

412.537 MHz

first good files in this setting are 18:16 onwards.

everything else remains same like last time.

changed 410 resonance frequency back to 212th harmonic
plunger 33

center freq:

410,600 MHz

first good files in this setting are 18:36 onwards.

everything else remains same like last time.

changed 410 resonance frequency back to plunger 8
245 MHz plunger stays at 350


center freq:
410 at 414.474 MHz
245 at 244.000 MHz

first good files in this setting are 18:51 onwards.

everything else remains same like last time.

I examined the spectrum of 194Pb at the 211 harmonic. It was observed that the peak corresponding to 194Pb82+ was mixed with signals 
from some unknown ions. Consequently, we switched to the 212 harmonic, where the frequency of 194Pb82 was measured at 410.5385024.

stop and delete NTCAP data from Weekend test

for now the NAS data2 bank has been flushed to make sure good operation for today's beam.
we have now 35 TB space on bank 2.

the recording will be done on the bank2 of the NAS.

There are still some junk data on bank1, which we will remove later.

2025-04-05 15:25
Stop the RSA02 looper script to change the settings of analysis

STOP RSA for beam tuning

A Bio-REM detector on the roof of ESR caused an alarm and shut down the whole accelerator.
Too much primary beam going to ESR, noe we avoid it by catching the primary beam at TE4 slits.
The distribution on current grids looks liek in the LISE simulation, we cut at 5mm.
The beam come sin three charge states tehouter ones 82+, 81+ anyway do not make it to ESR, we need to cut also the 80+ at least half.
Then the dose rate on ESR roof is much lower 0.8 uSv/h -> 0.2 uSv/h.

has been restored.

186Hf, 510MeV/u of 208Pb beam, ecooling not working 

At HKR, there is a Windows computer equipped with X2go software, which allows users to log in to the GPU computer. The login process is as follows: [login steps detailed below]. Once you 
have successfully logged into the GPU computer, you can run the rionid program to identify ions at HKR.

we removed the wrong entries from the PKL file, and restarted the looper script for RSA02.

important change:

nframes = 84 
lframes = 131072
navg = 4



here are the new parameters:

# Config file for the multiprocessing looper script

[paths]
monitor_dir = "/data.local/G22-00018_00203/data/analyzers/RSA02"
output_dir = "/data.local/G22-00018_00203/results/analyzers/RSA02"
state_file = "/data.local/G22-00018_00203/scripts/e0018_e0203_scripts/processed_files_rsa2.pkl"

[processing]
num_cores = 12
interval_seconds = 0.5
file_ready_seconds = 0.5

[analysis]
nframes = 84 
lframes = 131072
navg = 4
zzmin = 0
zzmax = 1e6
mask = false
dbm = false
todo = ['spectrum', 'spectrogram'] # choose any of or combination 'png', 'spectrum', 'spectrogram'

NTCAP restarted 17:43

we have 63% full on bank 2 of the NAS
which means about 11% every day
this gives us roughly another 3 days of recording time
we can always switch to bank 1, but changing that, needs changing the analysis paths. so for now, we continue on bank2

:-)

Deleted 14 TB of unused spectrum.npz files from APPC, so that there is more disk space.

switched off the production of .tiq_spectrum.npz files to save disk space in the looper script



Explanation:

.tiq_spectrogram.npz —> 3D NPZ files, that can be used for add up and create small 2D "spectrum" file for RionID

.tiq_spectrum.npz —> 2D NPZ files with super high resolution, noone needs them up to now

The pleiades detectors are now moved into a position which does not disturb the stored beam. 

inner detector: BGO
device: GE01DD2IG 
position: +20mm
scraping beam: not possible

outer detector: GAGG
device: GE01DD2AG
position: -55mm
scraping beam at: -45mm

These positions are fixed, i.e. not moving automatically.

We started moving the pleiades detectors at 16:13 04-04-2025.

We have the inside pocket (GE01DD2IG) at 2mm. 
The outside pocket (GE01DD2AG) cannot be moved by the Device Control program, some problem with the tolerance (error message: outside of tolerance). Need to go in in a short break and check what is wrong.

We will partly scrape the beam.

last file with old setting:

RSA01-2025.04.08.21.55.22.661.tiq

new plunger position 410: 13mm
new plunger position 245: 390mm

new frequency 410: 413555918
new frequency 245: 243.497403


first good file in this setting:

RSA02-2025.04.08.22.09.53.178.tiq

new settings:
1.8 seconds recording on 245 MHz on RSA02

starting from file name:

2025.04.04.18.36.32.895


settings are in the attachment

anything from RSA01-2025.04.01.02.54.25.976.tiq onwards is good data

recording parameters:

5 MHz with 6.25 MSPS, 2.5 seconds, analyzer span 100 khz, trigger at 5%

All analyzer times are now set to summer time
file time stamps are correct

settings are in the attached pictures.

NTCAP Started

RSAs started:

New plunger settings for 410 --> 20mm
frequencies: 410 -->
245 -->

recording time: 1.7s
ACQ BW--> 5 MHz
fs --> 6.25 MSPS
trigger --> 8%

lframes = 65536
nframes = 160

first good file in this setting is: 20:34 onwards

mesycontrol process starts but shows no GUI at all.

Around 02:51 we wanted to record leakage currents for PLEIADES. 
The windows of the mesycontrol were not present on the screens. 

We followed the instructions for restart:
-ssh -X into x86l-128 (-X is important, otherwise qt will not be initialized)
-mesycontrol

as a result we see nothing but the terminal is busy, and the process exists. 
We noticed that ssh connection establishes very slow, the terminal after the connection responds to typing with a delay of several seconds(one press 'm', after 1-2 sec that letter appears on 
the screen).
 
htop hanged the terminal entirely without showing a thing. Several minutes before we started htop and 12th thread(processor?) has been fully busy, 100%.

our assumption is that GUI has been closed because computer had not enough resources for sustaining it. We would not expect such a slow response even in terminal. 
Could anybody have a look on x86l-128 and figure out why is it so slow? 

UPD: started mesycontrol around 03:40, until 04:02 nothing happened except first two commands. 
Tried to start it from x86l-124 and everything works fine except that the connection to /dev/tty/USB0 can't be established (because it is occupied by x86l-128?)
So we are not able to read leakage currents. 

 

datafile = "/data.local/G22-00018_00203/results/analyzers/RSA01/RSA01-2025.03.31.22.18.16.965.tiq_spectrum.npz"
filep = "/data.local/G22-00018_00203/scripts/OnlineDataAnalysisSystem/rionid_exercises/exercise_194Pb_Exp_2025/New_TEline2022-ESR-194Pb-208Pb-nostripper_524MeV.lpp"
alphap = "1.4"
harmonics = "212"
refion = "194Pb+82"
circumference = "108.34"
mode = "Bρ"
value = "7.196596"
reload_data = true
nions = "100"

all settings are done.
any files coming after this one is good:

RSA01-2025.04.01.03.52.59.247.tiq

~ 20:00 changed E-SIS to 524.0 MeV/u to get 194Pb at the Brho of the primary beam before (=7.2008 Tm).
which corresponds to gamma = 1.400 for 194Pb82+. 
Before it was E-SIS = 480.5 MeV/u after Be-1839 mg/m^2 target Brho = 7.2014 Tm.
Keep target and beamlines and ESR the same, only SIS and TE-line before target is changed.

1. convert copy a tdms file into the folder:
(pyroot) gpuuser@appc256:/data.local/G22-00018_00203/data/ntcap/sc/SC_2025-03-28_18-48-51$ cp /mnt/ntcap-data2/G22-00018_00203/data/ntcap/sc/SC_2025-03-28_18-
48-51/0000216.sc.tdms ./
2. convert the tdms file into root file.
(pyroot) gpuuser@appc256:/data.local/G22-00018_00203/data/ntcap/sc/SC_2025-03-28_18-48-51$ /data.local/G22-
00018_00203/scripts/OnlineDataAnalysisSystem/iqt7/convert_iqt_sc -i 0000216.sc.tdms  -o ./
3. plot the result.
picture 1,2: trigger vs time
picture 3: solfware trigger vs time

new analysis settings for NPZ files:

[analysis]
nframes = 190
lframes = 65536
navg = 1


first file with this setting:

'RSA02-2025.04.07.18.57.17.454.tiq', 'RSA02-2025.04.07.18.57.02.328.tiq', 'RSA02-2025.04.07.18.58.17.958.tiq', 'RSA02-2025.04.07.18.57.40.143.tiq', 'RSA02-2025.04.07.18.58.25.520.tiq', 
'RSA02-2025.04.07.18.57.09.892.tiq', 'RSA02-2025.04.07.18.57.32.580.tiq', 'RSA02-2025.04.07.18.57.25.017.tiq', 'RSA02-2025.04.07.18.58.10.395.tiq', 'RSA02-2025.04.07.18.57.55.271.tiq', 
'RSA02-2025.04.07.18.56.54.765.tiq', 'RSA02-2025.04.07.18.58.02.833.tiq', 'RSA02-2025.04.07.18.57.47.707.tiq', 'RSA02-2025.04.07.18.56.47.202.tiq'

frequency of 194Pb82+ at 211 408606000
frequency of 194Pb82+ at 126 244001000

changed storage place to bank 1 of the NAS
restarted the NTCAP with new address
restarted Analyzers with new address
restarted the queqiao script
restarted looper scripts

new files on RSAs start from:

2025-04-07 15:23 onwards

new files on NTCAP have their corresponding time stamp on the directory

This is a preliminary result during 4:00-19:00 April 1st 2025. 
I correct the frequency drift of 194Pb82+ ions injection by injection.

I have analyzed all injection data during 4:00-19:00 and calculated the frequency of 194Pb82+ for each injection. This is the frequency of 194Pb82+ as 
a function of time. You can clearly see that the frequency of 194Pb82+ was drifted from 408.603 to 408.600 MHz. The variation of frequency is about 
3kHz.

here are all TOML config files of the automatic scripts.

From roughly 10:45 pm to 11:05 pm,  Sergey tuned the 
ion optics of the ESR to see if the mass resolution at 
413.55735 MHz improves or not. Please note that the 
frequencies of ions during the tuning process are not 
stable.

Q-magnets and S-magnets have been adjusted, see 
accelerator E-logs ID-844 titled ‘ ESR seting for 
204Pt77+’ created by Sergey.

Beam was gone at 13:04 due to fragment tuning.

410 MHz cavity resonance frequency tuned. motors both on 50 mm
245 MHz cavity resonance frequency tuned. motors both on 390 mm

This program is used to combine spectrum of many injections into one spectrum.

Example of usage:

(pyroot) gpuuser@appc256:/data.local/G22-00018_00203/scripts/OnlineDataAnalysisSystem/shift/20250331/data$ bash generate_data.sh /data.local/G22-00018_00203/results/analyzers/RSA01 RSA01- 
'*.tiq_spectrogram.npz' 2025.04.01.04.00.00.000 2025.04.01.19.00.00.000 0.001 408590000 408620000 0.3

In summary, the statistical results collected between 5:00 and 12:00 AM on April 2, 2025. For each injection, we calculate the frequency mean value 
(f_mean) and the peak height (P) of 194Pb ions for frames with t > 0.14 s, correct each injection’s frequency by subtracting f_mean, and only sum 
the 
spectra from injections with P > 100; moreover, by comparing the 194Pb82+ spectrum with that of 184Pt78+—whose isomer at 1.8 MeV (T1/2 = 1 ms) is 
clearly visible—the setup is demonstrated to be suitable for detecting an isomer with a lifetime of about 1 ms.
===================================================================
How to dod analysis and plot this result:
1. Add up injections and create accumulated spectrum.
(pyroot) gpuuser@appc256:/data.local/G22-00018_00203/scripts/OnlineDataAnalysisSystem/shift/20250331/data$ sh generate_data.sh /data.local/G22-
00018_00203/results/analyzers/RSA01 RSA01- 
'*.tiq_spectrogram.npz' 2025.04.02.05.00.00.000 2025.04.02.12.00.00.000 0.001 408.59e6 408.62e6 0.1 1

After run this command, you will create the accumulated spectrum under the folder with time stamp of start time and stop time.

2. Download the code "plot_fft.cxx" and plot the spectrum with following command:
...2025.04.02.05.00.00.000_2025.04.02.12.00.00.000$ root
   ------------------------------------------------------------------
  | Welcome to ROOT 6.32.10                        https://root.cern |
  | (c) 1995-2024, The ROOT Team; conception: R. Brun, F. Rademakers |
  | Built for linuxx8664gcc on Feb 12 2025, 01:50:41                 |
  | From tags/6-32-10@6-32-10                                        |
  | With                                                             |
  | Try '.help'/'.?', '.demo', '.license', '.credits', '.quit'/'.q'  |
   ------------------------------------------------------------------

root [0] .L plot_fft.cxx
root [1] plot_fft("2025.4.2 5:00~12:00",411.14e6,411.18e6,0,100)

The following images display the frequency spectrum at the start of every hour from 3:00 to 14:00.

this is the new setting after we lost the old one.


datafile = "/data.local/G22-00018_00203/results/analyzers/RSA01/RSA01-2025.04.01.00.55.55.572.tiq_spectrum.npz"
filep = "/data.local/G22-00018_00203/scripts/OnlineDataAnalysisSystem/rionid_exercises/exercise_194Pb_Exp_2025/New_TEline2022-ESR-194Pb-208Pb-nostripper_524MeV.lpp"
alphap = "1.399"
harmonics = "211"
refion = "194Pb+82"
circumference = "108.34"
mode = "Frequency"
value = "408637000"
reload_data = true
nions = "100"

We have the beam again the ESR since around 11:00.
The Schottky spectra look the same as before.
The ESR experts could not exactly identify the problem which caused this loss of the beam.

The beam is back. But, the experts have found a problem with one of the modules of the SIS kicker magnet. And, currently they have disabled this module. This fixed the problem. However, since the kicker system is not running with full power, it is not clear by how much this can affect the extracted beam intensity for the ESR. Therefore,  the ESR experts have been called and they will look at the injected beam intensity in the ring, in order to know if its still the same as before disabling the module. 
The experts will discuss at the upcoming meeting how to proceed with the damaged module, i.e. when to repair it.
In addition, the FRS started to take the beam now (again) which means that we will be getting less pulses from SIS as compared to the previous night.

From HKR info: there is a technical issue with SIS18 and we will have no beam for next 25 minutes. 

The repair of SIS electron cooler power supplies

In the meantime we received a few injections and confirmed that 194Pb setting is still as it was before entering into the ESR

Now we change to 208Pb82+ to do several ESR accelerator tests

Esis = 517 MeV/u
Change the beamline to 208 Pb 82+ and the ESR to 208 b 82+ and NO other changes

The (power supply of) SIS kicker magnet has been repaired and the beam has been restored from about 14:20.
But, the Schottky spectrum in the ESR looked pretty bad, so the measurement can not be restarted. 
The accelerator experts are currently looking into this problem.

The spill cycle distributions is absolutely nuts since beginning of the shift. On the positive side: we got a lot of spills since FRS did not take many, so I think we got more than our parasitic 1:10 share...

Operators seem to play with spill cycles, we get every 1:1 shot, then 1:10 again. During this, we noticed a few "empty injections" beeing triggered in the RSAs. They light up green, but spectrum is flat. Then it returns to normal operation again.

I would like to close E01 slits a bit more and get 30 min of data with higher 
resolving power.

EEX scraper from -10 now -1
E01 unchanged

Summary:

1.Simulated spectra for 194Pb and 188Hf.
2.The results are attached.
3. For the 188Hf simulation, some nuclides in the fragments are missing from the AME database, causing errors in the LiseReader program.
To fix this, please download the attached reader.py file and replace your local file at lisereader-main\lisereader\reader.py.
After replacing the file, recompile the program. Once recompiled, you should be able to simulate the 188Hf spectrum without issues.

This is sigma vs Freq plot for 188Hf72+ made out of 1hr of injections post Saturday, April 5th. 
The 2nd photo Compares the resolution of 188Hf setting by looking at peaks of 205Au and 205Pb which are very close in frequency range. The resolution in the second 188Hf72+ setting(on Right) seems much better as two peaks can be seen clearly. 

1st plot is of Sigma vs Freq for 186Hf72+ setting. The green vertical line is at 411.843MHz.
2nd plot is of Sigma vs Freq for 186Hf72+ setting from april 4th 20:00 to April 5th 09:00 with time cut 0.14, shift tracking applied and pwr-limit 100. About 5200 Injections.

1st plot is of Sigma vs Freq for 186Hf72+ setting. The green vertical line is at 411.843MHz.
2nd plot is of Sigma vs Freq for 186Hf72+ setting from April 4th 20:00 to April 5th 09:00 with time cut 0.14, shift tracking applied and pwr limit 100, about 5200 injections.( the green vertical line is at 411.843 and not at 411.7) 

We set up the Genesys. Channel map:

tr0:
IO1: Trigger MBS
IO2: Trigger NTCAP
IO3: None
IO4: Trigger RSA01
IO5: Trigger RSA02

tr1: 
None

Settings lost after the beam was lost. Trying to recover particle identification now that beam has returned.

The ntcap data record 410 detector continuously. The frame length is  26 ms/frame * 32 frames= 832 ms.

We are seeing spills being received but no peaks are seen in the analyzers. 

We are seeing several intermittent losses of beam. Awaiting action to see if it stabilizes.


23.51 Beam is back and we see the nice spectrum in the analyzer.

Screenshots of RSAs showing acquisition settings, for documentation, they show the time / date on the bottom left, in case needed for data analysis.

screenshots of Lassie

The peaks in the analyzer are slowly shifting back to the original position. 
Note that a quadrupole was the cause of the issue 45 mins ago and it was cycled.  Might be relevant...

Stable since last entry

Screenshots before opening ESR.

Lassie exports from the last morning shift + screenshot of Schottky TV after the last injection from SIS

Beam is back for 10 mins-

The peaks on the analyzer appear shifted to the right.

As I write this the beam disappeared again.... 02.59

and back again at 03.08

Lassie screen shots 186Hf

Settings similar to the 2-photon experiment.

Central frequency: 411.742243 MHz (based on Ruijius identification for 188Hf72+)

Beam is back with some fluctuations.
We did not have beam from 9:34 until 10:08, around 35 minutes. 

Starting at around 04:09 we don't see anything on RSAs. RSAs are still triggering and writing files, but only see noise. Lassie indicates beam current in the ESR

We called HKR, they said they will investigate, awaiting response.


last file that contains data: RSA01-2025.04.02.04.09.27.044.tiq_spectrogram.npz
file from which only noise is contained: RSA01-2025.04.02.04.09.31.905.tiq_spectrogram.npz 

At 04:09: drop of beam in the SIS as shown in screenshots.


For a minute there were still good data. Files from:
RSA01-2025.04.02.04.13.44.629.tiq_spectrogram.npz
to:
RSA01-2025.04.02.04.14.47.805.tiq_spectrogram.npz



05:30 update from HKR: There is a problem with the ESR main power supply. We have to wait.

RSAs had to stop because the cycle of 1.8 came too often, both analyzers could not catch up with the file transfer.


changed to 1.7 seconds

last file in the 1.8 setting:

RSA01-2025.04.05.18.20.46.005
RSA02-2025.04.05.18.20.43.346


new filenames from the 1.7 s settings:

RSA01-2025.04.05.18.28.12.146.tiq

new analysis settings:

[analysis]
nframes = 80
lframes = 131072
avg = 4




Explanation:

every file has 10625050 samples with 1.7 seconds length
sampling rate: 6.25 MSPS
this means every sample is worth: 1.6e-7 seconds
this means every frame with length of 2^17 samples will have a time length of: 21 ms
finally with an averaging of 4 frames into one, this means that every time frame in the NPZ file will have 80ms length



frequency setting

please see attached pictures.

first file name RSA01....17.38 onwards.

Since there will be no beam for about one hour, the data taking in RSAs has been stopped.

Started both RSAs for the tuning of the ESR to 188Hf. Both pockets are in parking position OUTSIDE.

The `queqiao` program used for RSA data analysis is located at:
  
  (pyroot) gpuuser@appc256:/data.local/G22-00018_00203/scripts/OnlineDataAnalysisSystem_rsa/queqiao

It is currently running in the screen session named:

  OnlineDataAnalysisSystem_rsa

1. Login the server gpuuser@appc256

2. Reattach to the session, use:

  screen -rd OnlineDataAnalysisSystem_rsa

3. Run the program manually, activate the pyroot environment and execute the following command:

  queqiao ../parameters/queqiaosettings_194Pb_rsa.toml

4. Then press "start" botton, the `queqiao` program copies data from:

  /mnt/ntcap-data2/G22-00018_00203/data/analyzers/RSA01
  /mnt/ntcap-data2/G22-00018_00203/data/analyzers/RSA02

to:

  /data.local/G22-00018_00203/data/analyzers/RSA01
  /data.local/G22-00018_00203/data/analyzers/RSA02

HKR has called someone to fix the quadrupole, they think it will take about an hour.

Attached are the proposals submitted to and approved by G-PAC.

Since around 01:45 we get spills but see nothing on analysers. HKR says there is a problem with one of the quadrupoles; they are working on it.

20:48: Inside pocket moved to 60mm and back to the outside position.

We started playing with the detector pockets of the pleiades arrays at 14:23 01.04.2025.

This might disturb the beam sometimes.

The beam is lost in SIS at 14:35. 

Beam came back at 16:40, we continued playing with pleiades positions until 17:14.

the ACC pattern for both experiments.

PLEIADES shift instructions available at:
https://docs.google.com/document/d/19b4wyugC3OpVAjwt1ONM9u8EYdMJsBpL7GVNzoziv0M/edit?usp=sharing

Leakage current tracking:
https://docs.google.com/spreadsheets/d/1Gt1tFHwn4XFrJ5_-nQvTi635UD0aHgN6gCdXDTHQdkI/edit?gid=299353113#gid=299353113

Leakage currents should be documented every ~1-2 hours while the detectors are biased.

Leakage currents were steadily increasing in the PLEIADES detectors so we decided to stop taking data, move both the detectors back and turn off bias.

12:23 moved PLEIADES inside detector in to 2mm.

17:12 We moved the PLEIADES detector out, both are outside now (in parking position)

11:37 Outside particle detector (GE01DD2AG) moved in to -100mm to take data

datafile = "/data.local/G22-00018_00203/results/analyzers/RSA01/RSA01-2025.04.01.14.13.07.068.tiq_spectrum.npz"
filep = "/data.local/G22-00018_00203/scripts/OnlineDataAnalysisSystem/rionid_exercises/exercise_194Pb_Exp_2025/New_TEline2022-ESR-194Pb-208Pb-nostripper_524MeV.lpp"
alphap = "1.399"
harmonics = "211"
refion = "194Pb+82"
circumference = "108.34"
mode = "Frequency"
value = "408602000"
reload_data = true
nions = "100"

Code used to add up injection data.
(pyroot) gpuuser@appc256:/data.local/G22-00018_00203/scripts/OnlineDataAnalysisSystem/shift/20250331/data/2025.04.04.13.00$ find /data.local/G22-00018_00203/results/analyzers/RSA01 -name "RSA01-2025.04.04.*.tiq_spectrogram.npz" > filelist.txt
(pyroot) gpuuser@appc256:/data.local/G22-00018_00203/scripts/OnlineDataAnalysisSystem/shift/20250331/data/summed_spectrum$ python npz_addup.py --time-cut 0.14 filelist.txt

continuing PID with better / higher resolution:

RSA01-2025.03.31.21.10.54.758.tiq_spectrum.npz
...
RSA01-2025.03.31.21.12.29.106.tiq_spectrum.npz

trying to do PID....

trying to do PID with some injections:

RSAs are still on winter time. they show summer time but files have winter time.

data used for PID is range from:

RSA01-2025.03.31.20.21.13.217.tiq_spectrum.npz
...
RSA01-2025.03.31.20.53.06.492.tiq_spectrum.npz

gamma_t = 1.4

but files are not so good.

We tried to convince the outside pocket to move, no success. We can hear the "hissing sound" of the pressurized air but no movement. Sergey tried to move it from the HKR, also no success. After that I tried to move it again from the Messhuette...and the "Out of tolerance" error message is gone, and the pocket seems to move. (We cannot confirm from inside because the ESR is already closed).
Guess the outside pocket got intimidated by Sergey and decided to get moving again... ;-)

We will take a bit more beam once the setting is stable, but try not to fry another detector.

19:20 The outside and inside PLEIADES detectors are both moved back into their parking positions. Shifts should continue monitoring the leakage current on the mesycontrol screens and enter the values every 2h in the Google spreadsheet:
https://elog.gsi.de/esr/Beavertail/34

12:00 Outside particle detector moved out to parking position again (-125 mm)

Estimation of potential gain by changing. Files from this points are going to rubbish. Potential gains are c. 20% 

22:04: The current acquisition window is recording for 2.9 s. And is not recording for 3.9 s. We are running currently with a spill cycle of 5s every repetition.

22:22 The spill cycle between each injection was changed to 4->3->2s progressively and FRS also stopped taking spills so we settled on 2s spill request.

In the morning the spill request has to be changed back to 5s when the FRS goes back into operation.

new file with the setting is

RSA01-2025.04.01.22.19.06.761.tiq

[analysis]
nframes = 190
lframes = 65536
navg = 1

Night shift starts with no injections from SIS! We still have triggers; we called HKR and are waiting for response.

The SIS kicker has failed again.

Since few minutes do not see any beam in the ESR (on RSAs). There is beam in SIS and injection requests from the ESR seem to be there as well.

There is no beam in the ESR since couple of minutes. According to the info from HKR, the experts started to repair the magnets (power supplies) used for extraction and transfer of the beam from SIS to ESR. It is estimated to take about 1 hour.

The SIS kicker has failed again at 08:01.
Since this has happened already few times, the experts from the on-call duty service are now looking at the problem.

Beam resumed at 16:40. 

New settings for resonators:

410: plunger stay the same
center: 411.756955 MHz


245: plunger now at 150
center: 245.507668 MHz


first files on the resonators:


RSA01-2025.04.05.18.09.08.519.tiq
RSA02-2025.04.05.18.09.09.618.tiq

new DAQ Settings for the RSAs:

414475588 （192Pb+82   at 214 harmonic）
244.03689

plunger settings: 410 MHz cavity--> 8
245MHz cavity --> 350


recording at 50 MSPS
2^16 points each frame -->  1ms per frame

Average set to: 5 frames --> total of ca. 6.5 ms per average frame

first good NPZ file from this settings on RSAs starts from 17:41

NTCAP was stopped and restarted.

NTCAP restarted with new timestamp.

The NTCAP computer and crate are switched off.
The triggers are disconnected from the RSAs, but they remain on.

NTCAP Has been restarted (we restart every day around 15:00 so data goes in a new folder)

Since there are many NPZ summer scripts around, I thought I would also share mine. This one takes advantage of the power of filelists and has a progress bar. Creating file lists gives you more control over the range of analyzed data, for example, the command:

find /data.local/G22-00018_00203/results/analyzers/RSA02 -name "RSA02-2025.04.04.01.??.??.???.tiq_spectrogram.npz" > filelist.txt

makes a file list of everything file that was produced during the second hour of the morning of the April 4th. You can fine tune the wildcards according to the time range you are interested in.


then just call the script by:

python npz_addup.py filelist.txt

you can also provide time cuts, like this:

python npz_addup.py --time-cut 0.14 filelist.txt

which will cut away first 0.14 seconds of the spectrogram. Without time cuts, it will do over the whole range.


It creates 4 type of files:

summed_spectrum.npz --> for use with RionID for PID
summed_spectrogram.npz --> for general use / analysis
summed_spectrum.png --> for general view
summed_spectrogram.png --> for detailed view

if time-cut is provided, the filenames will have a "_time_cut" suffix at the end.


Here is the link to the script:

https://github.com/xaratustrah/e0018_e0203_scripts/blob/main/npz_addup.py

examples are in attachment:

9:53 Data taking with outside detector (GE01DD2AG) moved in to -110mm

17:35 Slowly moving PLEIADES outside detector (GE01DD2AG) in for some data. Clipping ions at -20mm. Leaving detector at -40mm for a few minutes.

14:12 We are moving the inside pocket out for a moment, change the bias

14:57 We are moving the inside pocket detector in again, this time to 20mm

The inner PLEIADES is moved into position close to the beam.
Device control for the outside pocket is not currently working so that pocket remains in its outward position.

NTCAP/Schottky data acquisition stopped during pocket position tests.

Inner detector (x86l-124 BGO)
Device: GE01DD2IG
Position: +20 mm
Scraping beam: not possible

Outer detector (x86l-131 GAGG)
Device: GE01DD2AG
Position: -127 mm
Scraping beam: 

17:08 Tried to move outside particle detector (GE01DD2AG) in - it is stuck again :-(
17:18 Sergey tried to move it, now it moves again. Moved to -100 mm.
17:30 Moved detector to outside parking position

10:16 Moved outside particle detector back into parking position (-126mm)

From roughly … to 0:05AM, Sergey moved GEEXDS1HA (not 
changed 
in the end) and GE01DS3HG (changed from -85 to -80 mm) to reduce 
the acceptance of the ESR to improve the mass resolution.

After the change, there are less small traces appearing in the 
413.55735 MHz +/-5 kHz range. 

The final positions of the two scrapers are 
GEEXDS1HA :-10 mm; GE01DS3HG:-80 mm.

more screen shots of RSAs.

Beam was lost from 00:44 until 00:59

Looks a bit more regular now (FRS people having dinner???)

Screeeeeeeenshooooots!

FRS started taking beam from 6:00 Am

After a ~ two minute outage of the "ESR via TE (FAST)" beam at 07:48 the particles dropped by half. See screenshot 2025-04-05_08-01-34-267.png

186Hf screen shots with better resolution

We managed to take some screenshots while Shahab harrassed us with AI-created "RammstAIn" music... happy to end my shift now!

The beam is gone in ESR via TE (FAST) and also in SIS18_RING (FAST) starting from 07.51 am until 07.59 am.

New sextupole settings at 13.45.
The beam will be stopped at 14.10 until around 7 pm.

(Who let the dog out?)
Sharing with FRS 6:1 since a while now.

First a setting with orbit bump for injection on central orbit was tried.
- quadrupoles tuned and scrapers optimized

Then back to an ESR setting without this bump like last year.
- again quadrupoles tuned and scrapers optimized
This gave a good resolution in which the isomer should be resolved.

Just after this was achieved all resolution was lost.
Making the input for ESR setting again recovered it, now with slightly different scrapers.

Quads: K'L Q3D / Q6D = -0.3603263
Sext: K''L GE01KS2 = -0.14
           GE01KS3 =  0.05

scrapers: GEEXDS1HA =  -5 mm
          GE01DS3HG = -70 mm 

Details see paper scans below.

We are inserting both PLEIADES detectors step-wise, one by one. Main beam should not be affected too long.

step by step pictures:

sometimes the name of the motor connection is not available in the menu, it should be added manually.

Add MBOX:

put some name, like "410 MHz Schottky Cavity in ESR"
put the IP address: 140.181.139.194

press connect

change to local control

press initialize

go to motor drive

go to motor 1 and 2

always move same value for both motors.

Currently, we only use 37% of the injections in our data analysis. However, 63% of the injections have a height below 100, and these may include 
single ion injections. We need to visually inspect these injections to identify the single ion injections.

We have not seen 184Hf and 186Hf so far. 

After the beam  was restored at 07:25, we think that the frequency peak in the 244 MHz RSA2 has jumped again (closer to the center). 
Previous to that, during the longer break in the previous night, the peak jumped to higher frequencies.

We had stopped the RSAs at 8:00 (call for restart)
Time stamp computer stopped and started at 9:35

The a final injection from SIS18 stored at 10:04.
The scrapers were moved out before to get the maximum intensity.
NTCAP is still running, the RSAs recorded the last files at 10:04.
The plan is to keep running like this for about an hour.

> The a final injection from SIS18 stored at 10:04.
> The scrapers were moved out before to get the maximum intensity.
> NTCAP is still running, the RSAs recorded the last files at 10:04.
> The plan is to keep running like this for about an hour.

Beam stopped at 10:58.
NTCAP and RSAs are stopped.

The PLEIADES team (pocket detectors) has discussed with Wolfram to get access to the ESR tomorrow (Thu) morning ~8:00 to check their detectors and install a dry N2 flow connection. This might take about 1h. Iris (or Jan) will call the HKR to get the RP shift for the transport of the N2 bottle into the ESR. Morning shift will be informed accordingly when we are onsite, just keep running (keep running...keep running...keep running) until we get access.

From 14:15, we have every injection to the ESR. FRS is on pause for 1-2 hours.

We are going to enter the ESR to check on the PLEIADES pocket detectors and install a nitrogen cooling.

At 10:45 we will enter the ESR and install a remote oscilloscope for the PLEIADES outside detector. Should take only 10 "GSI" minutes ;-)
After that, ESR tuning to 192Pb can start.

Since the FRS started to take the beam again, the ESR gets 1/10 shots from SIS. But, the ESR seems to request about twice more frequently the beam from SIS which means that every second shot in the ESR is empty (it contains the remaining beam from the previous injection). This also applies to the data stored by RSAs because they also (seem to) trigger each time the ESR requests the beam.

Regina, Jan, and Markus are in the ESR to check the electron cooler.

Electron cooler anode voltage needs a repair which might take 20-30 mins. If it takes longer, we'll proceed without a cooler curve measurement. 

No additional HV. So, have to proceed without the cooler. 
Spare Power supply did not work either, we will not be able to use the cooler for the rest of the experiment

ESR setting is changed from 188Hf72+ to 186Hf72+. SIS-18 beam energy for the primary beam transmission check is 528 MeV/u.

the new scraper setting for good isochronicity but still acceptable intensity losses is:
Done at ~ 15:00 today.
GEEXDS1HA (outside)          =  -8 mm
GEEXDS1HG (ToF-det-aperture) =  20.5 mm
GE01DS3HG                    = -84.2 mm  (fully open is -130 mm)
in addition, a detector pocket is in GE01DD2IG = 1.7 mm

7:05 ESR not requesting new pulses from the SIS. 
Operators are trying to fix the problem.

7:20 eam is back

At around 9:40, ESR timeout changed from 10 s to 30 s
Triggering only on real injections.
Before that, every second injection was not real but the old one. They can be identified since they should have no "kicker" disturbance.

Today, until 11 am, data were taken for the 188Hf setting. Since then, we are now tuning on the 192Pb82+.

All data acquisitions (both RSAs and NTCAP) are now running.

NTCAP and analysers are stopped at 17:00.Iris goes inside to move the detectors 

20:28 started NTCAP
started queqiao file transfer for RSAs only
started analyzer looper for RSAs

 

We will need to enter the ESR to connect the cables again for our DAQ and then drive in the outside detector for 20min to get some data.
9:35 entered
9:41 exit
9:44 ESR available again

Before changing we check how much we cut with the ESR scrapers
two lines
208Pb80+ with slits intensity 15 arb u
204Hg78+ ... 0.055

Now, slits fully open


208Pb80+ with slits intensity 127 arb u
204Hg78+ ... 0.25

Increase compared to 188Hf measurement:
208Pb80+  increase of factor 8.5
204Hg78+  increase of factor 14

Acquisition stopped at 20:36. 

First file from this setting: RSA01-2025.04.01.03.52.59.247.tiq

Last file from this setting: RSA01-2025.04.01.20.36.54.257.tiq

acq. length changed to 500 ms

acq bw changed to 50 MHz

==> 12 MSamples

Trigger window condition set to 50%.

First file from this setting: RSA01-2025.04.01.20.45.40.053.tiq

Analysis setting the the frame length 2^16 and frame number = 190.

> Acquisition stopped at 20:36. 
> 
> First file from this setting: RSA01-2025.04.01.03.52.59.247.tiq
> 
> Last file from this setting: RSA01-2025.04.01.20.36.54.257.tiq
> 
> acq. length changed to 500 ms
> 
> acq bw changed to 50 MHz
> 
> ==> 12 MSamples
> 
> Trigger window condition set to 50%.
> 
> First file from this setting: RSA01-2025.04.01.20.45.40.053.tiq
> 
> Analysis setting the the frame length 2^16 and frame number = 190.

Last file from previous setting: RSA01-2025.04.01.21.06.30.580.tiq

Changed the RSA01,02 to 50 MSamples/s (20nsec/sample) for 500.00 ms acq. length, 25 MHz acq. BW, 33% trigger position.

First good file from this time: 21:37 04.01.2025 -- RSA01-2025.04.01.21.37.13.721.tiq

23:55 stop the RSAs. 

410:
last file from previous setting (harmonic=211): 2025.04.01.23.55.21.712.
new plunger position for 410 cavity: 33.5 inside and outside.
new center frequency: 410535000 Hz.

245:
harmonic didn't change, still 126.
adjusted center frequency to 243997000 Hz.

00:31 restart the RSAs.
new files from: 2025.04.02.00.31.11.796.

There was no beam from SIS between about 06:28 and 06:39.

Again from 07:02 to 07:11.

And again from 07:49 to 07:55.

We stop taking beam at 10:47 for tuning a new setting. 

Team PLEIADES is wanting to get access for 10 mins to install a remote oscilloscope, so entry to the ESR has been requested. 

The beam was stopped for the evaluation accelerator tour. RSAs and NTCAP stopped now.

Beam stopped due to device trouble.

Beam sharing with FRS is now 1 to 1.

Now we have every injection.

again, ESR : FRS = 1 : 1

Beam was returned to the ESR at 05:11.

HKR said there had been some problem with one of the dipoles and in order to restore it a power supply had to be reset, which took some time.

05:41 data are back in the RSAs. Files that contain data from:
RSA01-2025.04.02.05.41.14.938.tiq_spectrogram.npz
to:
RSA01-2025.04.02.06.24.01.530.tiq_spectrogram.npz


06:24 data not visible again, only noise.

06:43 data are ack in the RSAs. Files that contain data from:
RSA01-2025.04.02.06.43.43.580.tiq_spectrogram.npz

Spike in beam intensity at 06:27 (5x usual intensity) and then beam is lost. HKR says it's a problem with the magnet's power supply. Once the beam returned, the peaks are shifted to the left but are slowly shifting back into position.

HKR just called to say a power supply to the SIS18 extraction kicker has failed.
The service person has been called and is expected to take ~1h to arrive and approx. ~2h to carry out the repair.

02:44 beam is back

Beam is gone since 7:02. Control room is notified. Beam is back since 7:14. FRS started taking spills.

The SIS operator says that FRS doesn't need beam now, ESR will receive the full SIS beam extraction every 3 secs overnight. All the secondary beams are injected into ESR from now on.

7:29, beam gone again, operators say they need another 5 minutes.

Beam is gone since 10:45.
According to the main control room there is a problem in SIS18. They are looking into the problem.

Beam gone again between 01:14 and 01:18, then again at 01:19. HKR says there are problems with the source.

No beam from 19:57:41.

> No beam from 19:57:41.

Beam back from 20:02

> > No beam from 19:57:41.
> 
> Beam back from 20:02

beam is back, we started DAQ again. All files created after 15:45 should be good from now on.

07:20  we have beam back.

The beam is back as before since 11:02.

Beam is back now.

Intensity dropped a lot, ion source fix ongoing
ESR access for 5-10 mins to restart PLEIADES DAQ
FRS has also taken beam again, so ESR is sharing

08:55: ESR closed and takes beam again

still can not see both 186Hf72+ and 184Hf71+

Until now, there is no 184Hf72+ and 186Hf72+ ions. 

I added automatic shift tracking and a check for a minimum wanted power in that bin to Shahab's npz_addup.py script.
It looks for the highest bin in the projected spectrum (so after time-cut) and tracks it position. Careful, it uses the position in the very first FILE as reference. So, the ordering in the given file list affects this.

Here's Shahab's log entry about the initial script:
https://elog.gsi.de/esr/E0203_E0018/137

Created pull request in Shahabs repo:
https://github.com/xaratustrah/e0018_e0203_scripts/pull/1

Before that is accepted, find the script here:
https://github.com/mijja-koeln/e0018_e0203_scripts/blob/main/npz_addup.py


New command line options are:
  -h, --help            show this help message and exit
  -t TIME_CUT, --time-cut TIME_CUT
                        Start time as a float (optional)
  -s, --shift-track     Enable shift tracking based on strongest peak in spectrum (optional)
  -l PWR_LIMIT, --pwr-limit PWR_LIMIT
                        Set minimum power required to process file (optional)
  -v, --verbose         Print additional information (optional)


"-s" enables shift tracking and correction.

"-l" enables power limit / threshold. Only files with at least this power in the highest bin are used for summation.

"-v" prints infos abuot the tracking in each file. Optional, if you want to see how good it works.

The --time-cut option is applied in all scenarios, i.e. also before projection used for tracking.

Have fun!

This shows the spectrum of 188Hf72+ during "April06_01:00_02:00". Until April 6 2:00, the Bp = 7.918262 Tm has not been changed. 
The ntcap spectrum is from:
/data.local/G22-00018_00203/results/ntcap/iq/IQ_2025-04-05_17-43-49/0000756.iq.tdms.root


analysis settings:

2^18 samples per frame + average over 32 frame.
26.21 ms per frame
838.86 ms for 32 averaged frames

Now ESR is set to the 188Hf72+ setting.

The 188Hf72+ setting measurement starts now. Exactly the same setting like two days ago.

Tuning is finished, 186Hf is running. Sharp peaks now.

DAQ stopped with last file in RSA1-2025.04.04.17.58.49.340.tiq

Now the plan is to change one of the analyzers to narrow band recording for longer from the 245 Schotkky. 

We have been working together with IT on the speed of data transfer: with the new 10 GB interface we can now transfer data from NAS to Lustre with 400MB/s. From NAS to GPU Computer up to 700MB/s. All cables around the rack are now 10GB capable.

ESR setting is changed from 188Hf72+ to 186Hf72+. SIS-18 beam energy for 
this fragment is 510 MeV/u.Brho = 7.86166 Tm.