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.

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.

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)

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.

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:

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

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

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

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

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

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!

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)