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.