ELOG MUGAST

Sat Mar 13 09:19:14 2021

ONLINE

run62 screenshots at 9h10

CD2

Online spectra reset at 9h20

Attachment 1: run62_MG_IMPACT_9h10.png

Attachment 2: run62_MM_ToF_9h10.png

Attachment 3: run62_MM_DeE_9h10.png

Attachment 4: run62_MG_ToF_9h10.png

Attachment 5: run62_TAC_9h10.png

Attachment 6: run62_FSC_9h10.png

Attachment 7: run62_Vamos-MW_9h10.png

Attachment 8: run62_MM_IMPACT_9h10.png

Attachment 9: run62_Theta_E_9h10.png

Attachment 10: run62_scaler_9h15.png

Sat Mar 13 10:14:16 2021

VAMOS

Vamos tripped @ 10:10 & fixed

Vamos tripped around 10:10. we switched back 3 HV on
Online spectra reset to check

Attachment 1: run62_scaler_9h16.png

Sat Mar 13 11:16:38 2021

BEAM

beam lost and back

we loose the beam around 11:12, it should be back in few minutes according to pcp.

11:18: the beam is back (3.5E5 pps)

Sat Mar 13 11:52:26 2021

A security problem occurs at a door near CSS1 ( AFR alarm ), need to call the security to fix the problem
The person needs to come so it will take ~1h

Sat Mar 13 12:07:32 2021

ONLINE

run 62 screenshots at 11h55

CD2

Attachment 1: run62_Theta_E_11h55.png

Attachment 2: run62_MG_IMPACT_11h55.png

Attachment 3: run62_MM_IMPACT_11h55.png

Attachment 4: run62_Vamos-MW_11h55.png

Attachment 5: run62_FSC_11h55.png

Attachment 6: run62_TAC_11h55.png

Attachment 7: run62_MG_ToF_11h55.png

Attachment 8: run62_MM_DeE_11h55.png

Attachment 9: run62_MM_ToF_11h55.png

Attachment 10: run62_scaler_graph_13h44.png

Sat Mar 13 14:41:28 2021

Beam is back ~ 14h35, safety problem fixed
PCP said that the source is unstable so the beam intensity will fluctuate

Attachment 1: run62_scaler_graph_14h48.png

run63 screenshots at 00h45 (16/03)

Tue Mar 16 00:54:29 2021

Attachment 1: run63_Etheta_00h40.png

Attachment 2: run63_mgimpact_00h40.png

Attachment 3: run63_mmimpact_00h40.png

Attachment 4: run63_mmtof_00h40.png

Attachment 5: run63_mmdE_00h40.png

Attachment 6: run63_mgtof_00h40.png

Attachment 7: run63_tac_00h40.png

Attachment 8: run63_vamos_00h40.png

Attachment 9: run63_fsc_00h40.png

Attachment 10: run63_sclalers_00h50.png

Tue Mar 16 01:31:37 2021

Beam intensity increased

We asked for a beam intensity increase around 01h10
The slits L5 were opened and more power (~ 100 W) on primary target
Now ~ 5.6e5 pps on Cats2

Attachment 1: run63_sclalers_01h35.png

run63 screenshots at 03h45 (16/03)

Tue Mar 16 03:58:13 2021

Beam intensity fluctuates from 5e5 pps to 6e5 pps

Attachment 1: run63_mgimpact_03h45.png

Attachment 2: run63_mmtof_03h45.png

Attachment 3: run63_mmdE_03h45.png

Attachment 4: run63_mgtof_03h45.png

Attachment 5: run63_tac_03h45.png

Attachment 6: run63_fsc_03h45.png

Attachment 7: run63_vamos_03h45.png

Attachment 8: run63_Etheta_03h45.png

Attachment 9: run63_mmimpact_03h45.png

Attachment 10: run63_sclalers_03h35.png

Tue Mar 16 04:06:46 2021

crystal 12B counting rate is too low ~ 5 / s compared to an average of ~ 80/s - 100/ s for the other crystals
and 05B counting rate is too high from time to time reaching ~2000/s
but every thing is "green" ?!

Issue solved By Emmanuel Clement at 10h45

summary of run#63 @06:00hrs

Tue Mar 16 06:08:02 2021

we had seen sufficient decrements in the beam current from time to time in the last few hours, everything else is going smooth so far..

Attachment 1: Screenshot_from_2021-03-16_06-13-27.png

Attachment 2: Screenshot_from_2021-03-16_06-12-57.png

Attachment 3: Screenshot_from_2021-03-16_06-12-05.png

Attachment 4: Screenshot_from_2021-03-16_06-11-48.png

Attachment 5: Screenshot_from_2021-03-16_06-11-32.png

Attachment 6: Screenshot_from_2021-03-16_06-11-12.png

Attachment 7: Screenshot_from_2021-03-16_06-10-59.png

Attachment 8: Screenshot_from_2021-03-16_06-10-46.png

Attachment 9: Screenshot_from_2021-03-16_06-10-34.png

Attachment 10: Screenshot_from_2021-03-16_06-09-56.png

Tue Mar 16 07:22:12 2021

Beam intensity decrease

The beam intensity decreased around 6h55 to less than 1e5 pps
It is due to a change of the state of the source, PCP is working to increase the intensity

Attachment 1: run63_sclalers_07h20_16march.png

Run 56 : AGATA gamma rays in coincidences with VAMOS, MUST2 and/or MUGAST

e786s

Tue Jun 25 03:44:12 2019

As attachment are some gamma spectra we obtained while trying several conditions on the run 056.

*Beam excitation has been investigated by gating on PID in VAMOS. Both 46Ar and 47K were selected. Excitation of 46Ar appears clearly while no clear conclusions could be drawn for the 47K.

*46Ar(3He,d)47K was investigated gating 47K in VAMOS and requiring an event in MUGAST (no specific gate could be performed on deuteron). Data size is very small but the maximum of the distribution is very close to the energy of the expected gamma ray from 47K.

*Fusion-evaporation of beam tqrget materials were investigated by requiring proton PID in MUST2. Due to the large number of possible fragments is not not possible to clearly identify the nature of the first to observed gamma ray. Yet the highest energy might correspond to a known gamma transitions in 87Zr in the case of fusion-evaporation with HAVAR window

Sylvain & Louis

Attachment 1: Run56_BeamExcitation.png

Attachment 2: run56_K47plusMugast.png

Attachment 3: run56_FusionEvaporation.png

Preliminary spectroscopic factors

Sat Mar 13 19:54:47 2021

1) Preliminary spectroscopic factors has been extracted for the first 2- exited state @ 143 keV and for the 0- excited state @ 1985 keV. DWBA calul has been performed by cyril for a p3/2 transfer at 0MeV and a p1/2 transfer at 2MeV. Experimental differential cross section has been extracted by normalising the number of counts with the total number of incoming 47K (from CATS div), the number of deuteron in the target, and correcting from MUGAST geometrical efficiency (computed by franco for the gs) and from AGATA efficiency (with the energy depence given by Emmanuel). The 1p3/2 C2S of the first 2- state was found to be 0.22. The 1p1/2 C2S of the 0- excited state was found to be 0.88.

2) gg analysis from Chloé identified a new transition at 997keV in coincidence with the 143 keV gamma. Ex spectra gatted on the 997 keV transition is shown. One can identified a clear state at about 1.1MeV corresponding to the 998+143 gamma cascade. A second clear state is identified at 2.2 MeV but no 1.2MeV gamma has been identified to complete the gamma cascade of this state.

3) the usual analysis plots updated with full statistics.

Attachment 1: C2S.png

Attachment 2: gg_gEx.png

Attachment 3: AnaPlot.png

Ex vs Eg analysis and C2S

Mon Mar 15 13:36:42 2021

Louis wrote:

1) Summary of the the Ex vs Eg analysis with all the gamma ray identified highlighted in red. Green line shows the corresponding position of the excited states.

2) C2S extracted from DWBA analysis for the 0.143 (p3/2), 1.130 (p1/2), 1.985 (p1/2) and the 4 MeV (f7/2) states

3) A gamma ray transition is observed from the unbound states of 48K. Interesting is to notice that this 367 keV transition appear only for those states and that no high energy gamma are observed here.

4) usual Analysis plot

=> as regard as the unbound 48K*>Sn at 6MeV, the gamma ray at 361keV comes from the 1st excited state in 47K.
the other low gamma ray (2234keV) is not observed in coincidence with Eg=280keV or Eg=143keV.

Time calibration for e744

e744s

Wed Apr 10 11:24:52 2019

Time calibration has been done for Mugast and MUST2 using run 17 to 22.
Calibration file are in:
/home/mugast/analysis/nptool/Projects/calibration/Time/Coeff/e744
Plot of calibration run after calibration are shown for MUST2

Attachment 1: TimeCalibMM.png

Brho and energy of the 14O beam

e744s

Fri Apr 12 06:51:59 2019

Attachment 1: DSC_3261.JPG

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