MUST2 SAMURAI_2018 S3-LEB-LPC SUPERNEMO MUGAST EXPAND SCALP GALATRON HiCARI VELO
  MUGAST, Page 2 of 132  Not logged in MUGAST
Status ExpNbr Date Author Type Categorydown Target-Source Subject
Fixedcom2019 Sat Apr 6 08:18:55 2019 mugastRUNSoftwareCD2Online Scalers run 256 @8h00 am 06/04 for reference
Fixedcom2019 Sat Apr 6 10:57:35 2019 NicolasOFFLINESoftwareCD2time of flight v.s. energy in MUGAST (run 256, all stat)
Fixedcom2019 Sat Apr 6 11:40:08 2019 mugastOFFLINESoftwareCD2 AGATA spectrum in coincidence with MUGAST VAMOS run 256
Fixedcom2019 Sun Apr 7 14:24:18 2019 ValerianOFFLINESoftwareCD2Ex and E gamma with all statistic (run 256+257)
Fixedcom2019 Tue Apr 9 10:44:40 2019 ValerianMUST2SoftwareCD2CsI Calib files from the commissioning for proton
CsI calibration obtained from the proton data of the commissioning of mugast.
Fixede744s Tue Apr 9 18:08:22 2019 Marlène and FrançoisDAQSoftware new inputs in the ADC Mugast
new inputs in the ADC mugast
T_Mugast_HF = input N°2
E_AGATA = agata 42 = input N°3
T_AGATA_HF = N° 4

gains of the signal AGATA 42 were changed from 200 to 50

Pinnede744s Wed Apr 10 11:57:37 2019 A. LemassonOFFLINESoftware VAMOS Conversion HowTo

HOW TO convert a run in VAMOS
  • Do : source $HOME/GoToVamosAna
  • To Convert a Run : MyVAna -d2Ar <RunNr>
  • Otherwise, If you want to convert a single file : MyVAna -d2Ar -f <Infile> <OutFile>
  • Output Root rile is written to : ./RootA/

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
Pinnede786s Wed Apr 10 13:30:48 2019 Valerian, Adrien and Antoine (edit by Louis)OFFLINESoftwareN/AHow to perform analysis for e786s

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


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
Fixede744s Thu Apr 11 11:36:09 2019 ValerianOFFLINESoftwareCH2Comparison between the two e744
Current calibration is off, a shift of -1.5MeV was done to reproduce the previous data.
Fixede744s Thu Apr 11 13:43:26 2019 ValerianOFFLINESoftwareCH2Target position for 14N runs
Fixede744s Thu Apr 11 16:07:59 2019 Valerian and LouisOFFLINESoftwareCH2HF 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
Fixede744s Thu Apr 11 18:20:27 2019 Valerian and DiegoOFFLINESoftwareCH2Timing issue between vamos and mugast
A cut is seen on the TAC between MUGAST and the focal plane multiwire of VAMOS when one select XF or DC0_Y>-1500


Edit: This must be a reconstruction problem as it is not seen in the Raw files (using DC0_X for example)

Edit: This is not only a reconstruction problem as the cut appear again if one select DC0_Y

Edit: We changed VAMOS FAG validation window from 500ns to 800ns
Fixede744s Fri Apr 12 10:12:45 2019 ValerianOFFLINESoftwareCH2Comparison between HF and CATS for ELab ThetaLab
Using the HF show noises that is not seen with CATS on the ToF spectra
Fixede744s Fri Apr 12 14:13:11 2019 Giuseppe D'AgataOTHERSoftwareN/AConverted runs

Runs additionally converted up to now:
70
71
80.0
80.1
81.0
81.1
82
83
84
85

86.1

91
94
95

96.1
97
98
Fixede744s Fri Apr 12 19:44:09 2019 diegoVAMOSSoftware SetAlias script for VAMOS identification
Fixede744s Fri Apr 12 22:44:43 2019 Valerian and DiegoOFFLINESoftwareCH213N measured in Vamos do correspond to protons events in MUST2
Doing a cut on M vs M/Q corresponding to 13N one can see that most of the events do correspond to protons events in MUST2!!!
Fixede744s Sat Apr 13 00:27:08 2019 iulian nicolas Nikola MariluzRUNSoftwareCH2Screenshots run119 v1
Fixede744s Sat Apr 13 22:45:27 2019 Beyhan, Sylvain, JaromirAGATASoftwareN/AAgata yellow phase 1 minute
Agata yellow 1 minute

All the trigers emitted by (every) single crystal were refused by ACQ for 1 minute.
Reason unknown now.
Fixede744s Sat Apr 13 23:19:57 2019 Valerian, Freddy, Iulian and FairouzOFFLINESoftwareCH2Very preliminary results for two protons
Join are very preliminary spectra for the two protons events gated on 13N in VAMOS with a multiplicity 1 event in MUST2. This condition adds a lot of noise.
Fixede744s Sun Apr 14 12:11:52 2019 Valerian and IulianOFFLINESoftwareCH2VERY VERY preliminary results Gamma-p
Around 8-10 events are found in the good energy vs Brho region and Si_T vs Si_E region for the gamma emission.

Joined are :

- the cut done for Energy vs Brho
- the "good" Events plotted on the Si_E vs Si_T spectra for each telescope.


one can see that most events are in, or close to the punch through but some of them ~8-10 are not -> very good candidates for proton after gamma emission

ELOG Home Page