|
ID |
Date |
Author |
Subject |
Text |
 |
|
738
|
Wed Jun 11 10:13:42 2025 |
EW, CB, PJW, AR, JM | Run 67 | As run 66, optimisation of beam completed
DSSD4 now working and thresholds
to 0x30 (480keV), switched to LEC |
14x |
|
737
|
Wed Jun 11 09:16:55 2025 |
CB | ASIC Control Settings | 11 June 10:18
2025Apr08-13.45.30 settings
DSSD4 not working as of the screenshots |
17x |
|
736
|
Wed Jun 11 08:37:48 2025 |
CB, PJW | Run 66 | 09:38
As Run 65, no changes, CRYRING
operators attempting to improve beam intensity. |
 |
|
735
|
Tue Jun 10 22:38:59 2025 |
JM, CB, PJW | Run 65 | 23:40
Offline anlaysis shows two clear
peaks for DSSD1 and 2 at very low energies |
7x |
|
734
|
Tue Jun 10 16:46:39 2025 |
JM, CB, EW, AY, PC | 150 keV - Run64 | Run 64 started.
150 keV/u beam on target, Target
overlap confirmed with lifetime measurement |
42x |
|
733
|
Tue Jun 10 13:29:23 2025 |
EW, CB, JM | Thresholds changed | Experimented with slow comparator thresholds
as we go down to lower beam energies
Checked deadlayer loses with SRIM, |
   |
|
732
|
Tue Jun 10 09:57:50 2025 |
CB, JM, PJW, YuL, JG | Run 62 | 10:58
As Run 61, no target for background.
200 keV/A |
|
|
731
|
Tue Jun 10 09:44:33 2025 |
JG | MBS not running for a week | The MBS daq was not writing data since
June 2. 22:39 (run_0035.lmd)
This means, no detector and target |
|
|
730
|
Tue Jun 10 09:44:30 2025 |
JG | MBS not running for a week | The MBS daq was not writing data since June
2. 22:39 (run_0035.lmd)
The reason is that
the rfio server was running on atppc025 which |
|
|
729
|
Tue Jun 10 09:44:20 2025 |
JG | MBS not running for a week | The MBS daq was not writing data since June
2. 22:39 (run_0035.lmd)
The reason is that
the rfio server was running on atppc025 which |
|
|
728
|
Sun Jun 8 11:55:00 2025 |
EM, PC, JM, CB, EW, AY, CB, PJW, YuL | Run 58,59,60, 61 | 12:52
Started Run 58 - Beam energy
200 keV/u. |
50x |
|
727
|
Sun Jun 8 10:05:30 2025 |
EM, PC, JM | Run57 | 11:06
Run during beam change. We will
go down to 200 keV/u |
|
|
726
|
Sun Jun 8 09:07:22 2025 |
EM, PC, JM | Run56 | NOTE: RunR55 is missing
Run56: Background run with 250
keV/u. Target off using the usual procedure. |
 |
|
725
|
Sat Jun 7 10:23:26 2025 |
JM, CB | carme-gsi rebooted | 10:00
The computer screen controlling
the DAQ on carme-gsi appeared to have crashed. |
|
|
724
|
Sat Jun 7 10:06:27 2025 |
JM, EM, CB, DB, AY, PC, CB | Run 54 | 11:10
We have started a new run at the
same energy as R53 (250 keV/u) due to an |
50x |
|
723
|
Fri Jun 6 17:27:03 2025 |
AY, ST, JM, EM, DB | Run 53 | Run 53 started at 18:25 (started already
earlier but since then data is taken). Everything
is running again. We started at 3E12 at/cm2. |
11x |
|
722
|
Fri Jun 6 16:49:59 2025 |
CB, AY, ST | Beam overlap results for 200keV and 250keV | For 200keV the optimal horizontal position
is -5mm.
For 250keV the optimal horizontal |
|
|
721
|
Thu Jun 5 16:54:18 2025 |
EW, ST, CB | Run 52 - 0.3 MeV/A | Run 52 started at 17:53. Everything is
running again. We started at 3E12 at/cm2
D+ beam deuterium target. D+ beam |
14x |
|
720
|
Thu Jun 5 08:50:00 2025 |
JM, CF, CB, EW | Run 51 - background | 09:49
DSSD4 has been biased to 100V in
steps of 5V from 60V. It was previously stable |
  |
|
719
|
Wed Jun 4 10:44:36 2025 |
EW, CB, JM, OF, JG, ST | Run 50 - 0.35 MeV/A | 11:30
Run 50 started.
D+ beam deuterium target. D+ beam |
13x |
|