 Mon Jun 16 08:17:41 2025, JG, D2 consumption
|
The current bottle of D2 was installed on friday 06.06. at around 12:00. I assume we started at 200 bar.
Right now we have 50 bar remaining in this bottle (16.06. at 8:00).
This is an average consumption of ~15 bar/day |
Sun Jun 15 10:46:35 2025, EW, EM, AR, AB, CB, JG, AK, Run 81 30x
|
11:45 New run started - run 81, same settings as previous runs (75, 76 etc)
ROOT histograms NOT zeroed
Beam at 2.5e8, target density at 3e12 |
|
Sun Jun 15 07:01:37 2025, EW, EM, Run 80
|
08:00 New run started - run 80
Run whilst they are optimising the beam after losing it, everything else same as previous runs
ROOT histograms NOT zeroed |
|
Fri Jun 13 19:41:32 2025, JG, SHB, JM, AR, EW, OF, Run 77, 78, 79 17x
|
New run started - Run 77 after refilling LN2 dewar
Same settings as Run 75 & 76
The root histos have not been reset, i.e. they show combined statistics of run 75, 76 and 77. |
|
Fri Jun 13 16:39:18 2025, JG, SHB, Run 76 7x
|
Same settings as run 75.
Detector 4 is biased at 100V and switched from MEC to LEC.
The root histos have not been reset, i.e. they show combined statistics of run 75 and 76. |
|
Fri Jun 13 14:45:58 2025, JG, SS, JM, CB, EW, AR, Run 75
|
90 keV/u beam on target, Target overlap confirmed with lifetime measurement using bunched beam - @ -12.5mm
We do not expect to see see Rutherford due to energy loss in the dead layer, using other particle detector for normalsiation. |
|
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). |
|