ELOG MUGAST

T_Si_CATS1 (stop should be CATS n FAG --> to be checked)
T_Si_VAMOS (seen now in T_CATS1_CATS2) --> check the signals (if CATS is the START we should use CATS n FAG, if it is the stop it should be delayed by 800 ns , the delay is prepared)

Fixed

e744s

Thu Apr 11 05:08:20 2019

Screenshots from RUN 74

RUN 74 with 14N beam and CD2 104um target
First screenshots from MUGAST

Time of flight is OK for MM and MG --> we keep CATS n FAG the way it is
CATS2 position is shifted in X by 3mm but it seems to be well centered on MUST2 and MUGAST

We see proton elastic scattering in MUST2 and in the square (by the way the square is working !)
I had to mask one mate Y on MG4 because it was counting about 50 Hz in the noise.

Attachment 1: correlation_AGATA.png

Attachment 2: correlation_TAC.png

Attachment 3: DeltaE_E_MM.png

Attachment 4: DeltaE_Tof_MUGAST.png

Attachment 5: MUGAST_impact.png

Attachment 6: MUST2_impact.png

Attachment 7: cats2_pos.png

Attachment 8: TAC.png

Fixed

e744s

Thu Apr 11 06:38:12 2019

+300 ns of delay in the HF validated signal that gives the STOP of T_FPMW_HF && T_CATS2_HF.
Range of TAC FPMW_CATS2 increased to 1us.

Fixed

e744s

Thu Apr 11 06:41:14 2019

========================================
*************************
Run : 75
*************************

Start at 2019-04-11 06:40:54.479084

Run Conditions:

Operator: A. Lemasson
Trigger: Mugast & Vamos % 1000 & Cats2 % 40000
Target/Source: CH2 105 um (Position 2)
Beam: 14N
Intensity: ~ 2e+5
Brho = 0.437 Tm
CATS 2 IN

Comment:

Stop at 2019-04-11 07:29:11.245553
Stop comment:

Fixed

e744s

Thu Apr 11 06:48:23 2019

mugast wrote:

- 2 TACS are not working:

T_Si_CATS1 (stop should be CATS n FAG --> to be checked). Also Ok now. Same problem as below
T_Si_VAMOS (seen now in T_CATS1_CATS2) --> check the signals (if CATS is the START we should use CATS n FAG, if it is the stop it should be delayed by 800 ns , the delay is prepared)
The was a broken Cable from the delay to fan in fan out.

Still remains T_Vamos_Cats1 with no counts. I suspect the necesity to put a 2 us delay on Cats1, or to inverse it and pout Cats1 fag validated as start

Attachment 1: run275_tacs_mugast.png

Fixed

e744s

Thu Apr 11 07:00:17 2019

ToDo List and plan for today

To Do/Understand
1) T_Vamos_Cats1 in Mugast and T_FPMW_CATS2 in Vamos are not working. I suspect it is the same reason, meaning stop arrives before start. Longer delay or inverse putting Cats2-Fag validated.
2) MM3_E_TOF there is a 5 MeV threshold see below?

For today:
1) We give the beam back to them at 10 am.
2) Analyse the data from RUN 74 & 75 to see the excitation function for 1H(14N,p)
3) If we have the beam back, take more data merged with Agata. Intensity around 2e+5 pps to protect CATS2.
4) If Vamos/Mugast need debugging for reconstruction/validation they have priority.

Summary of the night :
1) Measured the target thicknesses for the targets: 1) Hole 2) CH2 105 um 3) CH2 100 um 4) C 70 um 5) CH2 73 um
2) The C target was not very homogeneous, meaning that was dramatically spreading the momentum distribution of the beam charge states.
3) Vamos debugging went forward, transmission was 95% with Cats2 in with 2e+4 pps beam intensity
4) At 4h30 started the statistic run with Vamos setted at a Brho of 0.437 Tm to completely remove 14N7+ and all others from the focal plane. The beam spot was about 50 mm pied a pied ... This makes imposible the use

Attachment 1: run275_tacs_mugast.png