MUST2 SAMURAI_2018 S3-LEB-LPC SUPERNEMO MUGAST EXPAND SCALP GALATRON HiCARI VELO
  MUGAST, Page 1 of 132  Not logged in MUGAST
Statusdown ExpNbr Date Author Type Category Target-Source Subject
PinnedTEST Tue Feb 26 09:30:21 2019 FreddyOTHERHardwareN/ACabling - MUVI / HT-BT / SA-SL
Cabling scheme - to update until final
Attachment 1: Cabling_2019_03_01.pdf
Cabling_2019_03_01.pdf
Pinnedcom2019 Mon Apr 1 11:02:00 2019 Adrien MattaMUST2HardwareN/ASwitching on and off LV/HV for MUST2 crate
HVM group could be used to switch on and off the LV and HV for the MUST2 crate.

The command could be lauched from the analysis environment: start a terminal and type:

> lpcgrit

This will connect to lpcgrit and source the correct environment.

Be careful: HV on mugast should not be on when the BT are off, this could damaged the PAC:
  • Power up sequence : switch on BT first, then HV
  • Power down sequence :Switch off HV first, then BT.


To switch on group use:
> hvm_group <group name> <on|off>

The following group exist:

  • BT-MGA -> Low voltage for GRIT trapezoid and annular detector
  • BT-MGB -> Low voltage for GRIT trapezoid
  • BT-MUST -> Low voltage for MUST2 and 90 deg
  • HV-MG -> GRIT Trap and Annular HV
  • HV-MUST -> MUST2 Si and CsI HV


The programme return only once the voltage finished ramping up, so be patient. Once the voltage are set, it will print-out the relevant channel. If a channel trip, the programm print out the status of all the channel.


NB: over voltage on +5V channel is "normal" and ignored as an error by the program

To check the status of the voltage crate use the hvm_print command:


to print VAMOS and MUST2:
> hvm_print

to print MUST2:

> hvm_print MUST2

to print VAMOS:
> hvm_print VAMOS






Pinnedcom2019 Thu Apr 4 14:45:53 2019 ValerianOTHERHardwareN/ASurveyor's measurements
Summary of the Surveyors. Joined the pdf and the Excel file
Attachment 1: GANIL-0057_E744_I-Stefan.pdf
GANIL-0057_E744_I-Stefan.pdf GANIL-0057_E744_I-Stefan.pdf GANIL-0057_E744_I-Stefan.pdf GANIL-0057_E744_I-Stefan.pdf GANIL-0057_E744_I-Stefan.pdf
Attachment 2: E744_XYZ_deÌtecteurs_Si.xlsx
Pinnedcom2019 Fri Apr 5 23:34:46 2019 Adrien et ValerianOFFLINEGeneralN/AConverting data and adding stat to Kine Plot
Here is a procedure to convert a run and add data the Kinematic plot.

Every 4Go there will be a file change, convert the file and add it to the chain using the following step:

Step O: Take your favorite ortholinear keyboard

Step 1: Login in the right environment

  • open a terminal from one of the mugast computer
  • type lpcgrit to login to lpcgrit and source the right environmt
  • you should see red lpcgrit invite of command


Step 2: Convert the file using the offline program
This Convert the file from the ganil .dat file and contained only MUGAST and CATS stuff

  • type npp MUGAST/offline in the terminal to reach the correct folder
  • ./Offline run_com2019/run_0ZZZ-DD-MM-YY.HHhMMmSSs root_com2019/run_ZZZ_0.root
  • OR
  • ./Offline run_com2019/run_0ZZZ-DD-MM-YY.HHhMMmSSs.R root_com2019/run_ZZZ_R.root

Step 3: Analyse the file using the npanalysis program
This could be used with any file, either from Offline conversion, or the VAMOS Analysis conversion or the Merged Tree from AGATA.
  • type npp MUGAST in the terminal to reach the correct folder
    there is an error below caused by the ortholinear keyboard, I guess, corrected using a normal keyboard:
  • npanalysis -D mugast.detector -C Calibration.txt -E ./Reaction/16Odp.reaction -T offline/root_com2019/run_0253.root AutoTree -O PhyZZZ.root
  • The run will be created in the NPOutputs/ folder

Step 4: Add the file to the KineMacro
  • vim macros/Kine.cxx
  • Add the new file in the LoadChain method
  • root macros/Kine.cxx
  • Enjoy the soothing feeling of a smooth knematic line during a late night shift.
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
Pinnede768s Sat Jul 27 04:12:57 2019 Sylvain & FreddyBEAMGeneralLiFRun 152 - Scaler & screenshot + Beam profile
Attachment 1: Tab_8bis_run152_4.png
Tab_8bis_run152_4.png
Attachment 2: IC_IC_run152_4.png
IC_IC_run152_4.png
Attachment 3: REC_run152_4.png
REC_run152_4.png
Attachment 4: IC_run152_4.png
IC_run152_4.png
Attachment 5: MW_run152_4.png
MW_run152_4.png
Attachment 6: DC_E_run152_4.png
DC_E_run152_4.png
Attachment 7: DC_Y_run152_4.png
DC_Y_run152_4.png
Attachment 8: DC_X_run152_4.png
DC_X_run152_4.png
Attachment 9: Tab_10_run152_4.png
Tab_10_run152_4.png
Attachment 10: Tab_9_run152_4.png
Tab_9_run152_4.png
Attachment 11: Tab_8_run152_4.png
Tab_8_run152_4.png
Attachment 12: MG_IMPACT_MATRIX_run152_4.png
MG_IMPACT_MATRIX_run152_4.png
Attachment 13: SCALERS_run152_3.png
SCALERS_run152_3.png
Attachment 14: index.jpg
index.jpg
Pinnede768s Sat Jul 27 06:47:16 2019 Sylvain & AndreaOTHERGeneralLiFWater tray of MUGAST air conditioner cooling system is almost full
During a room inspection it was notice that the water tray used as an output of the fan system which is cooling MUGAST electronic crates is almost full of water. The floor is dry but the we suspect a leakage from the air conditioner. To avoid to flood the floor we took some of the water and put in in the water tray of the fan system located in front of VAMOS.

One would probably need during the day to investigate the origin of this water.
Pinnede775s Thu Feb 27 12:44:37 2020 NicolasOFFLINESoftware How to produce control spectra
In /home/mugast/analysis/nptool/Projects/MUGAST/e775s directory there is the Control.C macro which draws: Ex, Ex vs Eg and Elab vs thetalab for each run (run number must be given in argument) or for chained runs (argument must be 0)
Pinnede775s Thu Feb 27 16:35:26 2020 NicolasOFFLINESoftware How to produce control spectra

Nicolas wrote:
In /home/mugast/analysis/nptool/Projects/MUGAST/e775s directory there is the Control.C macro which draws: Ex, Ex vs Eg and Elab vs thetalab for each run (run number must be given in argument) or for chained runs (argument must be 0)



A new file has been created to look into the CD2 target runs : Control_CD2.C
Pinnede793s Tue Mar 9 09:35:18 2021 AdrienOTHERGeneralN/AE793s proposal
Attached is the proposal of the experiment.
Attachment 1: Proposal_K48_by_dp_MUGAST_FINAL.pdf
Proposal_K48_by_dp_MUGAST_FINAL.pdf
Pinnede793s Wed Mar 10 13:10:14 2021 AdrienBEAMGeneralCD2Kinematical line from Ti contamination
In black the Kinematical line for states known to be populated strongly in 47Ti(d,p).
In blue range of the states of interrest.

The contamination is in a different region and should not cause any issue.
Attachment 1: KineTiK.pdf
KineTiK.pdf
Attachment 2: Kine.cxx
void AddTiStates(double E);

void Kine(){
  
  
 NPL::Reaction K("47K(d,p)48K@362");
  
 // K states
 auto g = K.GetKinematicLine3();
 g->SetLineColor(kAzure+7);
 g->SetLineWidth(3);
 g->Draw("ac");
 K.SetExcitationHeavy(4);
 g = K.GetKinematicLine3();
 g->SetLineColor(kAzure+7);
 g->SetLineWidth(2);
 g->SetLineStyle(1);
 g->Draw("c");

 AddTiStates(0); 

 AddTiStates(0); 
 AddTiStates(0.969); 
 AddTiStates(2.2292); 
 AddTiStates(2.419); 
 AddTiStates(3.223); 
 AddTiStates(3.332); 
 AddTiStates(3.622); 
 AddTiStates(4.388); 
 AddTiStates(4.458); 
 AddTiStates(4.719); 
 AddTiStates(4.852); 
 AddTiStates(5.151); 
   
  }

void AddTiStates(double E){
  
 NPL::Reaction Ti("47Ti(d,p)48Ti@362");
   // Ti states
 Ti.SetExcitationHeavy(E);
 auto g = Ti.GetKinematicLine3();
 g->SetLineWidth(1);
 g->SetLineStyle(2);
 g->Draw("c");


  
  }
Pinnede793s Fri Mar 12 15:48:35 2021 AdrienRUNGeneralN/AVamos D and Q value and MW HV
Pinnede793s Fri Mar 12 15:50:12 2021 AdrienRUNGeneralN/AVamos D and Q value and MW HV
Attached are the value for D and Q pole of vamos in case they trip.
Also attached is the computer driving the HV of the focal plan.
Attachment 1: 1613EC0C-1F4A-4933-B90A-D98A37421BFF.jpeg
1613EC0C-1F4A-4933-B90A-D98A37421BFF.jpeg
Attachment 2: 4ACA3448-35FF-472C-977C-E642B4ADE6A6.jpeg
4ACA3448-35FF-472C-977C-E642B4ADE6A6.jpeg
Pending  Fri Jul 26 11:25:46 2019 UK refugeesOTHERGeneral Be positive and the experiment will work if we put lead in our pencil
Attachment 1: bojoonazipwire.jpg
bojoonazipwire.jpg
PendingTEST Fri Jul 26 13:12:59 2019 OttoH.V.OTHERHardwareN/AHVM_ERROR
*** hvm watcher error ***
FP_CATS4 Slot: 2 (A1821HMP) Channel:10 Vmon: 515 V Imon: 0.96 uA Status: OVER CURRENT

FP_CATS5 Slot: 2 (A1821HMP) Channel:11 Vmon: 12.5 V Imon: 0 uA Status: INTERNAL TRIP

PendingTEST Tue Jan 21 17:55:12 2020 MarlèneMUST2Hardware Ovv error on the -5V of CAEN boards
The Ovv error shows on the -5V (first one) of the 3 board (5,3.3,10V for MUST2§squares)
It means that the voltage is over the asked value.
If we ask 5V, we get 5.5V in reality

We changed for 4.5V and we get 5V. The current is different from the one on the MUGAST BT box but we don't know how many detectors are connected.
We exchanged cables and found the same current in the other board, so we guess that it is still working properly.
A check of stability should be done.
Attachment 1: BT_referenve_5V_cables_inv_a_comp_referenve_5V_partMUST2
Attachment 2: BT_referenve_5V_partMUST2_cables_inv_a_comp_referenve_5V
Attachment 3: BT_referenve_5V_partMUST2
Attachment 4: BT_referenve_5V
PendingTEST Mon Feb 24 09:16:59 2020 OttoH.V.OTHERHardwareN/AHVM_ERROR
*** hvm watcher error ***
FP_CATS4 Slot: 2 (A1821HMP) Channel:10 Vmon: 0.5 V Imon: 0.06 uA Status: INTERNAL TRIP

FP_CATS5 Slot: 2 (A1821HMP) Channel:11 Vmon: 544.5 V Imon: 0.04 uA Status: OVER CURRENT

PendingTEST Mon Feb 24 11:54:50 2020 OttoH.V.OTHERHardwareN/AHVM_ERROR
*** hvm watcher error ***
FP_CATS1 Slot: 2 (A1821HMP) Channel:7 Vmon: 0.75 V Imon: 0 uA Status: INTERNAL TRIP

FP_CATS2 Slot: 2 (A1821HMP) Channel:8 Vmon: 49.5 V Imon: 0 uA Status: INTERNAL TRIP

PendingTEST Tue Feb 25 14:43:16 2020 OttoH.V.OTHERHardwareN/AHVM_ERROR
*** hvm watcher error ***
FP_CATS0 Slot: 2 (A1821HMP) Channel:6 Vmon: 6.5 V Imon: 0 uA Status: INTERNAL TRIP

FP_CATS2 Slot: 2 (A1821HMP) Channel:8 Vmon: 541 V Imon: 0.391 uA Status: OVER CURRENT

ELOG Home Page