Fixed, e744s, Thu Apr 11 07:00:17 2019, iulian, BEAM, General, CH2, 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 |
|
Fixed, e744s, Thu Apr 11 07:17:33 2019, OttoRun, RUN, General, CH2, Run75 12x
|
| OttoRun wrote: | *************************
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: |
|
|
Fixed, e744s, Thu Apr 11 07:30:15 2019, mugast, BEAM, Social, N/A, Beam stop
|
| The beam will be back around 8:30. |
|
Fixed, e744s, Thu Apr 11 08:01:12 2019, OttoRun, RUN, General, CH2, Run76
|
*************************
Run : 76
*************************
Start at 2019-04-11 07:59:50.438662
Run Conditions:
- Operator: Nikola, Marion
- 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: Beam stopped (Balise).
Stop at 2019-04-11 08:33:56.045621
Stop comment: |
|
Fixed, e744s, Thu Apr 11 08:55:23 2019, OttoRun, RUN, General, CH2, Run77 23x
|
*************************
Run : 77
*************************
Start at 2019-04-11 08:54:59.257928
Run Conditions:
- Operator: Nikola, Marion
- Trigger: Mugast & Vamos % 1000 & Cats2 % 40000
- Target/Source: CH2 105 um (Position 2)
- Beam: 14N
- Intensity: ~ 2.2e+5
- Brho = 0.437 Tm
- CATS 2 IN
Comment:
Stop at 2019-04-11 10:08:08.427024
Stop comment: Beam stopped for radiactive preparation |
|
Fixed, e744s, Thu Apr 11 09:05:37 2019, mugast, CATS, General, N/A, CATS HV changed to 580
|
| CATS HV changed from 600V to 580V. |
|
Fixed, e744s, Thu Apr 11 10:38:13 2019, Adrien and Valerian, BEAM, General, N/A, They are preparing 14O beam
|
News from (edit after talking to Pierre D.)
- They are preparing the 14O beam.
- We should have 14O at moderate intensity early afternoon.
- The beam should be at full intensity inG1 around 21h-23h.
- Run end Wenesday 18h sharp
- Omar is on call at any time
|
|
Fixed, e744s, Thu Apr 11 11:26:52 2019, Adrien, MUST2, General, CH2, TOF in MUST2 MM3 is now fixed
|
The E-TOF plot in MM3 was showing a 5MeV threshold.
After investigation the 12 strip was not disable on MM2 to MM4, and particularly noisy on MM3, killing the counts at small angle where most of the proton are.
After disabling the Strip 12 all 4 telescope show the same amount of statistics.
I added the Impact matrix and the E-DE plot for each of the forward telescope as well. Looks like the beam is not centered but shifted. Need more investigation.
The online need to be restarted to take this into account.
|
|
Fixed, e744s, Thu Apr 11 11:36:09 2019, Valerian, OFFLINE, Software, CH2, Comparison between the two e744
|
| Current calibration is off, a shift of -1.5MeV was done to reproduce the previous data. |
|
Fixed, e744s, Thu Apr 11 13:43:26 2019, Valerian, OFFLINE, Software, CH2, Target position for 14N runs
|
|
|
Fixed, e744s, Thu Apr 11 14:03:45 2019, Valerian, CATS, Hardware, N/A, In case of a CATS2 tripped
|
Currently, CATS2 is inserted, if the window :
CATS2 has tripped appear, one should do the following :
- Open a terminal
- Type: HV
- Username is : admin
- Password is : admin
- Press enter twice
The list of channels is going to appear.
- Using the arrow of the keyboard, go down until you reach cats2
- then go right until you reach Off
- press space, the dectector should start ramping up
- If it trips again, you can try to put voltage to cats1 (right above cats2)
Two possibility :
- If cats1 trip it is the gas bottle that is empty call : 07 83 34 30 81 (Sebastien)
- If cats1 doesn't trip try cats2 again, and if it trips lower the voltage of cats2
To lower the voltage of cats2 : go to the left until you reach the first cell after cats2 name and lower the voltage 10 volts and try to start cats2 again.
THEN CLOSE THE TERMINAL |
|
Fixed, e744s, Thu Apr 11 15:16:10 2019, Adrien, Valerian, Louis, CATS, General, CH2, run77 CATS efficiency
|
CATS efficiency has been computed for run 77 using T_FagHF an T_Si_Cats1 with different triggers:
Trigger GATCONF_MASTER<8 (MUST+Mugast) : 94%
Trigger GATCONF_MASTER=4 (MUST) : 99.4%
Trigger GATCONF_MASTER=2 (square) : 85%
Trigger GATCONF_MASTER=1 (trapezoidal+annular) : 22%
The 22% resolution is due to the fact that the trapezoidal detectors are noisy. Doing the same on an analysed run we obtain ~ 85% efficiency |
|
Fixed, e744s, Thu Apr 11 16:07:59 2019, Valerian and Louis, OFFLINE, Software, CH2, HF resolution
|
| Using the value of the HF=83,4ns. We can obtain the calibrated plot of T_CATS2_HF which is joined and gives us roughly a 2-3 ns resolution for the HF |
|
Fixed, e744s, Thu Apr 11 16:56:34 2019, OttoRun, RUN, General, Empty, Run78
|
*************************
Run : 78
*************************
Start at 2019-04-11 16:55:28.720017
Run Conditions:
- Operator: Adrien
- Trigger: Mugast
- Target/Source: hole
- Beam: 14O
- Intensity: ~ 3e+3
- Brho = ?? Tm
- !CATS/VAMOS (CATS Efficiency)! : XXXX
Comment:
Alignign beam, daq on for online monitoring
Stop at 2019-04-11 17:07:49.331973
Stop comment: changing trigger to vamos |
|
Fixed, e744s, Thu Apr 11 17:08:39 2019, OttoRun, RUN, General, Empty, Run79
|
*************************
Run : 79
*************************
Start at 2019-04-11 17:08:21.837538
Run Conditions:
- Operator: Adrien
- Trigger: VAMOS
- Target/Source: hole
- Beam: 14O
- Intensity: ~ 3e+3
- Brho = ?? Tm
- !CATS/VAMOS (CATS Efficiency)! : XXXX
Comment:
Aligning beam, daq on for online monitoring
Stop at 2019-04-11 17:31:48.540765
Stop comment: Entering to Remove CATS2 and remove VAMOS %1000 |
|
Fixed, e744s, Thu Apr 11 17:35:21 2019, François, BEAM, General, , 14O beam is in G1 since 17H00
|
alignment of the beam in VAMOS
intensity ~ 5x10^3 pps |
|
Fixed, e744s, Thu Apr 11 17:37:29 2019, Valérian, Chloé and François, OTHER, Hardware, , changes in the electronic
|
Changes made in the electronic during the break between 14N and 14O
1) T_VAMOS-CATS1
it was not connected. We added 500 ns delay in CATS1 (CATS2 in reality) (48+150ns before)
2) T_CATS1_HF
range changed from 2µs to 200 ns |
|
Fixed, e744s, Thu Apr 11 17:38:24 2019, mugast (beyhan), BEAM, General, , 14O8+ beam characteristics
|
Brho 14O8+ = 0.69186 Tm
update Adrien:
La dream team de Division (non) Opération n'arrive pas a mesurer l’énergie en sortie de CIME (WTF??!!)
Du coup ils ont mis une énergie fausse mais avec une super précision de 1.8 Mev/A dans la fiche.
#onlyatganil |
|
Fixed, e744s, Thu Apr 11 17:38:28 2019, iulian, RUN, Hardware, Empty, Setting trigger Vamos and Cats
|
Removed division %40000 on Cats and %1000 on Vamos.
Removed Cats2 from the beam |
|
Fixed, e744s, Thu Apr 11 17:43:44 2019, OttoRun, RUN, General, Empty, Run80
|
*************************
Run : 80
*************************
Start at 2019-04-11 17:42:44.178301
Run Conditions:
- Operator: Adrien
- Trigger: VAMOS %1
- Target/Source: hole
- Beam: 14O
- Intensity: ~ 5e+3
- Brho = 0.69186 Tm
- !CATS/VAMOS (CATS Efficiency)! : XXXX
Comment:
After removing division on Cats and Vamos.
Aligning beam, daq on for online monitoring
Stop at 2019-04-11 18:50:52.122268
Stop comment: Stop to remove target hole |
|