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

last file names with this setting:

245: 2021.05.08.20.42.03.743.tiq
410: 2021.05.08.21.42.17.969.tiq

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.








 

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

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

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

this is how it should look like

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

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

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



  

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

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

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

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

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 3-4am (computer time).
-s 0.1 -t 8.0

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. 

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)