| Status |
ExpNbr |
Date |
Author |
Type |
Category |
Target-Source |
Subject |
| Fixed | e768s |
Mon Jul 22 17:54:49 2019 |
Christian and Jeremie | AGATA | General | LiF | Comparison EGamma 19Ne, Q8 vs Q9 |
1) Beam velocity from VAMOS for AGATA doppler correction. Beta is understandable for the three main charge states seen (with Q9 and Q10 as the transfer states, and centroid shifted higher for Q10 state, possibly because of reduced acceptance for the very high-lying states.
2) Entire doppler corrected gamma-ray spectrum. Blue is transfer (Q9), red is fusion evaporation (Q8). 1880 keV line only seen in fusion evaporation as expected, 13/2+ state.
3) Zoom at the region around 2.5 MeV. Note that |
| Fixed | com2019 |
Tue Apr 2 16:24:06 2019 |
marlene freddy | OTHER | General | N/A | Commissioning proposal |
|
| Fixed | e768s |
Mon Jul 22 16:54:33 2019 |
Marlène, Franck, François & Nicolas | BEAM | General | | Cheking beam transmission from G1 profiler to VAMOS |
Goal:
Estimate beam transmission from profiler to VAMOS (FP)
Method:
1. Beam intensity is reduced with the pepper pot 1/9 and by closing slits after the 15O target production and the accelerators so that the beam quality (emittance, etc...) is not affected.
2. VAMOS plate is removed to allow the direct beam detection
3. LiF (1.25 mg/cm2, number 1) is in position
Results:
1. beam intensity at G1 profiler ~ 4e4 pps
2. VAMOS FP ~ 2e4 pps
Discussion:
1. There is a factor of two loss between the profiler and VAMOS. Taken this factor into account in the g-ray yield estimate (see post ..) the numbers of 1297- and 1340-keV g-rays is in line with what is expected from cross-section calculation.
2. Loosing a factor of two means a substantial amount of 15O is implanted in the pipe/target frame/MUST2 masks. A dedicated AGATA activation measurement could be performed to cross-check this factor of two. |
| Fixed | e768s |
Tue Jul 23 14:33:03 2019 |
Marlène, Yorick, Faïrouz & Nicolas | BEAM | General | | Cheking beam transmission from G1 profiler to VAMOS |
Goal:
Estimate beam transmission from profiler to VAMOS (FP)
We question whether the factor of two found yesterday (VAMOS/Profiler ~ 0.5) could be due:
1. to an incorrect measurement of the beam intensity with the profiler
2. a charge state equilibration in the target (LISE++ calculation indicates 8+/7+ = 85%/15%)
Same conditions as yesterday:
1. Beam intensity is reduced with the pepper pot 1/9 and by closing slits after the 15O target production and the accelerators so that the beam quality (emittance, etc...) is not affected.
2. VAMOS plate is removed to allow the direct beam detection
Results:
We measure in VAMOS with the LiF target and with the target ladder totally removed. In the latter case, direct beam 15O(8+) is sent in VAMOS and no charge state effect enter into the game.
1. Beam intensity at G1 profiler ~ 6.5e4 pps
VAMOS (FP) + no target ~ 3.8e4 pps
2. Beam intensity at G1 profiler ~ 3.8e4 pps
VAMOS (FP) + thick LiF (nb 1) ~ 2.0e4 pps
Discussion:
We find the same results as yesterday, e.g. a factor of two attenuation between the profiler and VAMOS. If part of this loss would happen in the pipe/target/MUST2 mask, this should be observed in AGATA which is not the case. Could it be that the PPAC in VAMOS is not as efficient as announced at the beginning of the campaign (98%)? This must be checked when we get beam back later on.
Note:
While doing the above measurement, we observed a factor of 3 loss between profiler AR.Gaz13 and G1.Gaz31. Numbers follows:
L3.GAZ42 AR.GAZ13 G1.GAZ31
2.1e4 1.5e4 4.1e3
1.4e5 1.0e5 2.5e4
??? 1.8e5 6.5e4 |
| Fixed | com2019 |
Mon Apr 8 10:58:16 2019 |
Adrien | OFFLINE | General | CD2 | Checked alignement of the different Silicon at backward angle |
Here is a plot of Ex for all the com. stats detector by detector.
The Spectrum are overall well aligned. |
| Fixed | e768s |
Tue Jul 30 07:49:09 2019 |
Teodora & Franco | RUN | General | LiF | Check beam intensity and profile run158 h 8:00 |
|
| Fixed | e768s |
Fri Jul 26 23:58:08 2019 |
Andres & Franco | RUN | General | LiF | Check beam intensity and profile run152 h 23.40 |
|
| Fixed | e768s |
Fri Jul 26 19:47:18 2019 |
Andres & Franco | RUN | General | LiF | Check beam intensity and profile run152 h 19.30 |
|
| Fixed | e744s |
Thu Apr 11 02:54:09 2019 |
mugast | RUN | General | | Changing Brho to 0.51 Tm starting run 70 |
|
| Fixed | e793s |
Tue Mar 10 18:46:13 2020 |
Franco & Marlène | GRIT | Hardware | | Changes in MUGAST |
- MG6 (FZ) is disconnected.
- MG7 (500um) is dismounted and MG8 (375um) is replacing it.
- The Y kapton of the annular has been changed.
Attached the alpha source spectra acquired on March 11th after the changes described above.
- MG8 looks better than MG7 but it looks like a part on X that was missing on MG7 is also missing on MG8, it can be due to a kapton.
- The annular behaves exactly as before and during e775s, the change of kapton did not solve the problem.
- MG9 here was not biased (it is on the MUST2 box). |
| Fixed | TEST |
Wed Jan 22 15:53:25 2020 |
Marlène | GRIT | Hardware | | Changes for MUGAST2020 |
Changes were made for MUGAST 2020 :
1- the board for MG10 before (2nd square) is now for MG6 new trap
2- the board for MG9 is put vertical and used for the MUST2 at 90 deg
3- a new board has been installed for MG2
Now there will be 13 detectors in the chamber: 7 trap + 1 square + 4 MUST2 forward. |
| Fixed | e744s |
Thu Apr 11 19:19:21 2019 |
Iulian Beyhan | RUN | General | N/A | Change target CH2 to no target |
| Target hole is now removed -> No target |
| Fixed | e744s |
Sun Apr 14 15:05:06 2019 |
A. Lemasson | VAMOS | Hardware | | Change of Offset in DC Numexo |
- Increasing offset to minimize saturation.
- Reducing DC Threholds
- DC0 436 ->355 mV
- DC1 255 ->255 mV
- DC2 269 ->269 mV
- DC3 600 ->433 mV
|
| Fixed | |
Wed Jan 23 12:24:10 2019 |
Marlène | GRIT | General | | Change cable MG1T - Exchange of detectors named MG9C & MG10C |
23/01/19
Change of the HT/BT cable of MG1T (the one that had a short cut before when the chamber was closed)
MG9C is now the square detector nb 4 (Micron number) and coupled with the thick detector --> this detector was working properly
MG10C is detector nb 3 (Micron number) --> this detector was noisy before |
| Fixed | e793s |
Mon Mar 15 10:18:37 2021 |
Taras, cyril, Léo | ONLINE | Hardware | CD2 | Cats2 tripped |
Cats2 tripped with vamos, had to be reset
Beam is back |
| Fixed | com2019 |
Wed Apr 3 11:03:53 2019 |
Adrien Matta | CATS | Hardware | N/A | Cats mask will be shifted |
The propulsif supporting the cats mask is leaking.
It will be tighten to fix the leak, this lead to a small shift toward the left of the beam when looking at vamos. |
| Fixed | TEST |
Fri Jan 18 15:32:50 2019 |
Adrien Valérian | GRIT | General | N/A | Calimero tests Muvi2 MM7 MG10C |
After disabling nptool Multithreading, online is working fine again.
Concerning Calimero, it is currently working both on MUVI1 and MUVI2 for the X at least.
Joined here is the result of Calimero for MG10C on MUVI2 channel 3 (MM7). |
| Fixed | TEST |
Wed Jan 16 17:36:30 2019 |
Valérian-Marlène | GRIT | General | N/A | Calimero tests - How to configure Calimero in GECO |
Tests of Calimero time calibration with MUVI1 channel 2 (MM2)
1- channel 3 of all mates selected (see screeshots)
2- channel 1 of all mates
3- channel 1 of all mates - with channels enabled !!!!!
4- channel 1 of all mates - with channels enabled !!!!!
5- all channels telescope MM2
Number of counts = total number of counts for one channel on all mates
Conclusion :
Options to be chosen
1- with channels enabled
2- 10000 for the statistics
Remarks
To run calimero on MUVI1, caliWatcher should be set to 10202 and CaliSlave to 10223
The opposite for MUVI2, caliWatcher 10223, CaliSlave 10202 |
| Fixed | TEST |
Tue Mar 5 15:53:04 2019 |
iulian Marlene | MUST2 | Software | N/A | Calimero problems |
problems with Calimero solved by killing some processes on lpcgrit related with Narval.
to find the processes on lpcgrit:
ps aux | grep Cali*
ps aux | grep Narval
kill -9 all the ids
Other possible solution:
start_acq on lpcgrit
tk followed by kall
exit |
| Fixed | TEST |
Tue Mar 5 18:03:24 2019 |
iulian Marlene | MUST2 | Software | N/A | Calimero problem on Y side |
| Calimero not working properly on Y side of any mm detector |