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.