ELOG MUGAST

Timing change: -50 ns on CATS stop

Mon Jun 24 13:57:46 2019

We removed 50 ns of delay to the CATS signal used for the stop of the TOF (CATS-MUGAST/MUST) because we were at the edge of the FAG.
See the attached picture for the current situation:
Green: MUGAST/MUST2 ORD
Pink: FAG
yellow: CATS2
blue: CATS validated by FAG

Attachment 1: TimingCATSMUGAST.jpg

Mon Jun 24 20:39:54 2019

Attachment 1: scalers_run55_24062019_20h37.png

Wed Jun 26 03:46:09 2019

Screenshots at 3h30 on the 26th of june during RUN 58

Attachment 1: run58_CATS_26062019_3h39.png

Attachment 2: run58_Correl_26062019_3h39.png

Attachment 3: run58_TAC_26062019_3h39.png

Attachment 4: run58_MGdETOF_26062019_3h39.png

Attachment 5: run58_MGImpact_26062019_3h39.png

Attachment 6: run58_MMImpact_26062019_3h39.png

Run conversion with AGATA

Wed Jun 26 03:55:20 2019

To convert a run including the AGATA data, here is the procedure (Only if you know reasonably what you are doing Wink

1- Go to the AGATA Analysis computer, open a terminal and execute the following commands:

> a4
> t e786s
> cd Replay
> ./do_global_replay.sh -run ## (## is the run number you want to convert)

2- When it is finished copy the root file to the GANIL world:

> mkdir /dataganil/e786s/acquisition/root_agata/run_00##/
> cp ./run_00##/Out/Analysis/Tree_00*.root /dataganil/e786s/acquisition/root_agata/run_00##/.

AGATA validation problem (solved)

Wed Jun 26 04:54:07 2019

Since about 4h20, we realized that AGATA validated events and timestamps have suddenly dropped on the AGATA display (yellow bars instead of green).
We checked the counting rate on MUGAST, VAMOS and FAG and there is no obvious problem on this side. Same for the MUGAST/VAMOS data on disk.

We call Emmanuel...

Problem solved by restarting entirely GTS Tree (that was broken).

Restarted at 5h37 with run 59. (it took about 30 min).

Offline analysis run 56 and 58

Wed Jun 26 05:58:23 2019

Attachment 1: run56-58_analysis.png

Attachment 2: run56-59_analysis_gammarays.png

Attachment 3: run56_analysis.png

Attachment 4: run58_analysis.png

AGATA validation problem - again - during run 59

Wed Jun 26 07:01:00 2019

30 min after Emmanuel left (around 6h00), the AGATA problem of validation reappeared...

TO BE SOLVED....

Update of CATS calibrations

Wed Jun 26 07:04:06 2019

New calibrations in :
/home/mugast/analysis/nptool/Projects/calibration/cats/CATS2_X.vamos2019_e786s.npt
/home/mugast/analysis/nptool/Projects/calibration/cats/CATS2_X.vamos2019_e786s.npt

Calibration.txt was modified accordingly.
Attached are the CATS positions for run 56 and 58 (after the central strip problem)

Attachment 1: run56_cats_newcal.png

Attachment 2: run_58_cats_newcal.png

Fri Jun 28 08:54:50 2019

Daniele Mengoni wrote:

screenshots run 74 attached

frequent error message on the FP DC Wi1 --> defqlt. The elog said so, card tripped, but spectra are still present .. puzzling

Put the voltage back at 8h00 when i arrived.

CATS scaler not compatible with beam rate

Fri Jun 28 08:57:21 2019

The CATS scaler si now around 100-120 kHz while the beam rate is still 40 kHz.

I checked the CATS signal and there is clearly noise who induce double logic signals. Not all of them are validated by FAG.

We should raise the threshold- call sebastien

9h32 : Stop beam to enter and raise the threshold.

Attachment 1: ScalerCATSproblem.png

Scaler evolution + scaler file reader

Thu Jul 25 17:19:52 2019

Attached is a plot of several scaler (frequency as a function of time) for all data from run 120 to 140.

A software was written to process the scaler.dat files and is located in:
~/analysis/scalereader/

you can find an example of how to execute it in:
~/analysis/scalereader/exe.sh

Attachment 1: ScalerDisplay_r120_140.png

Scaler summary since r120

Sat Jul 27 04:50:45 2019

run 120 - 152

/home/mugast/analysis/scalereader/out/Chain.C

Attachment 1: scaler_update.png

Sat Jul 27 11:49:40 2019

I posted a detailed entry during the night about the evolution of the annular detector but it was deleted somehow...

Signals on 3-4 segments were entirely lost between run 139 and 140. It creates a lot of holes on the impact matrix.

An increase of leakage current from 0.2 to 1.4uA occurred at about the same moment:

*Wed Jul 24 21:44:44 2019 --> 0.2 uA
*Thu Jul 25 06:53:15 2019 --> 0.6 uA
*Thu Jul 25 13:23:48 2019 --> 1.4 uA
*Thu Jul 25 22:25:35 2019 --> 1.3 uA
*Fri Jul 26 07:26:23 2019 --> 1.9 uA

Screenshots about this issues are in the e768s screenshot folder.

Edit : Adding some related files from the folder, not sure if the good ones (Sylvain)

Attachment 1: annular_diag_run139_0.pdf

Attachment 2: annular_diag_run140_0.pdf

Attachment 3: annular_diag_run149_0.pdf

Attachment 4: annular_diag_run152_0.pdf

Attachment 5: HV7.pdf

Mon Feb 24 08:46:15 2020

After a quick offline check, it seems that we get MUGAST data only if MUGAST has triggered (GATCONFMASTER = 1,2,4).

In the de/TOF spectra the different structure in time are thus not due to different timing between VAMOS and MG triggers.

Attachment 1: r116_GATCONFMASTER.png

Attachment 2: r116_DSSDE_GATCONFMASTER.png

Fri Apr 12 02:05:34 2019

Changed from Target 1 hole to Target 2 (104microns).

e744s

Fri Apr 12 04:13:49 2019

TAC of
- MUGAST-HF : HFvalidated is suspected to come every 200ns after MUGAST, it suggests to go to a range of 500ns
- T_SI_CATS1 : CAST1 stop comes before T_SI start (roughly 100ns to be delayed)

Spectra Run 135 25/07/19 4:00

Thu Jul 25 03:58:19 2019

Second snapshot of run 135
Spectra refreshed

Attachment 1: Scalers_run135b

Attachment 2: MG_TOF_run135b

Attachment 3: MM_deE_run135b

Attachment 4: MM_ETOF_run135b

Attachment 5: MG_IMPACT_run135b

Attachment 6: MG_ETOF_run135b

Mon Jul 22 14:45:34 2019

Intensity = 1.3e7 pps

Beam position shift compared to this morning 8:30

x: -1.8 mm
y: +3.3 mm

Attachment 1: Beam_profile_run125_22July2019_14h39.jpg