MUST2 SAMURAI_2018 S3-LEB-LPC SUPERNEMO MUGAST EXPAND SCALP GALATRON HiCARI VELO
  MUGAST, Page 22 of 132  Not logged in MUGAST
Status ExpNbrdown Date Author Type Category Target-Source Subject
Fixede775s Sat Feb 29 07:33:42 2020 OttoRunRUNGeneralCD2-AuRun154
*************************
Run : 154
*************************

Start at 2020-02-29 04:31:41.631084

VAMOS+AGATA+MUGAST
CD2+Au Target #2 (250-300ug + 20 umAu)
Trigger

* MG Annular
* MG Trapezoid

Beam intensity 4e+5

Restart in same conditions as run 152 after reloading RCC config and initializing
Fixede775s Sat Feb 29 07:33:46 2020 OttoRunRUNGeneralCD2-AuRun156
*************************
Run : 156
*************************

Start at 2020-02-29 06:00:50.625977

VAMOS+AGATA+MUGAST
CD2+Au Target #2 (250-300ug + 20 umAu)
Trigger

* MG Annular
* MG Trapezoid

Beam intensity 4e+5

Restart in same conditions as run 152 after reloading RCC config and initializing
Fixede775s Sat Feb 29 07:34:54 2020 OttoRunRUNGeneralCD2-AuRun160
*************************
Run : 160
*************************

Start at 2020-02-29 06:49:38.061167

VAMOS+AGATA+MUGAST
CD2+Au Target #2 (250-300ug + 20 umAu)
Trigger

* MG Annular
* MG Trapezoid

Beam intensity 4e+5

Restart in same conditions as run 152 after reloading RCC config and initializing


CURRENTLY ISSUES WITH AGATA : AGATA IS NOT RESPONDING SINCE ~4Am ISSUE STILL PENDING

Stop at 2020-02-29 07:39:20.250159
Stop comment: stop for agata test
Ongoinge775s Sat Feb 29 07:35:21 2020 mugast : ValerianAGATAGeneralCD2AGATA is not responding
Since ~4:30am AGATA is not responding, everyhting was frozen. Unclear if it comes from disk problem or other...
Fixede775s Sat Feb 29 08:01:52 2020 OttoRunRUNGeneralCD2-AuRun161
*************************
Run : 161
*************************

Start at 2020-02-29 07:57:29.567615

VAMOS+AGATA+MUGAST
CD2+Au Target #2 (250-300ug + 20 umAu)
Trigger

* MG Annular
* MG Trapezoid

Beam intensity 4e+5

Restart in same conditions as run 152 after reloading RCC config and initializing


CURRENTLY ISSUES WITH AGATA : AGATA IS NOT RESPONDING SINCE ~4Am ISSUE STILL PENDING
test AGATA

Stop at 2020-02-29 08:01:56.572900
Stop comment:
Fixede775s Sat Feb 29 08:51:28 2020 OttoRunRUNGeneralCD2-AuRun162
*************************
Run : 162
*************************

Start at 2020-02-29 08:49:53.401544

VAMOS+AGATA+MUGAST
CD2+Au Target #2 (250-300ug + 20 umAu)
Trigger

* MG Annular
* MG Trapezoid

Beam intensity 4e+5

Restart in same conditions as run 152 after reloading RCC config and initializing


CURRENTLY ISSUES WITH AGATA : AGATA IS NOT RESPONDING SINCE ~4Am ISSUE STILL PENDING
test AGATA

Stop at 2020-02-29 08:51:59.327149
Stop comment: agata not working
Fixede775s Sat Feb 29 09:02:46 2020 OttoRunRUNGeneralCD2-AuRun163

Stop at 2020-02-29 17:52:47.142006
Stop comment:
Ongoinge775s Sat Feb 29 10:34:31 2020 mugast ; valerian ireneOFFLINESoftwareCD2-AuIssues in the EX reconstruction
We are currently working on the EX reconstruction which is off for detector 1, 3 and 7... One of our guess might be that there is an issue with the position of the detectors which gives error in theta... As the energy calibration is ok. Joined are :

- the Excitation energy for good detectors compared to all detectors,
- the theoretical kinematic line for the 3.57 state for each detectors,
- the excitation energy as a function of the laboratory angle (for this last spectra a clear dependency is visible for telescopes 1,3 and 7)
- the 3D view, which doesn't show clear problem in position...
Ongoinge775s Sat Feb 29 14:27:48 2020 mugast ; ValerianOFFLINESoftwareCD2Issues in the EX reconstruction

mugast ; valerian irene wrote:
We are currently working on the EX reconstruction which is off for detector 1, 3 and 7... One of our guess might be that there is an issue with the position of the detectors which gives error in theta... As the energy calibration is ok. Joined are :

- the Excitation energy for good detectors compared to all detectors,
- the theoretical kinematic line for the 3.57 state for each detectors,
- the excitation energy as a function of the laboratory angle (for this last spectra a clear dependency is visible for telescopes 1,3 and 7)
- the 3D view, which doesn't show clear problem in position...


Testing changing the beam impact :

-Kine for beam impact = (0,0,0) for reference
-Kine for beam impact = (0,0,-5mm)
-Kine for beam impact = (0,0,+5mm)

-Ex vs ThetaLab for beam impact = (0,0,0) for reference
-Ex vs ThetaLab for beam impact = (0,0,-5mm)
-Ex vs ThetaLab for beam impact = (0,0,+5mm)
Red lines corresponds to Ex = 3.570 MeV and Ex = 4.070 MeV

To try to correct the problem i also offseted the beam in X and Y, but this doesn't solve the problem quite the opposite as it make the result worse for other detectors also... The fact that it is better at lower angle and worse at higher angle might mean that the detectors angles are tilted compared to the
surveyors measurments... I also tried to use the CAO positions for MG3 (see Detectors/mugast.detector) but it didn't solve the problem.
Fixede775s Sat Feb 29 14:32:39 2020 mugast : ValerianGRITHardwareN/AScheme of the Mugast position in the nptool referential
The detectors with a cross show the problematic detectors
Ongoinge775s Sat Feb 29 15:53:12 2020 mugast ; ValerianOFFLINESoftwareCD2-AuIssues in the EX reconstruction

mugast ; Valerian wrote:

mugast ; valerian irene wrote:
We are currently working on the EX reconstruction which is off for detector 1, 3 and 7... One of our guess might be that there is an issue with the position of the detectors which gives error in theta... As the energy calibration is ok. Joined are :

- the Excitation energy for good detectors compared to all detectors,
- the theoretical kinematic line for the 3.57 state for each detectors,
- the excitation energy as a function of the laboratory angle (for this last spectra a clear dependency is visible for telescopes 1,3 and 7)
- the 3D view, which doesn't show clear problem in position...


Testing changing the beam impact :

-Kine for beam impact = (0,0,0) for reference
-Kine for beam impact = (0,0,-5mm)
-Kine for beam impact = (0,0,+5mm)

-Ex vs ThetaLab for beam impact = (0,0,0) for reference
-Ex vs ThetaLab for beam impact = (0,0,-5mm)
-Ex vs ThetaLab for beam impact = (0,0,+5mm)
Red lines corresponds to Ex = 3.570 MeV and Ex = 4.070 MeV

To try to correct the problem i also offseted the beam in X and Y, but this doesn't solve the problem quite the opposite as it make the result worse for other detectors also... The fact that it is better at lower angle and worse at higher angle might mean that the detectors angles are tilted compared to the
surveyors measurments... I also tried to use the CAO positions for MG3 (see Detectors/mugast.detector) but it didn't solve the problem.


By looking at the EnergyCalibrator.C, I saw that the extrapolation used to find the dead layer of aluminum is commented... This might be an answer to the problem...
Ongoinge775s Sat Feb 29 17:18:02 2020 mugast ; Valerian, Marlène , PierreOFFLINESoftwareCD2-AuIssues in the EX reconstruction

mugast ; Valerian wrote:

mugast ; Valerian wrote:

mugast ; valerian irene wrote:
We are currently working on the EX reconstruction which is off for detector 1, 3 and 7... One of our guess might be that there is an issue with the position of the detectors which gives error in theta... As the energy calibration is ok. Joined are :

- the Excitation energy for good detectors compared to all detectors,
- the theoretical kinematic line for the 3.57 state for each detectors,
- the excitation energy as a function of the laboratory angle (for this last spectra a clear dependency is visible for telescopes 1,3 and 7)
- the 3D view, which doesn't show clear problem in position...


Testing changing the beam impact :

-Kine for beam impact = (0,0,0) for reference
-Kine for beam impact = (0,0,-5mm)
-Kine for beam impact = (0,0,+5mm)

-Ex vs ThetaLab for beam impact = (0,0,0) for reference
-Ex vs ThetaLab for beam impact = (0,0,-5mm)
-Ex vs ThetaLab for beam impact = (0,0,+5mm)
Red lines corresponds to Ex = 3.570 MeV and Ex = 4.070 MeV

To try to correct the problem i also offseted the beam in X and Y, but this doesn't solve the problem quite the opposite as it make the result worse for other detectors also... The fact that it is better at lower angle and worse at higher angle might mean that the detectors angles are tilted compared to the
surveyors measurments... I also tried to use the CAO positions for MG3 (see Detectors/mugast.detector) but it didn't solve the problem.


By looking at the EnergyCalibrator.C, I saw that the extrapolation used to find the dead layer of aluminum is commented... This might be an answer to the problem...


WE HAVE A SOLUTION!!! It seems that the order of the detectors in mugast.detector matters!! Now we start with a dummy MG8, then MG1, MG2, ... And everything is fine!! We think that is because it was taking the wrong calibration files (to be checked).

Joined are (for run 128,137,138,139,151,152,153):
-Ex vs ThetaLab
-Ex for all detectors
-Egamma vs Ex
Fixede775s Sat Feb 29 17:50:47 2020 OttoRunRUNGeneralCD2-AuRun164
*************************
Run : 164
*************************

Start at 2020-02-29 17:42:27.094034

VAMOS+AGATA+MUGAST
CD2+Au Target #2 (250-300ug + 20 umAu)
Trigger

* MG Annular
* MG Trapezoid

Beam intensity 4e+5

Restart in same conditions as run 152 after reloading RCC config and initializing

Pbm with AGATA
Fixede775s Sat Feb 29 18:08:41 2020 OttoRunRUNGeneralCD2-AuRun165
*************************
Run : 165
*************************

Start at 2020-02-29 18:07:20.986327

VAMOS+AGATA+MUGAST
CD2+Au Target #2 (250-300ug + 20 umAu)
Trigger

* MG Annular
* MG Trapezoid

Beam intensity 4e+5

Restart in same conditions as run 152 after reloading RCC config and initializing

Pbm with AGATA on ATC13, we stopped the cluster and wait for debug later

Stop at 2020-03-01 00:21:02.566635
Stop comment: ZMQSpy borken link
Fixede775s Sun Mar 1 00:33:18 2020 OttoRunRUNGeneralCD2-AuRun166
*************************
Run : 166
*************************

Start at 2020-03-01 00:23:26.889299

VAMOS+AGATA+MUGAST
CD2+Au Target #2 (250-300ug + 20 umAu)
Trigger

* MG Annular
* MG Trapezoid

Beam intensity 4e+5

Problem with ZMQSpy solved

Stop at 2020-03-01 04:22:14.420928
Stop comment: ZMQSpyr borken link
Fixede775s Sun Mar 1 04:22:16 2020 OttoRunRUNGeneralCD2-AuRun167
*************************
Run : 167
*************************

Start at 2020-03-01 04:12:30.866591

VAMOS+AGATA+MUGAST
CD2+Au Target #2 (250-300ug + 20 umAu)
Trigger

* MG Annular
* MG Trapezoid

Beam intensity 4e+5

Problem with ZMQSpy solved
Fixede775s Sun Mar 1 08:13:08 2020 OttoRunRUNGeneralCD2-AuRun168
*************************
Run : 168
*************************

Start at 2020-03-01 08:11:13.754980

VAMOS+AGATA+MUGAST
CD2+Au Target #2 (250-300ug + 20 umAu)
Trigger

* MG Annular
* MG Trapezoid

Beam intensity 4e+5

Recover cristal 04A

Stop at 2020-03-01 08:13:41.634716
Stop comment:

Stop at 2020-03-01 11:58:26.013122
Stop comment: checking the filling of the detectors
Fixede775s Sun Mar 1 12:20:52 2020 OttoRunRUNGeneralCD2-AuRun169
*************************
Run : 169
*************************

Start at 2020-03-01 12:07:09.128555

VAMOS+AGATA+MUGAST
CD2+Au Target #2 (250-300ug + 20 umAu)
Trigger

* MG Annular
* MG Trapezoid

Beam intensity 4.3e+5
RUN 169

After checking LN2 detector issue

Stop at 2020-03-01 19:49:20.227166
Stop comment: stop to change a "canule" in AGATA
Fixede775s Sun Mar 1 17:04:43 2020 Marlène FrançoisRUNGeneral Preliminary analysis of runs from 128 up to now (169)
Preliminary analysis with all stat up to now.
Fixede775s Sun Mar 1 20:13:08 2020 OttoRunRUNGeneralCD2-AuRun171
*************************
Run : 171
*************************

Start at 2020-03-01 20:11:57.032998

VAMOS+AGATA+MUGAST
CD2+Au Target #2 (250-300ug + 20 umAu)
Trigger

* MG Annular
* MG Trapezoid

Beam intensity 4.3e+5
RUN 171

canule was changed on AGATA

Stop at 2020-03-02 10:28:31.607441
Stop comment: run change

ELOG Home Page