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

 150 bar / 9.83 days

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

11:50 All checks okay

12:45 All checks okay

13:45 All checks okay

14:45 All checks okay

15:45 All checks okay.

17:00 All Checks okay. Target temp manually dropped from 30.4K to 30.1K to try and improve density as would not get much above 2.5-3ish. Also played with target position for a while - now seemed to have stabilised it at 4.5e12 as of now.

18:00 All checkd okay. Target been stable at 4.5-5.3e12.

18:20 Done checks again (all ok) as the beam is being a little stange. Attatched ss of peaky peaks (some of them very nice) but detector 3 histogram wont cooperate and wont let me see the counts if I zoom further down, but can see proton peak fine. Seeing periodic spikes in the counts plot for the particle detector - monitoring. Also the tail of the beam seems more red than usual.

19:00 More photos of strange spikes in the counts for particle detector uploaded. Sometimes, the baseline has decent sized spikes too. Attatchments 10-14

19:20 Checks ok. Traget stable. Spikes in particle detector seem to be more frequent, uploading more photos below. Also attatched peaks at this stage (attatchemtn 15).

19:36 Very strange spikes in particle det. Two bigish peaks at baseline and then strange beginning at the injection. Attatchment 19.

19:45 Another spike in the baseline for particle det. Attatchment 20. 

20:25 Checks ok. Spikes still in particle det plot.

21:20 Checks ok. Screenshot of peaks in attatchment 21.

22:20 Checks ok. Target been relativly stable all shift at 5e12. Spikes still periodically turning up in particle detector. Histograms are gaining counts, attatchment 22 is the peaks.

22:30 Target suddenly got really dense up to 1e13. Lifetime of the beam is ok. Trending down slowly. Did checks again and all is good.

01:45. Checks OK. Target seems thick.

04:30

Temperatures OK - attach

Rates OK - attach

Merger OK - attach

Hisograms look OK - attached

Target looks very thick from ring vacuum worsening.

7:15 all checks okay - historgams attached

beam 2e8, target 1e13, scintillator rate 2000 in peak

10:00 

Run stopped to gain cave access.

Before beam was stopped, target was moved out. We still see some signal on the neutral particle detector, roughly a factor 10 below with target on at 1e13 at/cm2

Will need a beam background run for normalisation procedure. See attachment 29

10:30

Now we have no beam in the ring we still observe some events in the neutrals detector. Some spikes up to 150 counts observed, could explain some of what we have seen so far. See attachment 30

Note we are saving all this data to MBS so it is effectively background for the neutral detector. 

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

All checks fine

09:05 All checks okay

Attachment 5 current histograms zoomed into area of interest, detector 3 only proton peak visible

10:00 All checks okay

11:00 All checks okay

11:45 Run stopped as beam is back

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.

20:45 - all checks OK

22:00 - all checks OK

00:10

Observed no data writing to disk. Checked merger no data merging. No ADC data items. Seems daq crashed again.

Appears aida09 had crashed causing system to stop. Tried fix suggested in earlier elog by Tom. No success. All FEEs show error and system became unresponsive. 

Power cycling FEEs. 

00:30

New run started Run 78. Same conditions as previous runs. 

All thresholds remain unchanged ->0x28 (400 keV)

Had to reset monitoring histograms as they were unresponsive too. 

All system checks OK. 

Data rate is ~300 kB/sec

ADC data items rate is similar to previous run (screenshot already attached)

Detector leakage currents look OK. Plots attached. 

WS6 (elog and internet) appeared to freeze before. This could be similar to the issue osserved last weekend. All seems fine now and DAQ continues. Should keep an eye on it.

02:00

Checls OK

05:00

Checks OK

7:10 Checks OK. Target was fluctuating over night, dropped around midnight then back up but had no target for about 2-3 hours overnight. Fixed target thickness this morning and now have 5e12.

8:15 Checks Ok.

9:15 Checks Ok.

10:15 Checks ok. Target good at 5e12. Attatched screenshots of the peaky peaks so far (can't put numbers on excel as lost the ability to see it - see 9 10 and 11)

11:35 All checks ok. Screenshot of peaks attatchment 12 (decently peaky).

12:30 All checks ok. Peaks are beginning to show, especially proton and triton but on det 3, cant distinguish trition from noise peak so no value in spreadhseet for that. Target stable at 4.8e12.

13:30 All Checks ok.

14:30 All Checks ok.

15:40 All checks okay, lost beam at 15:25, let HKR know and they are looking into it, have put to no storage.

16:35 All checks okay, still no beam, taget is steady at 3e12

17:35 All checks okay, beam is back but being optimised

18:33 New run started- run 79, same settings as previous runs, did NOT reset histograms, beam now 2e8 (previously was 7e8)

18:33 All checks okay apart from temp of aida 3 which is a little high (see attachment 13), rates also attached (attachemnt 14), current histogram attached (15)

19:35 All checks okay, aida 3 temp now back within range, target density dropped but have managed to get it back up to 2e12

21:30 All checks okay, target has been very unstable, beam now at 3.8e8

22:30 All checks fine, target at 3e12 for past 45 minutes, beam at 4e8, current histogram attachment 16

23:40 All checks ok. Integral value for range to 4000 seems to be increasing for all histograms - meaning target is probably ok for now. Vacuum plot doesnt show any issues.

02:00 All checks ok. Integral values for proton peak have increased so assuming target is still holding as of now (only peak I can clearly isolate to get value from) - no indication that it is off via vacuum plot. 

5:00 All Checks ok. Integral values increasing. 

7:00 All checks ok, can't see target density as of 6:20

08:00 Run stopped as lost beam, histogram attachment 17

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.

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.

Moved detectors in with servos only. Both arms are IN and stationary.

Left potentiometer = 36.54 mm

Right potentiometer = 37.96 mm

Horizontal beam position = -12.5 mm

Thresholds increased for all to 0x28 (400keV)

data rate is ~0.7 MB/sec

Electron cooler read values; Cooler voltage = 50V (dodgy accuracy need to ask about fc20 on monday), cooler current=0.26 mA.

15:50 All Checks ok. Overlap on beam found. Target at 4e12. Bottle at 90 bars.

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.

Attachment 22 - IPM (no target)

Attachment 23 - IPM (target)

Attachment 24 - YR10 particle detector (gap in events corresponds to target off period)

16.42 DSSSD bias & leakage current - attachments 1-2

DSSSD #4 currently conditioning at -20V

FEE64 temperatures OK - attachment 3

ADC, DISC, PAUSE & RESUME data item stats - attachments 4-7

System wide checks OK *except* WR deocder status aida04 - attachment 8

WR timestamps OK - attachment 9

per FEE64 Rate spectra - attachments 10-12

per FEE64 1.8.L spectra - attachments 13-14

per FEE64 1.8.W spectra - 20us FSR - attachments 15-16

pulser peak width aida06 69 ch FWHM, aida08 67 ch FWHM

Merger, TapeServer OK - attachments 17-18

ASIC settings 2025Apr08-13.45.30

 aida01-aida04 slow comparator 0xc

aida05-aida12 slow comparator 0x8

aida13-aida16 slow comparator 0x64, LEC/MEC 0x1

17.23 CRYRING vacuum and temperature - attachments 19-21

17.34 routine checks OK

target density c. 5e+12, beam 3e+6

18.40 changed target x,y position to check correlation between target density and detector counts. New position: x:-1500, y:2400.

checks OK.

target density c. 3.7e+12, beam 3.1e+6

20.00 online analysis - per DSSSD energy spectra - attachment 25

 t, h and p energy peaks clearly observed DSSSD #1 and #2 - p energy peak less clear in DSSSD #3

20.30 checks ok

target density increased to c. 5e+12 for some minutes then back at c. 3.7e+12, beam 3.1e+6.

21.47 checks ok

target density increased to c. 5.7e+12 around 21.35, then back at c. 3.7e+12. beam 3.1e+6.

22.30 online analysis - per DSSSD energy spectra - attachment 26

22.35 Analysis of data file G22-205/R74_29 - attachment 27

no timewarps, all deadtimes << 1%

22.45 DSSSD#4 bias -20V -> -40V, leakage current -2.7uA -> -4.09uA

23.14 DSSS\D#4 leakage current c. -9uA, return to bias -20V

23.21 target density slightly unstable in the last hour, changed nozzle position to x=-2000, y=2500.

00:04

Temps OK

System wide checks OK

Rates OK

Merger OK (1400 kb/s)

Target oscillating, but looks usable. Need to have another look at temperatures tomorrow morning.

01:57

Temps OK

Rates OK

Merger OK

Target getting thicker.

05:00

Temps OK

Rates OK

Merger OK

Target fluctuating

7:20 All sysytem checks ok. Target lost density @ 6;55 from 4.6e12 to 2.6e12 - will try moving. Update 7:30 after moving density back up to 4.4e12.

8:45 All Checks ok but target is fluctuating - really wants to be around 2e12. Had it up to 5e12 about 25 mins ago. Naughty target tbh.

9:25 All checks ok, gone to no storage as now tuning next beam energy.

10:30 All system checks OK, still tuning.

11:38 All system checks ok, still tuning. Frank entered cave to adjust magnetic field as the beam was not cooling at 90 keV/A

12:36 All checks okay, cave still open

13:40 All checks okay, tuning beam currently

14:50 All Checks OK. Target beam overlap currently happening - scanning range not showing anything. Target back on but not hitting - thickness 1.2e12.

15:00

Cave closed, waiting for beam to come back.

Reset all ASIC settings to those in elog 737

DSSD4 remains OFF and is set to the MEC channel.

ADC data items and data writing to disk - Attachments 1+2

While the cave has been closed we warmed the target up to 80K and have now cooled back to 30.5K to increase the density which was dropping into the 10^11 range. We have now recovered densities in the mid 10^12 at/cm2 range.

Detector leakage current plot - Attachment 3,4

All system checks OK

Started at 16:20

EM and JG trying to get scintillator signals in MBS

Configuration completed?

Stopped 16:32

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.

All thresholds set to 0x64 for the pulser walkthrough

07:20

Started a background run while the cave is open.

All ASIC settings remain unchanged, we just have no beam.

We see obvious difference in the rate plots for DSSD2 from the monitoring code. Attachment 1 - beam on, Attachment 2- beam off.

Data rate ~1.6 MB.sec

Checks OK.

10:30

Lost DSSD4 again. Writing a lot of junk to disk.

Switched to MEC channels. Still writing lots of data. Stopped the run.

Required ASIC check load on aida13,14,15,16 in order to bring rates back down.

Slowly re-biasing detector. At 35V

Moved detectors fully out for safety. Left potentiometer = 18.86 mm and right potentiometer = 19.8 mm. No effect on leakage currents.

Past 40V we large increases in leakage current. Only went up to 10uA and didn't trip. Set to 40V, current back down to normal levels.

Note we have turned the target compressor off to heat up before cooling later to try and get higher densities. This follows a drop in E1 yesterday reducing the target density.

10:45

Started new background run - Run 69.

DSSD4 set to MEC.

Thresholds still as in previous runs (120, 80, 80 keV).

As run 66, optimisation of beam completed

DSSD4 now working and thresholds to 0x30 (480keV), switched to LEC

Tape service at 1.7MB/s

Did NOT reset the root histograms!!

11:30 All checks OK

13:48 All checks OK

15:15, fULL CHECK, STATUS - Okay. Target density ~2E12

16:15 All Checks OK. Target 2.9e12

17:30, Full check! status - okay. target 2.3e12

18:30 All Checks Ok

19:30 All Checks OK

21:30: All System Checks OK but targte density started dropping around 8:20. Tried to move the nozel but any x direction made it drop alot and y did nothing. Values hovering steadily between 1.1e12 to 1.4e12. Will try and move nozel again in 1 hour.

22:40: Full check, Status -okay! thickness 1.4E12. For more details look at the attchments

00:55: Full check. All looks okay!

03:55: Full check. All looks good!

06:28 Checks OK. Target density has dropped and is ~9e11 at/cm2. It will require some attention this afternoon

07:00 Run stopped. Final histogram attached. Number of counts somewhat obscured by background level.

11 June 10:18

2025Apr08-13.45.30 settings

DSSD4 not working as of the screenshots (MEC + High Threshold)

See attached.

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.

Checks OK

Root histograms NOT zeroed.

10:20

Checks OK

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.

For DSSD3 the noise level is so exceptionally high due to the low threshold that nothing can be discerned from background.

Therefore I decided to stop the previous run and increase the slow comparator threshold for DSSD3 from 50 keV to 80 keV (same as DSSD2).

Run 65 started.

150 keV/u beam on target, Target overlap confirmed with lifetime measurement using bunched beam.

Detectors in with servos only. Both arms are IN and stationary.

Left potentiometer = 36.54 mm

Right potentiometer = 37.96 mm

Data rate has dropped to 1.5 MB/sec and merger is between 600k and 900k.

Stats attached at new thresholds.

Stats zero'd to see number of pause and resume overnight.

02:30

Some reaction counts visible on monitoring histograms (rate v low)

Checks OK, same fee (aida16 fails clock and adc as before)

pause info items after a few hours attached

05:00

We see the peaks much more clearly now. Rate is low but they are there. Target density looks like it has been fluctuating in the low 10^12 region. 

Note for this energy with 1e8 pps, 1e12 target density I estimate ~2 counts/h per detector for the 3He peak.from our spreadsheet calculator. After 6 hours of this run I saw about 10-15 counts in the peak of DSSD2, perhaps the same in DSSD3. DSSD1 has missing strips so is harder to see. This rate is about 48 hours for 5% (if we had 4 dssds).   

Checks OK

Leakage current of dssd4 has been stable at 40V for a while now. Pushed voltage up to 75V with leakage current stable. At 80V it started to go over current

Turned bias to 60V and have left on at this level. It looks stable. Perhaps in the morning it can be pushed to close to 100V.

07:15

Temps OK

System wide checks: 16 fails ADC calibration, 14 fails WR decoder

Rates OK, some Pause/resume statementes overnight. See attached x2

Merger OK. 1.5 Mb/s

Peaks clearly visible in two detectors.

08:25 All checks OK. DSSD 4 to 75V - OK.

09:10 All checks OK. DSSD 4 to 80V. Trying to improve target (2-4E12).

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.

We leave for a few hours to see if we obsrerve any reactions peaks

Moved detectors in with servos only. Both arms are IN and stationary.

Left potentiometer = 36.54 mm

Right potentiometer = 37.96 mm

Horizontal beam position = -3.0 mm

data rate is ~5 MB/sec

Electron cooler read values; Cooler voltage = 88.57V, cooler current=1.28 mA.

19:05

Full check, Status - Okay! Target thickness ~ 2E12. For more details, check the attached screenshots

20:12

Full check, Status - Okay! Target thickness ~ 1.6E12, For more details, check the attached screenshots

21:22

Full check, Status - Okay! For more details, check the attached screenshots

22:30

Full check, Status - Okay! Target thickness ~ 1.8E12, For more details, check the attached screenshots

23:00

Checks OK. I have increased the equal energy cut back to 500 keV and increased bin size on Ey energy histogram to 50 keV to try and see the nuclear peaks better.

Screen shot attached of monitoring code before it was reset. Some small peaks visible.

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

100keV/u -> 120keV

80keV/u -> 76keV

New thresholds:

aida1-4 0xc (120keV)

aida5-8 0x8 (80keV)

aida9-12 0x5 (50keV)

aida13-16 0x64(1MeV) set to MEC channel

Statistics and data rate with beam on but no target

Deleted April 24,25 and G22-86 from GSI, backup in Edinburgh

10:58

As Run 61, no target for background.

200 keV/A

Saved the ASIC settings for currently running. I made a mistake and overwrote the 2025APR08 settings.

Current settings have aida13-16 set to MEC channel and slow comparator set to 0x64.

All ither channels set to 0xc slow comparator.

Energy changed to 150 keV/A a few minutes before the end of this run. No storage. Waiting for the new beam.

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.

We resumed running MBS now at 10.06. ca. 10:35. (run_0036.lmd).