We stopped the beam at 08:10

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

Here's a list of the spectra to look at for the potential isomer, taken btw 21:00 on July 2nd and 6:30 on July 3rd. Two examples attached.

Name	Comment
410MHz-2021.07.02.21.18.54.456.tiq	
410MHz-2021.07.02.21.27.19.948.tiq	slightly different freq
410MHz-2021.07.02.21.33.07.438.tiq	
410MHz-2021.07.02.21.42.36.139.tiq	slightly different freq
410MHz-2021.07.02.21.52.04.801.tiq	
410MHz-2021.07.02.22.03.37.550.tiq	appears at ~3.5s
410MHz-2021.07.02.22.12.31.601.tiq	slightly different freq
410MHz-2021.07.02.22.30.24.641.tiq	slightly different freq
410MHz-2021.07.02.22.40.24.894.tiq	triplet
410MHz-2021.07.02.23.04.38.838.tiq	
410MHz-2021.07.03.01.00.29.856.tiq	slightly different freq
410MHz-2021.07.03.01.29.59.709.tiq	slightly different freq
410MHz-2021.07.03.01.45.47.532.tiq	
410MHz-2021.07.03.01.47.22.303.tiq	a bit more shifted to the left
410MHz-2021.07.03.01.54.44.606.tiq	
410MHz-2021.07.03.02.14.45.610.tiq	a bit more shifted to the left
410MHz-2021.07.03.02.28.58.637.tiq	slightly different freq
410MHz-2021.07.03.02.55.49.838.tiq	a bit more shifted to the left
410MHz-2021.07.03.03.15.50.713.tiq	a bit more shifted to the left
410MHz-2021.07.03.03.55.52.357.tiq	slightly different freq
410MHz-2021.07.03.03.56.55.568.tiq	a bit more shifted to the left
	
410MHz-2021.07.03.01.11.33.702.tiq	
410MHz-2021.07.03.01.20.31.004.tiq	
410MHz-2021.07.03.00.07.18.136.tiq	
410MHz-2021.07.03.00.42.04.236.tiq	
410MHz-2021.07.03.00.45.45.337.tiq	
410MHz-2021.07.03.04.22.44.303.tiq	
410MHz-2021.07.03.04.26.25.486.tiq	
410MHz-2021.07.03.04.45.54.495.tiq	
410MHz-2021.07.03.04.49.35.705.tiq	
	
410MHz-2021.07.03.05.25.24.517.tiq	
410MHz-2021.07.03.05.58.03.370.tiq	
	
410MHz-2021.07.03.06.19.07.475.tiq	

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

> After looking through >800 shots from Jul 2nd 21h to Jul 3rd 05h, we couldn't find a single example of a "smoking gun" isomer decay. I.e. I'm talking about the examples Liliana posted earlier. We did find many examples (roughly 10%) where the ion track spontaneously 
> disappeared, but this shouldn't be the isomer as there was no frequency shift.
> 
> We did, as Iris mentioned, observe some line "in-between" the broad peak unique to the 410MHz, and listed them here (https://triumfoffice365-my.sharepoint.com/:x:/g/personal/dillmann_triumf_ca/EdKsMfSC3AlHopA36PdLBlsBE2MCSY0hh5qIsuau5HFBmg?rtime=Z2os4J492Ug).
> I then proceeded to sum these files to see if they lined up. The result it attached, with the previous total sum from 21-00h Jul 2nd at the bottom for comparison. It seems the 70Se line has shifted, this is observed in the other shots too. However, despite the low 
> statistics, these other shots don't line up with the broad peak identified before, although they don't line up well with each other individually either.
> In either case, we think these files might be worth offline analysis as they're the only possible hint of the 70Se isomer so far.

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

Attached is an example for the possible isomer (on the left) next to the 70Se (right). 

Here's the list with the files to look at, btw 21:00-6:30. Further analysis needs to be done offline. The slight frequency shift overnight made it a bit harder to see, unfortunately.

Name	Comment
410MHz-2021.07.02.21.18.54.456.tiq	
410MHz-2021.07.02.21.27.19.948.tiq	slightly different freq
410MHz-2021.07.02.21.33.07.438.tiq	
410MHz-2021.07.02.21.42.36.139.tiq	slightly different freq
410MHz-2021.07.02.21.52.04.801.tiq	
410MHz-2021.07.02.22.03.37.550.tiq	appears at ~3.5s
410MHz-2021.07.02.22.12.31.601.tiq	slightly different freq
410MHz-2021.07.02.22.30.24.641.tiq	slightly different freq
410MHz-2021.07.02.22.40.24.894.tiq	triplet
410MHz-2021.07.02.23.04.38.838.tiq	
410MHz-2021.07.03.01.00.29.856.tiq	slightly different freq
410MHz-2021.07.03.01.29.59.709.tiq	slightly different freq
410MHz-2021.07.03.01.45.47.532.tiq	
410MHz-2021.07.03.01.47.22.303.tiq	a bit more shifted to the left
410MHz-2021.07.03.01.54.44.606.tiq	
410MHz-2021.07.03.02.14.45.610.tiq	a bit more shifted to the left
410MHz-2021.07.03.02.28.58.637.tiq	slightly different freq
410MHz-2021.07.03.02.55.49.838.tiq	a bit more shifted to the left
410MHz-2021.07.03.03.15.50.713.tiq	a bit more shifted to the left
410MHz-2021.07.03.03.55.52.357.tiq	slightly different freq
410MHz-2021.07.03.03.56.55.568.tiq	a bit more shifted to the left
	
410MHz-2021.07.03.01.11.33.702.tiq	
410MHz-2021.07.03.01.20.31.004.tiq	
410MHz-2021.07.03.00.07.18.136.tiq	
410MHz-2021.07.03.00.42.04.236.tiq	
410MHz-2021.07.03.00.45.45.337.tiq	
410MHz-2021.07.03.04.22.44.303.tiq	
410MHz-2021.07.03.04.26.25.486.tiq	
410MHz-2021.07.03.04.45.54.495.tiq	
410MHz-2021.07.03.04.49.35.705.tiq	
	
410MHz-2021.07.03.05.25.24.517.tiq	
410MHz-2021.07.03.05.58.03.370.tiq	
410MHz-2021.07.03.06.19.07.475.tiq	

After looking through >800 shots from Jul 2nd 21h to Jul 3rd 05h, we couldn't find a single example of a "smoking gun" isomer decay. I.e. I'm talking about the examples Liliana posted earlier. We did find many examples (roughly 10%) where the ion track spontaneously 
disappeared, but this shouldn't be the isomer as there was no frequency shift.

We did, as Iris mentioned, observe some line "in-between" the broad peak unique to the 410MHz, and listed them here (https://triumfoffice365-my.sharepoint.com/:x:/g/personal/dillmann_triumf_ca/EdKsMfSC3AlHopA36PdLBlsBE2MCSY0hh5qIsuau5HFBmg?rtime=Z2os4J492Ug).
I then proceeded to sum these files to see if they lined up. The result it attached, with the previous total sum from 21-00h Jul 2nd at the bottom for comparison. It seems the 70Se line has shifted, this is observed in the other shots too. However, despite the low 
statistics, these other shots don't line up with the broad peak identified before, although they don't line up well with each other individually either.
In either case, we think these files might be worth offline analysis as they're the only possible hint of the 70Se isomer so far.

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

Looks like the beam is slightly drifting...the 70Se peak frequency is slightly shifted to the left, by ~0.5 kHz compared to earlier spectra. Might be a problem with the analyzer (?) or the storage ring energy (slightly lower?)... nothing drastical but to be observed.

To summarise the method of bulk summing the spectra, I've created frequency vs time spectra by using the e143_analyser.py script to stack a series of -s slices. I applied it to some of last runs data with 72Ge, to the 72Br data, last night's less-scraped 70Se, and tonight's more-scraped 70Se, respectively.

A few comments: the 72Ge isomer trail is obvious, but I would never have found it in this total sum if I didn't know where to look. I had to turn up the contrast a lot before it was visible. The 72Br isomer is less obvious than in the single particle tracks, but it too is obvious. You can see that the peak is wider to left at the injection, and 
then narrows out as the isomer decays. This is what we would see if the two peak weren't well resolved.
With that in mind, the 70Se data is challenging. We've established the broad peak is not the isomer as it is not present in the 245MHz detector., and the many single lines seen in the well-scraped data correspond in frequency exactly to this broad band. The 70Se peak doesn't get broader at the base at injection like 72Br, and there isn't any 
line visible in the sum in between. I was nervous that the contrast might be the problem like with 72Ge, but I turned up the contrast on the less-scraped data, but no signal emerged.

So I conclude that if the 70Se isomer is to be found, it needs to be done on a shot-by-shot basis with comparison to the sum to see if it matches the intruder broad peak.

Attached are some single spectra with a rough attempt to group them according to the different ions that appear.

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000707
 p:\E143\iq\IQ_2021-06-30_23-27-34\0003452
2. The rest space on the drive "p:\" : 21,4 TByte

Here's a picture with all injections with an ion in the spectrum (empty ones were removed- list below). The time slices are 0-0.5-1-1.5-2s, then in 0.2s steps up to 3s. Not really anything to see :-(  The previous shift was right, looking at single spectra might be more useful. I'll group the pictures and upload some "interesting" ones.


Here is the list of spectra btw 21-23:59 which we have removed since they were empty or had just an ion on the far left side:

Name	
410MHz-2021.07.02.22.00.29.051.tiq	
410MHz-2021.07.02.22.02.03.277.tiq	
410MHz-2021.07.02.22.05.11.820.tiq	one line far left
410MHz-2021.07.02.22.10.57.361.tiq	
410MHz-2021.07.02.22.12.00.189.tiq	
410MHz-2021.07.02.22.16.11.439.tiq	possible weak at beginning, up to 2.5s, tbd
410MHz-2021.07.02.22.16.42.837.tiq	
410MHz-2021.07.02.22.17.14.236.tiq	
410MHz-2021.07.02.22.18.17.037.tiq	possible weak at beginning, up to 2.5s, tbd
410MHz-2021.07.02.22.18.48.439.tiq	
410MHz-2021.07.02.22.22.55.403.tiq	
410MHz-2021.07.02.22.23.26.786.tiq	
410MHz-2021.07.02.22.28.48.088.tiq	
410MHz-2021.07.02.22.35.40.568.tiq	
410MHz-2021.07.02.22.36.12.157.tiq	weak on left?
410MHz-2021.07.02.22.36.43.749.tiq	
410MHz-2021.07.02.22.37.15.343.tiq	
410MHz-2021.07.02.22.37.46.933.tiq	
410MHz-2021.07.02.22.45.40.791.tiq	
410MHz-2021.07.02.22.52.31.388.tiq	
410MHz-2021.07.02.22.53.02.969.tiq	
410MHz-2021.07.02.22.56.44.073.tiq	
410MHz-2021.07.02.22.31.59.417.tiq	possible weak at beginning, up to 2.5s, tbd
410MHz-2021.07.02.22.49.21.896.tiq	possible weak at beginning, up to 2.5s, tbd
	
	
410MHz-2021.07.02.21.00.28.254.tiq	
410MHz-2021.07.02.21.04.09.536.tiq	
410MHz-2021.07.02.21.04.41.147.tiq	
410MHz-2021.07.02.21.12.03.629.tiq	
410MHz-2021.07.02.21.14.10.043.tiq	
410MHz-2021.07.02.21.16.16.423.tiq	
410MHz-2021.07.02.21.16.48.033.tiq	
410MHz-2021.07.02.21.17.19.643.tiq	
410MHz-2021.07.02.21.17.51.252.tiq	
410MHz-2021.07.02.21.19.57.661.tiq	
410MHz-2021.07.02.21.20.29.255.tiq	
410MHz-2021.07.02.21.23.07.234.tiq	
410MHz-2021.07.02.21.26.48.358.tiq	
410MHz-2021.07.02.21.28.23.122.tiq	only peak on left
410MHz-2021.07.02.21.29.57.884.tiq	
410MHz-2021.07.02.21.30.29.475.tiq	
410MHz-2021.07.02.21.34.42.242.tiq	
410MHz-2021.07.02.21.43.39.320.tiq	
410MHz-2021.07.02.21.44.42.497.tiq	
410MHz-2021.07.02.21.46.48.867.tiq	
410MHz-2021.07.02.21.47.20.469.tiq	
410MHz-2021.07.02.21.49.58.434.tiq	maybe something on the left
410MHz-2021.07.02.21.51.33.210.tiq	
410MHz-2021.07.02.21.53.07.993.tiq	
410MHz-2021.07.02.21.53.39.589.tiq	only peak on left
410MHz-2021.07.02.21.54.12.383.tiq	
410MHz-2021.07.02.21.56.17.947.tiq	
410MHz-2021.07.02.21.57.52.120.tiq	
410MHz-2021.07.02.21.59.57.662.tiq	
	
	
410MHz-2021.07.02.23.04.07.211.tiq	
410MHz-2021.07.02.23.06.45.360.tiq	
410MHz-2021.07.02.23.07.16.983.tiq	
410MHz-2021.07.02.23.13.04.692.tiq	
410MHz-2021.07.02.23.14.07.894.tiq	
410MHz-2021.07.02.23.20.26.941.tiq	possible line at beginning
410MHz-2021.07.02.23.22.33.289.tiq	
410MHz-2021.07.02.23.24.39.645.tiq	possible line at beginning
410MHz-2021.07.02.23.25.42.835.tiq	
410MHz-2021.07.02.23.27.17.623.tiq	
410MHz-2021.07.02.23.27.49.229.tiq	
410MHz-2021.07.02.23.28.20.832.tiq	
410MHz-2021.07.02.23.28.52.428.tiq	
410MHz-2021.07.02.23.29.24.021.tiq	
410MHz-2021.07.02.23.29.55.608.tiq	
410MHz-2021.07.02.23.33.36.787.tiq	
410MHz-2021.07.02.23.35.11.557.tiq	
410MHz-2021.07.02.23.37.17.912.tiq	weak line at beginning
410MHz-2021.07.02.23.42.02.249.tiq	
410MHz-2021.07.02.23.46.46.400.tiq	weak line on the left
410MHz-2021.07.02.23.47.17.981.tiq	
410MHz-2021.07.02.23.48.21.143.tiq	
410MHz-2021.07.02.23.48.52.727.tiq	
410MHz-2021.07.02.23.53.36.878.tiq	
410MHz-2021.07.02.23.55.43.122.tiq	
410MHz-2021.07.02.23.56.14.685.tiq	
410MHz-2021.07.02.23.59.55.607.tiq	

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000680
 p:\E143\iq\IQ_2021-06-30_23-27-34\0003322
2. The rest space on the drive "p:\" : 21,9 TByte

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

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000627
 p:\E143\iq\IQ_2021-06-30_23-27-34\0003062
2. The rest space on the drive "p:\" : 22,9 TByte

We tune back to 70Se.
The scrapers stay closed at EEXDS2HA=0 mm, EEXDS1HG=+5 mm
"Single"-particle run

At 19:56 the DAQ is stopped. 
The plan is to go back to the setting for Se. 
Last files for the Br setting:
- 410MHz-2021.07.02.19.57.36.721.tiq
-245MHz-2021.07.02.19.58.03.216.tiq

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000600
 p:\E143\iq\IQ_2021-06-30_23-27-34\0002931
2. The rest space on the drive "p:\" : 23,4 TByte

at 17:20 intensity was suddenly reduced. 
Operators checked. Intensity was a bit low and fluctuating for a while (8e8 to 1e9)
Intensity (1.5e9) was recovered at 18:16

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000577
 p:\E143\iq\IQ_2021-06-30_23-27-34\0002818
2. The rest space on the drive "p:\" : 23,8TByte

Starting 15:15
The scrapers are moved very much close to each other to eliminate all background particles and leaving basically single ions injected for 72Br. Do not wonder, this means that also many empty files are created.
Scrapers:
E02DS3HG -> -40 mm
EEXDS1HG -> +5 mm
EEXDS2HA -> 0.0 mm

One sees probably a decay of 100 keV isomer, see the attached figure at about 18 s
We will run a few hours with this setting

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000543
 p:\E143\iq\IQ_2021-06-30_23-27-34\0002655
2. The rest space on the drive "p:\" : 24,5TByte

Both resonators will now be retuned to look for the isomeric state in 72Br.

Last files for 70Se are:
245MHz-2021.07.02.14.17.14.507.tiq
410MHz-2021.07.02.14.16.48.528.tiq

Up to now, attempts to cool the fat line between Se and Ar were conducted. We give up it now and remove cooling

Last files with the measurement time of 10s for the two resonators are:

245MHz-2021.07.02.13.36.00.674.tiq
410MHz-2021.07.02.13.35.34.758.tiq

12:46 moved the TOF detector scraper back to -11 mm

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000515
 p:\E143\iq\IQ_2021-06-30_23-27-34\0002516
2. The rest space on the drive "p:\" : 25,0TByte

0.1s time slices for 245MHz and 410MHz, with e143_analyzer.py script

python $AnalyzerPath -s 0.$start -t 0.$time sparc-daq-02.gsi.de/E143-245MHz/245MHz-2021.07.02.$hour.* -o t_0.$start-0.$stop

Sergey Litvinov will now try to setup the e-cooler to cool the beam in the ESR. 
The data taking has been stopped (except the NTCAP).

We close the arc inside and straight section inside scrapers to narrow and cut the 70Se line.
Then look what the other lines left of 70Se will do.

1st series with E01DS_HI
 -58  - intensity as before
 -52  - still as before
 -50  - still full
 -45  - less intensity but about same width
 -40  - almost gone 
   0  - gone
 -58  - back to old position

2nd series with EEXDS1HG
 16.0 - full
 15.0 - full
 12.5 - less
 10.5 - less intensity
  9.7 - appears only sometimes
  8.2 - gone
 10.8 - middle intensity and more narrow, measure for a while

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000485
 p:\E143\iq\IQ_2021-06-30_23-27-34\0002370
2. The rest space on the drive "p:\" : 25,6TByte

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000459
 p:\E143\iq\IQ_2021-06-30_23-27-34\0002242
2. The rest space on the drive "p:\" : 26,1TByte

Using the scripts I posted previously, I summed 5.5 hours of data from midnight to 5:30 July 2nd CEST. 
I used 10ms time steps for better time resolution, but that did leave questionable frequency resolution. If anyone would like to see higher resolved frequency plots for the 
full 5 hours, let me know.
I've attached the spectra from 0s to 4s  for the 410MHz and 0s to 2s for the 245MHz, including zooming in on the injection timing. 

Given that we are summing 5 hours of data so the background is very smooth, I can only conclude that either the isomer doesn't exit, we cannot resolve it, or we are 
producing incredibly low amounts such that the search needs to be needle in a haystack. 

Same as before but for 0-6h, 25ms time slices starting at 1.04s.

> Same as before for 4-5h and 5-6h.
> No isomer, I think :-( (Sorry, Wolfram!)
> 
> > Same as before for 0-4h on July 2nd.
> > 
> > > Same as before, for 0-1h on July 2nd
> > > 
> > > 
> > > > The last hour before the gas bottle change is summarized here. 
> > > > The first pic shows the 410 MHz spectra taken from 22-23h on the 410 MHz analyzer, in time slices of 0.1 sec from 0s-2s.
> > > > The second pic shows the spectra in 20ms slices from 1s-1.16s.
> > > > 
> > > > python3 e143_analyzer.py -s 1.0 -t 0.02 /home/dillmann/.../sparc-daq-02.gsi.de/E143-410MHz/410MHz-2021.07.01.22*
> > > > 
> > > > The third spectra was taken in May, for comparison.
> > > > 
> > > > I don't think we see anything...

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000431
 p:\E143\iq\IQ_2021-06-30_23-27-34\0002106
2. The rest space on the drive "p:\" : 26.6TByte

Same as before for 4-5h and 5-6h.
No isomer, I think :-( (Sorry, Wolfram!)

> Same as before for 0-4h on July 2nd.
> 
> > Same as before, for 0-1h on July 2nd
> > 
> > 
> > > The last hour before the gas bottle change is summarized here. 
> > > The first pic shows the 410 MHz spectra taken from 22-23h on the 410 MHz analyzer, in time slices of 0.1 sec from 0s-2s.
> > > The second pic shows the spectra in 20ms slices from 1s-1.16s.
> > > 
> > > python3 e143_analyzer.py -s 1.0 -t 0.02 /home/dillmann/.../sparc-daq-02.gsi.de/E143-410MHz/410MHz-2021.07.01.22*
> > > 
> > > The third spectra was taken in May, for comparison.
> > > 
> > > I don't think we see anything...

I've written two scripts that others might find useful for the on-line analysis. 
  1. The first is a simple bash script that runs a for loop to run the e143_analyzer.py script for a sequence of start values (-s). You'll need to change the increment and 
start/end of the for loop to set the time resolution.
  2. The second is a root script that takes the above generated scripts, reads the histograms, and then fills a 2D histogram. You'll need to adjust the TH2 bin number to 
match both the bin number of the TH1s and the number of analysed files. I've included a print line to help identify the TH1 bin number.

To see the first results, I've attached a sum of July 1st 22-23h data. Sadly, I don't see any indication of the isomer, or at least the production is very low.

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000405
 p:\E143\iq\IQ_2021-06-30_23-27-34\0001978
2. The rest space on the drive "p:\" : 27.1TByte

Same as before for 0-4h on July 2nd.

> Same as before, for 0-1h on July 2nd
> 
> 
> > The last hour before the gas bottle change is summarized here. 
> > The first pic shows the 410 MHz spectra taken from 22-23h on the 410 MHz analyzer, in time slices of 0.1 sec from 0s-2s.
> > The second pic shows the spectra in 20ms slices from 1s-1.16s.
> > 
> > python3 e143_analyzer.py -s 1.0 -t 0.02 /home/dillmann/.../sparc-daq-02.gsi.de/E143-410MHz/410MHz-2021.07.01.22*
> > 
> > The third spectra was taken in May, for comparison.
> > 
> > I don't think we see anything...

And the intensity is back again to 5E9 at 03:20

We see that intensity stabalized at 9E8 which is smaller then before. 
We neticed this at 2:50, keep observing.

Same as before, for 0-1h on July 2nd


> The last hour before the gas bottle change is summarized here. 
> The first pic shows the 410 MHz spectra taken from 22-23h on the 410 MHz analyzer, in time slices of 0.1 sec from 0s-2s.
> The second pic shows the spectra in 20ms slices from 1s-1.16s.
> 
> python3 e143_analyzer.py -s 1.0 -t 0.02 /home/dillmann/.../sparc-daq-02.gsi.de/E143-410MHz/410MHz-2021.07.01.22*
> 
> The third spectra was taken in May, for comparison.
> 
> I don't think we see anything...

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000360
 p:\E143\iq\IQ_2021-06-30_23-27-34\0001759
2. The rest space on the drive "p:\" : 28TByte

We see a drop in beam intensity from 7E9 to 2E8 between 01:30 and 01:43

The last hour before the gas bottle change is summarized here. 
The first pic shows the 410 MHz spectra taken from 22-23h on the 410 MHz analyzer, in time slices of 0.1 sec from 0s-2s.
The second pic shows the spectra in 20ms slices from 1s-1.16s.

python3 e143_analyzer.py -s 1.0 -t 0.02 /home/dillmann/.../sparc-daq-02.gsi.de/E143-410MHz/410MHz-2021.07.01.22*

The third spectra was taken in May, for comparison.

I don't think we see anything...

The first good spectra after the gas bottle change is from 23:38:25 (on the 410 MHz Analyzer) 

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000338
 p:\E143\iq\IQ_2021-06-30_23-27-34\0001651
2. The rest space on the drive "p:\" : 28,4TByte

No, everything okay! Must have had a very good earlier run to compare.

> Looks like there is a bit less beam now in the ring. I just looked at one spectra from before the gas bottle change and after...

Looks like there is a bit less beam now in the ring. I just looked at one spectra from before the gas bottle change and after...

The gas bottle has been changed and the beam is back.

The change of the source happens now

increase factor 4 in power for 410 



before:

410MHz-2021.07.01.18.48.07.516.tiq.png


after:

410MHz-2021.07.01.19.23.49.099.tiq.png

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000299
 p:\E143\iq\IQ_2021-06-30_23-27-34\0001462
2. The rest space on the drive "p:\" : 29,1TByte

15dB amplifier on 410MHz 

Checking if signal can be further amplified 

Last files:
245MHz 2021.07.01.20.36.11.218
410MHz 2021.07.01.20.35.46.847

increase factor 4 in power for 410 



before:

410MHz-2021.07.01.18.48.07.516.tiq.png


after:

410MHz-2021.07.01.19.23.49.099.tiq.png

410 MHz resolution and power optimised


Last files before the restart were
245Mhz-2021.07.01.18.48.31.725.tiq
410MHz-2021.07.01.18.48.07.516.tiq

DAQs and NTCAP

The latest recorded tdms files:
 p:\E143\sc\SC_2021-06-30_23-27-45\0000267
 p:\E143\iq\IQ_2021-06-30_23-27-34\0001305
2. The rest space on the drive "p:\" : 29,8TByte

Change the triggers to 10%. Last files with 50/50:
410MhZ 2021-.07.01.17.56.12.936
245MhZ 2021.07.01.18.02.16.938 

> The freqency suddenly shifted at time 16:11:47 and remained shifted until now 
> 
> The ESR status in the monitor stayed blue. No obvious sign that a magnet was down. The operators are checking
> 
> Sergey telephoned, he is also not sure but suggests stopping starting the ESR. We will wait for Yuri

In attachment, the moment when the shift occurred. 

The freqency suddenly shifted at time 16:11:47 and remained shifted until now 

The ESR status in the monitor stayed blue. No obvious sign that a magnet was down. The operators are checking

Sergey telephoned, he is also not sure but suggests stopping starting the ESR. We will wait for Yuri

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

Please check following two parameters every two hours into make sure the NTCAP is running well: 
1. The latest recorded tdms files:
 p:\E143\sc\**\**
 p:\E143\iq\**\**
2. The rest space on the drive "p:\" : **GByte.

So far only scrapers for low Brho were used:
  GE01DS_HI = -58mm (arc from inside) and
  GEEXDS2HA = -11.2 (straight from outside)
We also want a cut on high Brho to avoid possible strange lines.

GE01DS_HA is limited in motion, at the maximum inside position (0.0 mm) there is no effect.

Next EEXDS1HG (aperture for ToF-detctor) in mm
120 -  completely out
 60 - no effect full beam
 45 -   "
 30 -   "
 20 -   "
 10 - very little beam remaining
  5 - gone
 12 - little beam
 14 - narow but little
 16 - narrow with small tail in left side
 20 - again like full
100 - full (as reference for the eye)

Then similar with E02DSHG in arc dipole in mm
 -130 - full
  -60 - full
  -40 - gone
  -45 - very tiny
  -55 - full
  -50 - less beam
  -52 - similar
  -53 - no difference
  -58 - looks like full

Now add EEXDS1HG again with -16mm, no difference, so keep both in.
==> we cut in arc from both sides and on straight secton from both sides
    Intensity does not look different to scrapers out. 
    It looks like a bit less 70Se in ESR then 1h before, but maybe other reason.

Intensity went up from 5e8 to 1e9 extracted particles from SIS.

From 4:05 to 4:15 beam intensity was 1/2 as before. 

Changing ion source, no beam expected for the next 30 minutes.

2:15--> Beam is back, intensity not as high as before but will increase in the next few minutes as the source gets hotter.

For few minutes (starting at 00:05) beam intensity went down. Same as it was reported by the previous shift. 
Until 00:27 beam had lower intensity than before (3e8) 
Now intensity is back to 5e8.

reference level=-20 dBm.
p:\E143\sc\SC_2021-6-30_23_27_45
p:\E143\iq\IQ_2021-6-30_23_27_34

There was a disruption from the SIS side for a few minutes.

SIS intensity is back

There is a drop in SIS intensity and the operators are informed.

current scraper positions suggested by Sergey:

GEEXDS2HA = -11mm
GE01DS-H (innen) = -58mm

Data is being shared on the WWW server.
Time difference between the analyzers is in order of seconds:

time stamp of the 245MHz data is leading those of 410MHz by 21.733 [s]

Main user is finished. We started data taking again...

We just started data taking. But a few minutes later the main experiment needed to do some adjustements to the beam. This interrupts us for a couple of minutes...

After setting up on 70Se
Sextupoles were adjusted to optimize the resolution of the 70Se peak. Set values are in the ESR logbook.
The SIS energy was shifted up to increase the number of 70Se.
Esis original = 445.68 MeV/u
Esis now = 451.68 MeV/u (+6 MeV/u)

See attached pictures

scrapers: 
GE01DS_HI =  -58mm
GE01DS_HA = +130mm (fully open)
GEEXDD2_S = -0.5mm
GEEXDS2HA = -11.2mm

This is the latest ID of 70Se setting.

turned on extra 20dB amplifier for the 245 Resonator around 12:32 

SC_2021-06-30_12_35_52
IQ_2021-06-30_12_35_43
Reference level=-20dBm

SC_2021-06-30_11-00-12
IQ_2021-06-30_11-00-12
reference level -80dBm.
Amplifier is off.

1) Over night the source was conservated. It is being restarted now.
2) The approximated amount of Gas in this bottle shall allow for running until tomorrow morning (~24 h). There is still another bottle in reserve (1 l) and one reserve from GANIL (0.5 l).
3) Beam-time coordinator suggests to run until the gas is over, i.e., up into the weekend.

X(9Be)=1.815 g/cm2 (adjusted in primary beam setting)

Gamma_t=1.3956
E(70Se)=368.499 MeV/u
Br(70Se)=6.21993 Tm

Pre-drilling:
E(78Kr)@Br(70Se)=337.461 MeV/u
E(SIS) = 415.792 MeV/u

Fragment Setting:
E(SIS) = 445.68 MeV/u

still no beam in ESR: quadrupole magnets are down

This is an old spectrum which was recoded on May.

cooling water in UNILAC is out

moving in the plungers:

before: 400
after: 200

the new setting is roughly 400 khz lower in frequency.
Previous beam time Ge was on 243.100 now it is on 242.74

we decided to use the higher harmonic:

expecting it on 244.66 MHz

Carrier Frequency:245MHz.
IQ rate 20MSamples/s
Reference level:-90 dBm
SC_2021-06-29_20-38-27
IQ_2021-06-29_20-38-27

After optimisation of sextupoles we found a scraper position which makes a narrow peak and keeps 20% of the injected beam.
  GEEXDS2HA = +2.0 mm (out is +130mm)
  GE01DS_HI = -75 mm  (out is -130mm)
removed scrapers again for predrilling.

We agree on gamma_t = 1.3956, E/m = 368.50 MeV/u.
Then for 78Kr at Brho = 6.79675 Tm of isoc 72Ge 
E-SIS = 466.63 MeV/u, assume target of 1815 mg/cm² Be
after target E/m = 393.024 MeV/u
In ESR-Modi set for same E/m but different m/q (m=72, Z=q=32)

Injection looks good like before with isochronous 78Kr we go directly to the next step
72Ge with E-SIS = 440.16 MeV/u to get 72Ge at gamma_t.

Variation of quadrupole E01QS03D to change gamma_t in isoc. mode
measured with 78Kr at 368.5 MeV/u on 28.06.2021 evening.
The shape of the three curves looks very similar they would only require a different beam velocity.
But I suppose we stay with the value close to the old one (gamma_t ~ 1.3956).

Attached are two files with a proposed particle identification.
Different colors indicate different harmonic numbers

This is just a Brho selection by the ESR based on SIS-energy used, 
energy-loss in target with calibrated thickness and momentum spread by the reaction (Goldhaber formula).
Production cross sections are by EPAX 3.1

The beam was stopped at about 08:40.

Same as before for 5-6 am.
Peak still there, maybe a bit less than before.


> Same as before but for 4-5am on 410 MHz detector. Peak visible.
> 
> 
> > Same as before, but for 410 MHz detectors.
> > Peaks visible in the 3rd-5th slice.
> > 
> > 
> > > > 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.
> > > 
> > > Hi, attached is the sum of all spectra from 1-2am on May 10th, on the 245 MHz detector. Takes me forever to download everything...
> > > I used the same parameters as Guy and Xiancheng: LFRAMES = 512 (in analyzer); -t 0.011 (= 11 ms) -s 5 ... 5.175 s.
> > > 
> > > Resolution looks good... :-)

going back to shot by shot recording with 410 detector

Same as before but for 4-5am on 410 MHz detector. Peak visible.


> Same as before, but for 410 MHz detectors.
> Peaks visible in the 3rd-5th slice.
> 
> 
> > > 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.
> > 
> > Hi, attached is the sum of all spectra from 1-2am on May 10th, on the 245 MHz detector. Takes me forever to download everything...
> > I used the same parameters as Guy and Xiancheng: LFRAMES = 512 (in analyzer); -t 0.011 (= 11 ms) -s 5 ... 5.175 s.
> > 
> > Resolution looks good... :-)

doing some broadband spectra recording with the 410 MHz detector, for the purpose of future confirmation of identification lines.

Same as before, but for 410 MHz detectors.
Peaks visible in the 3rd-5th slice.


> > 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.
> 
> Hi, attached is the sum of all spectra from 1-2am on May 10th, on the 245 MHz detector. Takes me forever to download everything...
> I used the same parameters as Guy and Xiancheng: LFRAMES = 512 (in analyzer); -t 0.011 (= 11 ms) -s 5 ... 5.175 s.
> 
> Resolution looks good... :-)

> 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.

Hi, attached is the sum of all spectra from 1-2am on May 10th, on the 245 MHz detector. Takes me forever to download everything...
I used the same parameters as Guy and Xiancheng: LFRAMES = 512 (in analyzer); -t 0.011 (= 11 ms) -s 5 ... 5.175 s.

Resolution looks good... :-)

They are not easy to find, but we do occasionally see what might be the isomer.

How things look currently in Zoom-world.

The issue has been resolved and the beam is back since 00:56.

The beam was lost in SIS about 5 mins ago due to the failure of HF cavities. Operators are trying to solve the problem.

Beam gone ~0:34.
Working on getting it back.
Back in business ~0:57.

Start a new run. The data of new run is in :
SC_2021-05-10_00-08-08
IQ_2021-05-10_00-08-08

Start a new run. The data of new run is in :
SC_2021-05-09_23-56-42
IQ_2021-05-09_23-56-42

Start a new run. The data of new run is in :
reference level = -50dBm.
SC_2021-05-09_23-43-37
IQ_2021-05-09_23-43-37

Here are parammodi saves for TE-line and ESR for all four fragment settings:
For the first run of 72Ge (7.May) I do not have files.

2021-05-09_11-22-51_SIS18_FAST_20210506_ESR_78KR32.C1.txt:# Context: SIS18_FAST_20210506_ESR_78KR32.C1 E143 52Mn
2021-05-09_11-23-12_ESR_EXP21_06_ISO_78Kr_05May21.C1.txt:# Context: ESR_EXP21_06_ISO_78Kr_05May21.C1 E143 52Mn
2021-05-09_15-46-52_ESR_EXP21_06_ISO_78Kr_05May21.C1.txt:# Context: ESR_EXP21_06_ISO_78Kr_05May21.C1 E143 52Mn-2
2021-05-09_15-47-16_SIS18_FAST_20210506_ESR_78KR32.C1.txt:# Context: SIS18_FAST_20210506_ESR_78KR32.C1 E143 52Mn-2
2021-05-09_19-43-28_ESR_EXP21_06_ISO_78Kr_05May21.C1.txt:# Context: ESR_EXP21_06_ISO_78Kr_05May21.C1 E143 70Se
2021-05-09_19-43-45_SIS18_FAST_20210506_ESR_78KR32.C1.txt:# Context: SIS18_FAST_20210506_ESR_78KR32.C1 E143 70Se
2021-05-09_22-23-23_ESR_EXP21_06_ISO_78Kr_05May21.C1.txt:# Context: ESR_EXP21_06_ISO_78Kr_05May21.C1 E143 72Ge
2021-05-09_22-23-37_SIS18_FAST_20210506_ESR_78KR32.C1.txt:# Context: SIS18_FAST_20210506_ESR_78KR32.C1 E143 72Ge

starting filenames:

E143-410MHz-2021.05.09.23.28.24.018.tiq

E143-245MHz-2021.05.09.22.28.12.904.tiq

We tried the scrapers a bit, because right of peak some background appeared.

The GE01DS_HI shows a strange effect,
normal -65mm gives good resolution, -30mm kills the beam, but even more in at -15 there is beam again.
We suppose the scraper is not massive but has an empty space behind it.
GE01DS_HA has no effect even at +0V.
Therefore, put I to -100mm and also use GE01DS3HG (from outside),set to -55mm.
Then also the straight section EEXDS2HA from + 8mm to +10mm (a bit more closed).

we change back to 72Ge
just change SIS-energy       E = 441.0 MeV/u
beamline energy after target E = 392.9 MeV/u
set ESR to A=72, Z=32 (72Ge)
--> good injection and resolution in ESR, at old frequencies

We see a very strong line at the left end of spectrum, stronger than all other lines.
When we shift the target TE3UF_H from -35mm to -37mm it gete weaker, but -37mm is the end of drive.
In the other direction it becomes worse. At -25mm completely new peaks.
Also scan in Y direction TE3UF_V +25mm and +40mm give other fragments even very intense, while the old lines vanish.
So production happens in target frame. 
Use -37mm, +37mm as best target position.

We run with TCap only for some time hoping there is somewhere a peak of 70Se
running from about 9:15 to about 22:00
We set scrapers in the previous optimum position

still in the search of 70-Se

This some preliminary analysis results by using  NTCAP data.   The IQ rate of NTCAP is 20 MSamples/seconds. I analyzed data files recorded from May 7 
17:39 to May 8 2:20.  The frequency of 72Ge is bended by 4kHz at the beginning of some injections.  In order to check whether this frequency bending is 
due to isomer or unstable magnetic field. I compare the 72Ge with other isotopes. The similar bending was observed for other isotope in each 
corresponding injections. It seems that bend is due to unstable magnetic field.  

18:45  changed SIS, ESR setting for 70Se without predrilling blind change.
E-SIS =  446.55 MeV/u, is centerd as before on TE3UF target grid.
set beamline after taret as 78Kr 36+ E = 337.375 MeV/u
set ESR to A = 70, Z=34 at isochronous E/m + 0.8 MeV/u = 369.2 MeV/u
kicker delay unchanged

4 quadrupoles failed during the change, skip cycle and reset, they work again, (GE01QS0D, GE01QS1F, GE01QS2F, GE01QS4F)

Now many lines in Schottky.

also 2 corrector coils were off, on again, now good resolution.

last recorded filename:

E143-245MHz-2021.05.09.17.38.44.410.tiq

410 was not recording data in this period.

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.

first filename in this recording:

E143-245MHz-2021.05.09.15.16.49.816.tiq

We accept larger m/q values than we like to. m/q(low) cut ~ 2.08. Decrease ESR energy from 369.2 -> 368.4 MeV/u
frequencies shifted by -37.5 kHz (at 60 MHz)

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

Beam energy to be increase to move Mn into the ring. 
First step we set the energy to 445 MeV. 
The effect of the change can be seen on the plot: Right is how it was before and left after the change. 

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)

So far, we keep the setting as it is and wait for experts to come in. 
Few spills are missing from time to time. One of the peaks stays usually in the spectrum when this happens. 
Analysis of the last hours is being performed by the remote shift, in case it is useful. Some plots in telegram. 

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

The tune last night was unfortunately not to 52Mn. The two "isomers" that were identified are instead 45Sc and 75Br. But separation looks okay. ESR morning shift should try to tune to 52Mn to identify the 21-min isomer at 378 keV.

Uploaded some pictures to prove that we were not asleep :-) but they are of limited use...at least my analyzer script and wget works now !! 

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 :-)

Zoom into the triplet: the satellite peaks on the right are clearly visible.
This is just one file but one *might* see some substructure. Yuri mentioned a 318 ms isomer in 45Sc at 12 keV but that cannot be resolved.

Maybe someone can look at the added-up ROOT files if that looks better or is just statistics?

> Short update from Yuri: these are not our isomers. These are 45Sc (left, 12 keV isomer not resolvable) and 75Br (center), and the right-most peak of the triplet is a satellite (has a different line shape, much narrower).
> 

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...)

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

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?

> Run E143-245 MHz-2021.05.09.01.17.42.265.tiq is the first run of the experiment on 52Mn.


And Run E143-410MHz-2021.05.09.03.27.37.368.tiq	from 2021-05-09 03:27 is the first run on the 410 MHz detector. Started a bit later than the 245 MHz detector.
 

ESR warning (colour red in the panel)

Operator intervention required. 

Runs affected by this issue: 

-from E143-245MHz-2021.05.09.02.49.48.521 (03:50) 
-to E143-245MHz-2021.05.09.02.54.54.239 (03:54) .  



  

Short update from Yuri: these are not our isomers. These are 45Sc (left, 12 keV isomer not resolvable) and 75Br (center), and the right-most peak of the triplet is a satellite (has a different line shape, much narrower).




> So the "isomers" pop up at ~-600 Hz and +580 Hz... is the -600 Hz on the left the 378 keV isomer (21 min) and the +580 Hz on the right the g.s.?

So the "isomers" pop up at ~-600 Hz and +580 Hz... is the -600 Hz on the left the 378 keV isomer (21 min) and the +580 Hz on the right the g.s.?

this is how it should look like

the intensity of the line on the left side is so high, it is difficult to see the isomers in the middle as can be seen in the auto generated picture

Run E143-245 MHz-2021.05.09.01.17.42.265.tiq is the first run of the experiment on 52Mn.

It was done in steps:
isochronous 52Mn should come at Brho = 6.28239 Tm (gamma_t = 1.3955).
set ESR to m/q and E for 52Mn, 368.41 MeV/u

1.) predrilling 1st try
- set beamline to E, q for 52Mn and m = 51.9319 u by trim
- E-SIS = 422.1 MeV/u
but then not centred on profile grids, with thick Be target in 
-15mm on TE4DGC also not on Lecuhttarget, not good


2.) pre-predrilling 2nd try
don't set beamline for 52Mn but define it as 78Kr, in trim mass back to 77.92 u.
insert Cu-40 mg/cm² and inject, just use dE = 1.5 MeV/u in stripper for SIS-energy (343.353 + 1.5) MeV/u 
optimise a bit, then keep beamline energy set as 78Kr36+ beam the same. 

3.) pre-drilling 422.1 MeV/u in SIS
insert Be target and optimise with kicker and septum angle,
energy also tried but back to old value, reache 6 - 7 % transmission

4.) change E-SIS to 440.7 MeV/u to get 52Mn in ESR at gamma_t

To improve the isochronicity still in the 72Ge setting sextupoles and scrapers wer varies successfully.

1. E02DS_H -130 / 130mm  - wide rect. peak
            -30 / 130    - nothing 
            -35 / 130    - weak but broad
            -70 / 130    - wider rect peak
            -70 / 30     - two peaks
            -70 / 10     - peak + small peak
            -70 / 0      - peak  + tiny peak
   cannot move more than 0, back to 
            -70 / 50

2. E01DS_H: -130/130    -   wide rectangular distribution
             -40/130    -   wide double structure
             -35/130    -   very weak, still double structure
 some sectupole tuning
             -40/0      - nothing
             -50 / 0    - peak with right tail
  cannot close outside more than 0 so try next scraper

3. E01DS3HG
  -130  - peak with long right tail
   -30  - nothing
   -50  - peak with long right tail
   -40  - weak peak with long right tail
  ==> no good scraper do not use

4. EEXDS2HA
   -120   - peak with long right tail
    -20   - peak with long right tail
      0   - peak with less right tail
     10   - small peak, no right tail
      5   - smaller peak, no right tail
      3   - smaller peak, with small right tail
      8   - small peak no tail
  ==> good scraper use it (+8mm)

5. Try a bit more on E01DS_H
  -55 / 0  - small peak no tail
  -55 / 50 - same no loss in resolution
  -55 /130 - same no loss in resolution
  -65 /130 - same good peak, but higher intensity
  -75 /130 - same good peak, but left tail
  -65 /130 - same good peak, no tail

6. open E02DS_H to -130 / 130 no difference 

7. again E01DS_H
 -125 /130 - very wide left tail
  -68 /130 - one peak
  -72 /130 - one peak, samll left tail
  -66 /130 - one peak, no tail
 ==> good scraper use it (-66mm)

8. check all other scrapers they are all open
   also open TE4 slits to +/-20mm, no difference, back to +/-10 mm

9. bit more sextupole variation on the narrow line

===>  only two scrapers used 

   

picture shows result afterropimisation, the markers indicate the lines,
the left marker is for a +691 keV isomer.








 

last file names with this setting:

245: 2021.05.08.20.42.03.743.tiq
410: 2021.05.08.21.42.17.969.tiq

Details will follow
E(Mn) = 368.41 MeV/u

after optimizing the scrapers we have reached the highest possible resolution in the isochronous mode.

starting data taking with this new settings.

last files before this settings were:

245: 2021.05.08.14.14.55.114.tiq
410: 2021.05.08.15.15.10.101.tiq

The optimisation of sextuples is finished. Record a few files.

Start a new run. The data of new run is in :
SC_2021-05-08_19-51-35
IQ_2021-05-08_19-51-35

The beam in ESR is 78Kr36+@476 MeV/u.
Start a new run:
SC_2021-05-08_18-25-52
IQ_2021-05-08_18-25-52

Uc = 250mA
decay Kr 78, 476 MeV/u

in iso mode

NTCAP is running

Checked beam positions in beamline before ESR,
they all look the same as before, with direct Kr beam.
Compare with old elog entry #.
Also on Leuchttarget it is in the center like before.

Beam settings are being changed back to 78Kr beam at 467 Mev/u. 

EO1KP03 was on = -44.9 A
E01KP05 was off, now is on = 3.67 A
The beam is on the right frequency, but the width is still very broad.

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

08.43am: Beam stopped. HKR looking into it. Reason: they mentioned they don't know yet!

10.10am: SIS resumed operations. However, there are some issues with magnet power supplies for ESR and hence we still don't have beam. HKR member went to look for power supply expert.

10.15am: There were some random triggers coming from ESR, which resulted in files being written. To avoid this, the scope trig (both scopes) were taken out. As soon as the beam comes in 'properly', I will reconnect the trig in to the scopes (-akash).

10.40am: They sent something to ESR but it does not make sense...so HKR has called an ESR expert (Sergey).

11.30am: Yuri is here and trying to sort out the issue- no data being written yet.

(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)

The structure of SIS extraction seems to have changed a little...also for ESR injection.

In the span of a few minutes both the structures changed again...to look more like in the previous shifts, with lesser or no negative component.

Zoom kicked us all out... we managed to get back in...screen sharing is back on.

Things look ok. No settings have been changed...

Analysis attempts are going on...

Start a new run. The data of new run is in :
SC_2021-05-07_17-39-16
IQ_2021-05-07_17-39-16

Start a new run. The data of new run is in :
SC_2021-05-07_17-33-29
IQ_2021-05-07_17-33-29

If gamma_t = 1.3955 Tm stays, we will need Brho = 6.21902 Tm for 70Se.
The corresponding ESR Brho setting will be a bit shifted.
It then requires E-SIS = 446.55 MeV/u to get 70Se to this Brho and gamma_t.

For pre-drilling with 78Kr beam at same Brho use 416.70 MeV/u.
But we could also make a quick try without tuning before, just change all energies.

EXCEL table with all possible fragments injected into ESR.
The path length in ESR, gamma_t and harmonic are adjusted to the 72Ge data. 
Some lifetimes are limited but all intense lines are >30s in lab system.
There are two versions (for cooled beam with fixed v or uncooled (isochronous) 
with fixed average Brho, take the second (grey) column.
For larger frequency shifts harmonics will overlap.
You can add more isomers.

The signal of the transformer on the lower right panel is not really beam related. It is mostly noise. Changes are not so expected with this low beam intensity

The beam was lost for a few minutes from 23:01 to 23:06. It is back now.

In anticipation of the imminent shift change, a snapshot of how things look.

Brief interruption in beam, ~21:42-21:51.

now we are going back to 15 sec operation. Cave M (bio) operation is over

some pics.

restart zoom session

our pattern causes beam loss while scanning the biological probes in the Cave M bio experiment. They loose every other spill due to high request rate from ESR.

For the next 2 hours, the operators have changed the spill pattern that as long as they are scanning , we get only every 1 minute, otherwise we get our 15 seconds as usual.

after two hours this situation should be tuned back to the original spill pattern.

going back to the original energy 441 MeV/u

last filenames with the previous energy:

245: 2021.05.07.17.07.00.543
410: 2021.05.07.18.07.18.037

We will now go up in energy to 447 MeV (+6 MeV) from the original energy

last file name with previous energy:

245: 2021.05.07.16.33.47.178
410: 2021.07.05.17.34.04.780

changed trigger time back to 50%

last file with 1% trigger: 

245 MHZ 2021.05.07.16.07.03.493
410 MHz 2021.05.07.17.07.21.104


p.s. remember the 245 Analyzer has a 1 hour offset in time stamp because of daylight saving time in win10 setting

changed the energy down to 435 MeV/u

There is new sextupole settings, but the scrapers remain like last night (Helmut setting last night.)

new sextupole setting, isomer not visible yet.

We are back with the beam in the ESR since 12:30
ALL SCRAPERS ARE IN THE ORIGINAL POSITIONS
E02DS3HG = - 35 mm
EEXDS2HA = - 25 mm
EEXDS1HA = - 25 mm
E01DS_H = - 40 mm

For E02DS3HG a reset in the control system needed to be done.

Scraper is fixed, we start again. Scraper open to let everything through

The scraper is blocked at -10 mm and -unfortunately- blocks the beam in the ESR. Uli Popp is taking care.

E02DS3HG stays at -35 mm and does not react

SIS optimisation requires us to stop. Only sporadic shots.

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

It was requested from the SIS to stop the beam at 09:28 
Yuri is adjusting the scope in order to avoid UFO (unidentified frequency object)

Trigger for both the spectrum analyzers is changed from 50% to 1% by Yuri.
For this, the ESR pattern was stopped at 08:50 and was started back at 08:53.

(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

Xiangcheng suggested to change the trigger position in order to start the file with the injection. Nothing is changed at the moment. Maybe Shahab or Yuri can do it when they arrive.

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

Some plots of statistics up to now

File start being recorded at 4:38 am 
Sync with the server is working. 

Be aware that the timestamp of the files is 1h behind with respect to real time

made sure that the extra 20dB amplifier is off.

this picture is after scraping by helmut, showing the 410 MHz detector, that is we would expect an isomer where the marker M1 is, i.e. at 2.2kHz on the left side, which we unfortunately don’t see (yet).

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

Scraper settings have been played around with to try and remove satellite lines...

Helmut has now set scraper id GE01DS_H at -45mm (in position)

Image of injection structure attached... 72Ge is the isotope in focus on the RSA

Opened TE4 slits again to +/-10mm.

Then we tried different scrapers:
in south arc outside: E02DS3HG, cuts at ~ -25mm, at -15mm gone, leave at -35mm.

on straight section: EEXDS2HA cuts at ~ -25mm, leave at -25mm.

EEXDS1HA, closing it to -25mm revealed a double peak structure with distance just like the wanted isomer (-2.2MHz at h=211).
But it is present on all intense peaks at the same distance, so it must be an artefact of a strange isochronicity curve.
Closing it to -15mm even had only the smaller lower frequency line survive.
But then it must be also possible to have only the stronger line. leave at -25mm

This worked with scraper in north arc E01DS_H which can cut from both sides.
The insie can ve iused to cut the lower Brho, 
at -50mm still two peaks, at -45mm left peak almost gone, -40mm left peak gone but right still intense, leave at -40mm.

-> Lower Brho seems to be clearly related to lower frequency, higher Brho side is not so clearly related to frequency.

Measure in this setting, nice void at wanted frequency. But no isomers appear so far.
 

At the moment we see a second peak to the left of each intense line. 
The distance between the main peak and the shadow is roughly the same for each peak.
This hints to a sharp fall in the isochronicity curve.
Helmut now tries to remove these shadows by using different scrappers. 

RFQ fall-out (HKR working on it...)

Beam stop time: 01.58am

Beam resumption: 02.02am

This is a comparison of I_Raw/Q_Raw between different reference level. The range of NTCAP ADC is only 2^15 bit. So signals (I_Raw and Q_Raw) should 
not be outside ADC range. It is clear that there is not point outside the ADC range when using reference level -30dBm.

Reference Level: -30 dBm.

Start taking data.
SC_2021-05-07_00-11-24
IQ_2021-05-07_00-11-24

Reference Level: -40 dBm.

Start taking data.
SC_2021-05-07_00-06-57
IQ_2021-05-07_00-06-57

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:

Beam is secondary beam now. The intensity is lower. Change reference level to -50dBm.
Carrier frequency:245MHz
IQ rate(S/s): 20M.
Reference Level: -50 dBm.

Start taking data.
SC_2021-05-06_23_02_46
IQ_2021-05-06_23_02_33

parammodi exports, E-SIS = 441.0 MeV/u with Be-1840 mg/cm² target in, isoc. ESR, at least we see fragments

The two grids do not work very well, one x position is opposite to the other.
But at least a guidance for the future, this was good injection of 78Kr with a thick Be target.

gamma_t = 1.3955
Br(72Ge) corresponds to 6.79575 Tm
E (Kr) at Br(72Ge) = 392.9 MeV/u
ESIS = 467.45 MeV/u (pre-drilling, after 1.8 g/cm2 target)
ESIS = 440.98 MeV/u (final energy for 72Ge)

-during setup, a 20 mm offset in the TE line was observed. Beam centered via changing the Br of the beamline (~4 MeV/u up). Optimized pre-drilling transmission ~20% (with thick target)

NTCAP was stopped at 17:34 for the optimisation purpose.
NTCAP started again at 18:20 with the change in Reference Level (dBm): 0

SC_2021-05-06_18-20-05
\IQ_2021-05-06_18-20-05

Setting the 78Kr (after the target) to the Brho of the 72Ge beam at 368.4 MeV/u (gamma=1.3955), i.e. 6.79575 Tm, which leads to an energy of 392.93 (of 78Kr). 
With the 10mm Be target the beam energy should then be 467.8 MeV/u .
Yes, with my slightly different target thickenss 467.5 MeV/u (Helmut).

For 72Ge at this Brho after the target it then needs 440.95 MeV/u.
LISE in proj. fragmentation option Morissey for projectile energy loss and ATIMA 1.4 with Be 1839 mg/cm^2).

At the moment, we record 7 signals in scaler channels and one Schottky signal (245 MHz resonance cavity) in the NTCAP with the attached information.

NTCAP is on and data taking has started.
On time: 16:39

SC_2021-05-06_16-39-09
\IQ_2021-05-06_16-39-09

IQ Rate: 20 MS/s
Carrier frequency: 245 MHz
Reference level(dBm):-30
RF attenuation(dB):40
IF attenuation(dB):19.9288

Data file
Samples/records:2^18=262144
Records/File:2^12=4096

SC file: 
Entries/file:2^18=262144

Master path:
o:\E143\iq 
o:\E143\sc

Thickness of the Carbon target in the TE line has been measured by centering the primary 78Kr beam in the ESR:
Beam energy 370 MeV/u, with thin stripper, ESR energy 368.65 MeV
Adjust beam with "thick" target to keep ESR energy at 368.65 MeV/u -> Beam energy 445 MeV/u
Energy loss 75+1.35=76.35 MeV
Target thickness : 9.97 mm

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.

There are several issues.

1. The stepper motor drive does not react from Device-Control, -> check controller in FRS Messhütte
2. They don't get a trigger, other grids in TE-line do -> check raw signals also in FRS Messhütte, ask Strahldiagnose
3. For less noise pockets of grids should be evacuated, but most likely the pump is still off or not even connected -> enter ESR and connect

Check also manual at https://web-docs.gsi.de/~weick/frs/current_grids.html
Below picture of no trigger shown in App. Usually it should say last trigger a few seconds ago and display some noise.

This file has several options:
start in SIS, at TE3UF target or inside ESR, choose with GOTO LABEL (G L)after start system (S S).
Depending on the choice select different start beam parameters at top of file, others comment out.

There are also different optics setting with different quadrupoles:
- for TE beamline the standard and the mode by Hans for better focus on the target.
- for ESR a standard mode and variations of isochronous modes
also select by commenting in/out.

Input can be made also in units of K'L for fast import from parammodi, still by hand but with copy and paste.
One half of ESR is defined as a block, can be used more or less often (B I HALF ;)

The dispersion from the production target into the ESR is not matched.
This is not good for momentum acceptance, but we anyway want to cut the acceptance.
Dispersion will oscillate with the tune of ESR. After 3 turns we expect a maximum dispersion. 
The picture shows in red the dispersion curve for dp/p=0.1% and beam envelopes of 10 mm mrad.
So we can use scrapers in north or south arc to cut Brho. It should be done from both sides.
How much? Watch the intensity drop.
Best positions look at plot. Straight section outside for low Brho, arc outside for high Brho.
Could be EEXDS2HA and E02DSH (outside).

The slits at TE4 and TE5 can be used to cut away the unwanted 78Kr beam (see pictures).
We do not want activation of the beamline. 78Kr35+ even has a chance of being injected.

This file really has the optics like used in the last ESR experiments.
Now the transmission is also a little bit better.

A       Z      M/q                Int    difference in kHz@245MHz
68	30	2.263614752	35	-933.1
70	31	2.255131564	124	-457.0
36	16	2.247394703	1	-21.2
45	20	2.24726171	1	-13.7
81	36	2.247136805	1	-6.7
72	32	2.247041397	376	-1.3
72	32	2.247018215	376	0
63	28	2.246941324	1	4.3
54	24	2.246906236	1	6.3
74	33	2.239572482	568	420.9
65	29	2.238342523	100	490.5
76	34	2.232371568	62	829.3
67	30	2.230357529	100	943.7
69	31	2.222859086	172	1370.7
60	27	2.219224118	100	1578.3
62	28	2.211179746	100	2038.7
77	35	2.197207311	116	2842.5

Uncooled beam on target at TE3UF with dispersion and slit in TE beamlne and realistic injection into ESR.
Now tuned for 72Ge but can easily be modified to other fragment settings. 
The target thickness may need adjustemet after measurement.
The attched powerpoint file explains the settup a bit more.