| Emmanuel C wrote: |
TF1 *fit_1 = new TF1("fit_1","TMath::Exp([0]+[1]*TMath::Log(x)+[2]*pow(TMath::Log(x),2.0)+[3]*pow(TMath::Log(x),3.0)+[4]*pow(TMath::Log(x),4.0))",10,5000); //NRJ traite en keV et efficiency en %
Data
40.000000 3.404000 0.070000
45.000000 6.512000 0.150000
121.782997 14.250000 0.300000
244.692001 11.880000 0.270000
295.938995 11.870000 0.500000
344.276001 11.170000 0.240000
411.114990 9.926000 0.330000
443.976013 11.050000 0.290000
778.903015 8.007000 0.180000
867.388000 7.562000 0.240000
964.130981 7.492000 0.180000
1085.800049 7.110000 0.160000
1112.115967 6.956000 0.150000
1212.949951 6.113000 0.190000
1408.010986 6.157000 0.130000
p0 -9.87216e+01
p1 6.98517e+01
p2 -1.78362e+01
p3 2.00526e+00
p4 -8.41808e-02 |
| Fixed | e793s |
Fri Mar 19 09:54:58 2021 |
Adrien, Freddy and Franco | GRIT | General | 3-alpha | Alpha calibration and noise on MG3 and MG4 after the experiment |
While starting the alpha source runs after the experiment we found unexpected noise on MG3 and MG4 which cannot be excluded just by masking some Y mates (The X mates were already masked for both of them). We cannot figure out the origin of this noise.
Run 652 and 653 -> alpha runs without pedestal suppression
Run 655 -> alpha run during the night with pedestal suppression. Here MG3 and MG4 are not in the trigger.
Run 658 -> alpha run after an attempt to mask some noisy strips. The number of ORD is anyway high (some 10^4) but we see some alphas on MG3 and MG4.
Run 660 -> same as 658 but with higher thresholds on X (8250) and Y (7600 on MG3 and 7950 on MG4) to write less on disk but actually nothing changes. Therefore we are writing about 2.7 GB per hour.
The other runs (654, 656, 657 and 659) can be discarded. |
| Fixed | e793s |
Mon Mar 22 16:35:46 2021 |
OttoRun | RUN | General | N/A | Run67 |
*************************
Run : 67
*************************
Start at 2021-03-22 16:34:11.552975
run67. Time calibrator in TDC VAMOS
PERIOD: 80 ns
Trigger VAMOS
Raw Data: /data/mugastX/e793s/acquisition/run/run_0067.dat.22-03-21_16h34m11s
Raw RootFile: /home/mugast/Analysis_e793s/RootR/r0067_000r.root |
| Fixed | e793s |
Mon Mar 22 18:15:50 2021 |
mugast | RUN | General | N/A | TACS calibration - run 662 |
TACS:
FAG-CATS2 (range 500 ns)
VAMOS-AGATA (range 500 ns)
CATS2-CATS2 (not in modular label) (range 500 ns)
AGATA-CATS2 (range 200 ns)
Time calibrator settings:
640 ns range
20 ns steps |
| Fixed | e793s |
Mon Mar 22 19:04:55 2021 |
mugast | RUN | General | N/A | TACS calibration - run 653 |
TACS:
MUGAST-AGATA (range 2 us)
MUGAST-CATS2 (range 1 us)
MUGAST-CATS2b (range 2 us)
MUGAST-VAMOS (range 2 us)
VAMOS-CATS2 (range 2 us)
Time calibrator settings:
2.56 us range
80 ns steps |
| Fixed | e793s |
Tue Mar 23 10:22:48 2021 |
Emmanuel C | OFFLINE | General | | Efficiency gamma AGATA --- real measurement run70 |
I have been working on the high energy response.
The point is that we do not have source measurement beyond 2 MeV to constrain the fit.
In the attached file, the experimental points are the measured from run 70 in 152Eu source. The fit is then extrapolated up to high energy.
I have simulated the efficiency at 3.5 MeV in GEANT4 including real geometry, missing channels, unefficiency of capsules etc.... The overall agreement was checked on the 1408 line. The 3.5 MeV simulated point is shown. It disagrees strongly with the extrapolation. The blue fit includes the simulated point. It doesn't change the efficiency evaluation < 1.5 MeV but correct the high energy response.
Below, updated parameters
p0 -6.34543e+01
p1 4.24746e+01
p2 -1.00304e+01
p3 1.03468e+00
p4 -3.97076e-02
TF1 *fit_1 = new TF1("fit_1","TMath::Exp([0]+[1]*TMath::Log(x)+[2]*pow(TMath::Log(x),2.0)+[3]*pow(TMath::Log(x),3.0)+[4]*pow(TMath::Log(x),4.0))",10,5000); //NRJ traite en keV |
| Attachment 1: effi.png
|
|
| Pinned | e786s |
Wed Apr 10 13:30:48 2019 |
Valerian, Adrien and Antoine (edit by Louis) | OFFLINE | Software | N/A | How 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 |
| Fixed | e786s |
Fri May 31 09:53:14 2019 |
Marlène | GRIT | General | | Alpha source --> status of detectors |
MG3T has been fixed by changing the X kapton.
I have removed aluminium foil on square detectors, the noise is slightly higher.
MG4T is not working properly : noisy on X but no signal on Y !! I see no triggers on the Y side. I tried to increase bias but it did increase noise. I checked in the last calibration of e744 it was working properly. Also I had to do pedestal realignement for this detector because everything was shifted.
MG7T seem to be slightly different than before. Strips X are hidden from the trigger because it became suddenly noisy. |
| Fixed | e786s |
Mon Jun 3 18:00:10 2019 |
Marlène | GRIT | General | | MUGAST detectors status --> MG4T |
The problem of MG4T ha sbeen solved by changing the feedthrough.
The pulser on Y was not working and we were seeing no events (no ORD) because there was a problem with the bias of board. The issue is due to the feedthrough.
So now MG4T (HT &BT) are plugged in a free feedthrough (below MG1T) and I see pulser signals on Y.
The bias seems to apply normally on all detectors (in the dark).
The pulser is seen on each boards.
I have put back aluminium foil on square but I could not test it. |
| Fixed | e786s |
Wed Jun 12 17:59:01 2019 |
mugast | OTHER | Software | | Online Energy Calibration |
| Updated Online Energy calibration for MUGAST, based on run_0231 data |
| Attachment 1: x_E_cal.png
|
|
| Attachment 2: y_E_cal2.png
|
|
| Fixed | e786s |
Wed Jun 12 18:11:04 2019 |
mugast | OTHER | Software | | Online Energy Calibration |
|
| Fixed | e786s |
Wed Jun 19 10:09:10 2019 |
mugast | MUST2 | Hardware | N/A | Time calibrator cabled |
range 640 ns
period 20 ns |
| Fixed | e786s |
Wed Jun 19 12:02:07 2019 |
OttoTime | RUN | General | N/A | TimeCalibratorRun |
*** Run Time Calibrator FSC ***
- Run: 237
- MUVI: MUVI1
- Side : MUFEE X (Junction)
- Telescope: 1, 2, 3, 4 |
| Fixed | e786s |
Wed Jun 19 12:24:43 2019 |
OttoTime | RUN | General | N/A | TimeCalibratorRun |
*** Run Time Calibrator FSC ***
- Run: 238
- MUVI: MUVI1
- Side : MUFEE Y (Ohmic)
- Telescope: 1, 2, 3, 4 |
| Fixed | e786s |
Wed Jun 19 12:48:13 2019 |
OttoTime | RUN | General | N/A | TimeCalibratorRun |
*** Run Time Calibrator FSC ***
- Run: 239 - MUVI: MUVI2
- Side : MUFEE X (Junction)
- Telescope: 1, 2, 3, 4 |