MUST2 SAMURAI_2018 S3-LEB-LPC SUPERNEMO MUGAST EXPAND SCALP GALATRON HiCARI VELO
  MUGAST, Page 132 of 132  Not logged in MUGAST
Status ExpNbrdown Date Author Type Category Target-Source Subject
Fixed  Tue Jul 23 23:22:56 2019 UK refugeesOTHERSocial Kipper issues.
I would mail you some but the postage is nuts those days!
Fixed  Wed Jul 24 12:44:55 2019 UK refugeesOTHERGeneral Fire out thanks to de Piffle
Attachment 1: BorisJ_fireman.jpg
BorisJ_fireman.jpg
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
Fixed  Wed Jan 22 18:39:54 2020 Marlène & FrancoGRITHardware Tests of the new box
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.
Attachment 1: box_pin_map.pdf
box_pin_map.pdf box_pin_map.pdf box_pin_map.pdf box_pin_map.pdf box_pin_map.pdf box_pin_map.pdf box_pin_map.pdf box_pin_map.pdf
Fixed  Fri Feb 14 10:26:46 2020 Franco&MarlèneGRITHardware HT BT screenshots before e775s
Detectors are cooled down to 0 deg.
Attachment 1: BT_CAEN2_MGnew.png
BT_CAEN2_MGnew.png
Attachment 2: BT_CAEN1_part1_MM.png
BT_CAEN1_part1_MM.png
Attachment 3: BT_CAEN1_part2_MG.png
BT_CAEN1_part2_MG.png
Attachment 4: HV_part1_MM_MG.png
HV_part1_MM_MG.png
Attachment 5: HV_part2_MG.png
HV_part2_MG.png
Fixed  Thu Feb 20 17:58:51 2020 FrancoGRITGeneral Time calibration for e775s exp
Attached the raw and calibrated time spectra for the pulser runs.
Attachment 1: T_raw_MM.png
T_raw_MM.png
Attachment 2: T_raw_MG.png
T_raw_MG.png
Attachment 3: T_cal_MM.png
T_cal_MM.png
Attachment 4: T_cal_MG.png
T_cal_MG.png
Fixed  Mon Feb 24 08:46:15 2020 FreddyOFFLINEGeneralCD2r116 - check GATCONF
After a quick offline check, it seems that we get MUGAST data only if MUGAST has triggered (GATCONFMASTER = 1,2,4).

In the de/TOF spectra the different structure in time are thus not due to different timing between VAMOS and MG triggers.
Attachment 1: r116_GATCONFMASTER.png
r116_GATCONFMASTER.png
Attachment 2: r116_DSSDE_GATCONFMASTER.png
r116_DSSDE_GATCONFMASTER.png
Fixed  Mon Feb 24 22:34:43 2020 Marlène NicolasRUNGeneral Screenshots run 126 (target CD2+Au #2 rotated 180 deg)
Attachment 1: run126_theta_Elab.png
run126_theta_Elab.png
Attachment 2: run126_Tof.png
run126_Tof.png
Fixed  Wed Feb 26 14:31:47 2020 Fairouz, Nicolas, MarlèneGRITGeneral RUN 137
Run 137
CD2+Au #2
Beam intensity 6e+5pps on average

Beam was retuned during the night and the quality of the beam is probably degraded
Fixed  Wed Feb 26 15:04:29 2020 mugastRUNGeneral beam retuning
Beam is retuned from PCP to improve its quality
Fixed  Thu Feb 27 15:54:09 2020 Marlène RUNGeneral RUN 141 junk (problem at start)
Fixed  Thu Feb 27 15:56:09 2020 MarlèneRUNGeneral RUN 142 AGATA- 143 VAMOS-MUGAST
RUN142 on AGATA and RUN143 on MUGAST/VAMOS

target CD2 (350ug/cm2)
Trigger MUGAST
Beam intensity : 5e+5pps



!!!! there is a shift in the run number on AGATA with respect to VAMOS/MUGAST
Fixed  Thu Feb 27 16:25:45 2020 MarlèneRUNGeneral RUN 142-143 screenshots

Marlène wrote:
RUN142 on AGATA and RUN143 on MUGAST/VAMOS

target CD2 (350ug/cm2)
Trigger MUGAST
Beam intensity : 5e+5pps



!!!! there is a shift in the run number on AGATA with respect to VAMOS/MUGAST
Attachment 1: RUN143_ElabThetaLab.png
RUN143_ElabThetaLab.png
Attachment 2: RUN143_impact.png
RUN143_impact.png
Attachment 3: RUN143_tac.png
RUN143_tac.png
Attachment 4: RUN143_tof.png
RUN143_tof.png
Fixed  Thu Feb 27 16:30:53 2020 MarlèneRUNGeneral RUN 142 -143 preliminary analysis

Marlène wrote:

Marlène wrote:
RUN142 on AGATA and RUN143 on MUGAST/VAMOS

target CD2 (350ug/cm2)
Trigger MUGAST
Beam intensity : 5e+5pps



!!!! there is a shift in the run number on AGATA with respect to VAMOS/MUGAST
Attachment 1: RUN143_ana_Elab_Thetalab.png
RUN143_ana_Elab_Thetalab.png
Attachment 2: RUN143_ana_Ex_Eg.png
RUN143_ana_Ex_Eg.png
Attachment 3: RUN143_ana_Ex.png
RUN143_ana_Ex.png
Fixed  Fri Feb 28 11:20:22 2020 MarlèneGRITGeneral RUN 150
RUN 150
target CD2 300 ug/cm2
Beam intensity 4e+5pps

Note that there is no 144,145,146,147, 148 ans 149 runs
   Tue May 19 12:23:57 2020 mugastONLINE   

ELOG Home Page