 Thu Jun 12 15:33:17 2025, CB, JM, EM, JG, TD, AB, CF, AR, Run 74 27x
|
16:34
Like Run 73, but particle detector in YR10 now active, and recorded in MBS.
Clear effect of target on beam lifetime. Target off -> nearly no counts. |
|
Thu Jun 12 14:22:27 2025, JM, CB, TD, CF, JG, EM, Run 73
|
15:00
Cave closed, waiting for beam to come back.
Reset all ASIC settings to those in elog 737 |
|
Thu Jun 12 14:08:42 2025, JM, CB, Run 72 - pulser walkthrough
|
Pulser walkthrough conducted while the cave was open.
Pulser amplitudes 90000, 80000, 70000, 60000, 50000, 40000, 30000, 20000, 10000
DSSD4 was set to MEC and bias off as the detector had previously tripped. |
|
Thu Jun 12 06:20:50 2025, JM, Run 68,69 - background
|
07:20
Started a background run while the cave is open.
All ASIC settings remain unchanged, we just have no beam. |
|
Wed Jun 11 10:13:42 2025, EW, CB, PJW, AR, JM, Run 67 14x
|
As run 66, optimisation of beam completed
DSSD4 now working and thresholds to 0x30 (480keV), switched to LEC
Tape service at 1.7MB/s |
|
Wed Jun 11 09:16:55 2025, CB, ASIC Control Settings 17x
|
11 June 10:18
2025Apr08-13.45.30 settings
DSSD4 not working as of the screenshots (MEC + High Threshold) |
|
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.
We should be able to keep running while they do, but there is a chance of some missed injections or other oddities. |
|
Tue Jun 10 22:38:59 2025, JM, CB, PJW, Run 65 7x
|
23:40
Offline anlaysis shows two clear peaks for DSSD1 and 2 at very low energies close to the threshold. One must be elastics and the other a noise
peak. |
|
Tue Jun 10 16:46:39 2025, JM, CB, EW, AY, PC, 150 keV - Run64 42x
|
Run 64 started.
150 keV/u beam on target, Target overlap confirmed with lifetime measurement using bunched beam.
We do not see Rutherford on the detector - perhaps this is a calibration issue - perhaps too much noise at threshold. |
|
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, expected ruthford energies are as follows:
150keV/u -> 230keV |
|
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 |
|
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 timing is available for this period.
The reason is that the rfio server was running on atppc025, which crashed at that time. |
|
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 crashed at that time.
We
resumed running MBS now at 10.06. ca. 10:35. (run_0036.lmd). |
|
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 crashed at that time.
We
resumed running MBS now at 10.06. ca. 10:35. (run_0036.lmd). |
|
Sun Jun 8 11:55:00 2025, EM, PC, JM, CB, EW, AY, CB, PJW, YuL, Run 58,59,60, 61 50x
|
12:52
Started Run 58 - Beam energy 200 keV/u.
Slow comparator threshold set to 0xc (130 keV) for all channels. Fast discriminators turned OFF for all channels by setting enable mask in discrinator |
|
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
All the checks are ok. |
|
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.
All checks ok! |
|
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.
Unable to move throught the different windows etc. |
|
Sat Jun 7 10:06:27 2025, JM, EM, CB, DB, AY, PC, CB, Run 54 50x
|
11:10
We have started a new run at the same energy as R53 (250 keV/u) due to an issue with the DAQ pc
Server and DAQ restarted |
|
Fri Jun 6 17:27:03 2025, AY, ST, JM, EM, DB, Run 53 11x
|
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.
Side comment: Gleb told us 1h ago that he will switch to coasted mode and call us back as soon as he is done. So far he didn't call back and
he is not in the office... So we decided to start data taking already. But: the software says that coasting mode is already on, but the graph looks like |
|