Some plots of statistics up to now

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

Analysis attempts are going on...

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

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.

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

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.

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

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

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

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\0000299
 p:\E143\iq\IQ_2021-06-30_23-27-34\0001462
2. The rest space on the drive "p:\" : 29,1TByte

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 

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

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

(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

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

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

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