ELOG MUGAST

e775s

Mon Feb 24 17:14:57 2020

*************************
Run : 124
*************************

Start at 2020-02-24 17:05:18.339191

VAMOS+AGATA+MUGAST
CD2+Au Target #1 (350-300ug + 20 umAu)
Trigger
* MG Annular
* MG Trapezoid

Attachment 1: run124_Tof.png

Sun Feb 23 20:50:06 2020

Screenshots from MUGAST

The impact matrix looks fine but there are sectors missing but in the raw we see 13 sectors (instead of 16)

There E-Tof spectra missing because TY is either not working but we checked that TX is working --> TX should be used for MG2, MG5 and MG6
The ToF seems to have 2 components : one when MUGAST has triggered and one when Vamos has triggered.
We see alpha contribution that come from fusino-evaporation on Au that can go up to 120 deg backward.

We put the BT and HT screenshots as a reference

The cooling is at 0 degree.... there is not much alcohol left in the cooler, we will refill tonight.

Attachment 1: e775s_impact_matrix.png

Attachment 2: MG_TOF.png

Attachment 3: MG_TX_raw.png

Attachment 4: MG_TY_raw.png

Attachment 5: BT_MG1.png

Attachment 6: HT_MG.png

Attachment 7: MG_BT2.png

Attachment 8: TAC.png

Fri Jul 19 01:05:26 2019

Brho Change to 0.556 Tm

Moving Plate : Final Position +7mm
with 6 kHz

Slowly increasing

Fri Jul 19 00:59:20 2019

mugast

RUN

RUN 107 - Reference Target Run

Reference Target Run after beam tuning
Brho 0.5854 Tm

Tue Jul 16 19:21:19 2019

Brho = 0.640 Tm

RMN = 3247,742 Gaus (215.630 A)

Q31 = 18.5 A
Q32 = 20.9 A
Q41 = 170.579 A
Q42 = 150.829 A

e793s

Fri Mar 12 10:52:46 2021

Q-Pole tripped this night around 4am at the same time as the dipole but was switch on again only at 9am.

Tue Dec 3 18:14:45 2019

Marlčne & Franco

GRIT

Hardware

Pulser test of new board

The new board that will be installed for MG2 has been tested and validated with a pulser outside of the chamber.

Fri Feb 5 12:44:42 2021

Pulser on MG11 MUFEE Y

I managed to obtain the spectrum with the pulser on the annular (Y side, namely sectors).
The raw strip numbers where I should have the 16 sectors are: 14, 16, 18, 20, 22, 24, 26, 28, 36, 38, 40, 42, 44, 46, 48 and 50.
The 5 strips I could see with the alpha source are: 20, 40, 44, 48, 50.
Now with the pulser I don't see the following strips: 14, 16, 18, 20, 22, 24, 26, 28, 36, 40, 42, 44, 48, 50.
So the pulser apparently doesn't go through most of the channels that are connected to a sector and all the channels that were ok with the alpha source now don't see the pulser...
The plots below are the pulser energy vs the raw strip number with a zoom on the region where I should have all the sectors. The plot below is the projection on X (strip number) of the first plot, now considering all the strips -> only strips connected to sectors don't show the pulser peak.
Concerning the rings, most of them see the alpha source but only few of them (the ones between the two red lines in the last figure attached) correctly display three peaks. The others have many peaks as a result of missing sectors on the Y side.

Attachment 1: pulser_all_channels_MG11Y_05022021.png

Attachment 2: pulser_all_strips_MG11Y_05022021.png

Attachment 3: Working_rings_annular_05022021.png

Proton ToF from VAMOS ToF reconstruction

Sat Jul 13 16:28:30 2019

Comparison between the Proton ToF measured directly with the TAC between MUST and CATS (left) and the one recontructed from the time diference between the time MUGAST-VAMOS and the time Target-VAMOS (recontructed from the Brho) (right)

The resolution of the recontructed time looks slightly degraded with respect to the direct measurement but it is certainly much better than using the HF. Still, the resolution of the reconstructed time may be improved with a fine alignment of the different sections of the PPAC and with a better selection of the M/q in VAMOS.

Attachment 1: TOF_VAMOS.png

Marlčne, Franck, François & Nicolas

Mon Jul 22 17:07:39 2019

BEAM

Profiler conditions for measuring beam intensity

We checked that the measured beam intensity (present case 1.5e7 pps) is independent on the voltage on the profiler. Values from 93 V up to 177 V gave similar results.

Profiler and beam current scaling since 11;10

Tue Jul 23 12:00:25 2019

See also AGATA elog and run-log entry

Procedure to follow during runs

e744s

Fri Apr 12 10:36:09 2019

At the beginning of a run :

Do screenshots of the scalers and add them to the elog.(Say it is at the beginning of the run)

During a run, one should :

Check regularly the scalers.
Look at the different pages on vigru.
Check if there are any problem concerning the Voltages, a window should be prompted to you if it is the case. If the window has FP written it is on the VAMOS side.
Do conversion, see corresponding entry (Or paper next to computer)
Check the last pending issues in the elog and if they are fixed, edit them to fix (any HV trip or over-current are pending and shoudl be switch to fix).

Every hours and before stopping the run:

Do screenshots of the scalers and add them to the elog.(Say at which time it is done)
Do screenshots of all the vigru pages of MUGAST and VAMOS and add them to the elog.

Procedure to convert and calibrate runs

e786s

Mon Jun 24 01:52:00 2019

Here is the updated procedure to convert a run, with VAMOS data.

Every 4Go there will be a file change, to see if there is a file change do :

ls -ltrh /data/mugastX/e786s/acquisition/run/

convert the last 4Go file and add it to the chain using the following step:

Step O: Take your favorite ortholinear keyboard (optional)

Step 1: Login the VAMOS environment and convert the run :

Open a terminal from one of the mugast computer:

Type: source $HOME/GoToVamosAna
Type: MyVAna -d2Ar -f /data/mugastX/e786s/acquisition/run/run_$$$$-DD-MM-YY.HHhMMmSSs /data/mugastX/e786s/acquisition/RootA/r$$$$_000a.root

OR

Type: MyVAna -d2Ar -f /data/mugastX/e786s/acquisition/run/run_$$$$-DD-MM-YY.HHhMMmSSs.N /data/mugastX/e786s/acquisition/RootA/r$$$$_00Na.root

(If you encounter the error on Brho "Could not find the BrhoRef for the run <RunNr> ", Update the ./Calibs/ListBrho.dat file with relevant Brho for RunNr)

Step 2: Analyse the file using the npanalysis program:

Type: exit (<-this exit the environment of VAMOS)
Type: lpcgrit (<-this load the analysis environment )
Type: npp MUGAST
Type: edit the exe.sh to treat releverant run. command should be: npanalysis -D mugast.detector -C Calibration.txt -E ./Reaction/46Ar3Hed.reaction -T ./offline/root_e786svamos/r$$$$_00Na.root AD -O run_$$$$_N.root

(This could be used with any file, either from Offline conversion, or the VAMOS Analysis conversion or the Merged Tree from AGATA)

The run will be created in the NPOutputs folder

Fri Jul 19 15:11:10 2019

mugast

OFFLINE

Procedure for run conversion and analysis

Here is the procedure to convert a run with VAMOS and AGATA data and add those data to the Kinematic plot.

Every 4GB there will be a file change, to see if there is a file change type:

ls -ltrh /data/mugastX/e768s/acquisition/run/

Convert the last 4GB file and add it to the chain through the following steps:

Open a terminal from one of the Mugast computer:
Type: source $HOME/GoToVamosAna
Type: MyVAna -d2Ar -f /data/mugastX/e768s/acquisition/run/run_$$$$-DD-MM-YY.HHhMMmSSs /data/mugastX/e768s/acquisition/run/RootA/r$$$$_000a.root

OR (in case the run is split in more files)

Type: MyVAna -d2Ar -f /data/mugastX/e768s/acquisition/run/run_$$$$-DD-MM-YY.HHhMMmSSs.N /data/mugastX/e768s/acquisition/run/RootA/r$$$$_00Na.root

(If you get the error "Could not find the BrhoRef for the run <RunNr> ", update the ./Calibs/ListBrho.dat file with relevant Brho for RunNr)

Now you would be already able to run npanalysis to analyze the data VAMOS+Mugast with the following procedure:

Type: exit (to exit the VAMOS environment)
Type: lpcgrit (to load the analysis environment)
Type: npp MUGAST
Edit the exe_e768s.sh to specify which runs to analyze. The command should be the following:

npanalysis -D mugast.detector -C Calibration.txt -E ./Reaction/15N7Lit.reaction -T /data/mugastX/e768s/acquisition/run/RootA/r$$$$_00Na.root AD -O run_$$$$_N.root

Type: ./exe_e768s.sh

To convert a run including the AGATA data, the procedure is the following:
Go to the AGATA analysis computer (last on the right close to the window in the acquisition room), open a terminal and type the following commands:

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

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

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

Now you can analyze the file using npanalysis.
The command in the exe_e768s.sh file should now look like:

npanalysis -D mugast.detector -C Calibration.txt -E ./Reaction/15N7Lit.reaction -T /data/mugastX/e768s/acquisition/root_agata/run_00##/Tree_000N.root TreeMaster -O run_00##_N_agata.root

The run will be created in the ./NPOutputs folder.
Bon courage!

Problems with the annular persist

Thu Feb 4 18:16:47 2021

We opened the chamber to verify the connections of the kaptons but they were all well connected. We checked with the tester the conductivity of the kapton YA5 and it was fine so we excluded any problem related to the kapton. The boards are working properly (the pulser is well seen). We have to conclude that the problem comes from the detector. We made another alpha source run and indeed the result is the same as yesterday -> 5 sectors working on Y. We also tried to rise the HV of the annular up to 95V instead of the nominal 80V: the current went to 19 uA but no new sector appeared in the spectra.
Apart from the usual spectra, attached are also the pedestals of MG11, the alpha spectrum for ch48 of MG11_Y (one of the working sectors). The HV were the same as yesterday.

Attachment 1: MM_raw_04022021.png

Attachment 2: MG_X_raw_04022021.png

Attachment 3: MG_Y_raw_04022021.png

Attachment 4: MG_impact_04022021.png

Attachment 5: MM_impact_04022021.png

Attachment 6: pedestals_MG11.png

Attachment 7: LV_04022021.png

Attachment 8: alpha_spectrum_ch48_MG11Y.png

Pending

e793s

Sat Mar 13 05:11:08 2021

Problem with AGATA acquisition started at 4h40

There is a problem with AGATA Acquisition. All the bars in the global status & control are yellow!!!
This problem started at 4h40.
We called the acquisition astreinte but he doesn't know how to fix the problem.
We called Emmanuel but we got on the answering machine. We will call him again at 7 am.

The count rate of AGATA in the scaler looks ok: ~ 1200

Attachment 1: run61-scalers_5h19.png

Problem Crystal 00A during run 140

Thu Jul 25 12:55:19 2019

Problem with crystal 00A at 12h50:
- Very large counting rate 300 k

*Tried a resync as usual but did not work.
* Put in Drain temporarily until issue solved

Ongoing

e793s

Wed Mar 10 21:09:25 2021

mugast (Adrien, Nigel et co)

BEAM

Primary beam issues

The secondary beam intensity has been fluctuating around 4 - 5 x 10**5 Hz most of the evening. 15 mins ago it was realised that it had dropped off to only 1 x 10**5 Hz. As suspected, PCP confirmed that primary beam intensity has dropped off. They are investigating ...

It would be good to have the TI (primary beam intensity) available to monitor here in the daq room.

Sat Jul 20 11:33:01 2019

Christian

OTHER