|
Fixed, e768s, Mon Jul 29 18:59:51 2019, OttoRun, RUN, General, LiF, Run158
|
*************************
Run : 158
*************************
Start at 2019-07-29 18:59:00.751661
15O beam
Brho = 0.556 Tm
target LiF thick number 1
OR VAMOS 474
OR Mugast 106
Fag 133
beam intensity XX
TRIGGERS:
MG BACK
MG 90
MUST2
VAMOS%10
BF2%100
restart after VAMOS optimization
Stop at 2019-07-30 11:04:58.183397
Stop comment: changing AGATA 01B parameter file |
Fixed, e768s, Mon Jul 29 19:49:19 2019, Freddy, Sylvain, Nicolas, BEAM, General, LiF, Run 158 : Beam profile after beam tuning 
|
Below is the beam profile and the scaler corresponding to the beam after optimisation
Edit : beam intensity is strongly fluctuating : current intensity is 2 10⁶ |
|
Fixed, e768s, Mon Jul 29 22:00:00 2019, Freddy, Sylvain, BEAM, General, LiF, Scaler Evolution run 158
|
Evolution of scaler during run0158 _ from 19h to 24h00
--> Beam extremely unstable from zero to 10**7 pps (for not more than 5 min).
--> Several moment without beam, either lost at C0 or trying to optimize. |
|
Ongoing, e768s, Mon Jul 29 22:50:43 2019, Sylvain & Freddy, ONLINE, General, LiF, Screenshots run 158 @ 22h05 19x
|
|
|
Fixed, e768s, Tue Jul 30 01:20:21 2019, Jenn & Franco, BEAM, General, LiF, Beam intensity, profile check and SUMMARY night
|
In run 158 at around 01:00am PCP took the beam to try to optimize it. We got the beam back after ~15 minutes.
Beam intensity ~1.2e7
OR MUGAST ~ 160
OR VAMOS ~ 650
30 minutes later: comparing the actual beam profile with the previous ones it looks like the beam has shifted on the horizontal axis (before the centroid was -1.9, now it is -3.4).
At the same time we noticed an increase in the AGATA counting rate (~ 35k). AGATA itself is not very stable, each now and then all the detectors go in back pressure for few
seconds and then they come back to the normal status. Moreover we see more counts on the second line in the correlation matrix (see figure attached). We think that maybe
with the last optimization the beam is slightly touching somewhere out of the target.
At 02:15am there was a problem with the vacuum on the PCP side so the beam went off. We wait for a guy to come in ~45min and solve this issue or understand WThell is happening.
RUN 158 won't be stopped to avoid DAQ problems.
TO UNDERSTAND: even after beam stopped 30 min ago, OR Vamos is still counting ~100 Hz while AGATA and MUGAST are counting nothing. |
|
Fixed, e768s, Tue Jul 30 04:04:27 2019, Jenn & Franco, RUN, General, LiF, Beam back at 4.00 h
|
We had the beam back at 4.00 a.m.
Beam profile and intensity checked: 1.2e7
OR VAMOS ~ 630
OR MUGAST ~ 170
OR AGATA ~ 35k
The AGATA rate is still very high. |
|
Fixed, e768s, Tue Jul 30 04:25:49 2019, Jenn & Franco & Teodora, BEAM, General, LiF, Beam intensity, profile check and SUMMARY night
|
This is what we were seeing in agata. We think it might be possible we were having a bit of beam implanted somewhere. We called PCP to check.
| Jenn & Franco wrote: | In run 158 at around 01:00am PCP took the beam to try to optimize it. We got the beam back after ~15 minutes.
Beam intensity ~1.2e7
OR MUGAST ~ 160
OR VAMOS ~ 650
30 minutes later: comparing the actual beam profile with the previous ones it looks like the beam has shifted on the horizontal axis (before the centroid was -1.9, now it is -3.4).
At the same time we noticed an increase in the AGATA counting rate (~ 35k). AGATA itself is not very stable, each now and then all the detectors go in back pressure for few
seconds and then they come back to the normal status. Moreover we see more counts on the second line in the correlation matrix (see figure attached). We think that maybe
with the last optimization the beam is slightly touching somewhere out of the target.
At 02:15am there was a problem with the vacuum on the PCP side so the beam went off. We wait for a guy to come in ~45min and solve this issue or understand WThell is happening.
RUN 158 won't be stopped to avoid DAQ problems.
TO UNDERSTAND: even after beam stopped 30 min ago, OR Vamos is still counting ~100 Hz while AGATA and MUGAST are counting nothing. |
|
|
Fixed, e768s, Tue Jul 30 04:40:18 2019, Jenn & Franco & Teodora, RUN, General, LiF, Beam back at 4.00 h
|
Due to the high rate of AGATA and Mugast (probably due to some implantation) we asked the PCP to readjust the beam.
They centered it a bit more on the profiler and now it looks better. Attached are the new rates.
OR VAMOS ~ 620
OR MUGAST ~ 170
OR AGATA ~ 7k
| Jenn & Franco wrote: | We had the beam back at 4.00 a.m.
Beam profile and intensity checked: 1.2e7
OR VAMOS ~ 630
OR MUGAST ~ 170
OR AGATA ~ 35k |
|
|
Fixed, e768s, Tue Jul 30 05:32:33 2019, Teodora & Franco, RUN, General, LiF, Screenshots run 158 - 5:30h + beam profile at 6:00h 20x
|
| Scalers and beam profile measurement taken at 6:00 h. |
|
Fixed, e768s, Tue Jul 30 07:49:09 2019, Teodora & Franco, RUN, General, LiF, Check beam intensity and profile run158 h 8:00
|
|
|
Fixed, e768s, Tue Jul 30 11:08:30 2019, OttoRun, RUN, General, LiF, Run159
|
*************************
Run : 159
*************************
Start at 2019-07-30 11:07:33.907674
15O beam
Brho = 0.556 Tm
target LiF thick number 1
OR VAMOS 653
OR Mugast 156
Fag 206
beam intensity 1.3e7 pps
TRIGGERS:
MG BACK
MG 90
MUST2
VAMOS%10
BF2%100
Stop at 2019-07-30 16:22:08.584979
Stop comment: |
|
Fixed, e768s, Tue Jul 30 15:47:46 2019, Nicolas, BEAM, General, , Beam stopped since 11h30
|
| vacuum problem in CSS1 |
|
Fixed, e768s, Tue Jul 30 16:22:21 2019, mugast, RUN, General, LiF, Beam is back. Intensity= 7e6 pps. Start a new run : run 160
|
| Run 160. |
|
Fixed, e768s, Tue Jul 30 16:39:03 2019, OttoRun, RUN, General, LiF, Run160
|
*************************
Run : 160
*************************
Start at 2019-07-30 16:38:24.263869
15O beam
Brho = 0.556 Tm
target LiF thick number 1
OR VAMOS 715
OR Mugast 168
Fag 206
beam intensity 7 106pss
TRIGGERS:
MG BACK
MG 90
MUST2
VAMOS%10
BF2%100
Stop at 2019-07-31 16:43:13.641726
Stop comment: Let's go to the beach...... |
|
Fixed, e768s, Tue Jul 30 19:13:57 2019, Faïrouz & Ksenia, RUN, General, LiF, Screenshots run 160 @ 19h10 & scalers 20x
|
|
|
Fixed, e768s, Tue Jul 30 21:36:43 2019, Faïrouz & Ksenia, RUN, General, LiF, Beam profile & scalers (run160) @21h36
|
|
|
Fixed, e768s, Tue Jul 30 23:46:25 2019, Faïrouz & Ksenia, RUN, General, LiF, Beam profile & scalers (run160) @23h45
|
|
|
Fixed, e768s, Wed Jul 31 03:22:42 2019, Freddy, Chloé, BEAM, General, , Beam profile (run160) @2h24
|
|
|
Fixed, e768s, Wed Jul 31 03:25:57 2019, Freddy, Chloé, BEAM, General, N/A, Scaler Evolution run 160
|
Scaler evolution during run 160 until 3h30 on Wednesday 31st.
- rather stable condition around 1.5 * 10^7 pps
- square detector seems to have some fluctuating trigger rate certainly due to some strips with larger noise or baseline fluctuations. |
|
Fixed, e768s, Wed Jul 31 04:13:31 2019, Freddy, Chloé, BEAM, General, N/A, HF CIME disjonction
|
Disjonction HF CIME at 4h14
Restart at 4h30 (see beam profile and scalers after restart) |
|