ELOG MUGAST

G1 profiler & VAMOS efficiency

Factor of two between the profiler and VAMOS FP determination of incident beam is now understood.

Several effects were at work simultaneously and checked at 2 beam intensities (9e3 pps and 5e4 pps):
1. Profiler is using energy loss of the crossing beam particles to deduce the beam intensity. But the profiler was set to 15N instead of 15O.
We checked that for the same beam intensity of 15O the profiler gives 1.2e4 pps / 9e3 pps when tuned on 15N / 15O respectively. This amouts for 75% difference

2. Profiler tends to overestimate the real beam intensity by about 20% when compared to CATS1
Profiler / CATS1: 9e3 pps / 7.3e3 pps (81%)
Profiler / CATS1: 5e4 pps / 3.9e4 pps (78%)

3. VAMOS counting rates are lower than CATS1 by 20% which is consistent with the charge state distribution q(8+)/q(7+) = 80% calculated from LISE++
CATS1 / VAMOS: 7.5e3 pps / 5.8e3 pps (78%)
CATS1 / VAMOS: 3.9e4 pps / 3.0e4 pps (77%)

4. VAMOS PPAC efficiency was checked to be 100%: the PPAC logic signal is always present when triggerd by the drift chamber logic signal

Results:
By combining all previous factors and for 15O beam at the beginning of the experiment we obtain between the profiler and VAMOS FP a reduction factor of: 0.75 * 0.81 * 0.78 = 47%, CQFD!

Discussion:
This factor of two explains the difference we always observed when comparing estimated and measured g-ray yields.

Marlčne, Christian, Ksenia

Sun Jul 21 16:51:30 2019

BEAM

trial of tracking of the implantation of 15O

Looking at AGATA count rate, we have seen that the highest counting rate for 511 keV line is seen in the inner ring (0*A clusters).
The outer ring detectors (10B for example) counts 10 times less.

Our conclusion is that the beam is partly implanted at the entrance of MUGAST chamber.
The outer ring probably sees the implantation on MUST2 masks.

A more refined analysis is needed to backtrack where the 15O are implanted.

e768s

Sun Jul 21 16:39:38 2019

Marlčne, Antoine

BEAM

IMPORTANT :How to send scalers to PCP

Go to PCP

Open a terminal
> ssh -X mugast@ganp154
passwd : Spiral1+

> ./LaunchScalers.sh

new inputs in the ADC Mugast

e744s

Tue Apr 9 18:08:22 2019

Marlčne and François

DAQ

Software

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

Fri Apr 5 19:05:56 2019

Brho of 16O @ 6 MeV/A after 1mg/cm2 = 0.68906
Brho of 17O for g.s. after 1 mg/cm2=0.71065
Brho of 17O @ 871 keV after 1mg/cm2=0.70831

Mon Feb 24 22:34:43 2020

Marlčne Nicolas

RUN

Screenshots run 126 (target CD2+Au #2 rotated 180 deg)

e775s

Thu Feb 27 12:35:39 2020

Marlčne Nicolas

GRIT

RUN128-137_138 analysis

Kinematic lines for the full statistics up to now
States above E*>7 MeV are cut in the angles >140 because of energy threshold.

3He target filled with 700 mb

e786s

Mon Jun 24 03:52:11 2019

The 3He cryo target is filled with a pressure of 700 mb
The temperature on the target is 5.98K

The LHe dewar has been changed at 1 a.m.

test of MUST2 electronics

Thu Mar 7 14:02:03 2019

Test with pulser at 20 kHz
The OR of MUVI was scaled down by a factor of 100, to provoke some resets

e744s

Thu Apr 11 05:08:20 2019

Screenshots from RUN 74

RUN 74 with 14N beam and CD2 104um target
First screenshots from MUGAST

Time of flight is OK for MM and MG --> we keep CATS n FAG the way it is
CATS2 position is shifted in X by 3mm but it seems to be well centered on MUST2 and MUGAST

We see proton elastic scattering in MUST2 and in the square (by the way the square is working !)
I had to mask one mate Y on MG4 because it was counting about 50 Hz in the noise.

e775s

Sun Mar 1 17:04:43 2020

Marlčne François

RUN

Preliminary analysis of runs from 128 up to now (169)

Preliminary analysis with all stat up to now.

Some changes in the electronic scheme

Thu Jul 11 11:40:18 2019

Marlčne & Franco

OTHER

Hardware

- We checked the TACs with a time calibrator, all of them are working. Maybe to check the ADCs if some timings are not there during the exp.

- We set the possibility to have MUST2 divided by 100 (on a separate chain) in case of high rate on GMT channel number 7.

- We are now taking as input of the HF the clean HF validated by VAMOS instead of cleaning it on our side through the coincidence with FAG. This is sent to make the STOP of all TACs and MUVIs.

- We sent the OR of MUST2-MUGAST-SQUARES in an additional FIFO with cables of the same length (10 ns) and the output sent to VAMOS and to the TAC called Si-CATS in the acquisition.

Tue Dec 3 18:14:45 2019

Marlčne & Franco

GRIT

Hardware

Pulser test of new board

The new board that will be installed for MG2 has been tested and validated with a pulser outside of the chamber.

Wed Jan 22 18:39:54 2020

The new box has been tested together with the new CAEN SY4527 power supply. We connected a laptop with Linux to the power supply by means of an ethernet cable and communicated with it by opening a browser (http://192.168.0.1, then username: admin and pwd: admin). To control the channels we open a terminal, go to the folder where we saved the file ChannelsController.jar and run the command: java -jar ChannelsController.jar 192.168.0.1 admin admin
The output biases were checked with a test cable connected to the flange output and are reported in the attached file. For comparison we did the same thing on 3 Mugast detectors (MG1, MG3 and MG4) We saw that the polarity of all the 3.3V in the new box was inverted with respect to the Mugast box so we opened the box and, like sappers, we followed the colored cables until we found the ones giving the 3.3V and inverted them. It worked! So now the biases should be correct. A reminder for possible future modifications: the coupled colours for the wires are blue-grey, white-brown, yellow-green.
Some low voltages seem to be unused because they are present in some BT outputs but not in others, but anyway the detectors which are supplied by these cables have always been working properly, so the small differences between different BT outputs might be irrelevant.
It is then important to notice that BT2 and BT3 have a -2.5V instead of a +2.5V so it's recommended not to use them unless the relative cables are first switched inside the box.

Fri Feb 14 10:49:22 2020

We analyzed the behaviour of the annular. We realized that the 4-peaks behaviour on X was already present last year but only on one sector, now it's on two sectors. We noticed that there is a correlation between the malfunctioning sectors and the missing strips on Y. Last year there was only a missing strip on Y, affecting only one sector on X; now 3 strips are missing on Y, affecting 2 sectors on X. We believe that the fact that the boundings are missing have an impact on the grounding, therefore the sectors are not always biased properly, resulting in an oscillation of the pedestal. We estimate that this will cause a loss of efficiency of ~25% for the annular (from ~90% to ~67%).

mugast wrote:

RUN 500

start: 11/02/2020 @ 19h00
stop: 12/02/2020 @ 10h00

alpha source test - cooling 14°C

Remarks:
- The two new detectors (MG2 and 6) seem functional;
- MG11 annular, ok for sectors (Y) but many rings have double peaks;
- MM1 current was oscillating yesterday evening with values around 3 uA, this morning it was stable at ~0.55 uA.

e775s

Tue Feb 25 11:50:16 2020

Marlčne & Franco

OFFLINE

PID with gate on T_FPMW_HF

The black points are what remains after putting the condition abs(T_FPMW_HF-13000)<1000, for MG1 and the annular.

Wed Mar 11 18:12:40 2020

(Probably) final update of the status of the detector before the experiment:

- MG5 does not trigger on Y (no pulser, no alpha source). This can explain why in the last experiment we could not run the time calibration of its Y.
- We changed kapton on MG7 but we still miss the same part of the detector. This points to a problem of the board...
- There is nothing we can do for the moment for MG11, the re-bounding would take too long. We will keep it like this.
- MUST2 detectors have higher current than usual but the signals from alpha source are fine.
- MM1 was changed but still shows the problem of the fluctuation of current. We also tried to change the HV supply (now it's on MG6) but nothing changes. This also seems to point to a problem of the board...
- We noted that, with circulation of alcool-water liquid (but no cooling), the temperature of MG7 is around 45 degrees, about 20 degrees higher than the other Mugast detectors.

Debugging the cooling system

Thu Mar 12 10:14:02 2020

We realized that the increase of temperature of MG7 and MG9 during run 600 (alpha calibration) was due to the fact that a loop of the cooling system was not working since the pipes were not properly connected. We re-connected them and switched on the low voltage without making the vacuum just to monitor the evolution of the temperature.

Temperature after 10 minutes from the LV switch on:
MG1 X = 20 deg; MG1 Y = 18 deg
MG3 X = 20 deg; MG3 Y = 19 deg
MG4 X = 19 deg; MG4 Y = 17 deg
MG5 X = 21 deg; MG5 Y = 19 deg
MG7 X = 20 deg; MG7 Y = 18 deg
MG2 X = 20 deg; MG2 Y = 19 deg
MG11 X = 20 deg; MG11 Y = 19 deg
MG9 X = 56 deg; MG9 Y = 26 deg --> We believe that we cannot really trust these values, they didn't change since yesterday evening and the board is cold (we touched it)

MM1 X = 18 deg; MM1 Y = 18 deg
MM2 X = 18 deg; MM2 Y = 18 deg
MM3 X = 18 deg; MM3 Y = 18 deg
MM4 X = 19 deg; MM4 Y = 18 deg

Moving MG9 square to MUVI2

Thu Mar 12 14:47:59 2020

- Since we are not using MG6 anymore (card burnt), we replaced it with MG9 on slot 3 of MUVI2. MUVI4 is now unused. We changed the actions parameters accordingly.
- We cannot run the time calibration for MG9 because the pulser does not go through neither on X nor on Y.