The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000761
 p:\E143\iq\IQ_2021-06-30_23-27-34\0003720
2. The rest space on the drive "p:\" : 20,3 TByte

Injection was optimized before with Cu-40 mg/cm^2 stripper.
This reduces energy of 78Kr from 370 MeV/u -> 386.52 MeV/u.
To keep the same ESR injetion the SIS energy was raised with Be 10mm tatget.
For exactly 1850 mg/cm^2 a SIS-energy of 445.46 MeV/u would be needed. A scan of SIS energy resulted in 445.0 MeV/u as optimal.
This means target thickness is close to 1850 mg/cm^2, we can call it 1839 mg/cm^2.

With closed scrapers there are only a few weak lines.
Open temporarily all scrapers in the ESR to write down the frequencies. 

Settings don't look the same...so we are not yet writing files unless sure.

After looking at the spectrum it was concluded that the same isotopes, and no more, could be identified. 
Now we change the energy back to 441.7 MeV/u and will open the scrappers to see if Mn comes in. 

The picture shows the effect of going back to the previous energy and then the effect of opening the scrappers

We think we see the frequency range of A/q=2.25 at 243.1 MHz.
This would correspond to L=108.2m and E=386.4 MeV/u (gamma_t = 1.3955) at h = 126.
Path length is a bit short, for L=108.4m it should be 370.6 MeV/u. 
(later reanalysis shows the measured frequency corresponds to 108.38m, which is like expected)

We closed scrapers on arc outside and straight section outside to limit Brho from both sides.
GE02DS3HG = -35mm, GEEXDS2AH = -25mm

Expected frequencies see below:

a reference schematic of the peaks on 410 MHz (211th harmonic) and 245 MHz (126th harmonic)

Some plots of statistics up to now

In compliment to Liliana's plots, this is the summed spectra I calculated from 0338 to 0507.

(See
https://triumfoffice365-my.sharepoint.com/:w:/g/personal/dillmann_triumf_ca/Eb_LCp7yTx5Bgc8TO8khJmEBWeS-ycdPRnG02wQout-fgQ?rtime=3n3A3xMR2Ug
for remote shifter instructions. To be updated/corrected by the experts)

08:00 Analysed data from 6 am to 7 am  (Note file names are one hour behind).
Using e143_analyzer.py -t 0.5 E143-245MHz-2021.05.07.05.*
See attachments 1,2,3

08:17 Analysed data from 7am to 8am (Note file names are still one hour behind)
As above.
See attachments 4,5,6

Analysed data from 8am to 9am (Note file names are still one hour behind)
As above.
See attachment 7

At 8:50 Yury changes trigger on scope from 50% to 1% (minimum value).
We should now have the beginning of the injection as well, and isomers should appear at 0.1 s

9:35 Lost beam from SIS

09:45 Analysed data from 9am to 9:30 am (Note file names are still one hour behind)
These are the first data with the new trigger settings
As above
See attachment 8

11:50 Beam is back, scraper being optimised.
12:30 Scraper optimisation complete.

13:00 Analysed data from 12:30 to 12:45 roughly.
Attach 9 - default code. -t 0.5
Attach 10 - new untested code with skip function. See Slack#analysis. -t 0.5 -s 0.2
Attach 11 - as 10, log scale on the y

13:48 Analysed data from to 12:30 to 13:35
-t 0.5 Attach 12
-t 1 Attach 13 (log y) 

14:05 Lost beam in ESR

14:30 Analysed data from 13:00 to 14:00 before we lost beam.
-t 0.2 -s 0.1
Attach 13 & 14

14:35 Beam is back 

15:00 Shift handed over to AG and CJC

some pics.

(Jelena has analysed these data files)

E143_245MHz_2021.05.08.00* (-s 5.0 -t 0.5)  (2021.05.08.09.01.11.png)

E143_245MHz_2021.05.08.01* (-s 5.0 -t 0.5)  (2021.05.08.08.56.05.png)

E143_245MHz_2021.05.08.02* (-s 5.0 -t 0.5)  (2021.05.08.08.44.10.png)

E143_245MHz_2021.05.08.03* (-s 5.0 -t 0.5)  (2021.05.08.08.33.46.png)

E143_245MHz_2021.05.08.04* (-s 5.0 -t 0.5)  (2021.05.08.08.26.49.png)  

E143_245MHz_2021.05.08.05* (-s 5.0 -t 0.5)  (2021.05.08.07.58.22.png)

E143_245MHz_2021.05.08.06* (-s 5.0 -t 0.5)  (2021.05.08.08.12.14.png)

E143_245MHz_2021.05.08.07* (-s 5.0 -t 0.5)  (2021.05.08.09.12.53.png)

-------------------------------------------------------------------------

E143_410MHz_2021.05.08.00* (-s 5.0 -t 0.5)  (2021.05.08.10.20.39.png)

E143_410MHz_2021.05.08.01* (-s 5.0 -t 0.5)  (2021.05.08.10.16.46.png)

E143_410MHz_2021.05.08.02* (-s 5.0 -t 0.5)  (2021.05.08.10.13.09.png)

E143_410MHz_2021.05.08.03* (-s 5.0 -t 0.5)  (2021.05.08.10.07.05.png)

E143_410MHz_2021.05.08.04* (-s 5.0 -t 0.5)  (2021.05.08.10.04.05.png)

E143_410MHz_2021.05.08.05* (-s 5.0 -t 0.5)  (2021.05.08.09.51.12.png)

E143_410MHz_2021.05.08.06* (-s 5.0 -t 0.5)  (2021.05.08.09.45.12.png)

E143_410MHz_2021.05.08.07* (-s 5.0 -t 0.5)  (2021.05.08.09.38.33.png)

This might have been answered before but I looked at one png file and one tiq file from the same run that was stored on the server. There seems to be an offset of 2.2 s. The png file from the server (right) shows the injection at ~5s, whereas when I look at the tiq file in the GUI (left), the injection is at ~2.8 s???? Is the looper introducing this offset?

This is due to the 50% trigger setting in the spectrum analyzers ))

Attached is a summed spectra of all files taken between 1:17am and 1:59am (on the 245 MHz detector).

python3 e143_analyzer.py -s 5.1 -t 0.5 /home/dillmann/E143/e143-scripts/sparc-daq-02.gsi.de/E143-245MHz/E143-245MHz-2021.05.09.01.* -o Not_52Mn_245MHz_May09_1-2am
(Might need to adapt the skip time and read-in time, thou... used the same as for the 72Ge runs...)

Summed up runs on the 245 MHz detector between 2-3am (computer time).
One has -s 0.1 -t 8.0
the other -s 5.1 -t 0.5

Not sure if it is useful but here it is :-)

Summed up runs on the 245 MHz detector between 3-4am (computer time).
-s 0.1 -t 8.0

For the whole morning shift there were no significant changes in the spectra.

Some of the obtained histograms are attached below. 
The python code was used and the histogram was plotted in ROOT with log y scale. 
The time, the used code options and the data type are marked in the filenames or in the description below. 

Attachment 1-4: 245MHz, options used " -s 5.1 -t 0.5 ", time marked in the filename (time as in the title of the files on the server (-1h of the real time)).

Attachment 5: 410MHz, with the same options for the python code, real time names. It is different from 245MHz histogram.
Attachment 6: Comparison between 245MHz histogram and 410MHz histogram for real time 10:00 - 11:00.
Note: This difference is observed in the histograms from the early morning hours too (checked up to 4 o'clock).

Attachment 7: 245MHz data, with options "-s 5.0 (Red) / -s 5.05 (Green) / -5.1 (Blue) -t 0.5" (real time 08:00 - 09:00)
Attachment 8: 245MHz data, with options "-s 5.0 (Red) / -s 5.05 (Green) / -5.1 (Blue) -t 0.1" (real time 08:00 - 09:00)
Attachment 9: 410MHz data, with options "-s 5.0 (Red) / -s 5.05 (Green) / -5.1 (Blue) -t 0.5" (real time 08:00 - 09:00)

Following Xiangcheng Chen's analysis, I analysed 11 ms time slices separated by 25 ms to see the evolution of the potential isomer across the injection.

Attachment 1: Data from May 7th 19h-20h. -t 11ms progression from -s=5 to -s=5.175
Attachment 2: Data from May 8th 21h-22h. -t 11ms progression from -s=5 to -s=5.175

The extra resolution gained on the 8th (and potentially other settings too) make the isomer visible where it wasn't present on the 7th.