26 August

14:40

Turned CARME on 

Everything started up okay, all detectors on and stable. 

Note aida16 clock and ADC are uncalibrated. Note dssd4 is on MEC

Detector 1 noisy. 

AIDA started - all okay. 

All FEEs set to LEC (0x0) and slow comparator threshold set to 300keV (0x1e). 

Currently writing to data to G22-205/R100, doing background run, ~400 kB/s. 

16:40

Checks OK. 

19:00

Checks OK

22:30

Temps OK, Rates OK

x2go window size weird on different monitor as well.

27th August

Stopped Run 100. We had accidently set the threshold to 140 keV (0xe) not 300 keV (0x1e) as intended. 

Either way we require data on the alphas for electronics testing in October and the data rate at this threshold is too high. Threshold set to 0x64 (1 MeV) to look only at the alphas. 

Run 101 started. See attached leakage currents

20:30

Checks OK

28th August

10:00

Checks OK

CARME daq crashed this afternoon. Aida14 had a disconnection error. Seemed to coincide with dssd4 tripping again. 

Rebooting FEEs. On reboot there are always some FEEs which seem to have some error. The FEE changes each time. i.e aida12 one time, aida09 next time. I will give them a little while to compose themselves before trying again. 

Unable to get the system writing data to disk again. I think the system is unhappy with the merger / tape server not being closed properly. Will have a proper look tomorrow. 

29th August

20:15

Running again R102. 0x64 slow comparator thresholds. DSSD4 off due to leakage current tripping -> MEC

30th August

Daq continues R102

31st August

Daq continues R102

11:30

R102 stopped. CARME shutdown. This week, potentially tomorrow morning, the Kasell group will dismount the VUV spectrometer. CARME off and bias off during these works. 

08:07 CEST

Temperatures ok - attached

DSSDs on. Leakage currents still high. - attached

If ML & co cannot find the reason, will turn off FEEs later today

FEEs turned off, leakage current still high (DSSD off now). 

Motors out. 

---9 July---

11:00

Turned detectors on - all stable see attachment 1 

AIDA started - all okay. See attachment 2 for FEE temps.  

All FEEs set to LEC (0x0) and slow comparator threshold set to 300keV (0x1e). See attachment 3. 

After some issues tape server and merger all set up, NetVar not working??? have tried to reboot things but still getting issues. See attachment 4 for tape service and attachment 5 for merger. 

Currently writing to data to G22-205/R98 (R97 empty), doing background run.

13:30

All checks okay apart from white rabbit, see attachment 6.

Attachment 7 - stats 

18:30 CEST

More issues with anydesk - now refuses to connect with error message desk_rt_ipc

May be as simple as the monitor being turned off. Will have to be checked in person

Connected to atppc025 via x2go and from there checked

- Temperatures are fine (attached)

- Detector bias / leakage current is fine (attached)

- Data rate from file size being written is around 500 kB/s (fine)

- A number of interesting features in the online background spectrum. Likely all non-physical (attached)

- Stats OK (attached)

20:50 CEST

All checks good.

22:28 CEST

All checks good.

Features in the XY plot rensemble beam hitting the detectors. Attached.

Leakage currents and rates are good - unlikely to be major detector damage. Attached.

Only beam in the ring between now and end of D+D was stable uranium.

Killed CARMEsort via terminal (still no access to anydesk).

Restarted CARMEsort. No obvious structures appear after a few minutes. Was there beam in the ring today?

23:09 CEST

All checks good

Features in the XY plot and Ey plots disappeared.

---10 July---

03:22 CEST

All checks good.

Features gone. Attached.

05:15 CEST

All checks good.

07:34 CEST

All checks good.

10:40 CEST

All checks good. 

12:35 CEST

All checks good. Some features in plots again appeared in last 2 hours, attached Ey plot (attachment 15). 

14:40 CEST

All checks okay. 

16:40 CEST

All checks okay. 

18:40 CEST

All checks okay. Attachment 16 leakage current stable. 

Attachment 17 Ey plot.

19:35 CEST

All checks OK.

Reset the Root spectra again - highly unlikely to have beam overnight without experiments running.

23:39 CEST

All checks OK.

Still seeing peak at 6 MeV like attachment 17, after resetting the Root spectra. Detector damage? Still seems implausible.

Events are focussed as in attachment 12.

Reset again. No obvious peak or pattern after a few minutes running.

From Claude K

"CRYRING was running with the Uranium beam from ESR until Tuesday (8 July) night around 22:00.

From Wednesday noon we started to inject D+ from the local source and had the D+ beam stored at various energies from 14:30 until 17:40. During the night from Wednesday (9 July) to Thursday (10 July) there was no beam.

We then continued measurements with stored D+ On Thursday from ca. 11:00 to 21:00. Since then CRYRING is in shutdown."

---11 July---

08:07 CEST

All checks OK.

Peak at 6 MeV did not re-appear overnight. Attached x2.

12:00 CEST

All checks good! All plots look good!

16:00 CEST 

All checks okay! 

19:20 CEST

All checks OK.

Background peaks almost visible.

22:53 CEST

All checks OK.

---12 July---

07:25 CEST

All checks OK.

10:00 CEST

All checks OK. Temps attached.

11:00 CEST

All checks OK.

19:00 CEST

All checks OK.

23:00 CEST

All checks OK.

---13 July---

07:42 CEST

All checks OK.

11:00 CEST

All checks OK.

ELOG down during the afternoon

--14 July--

11:00 CEST

All checks ok. 

14:40 CEST

Tape service and merger now working on atppc025

All checks ok, briefly went no storage at around 14:38 CEST for 1-2 minutes whilst getting tape service and merger up. 

17:40 CEST

All checks ok. 

21:30 CEST
All checks OK.

23:16 CEST

All checks OK. Several screenshots attached.

Calibration appears to hinders clear alpha peaks.

---15 July---

07:47 CEST

All checks OK.

11:55 CEST

All checks ok. 

14:35 CEST

Issue with atppc025, see attachment 29 for error message (desktop 2, detectors etc)

Got error to go, all checks ok. 

17:35 CEST

Same issue with atppc025, otherwise all checks ok. 

20:30 CEST
All checks OK.

23:07 CEST

All checks OK

---16 July---

07:41  CEST

All checks OK

12:00 CEST

All check ok. 

15:15 CEST

Some fees have high rates, all other checks ok. 

15:32 CEST

The above behaviour appears to be correlated with an increase in leakage current across all four detectors. Most likely light?

The background is not reliable -> No storage.

Unfortunately the leakage current logger crashed a few days ago on the server, and without anydesk we did not realise. Restarted it on atppc025.

Informed ML about issue. If it cannot be solved we could increase the thresholds and keep going, but the background may not be representative.

16:35 CEST

Issue persists. ML and ZA are not aware of any changes, except power-saving mode enabled for cave AC. No effect on FEE temperatures - not the issue.

aida04 rates shows 0. Checkloaded. Fine for a few seconds. Back to 0. Data event rate 100,000 may be too high.

Increased thresholds to 1 MeV. Data rates lowered, but e.g. on aida04 still 40,000. Goes back to zero. Checkloaded. OK for a short while, then back to zero.

Tape server stopped. DAQ stopped - all FEEs respond, good! Merger still going.

DSSDs off. Will retry tomorrow morning.

23:44 CEST

Temps OK.

Updated anydesk to 6.3.2 CentOS7 release.

Works now.

15:20

DAQ stopped

Merger & Tape Server stopped

FEEs off

All detectors off

Leakage current plot attached

Leakage current file moved to /TapeData/

Will restart for a long background when the next experiment is over.

00.31 DAQ continues data file G22-205/R96_27
      
      DSSSD bias & leakage currents - attachments 7-8
      FEE64 temps OK - attachment 6
      ADC data item stats - attachment 5
      per FEE64 Rate spectra - attachment 4
      Merger & TapeServer - attachments 2-3

      Online analysis - attachment 1

      Analysis data file R96_29 - attachment 9
       no timewarps, all FEE64 deadtimes <<1%

04.04 FEE64 temps OK - attachment 10
      ADC data item stats - attachment 11
      DSSSD bias & leakage currents - attachments 12 & 15
      per FEE64 Rate spectra - attachment 13
      TapeServer - attachment 14

08.26 DAQ continues data file G22-205/R96_64

      DSSSD bias & leakage currents - attachments 16-17
      FEE64 temps OK - attachment 18
      ADC data item stats - attachment 19
      per FEE64 Rate spectra - attachment 20
      TapeServer - attachment 21

11:03 All checks OK
EyTotal histogram attached.

12:25 Temps OK. Rates OK.

15:03 run stopped - beam time over
all checks ok
EyTotal hist attached

20:00 - Go to YR cave to see what is going on

20:20 - Beam back

20:28 - Set Tape to Storage, rate ca 2500 kB/s
Temperature and rate OK, System wide checks OK

Target density low (4e12/cm2)

21:00 - target density still 4e12, Ey rate histograms attached (attach 4)

21:20 - Target density increased to 6e12, we see more indication of reactions

22:30 - All checks OK, tape rate still 2500 kB/s
Target density ~7e12/cm2, beam intensity ~1e9pps

23:00 - Target density 7.5e12/cm2, beam intensity: 1e9 pps. Particle detector rate: 8 kHz at injection
 Gas bottle pressure still above first tick 
 Target position X=-1000, Y=1400
 All running smoothly. CARME DAQ running OK. (Figs 5-7)

Run 94

Background with beam at 150 keV and no target.

Note energy is 0.15% off vs. beam and target to have a more realistic orbit.

As prior run but thresholds changed to

DSSD1 - 0xc

DSSD2 - 0x8

DSSD3 - 0x8

DSSD4 - MEC

Run 95

DSSD 4 worked briefly. Tripped again a few minutes into this run. Ignore

Run 96 - as run 94

run stopped at 14:00

Zoran reset to with-target settings for later

The plotted readout for the G35 voltage divider over several injections for this run is attached. This kind of data can be obtained from Konstantin also after the experiment.

The average is something like 88.4808 V.

Run 93- New run at 150keV, background with beam

13:15 All checks ok

Run 92- started at 09:00, background with beam

Same settings as run 91

See attachments for rates etc

All checks okay

09:58 Run stopped as now tuning 150keV beam

10:00 All checks ok

10:25 D2 bottle pack pressure 30 bar approximately

12:18 All checks ok

23:00 DAQ restored and data now being written okay. Checks all okay, see screenshots below. Histograms reset. 40 bars in bottle @ 23:45 - should last 30 hours.

12:00 Checks all ok. No problems with aidas or writing to disk.

01:10 Checks all ok.

02:05 Checks all ok. See attatchment 6 for peak update after reset histograms 3 hours prior. Target okay, dropped a little to 6e12 but seems to be going up itself. Will monitor and then move position if needed.

03:10 During checks, noticed detector 4 had tripped so turned it off. Writing to disk increased alot, statistics increased to alost 250000. Put aida13-16 in low/medium energy. Started new run. (see attatchment 7-14 for before and afters)

RUN 91

03:15 Checks all ok after turning off detector 4. Moved target around and got abit more density but x is very sensitive and y did not seem to do much. Density 5.5e12.

04:30 Checks all ok. Target decreasing in density - monitoring it.

04:35 Target density back up to 1e13 after moving in y.

05:30 Checks all ok. Target density decreased slightly to 8e12

06:30 Checks all ok, target density stable for past hour

07:30 Checks all ok

08:30 Checks all ok, target density at 1e13 for past two hours

09:00 Run stopped

Found all Merger Links background black - inactive. Nontheless the tapeservice was working, the data rate to disk was normal, and the file was being written and the histograms were being updated.

Decided to stop DAQ, stop Merger, restart merger. Links rest to green background - but no more writing to disk!

Killed Merger, killed Tape Service. Restarted.

Netvar read out at 3 - set to 1. When the Output of the Merger is enabled Netvar returns to 3. Tapeservice not writing to disk

Killed Merger, killed Tape Service. Restarted x3. Same behaviour.

Not working. No blocks being written.

With Tape Server status Stopped Ticked No storage, Unticked No storage -> Now writing blocks ?!

Tape Server Go. Writing to disk. Merger OK. Histograms updated, observables as normal (see next ELOG).

Lost runs 84-89 in the process.

12:15 restarted measurement with target - Run 83

same settings as for runs 76, 77 etc

ROOT histograms NOT zeroed

Beam at 8e8, target density at 1.5e13, scintillator @ 0 deg. peak rate 5000

status screenshots attached

15:15: Checks all ok, peaks are peaky (attatchment 8)

16:45 Checks all ok.

17:45 Checks all ok. IMP Froze and has been restarted. Peaks good. Light turned off iin cave.

18:40: Checks all ok. Target great at 1e13.

22:20 Checks done - all okay except aida green-to-red was not working, but still writing data to disk. Carlo trying to figure it out now. All other checks were okay. Daedalus crashed, restarted and target still at 1e13. 

Background without beam while source is optimised.

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).

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 control to 0xfffff. See attachments. 

D+ beam deuterium target. D+ beam energy is now 0.2 MeV/u. (beam calc calculation is 0.2037 MeV/u).

All four detectors positioned fully out and stationary.

Ring cycle time is 5 seconds.

Cooler read value = 117.58 V, 0.00178 mA

Target around 8.9E12 atoms/cm2

All checks ok!

Beam on ionisation profile monitor is lost quite rapidly and looks to increase in size quite a lot due to target interactions. We may have to look at lowering target density

Attachment 25 shows IPM with no target and attachment 26 shows IPM with the target 8e12 at/cm2. Compare also to attachment 12 (IPM with target at 2.6e12).  

14:20

Checks are ok!

15:25

Fees 13-16 switched to MEC and bias on DSSD4 switched off

All other checks ok

17:00

Target dropped to 1-2E12 atoms/cm2

All checks okay- 17:25

17:45

Moved nozzle from x=-1500 to x=-2000, density went from 1E12 to 3E12

Moved nozzle again at 18:00 from x=-2000 to x=-3000 in steps of 500, density at 4E12

18:45

Turned bias ON for dssd4 stable at V=10 but unstable at V=20 so bias turned back OFF

19:30

All checks ok!

IPM attached, target density 2.6 atoms/cm2 (attachment 12)

20:00

Tried moving the nozzle more as target density dropped to 2-3E12 again

Moved in 500 steps either side of x=-2500 but didn't improve, then moved in 100 steps from y=1600 to y=2300 and target density now 6E12 at x=-2500 and y=2300

Tried dssd4 again but only stable to V=20 so bias OFF 

21:50- All checks good, target density stable at 8E12

22:50- All checks fine (see attachments), target density at 6E12

00:10

Checks OK. Have zero'd statistics to see pause and resume statements over an hour.

Rates looks OK. ~140 c/h 3He, and ~80 c/h for 3H and 1H each.

Target has been stable at 7e12 at/cm2 for the last hour. 

02:10

Checks OK. See pause statements after 2 hours - attachment 27, very few overall.

03:07

Checks OK. Target (9-11)E12

04:06

Checks OK. Target (9-11)E12

07:00

Checks OK. Target 9.8E12

page AIDA/Check/Check.tml.  failed

ptoblem fixed

09:00

Checks OK. Target 8.9E12

10:32

No target data displayed for 10 minutes, but jet density unchanged. Restored display from remote access by M.L.

11:22

Storage data stopped and Faraday cup inserted to check the leakage current of Detector #4. Not good, current increases above 10 uA already at 40 V. 

11:29

HV Detector #4 swithced off, Faraday cup removed, data stored again.

11:35

Check OK. Target 8.6E12

13:06

Check OK. Target 7.5E12

15:00

Temperature check - aida03 returns "No response". No response for rates either. Merger looks fine for 3? Likely just happened.

Attempted to STOP the DAQ. All FEEs still going (refused to stop) and 3 in error. Decided to just turn all FEEs off.

Restored DAQ with no issues. 3 is working. Temperatures fine. Rates fine. Unclear what had happened.

Run59 is EMPTY. New run = run 60.

16:00, Full check, everything working after the restart

17:35  Full check, everything is working smoothly!

18:35: Full check, status -Okay.  thickness 5.7E12,

19:35: full ckeck! Status - OKAY, target theckness ~5E12

20:50 : Full check! status - okay

22:00 : Full check, status -okay. Target thickness 6.4E12

22:55 : Full check, status -okay! ------ target thickness 5.8E12

01:00 : Full check, all okay! 

04:00 : Full check, all okay! 

07:00 : Full check, all okay!

10:00

Attempted to change cooling to improve the beam. Changed cooling by 0.5V. Significant improvement in the IPM, but Rutherford goes down. Target missed?

Changed orbit bumps. Increased Rutherford. IPM is back to how it was. Rates are possibly slightly higher? Will attempt more systematically in the afternoon, when we change beam energy again.

Attempted to delay target on by 1 second. No significant changes in beam lifetime or rates. Can try systematically again in the afternoon.

Restored settings to how they were. Started new run 61.

Temps OK

Rates OK

Merger OK

Online histos look OK (did not reset)

Checks

Clock status

FEE64 module aida16 global clocks failed, 6
 Clock status test result: Passed 15, Failed 1

ADC calibration

FEE64 module aida16 failed
Calibration test result: Passed 15, Failed 1

White Rabbit decoder

   
         Base         Current     Difference
aida14 fault      0xbf08 :      0xbf08 :      0  
aida14 : WR status 0x10
 White Rabbit error counter test result: Passed 15, Failed 1

Understand the status reports as follows:-
Status bit 3 : White Rabbit decoder detected an error in the received data
Status bit 2 : Firmware registered WR error, no reload of Timestamp
Status bit 0 : White Rabbit decoder reports uncertain of Timestamp information from WR

FPGA Timestamp error counter test result: Passed 16, Failed 0

11:06

Run during beam change. We will go down to 200 keV/u

All the checks are ok.

No storage mode

Target off

We played with some of the slow comparator thresholds to judge the statistics and data rate. 

Deemed threshold at 100 keV too low for the current beam energy due to excessive rates observed on all FEEs. If required for lower energies we can go to this level. 

Data rate at 130 keV threshold is about 2 MB/sec compared to 8 MB/sec at 100 keV. Note beam energy is 400 keV so no significant benefit going to the lowest threshold. 

NOTE: RunR55 is missing

Run56: Background run with 250 keV/u. Target off using the usual procedure.

All  checks ok!

We moved to nostorage mode and will change the run during the beam change

10:00

The computer screen controlling the DAQ on carme-gsi appeared to have crashed.

Unable to move throught the different windows etc.

Unable to connect via anydesk. ssh access still available. It appears the x-server had crashed, we noticed earlier in the beam certain functions such as screenshots were glitchy so this was probably expected eventually.

We were able to access the DAQ on another CRYRING machine machine via 192.168.207.143:8015 and 192.168.207.143:8015 in the browser. DAQ is still running. We will try to reboot the x server without disturbing the DAQ.

ssh into carme-gsi and used the command 'systemctl reboot gdml' to attempt to reboot only this server.

This did not have the desired effect, whole of carme-gsi rebooted. We should have turned off the FEEs and stopped the DAQ gracefully but did not.

Restarted carme-gsi and rebooted the FEEs and DAQ system.

All checks OK -> clocks, ADC calibration etc.

ASIC settings loaded are 2025APR08. Only changes made to this settings were reducing the slow comparator threshold from 0x32 (1 MeV) to 0x14 (200 keV). aida03 and aida04 were set to the MEC on these settings, they have now been reset to the LEC channel (0x0). All channels on the LEC.

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

ASIC settings loaded 2025APR08. Only changes made are setting all FEEs to LEC (0x0) on channel 10, and setting the slow comparator thresholds to 0x14 (200 keV).

All beam settings are the same as the previous elog. Detectors remain stationary and in the fully out position.

All checks ok!

ADC data items statistics appear unchanged. See attachment.

Data rate ~ 800 kB/sec

12:40

All checks ok

The target is not super stable.

14:00

 Checks ok!  Target back to >3E12 1/cm2

15:00

 Checks ok! 

17:00

Full check, everything looks okay!, Areal density is in beetween 3-5E12. Rate in all the detectors look fine.

19:14

Full check, everything looks great. Average arial density around 5e12 atoms/cm2. For more details please look at the attached screenshots

20:20

Target density dropped to 8e10, We are waiting for 20 minutes before changing the nozzle positions!

20:41 : slowly increased to 2.2e11 but it is not increasing anymore

20:43 Changed the nozzle position X fromm -1000 to -1500

20:56, Target thickness recovered bsck to 5e12

21:25, Full check, everything runnig smoothly. There is nothing unexpected, for details, please have a look at the attached file

22:30 Full check, Stable target thickness of more than 5e12 atoms/cm2. everthig running fine:-) For more details, please look at the attached screenshots!

00:52

Temperatures OK

Rates OK

Leakage current stable

System wide checks OK

Merger OK

Beam is on

Target looks fine, 2E-10 mbar in YR09 Etarget

02:51

Temperatures OK

Rates OK

Leakage current stable

System wide checks OK

Merger OK

Beam is on

Target looks fine, 3E-10 mbar in YR09 Etarget

03:45

Temperatures OK

Rates OK

Leakage current stable

System wide checks OK

Merger OK

Beam is on

Target looks fine, 4E-10 mbar in YR09 Etarget

07:05

Temperatures OK

Rates OK

Leakage current stable

System wide checks OK

Merger OK

Beam is on

Target looks great!!! 1.1E13 this morning!!

08:05

All checks ok!

09:05

All checks ok! Target is perfect to make this Sunday amazing

10:00

All checks ok! We completed the data taking on this energy. Atatched the final stats.

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 bunched mode... So we started data taking and will update this situation as soon as Gleb called us. -> Update: Okay, we were the entire time in coasting mode

D+ beam deuterium target. D+ beam energy is now 0.25 MeV/u. (beam calc calculation is 0.2570 MeV/u).

All four detectors positioned fully out and stationary.

Left potentiometer = -2.76mm (corresponds to x = -2500, which is the more trustworthy value)

Right potentiometer = 1.77 mm (corresponds to y = 2500, which is the more trustworthy value)

Ring cycle time is 5 seconds.

Cooler set value = 146.25 V, 2 mA. Read value = 146.2 V, 0.00179 mA

All leakage currents look good.

Beam position. Vertical =0.0mm , Horizontal=-2.0 mm

Data rate ~ 812kB/s

After starting the run we struggled because we did not know whether we can trust the beam overlap test after going from bunched mode to coasting mode. We therefore stopped data taking for approx. 1h to to this test once again in coasting mode, but did it via the Rutherford measurement. The result showed that the optimum is exactly the same: x=-2mm (see attachment 1).

However, we are strugglign with the areal density... It quickly dropped to 2E10 and slowly recovered in a more or less oscillating way (see attachment 2; the first four columns are the integrals of the four detectors, the next column is the sum of them. Afterwards its the average areal density and the last column is the total integral divided by the average areal density).
 

19:29: Storage turned back on
Left potentiometer now = -2.79mm (corresponds to x = -5000, which is the more trustworthy value)

19:53: Areal density dropped to 2E11, so we moved the left potentiometer once from x=-5000 to x=-4500. Sudden increase in pressure, but slow decrease again.
19:59: Left potentiometer once from x=-4500 to x=-4000. Seems to be the right direction... But we do it slowly...

20:19: Full check. Everything is okay, but areal density is still... aweful... Most of the time its between 1E11 and 1E12 at/cm2
20:20: Left potentiometer once from x=-4000 to x=-3500. Seems again to be the right direction... Sudden increase from 7E11 to 2E12
20:40: Everything stabilized at a higher average areal density. We are now fluctuating between 1E12 to 5E12.

20:55: Left potentiometer once from x=-3500 to x=-3000. Seems again to be the right direction... Sudden increase from 9E11 to 3E12

21:56: Full check. Everything is okay and areal density finally stabilized. Its now since 1h between 3E12 and 5E12.
22:47: Full check. Everything is meraviglioso!

23:20 

Checks OK

Target density remains stable around 5e12 at/cm2. Count rate has improved to around 200 c/h for 3He, 150 c/h for 3H and 80 c/h for 1H.

02:20

All checks OK

Count rates look pretty good, target density has maintained mid-high e12 lavel over last 3 hours.

peaks in spectra very clear

05:00

Checks OK

Now have several thousand counts total. Target level in high e12 level.

07.06.2025

07:00

Full checks! Target level 1-6E12 [1/cm2]

10:00

The x server on the CARME-gsi computer appears to be struggling and is not able to be checked. Needs a reboot. 

We still have ssh access and are able to access the DAQ on another CRYRING machine machine via 192.168.207.143:8015. DAQ is still running. We will try to reboot the x server without disturbing the DAQ. 

oopsie whole carme-gsi rebooted not just the x server. Restarting DAQ

For 200keV the optimal horizontal position is -5mm.
For 250keV the optimal horizontal position is -2mm.

Both values are already given to the operators, so tomorrow we can just switch to 200keV and go on :)

Nonetheless, we now went to 250keV and start measuring.

Run 52 started at 17:53. Everything is running again. We started at 3E12 at/cm2

D+ beam deuterium target. D+ beam energy is now 0.3 MeV/u. (beam calc calculation is 0.3067 MeV/u).

All four detectors positioned fully out and stationary and also detector #4 is running again.

Left potentiometer = -3.03mm (corresponds to x = 0, which is the more trustworthy value)

Right potentiometer = 1.82 mm (corresponds to y = -1000, which is the more trustworthy value)

Ring cycle time is 5 seconds.

Cooler set value = 177.9 V, 4 mA. Read value = 177.65 V, 3.53 mA

All leakage currents look good.

Beam position. Vertical =0.0mm , Horizontal=1.0 mm

Data rate ~ 947kB/s

18:09: System check - everything perfect!

Leakage current attachment 1

Rates attachment 2

19:50: System check - everything marvelous!

22:05: System check - everything excellent!

22:50: System check - everything fabulous!

current spectra attachment 3

02:05

Temperatures OK

System wide checks OK

Statistics OK

Merger OK

Leakage current OK

Ring vacuum OK

04:52

Temps OK

System wide checks OK

Stats OK - attached

Merger OK - attached

Leakage OK - attached

Histos look good - attached

07:10

Temps OK

System wide checks OK

Stats OK - attached

Merger OK - attached

Leakage OK - attached

Histos look good - attached

11:31

All checks OK

13:54

All checks OK

Rates attached

09:49

DSSD4 has been biased to 100V in steps of 5V from 60V. It was previously stable overnight at 60V - attachment 1

Will keep an eye on it but looks OK at the moment. Current bias and leakage current - attachment 2

I have reset DSSD4 FEES (13,14,15,16) to the LEC and lowered the thresholds to be in line with other FEES.

Current slow comparator threshold for all FEES is 0x14 (200 keV).

Attachment 3 shows current ADC data items statistics.

Started a new run 51 with no beam and no target. Access to the cave is allowed.

Current data rate is 800 kB/sec.

All statistics and histograms in aida zero'd

12:57

Temps OK

Rates OK - attached

Merger OK

System wide checks

14:58

Temps - OK

Rates - OK

Merger - OK

15:00

Beam tuning to start soon. No storage.

11:30

Run 50 started.

D+ beam deuterium target. D+ beam energy is 0.35 MeV/u. (beam calc calculation is 0.3577 MeV/u)

Target density is about 4e12 at/cm2

All four detectors positioned fully out and stationary.

Left potentiometer = 18.86 mm

Right potentiometer = 19.8 mm

Ring cycle time is 10 seconds.

Target T1=30.1K, T2=31.8K.

Nozzle position unchanged since end of run 48

YR09-Etarget pressure = 2.05e-10 mbar.

Cooler  Read value = 207.1 V, 4.39 mA

All leakage currents look good (except dssd4, currently stable at V=60)

Beam position. Vertical =0.0mm , Horizontal=0.5 mm

Data rate ~ 172kB/s

Slow comparator threshold to 0x14 (200 keV) since we decreased beam energy.

13:00

All checks OK

We were seeing some rubbish obscuring the 3He peak. JM remembered setting the EYEX cut very high (3 MeV) on the online plot, Now it is reduced to 500 keV

See attachments of histograms before restarting code.
 

16:32 all checks okay
18:19 all checks okay
20:20 all checks okay
21:45 all checks okay

01:00 all checks okay

04:00 all checks okay

7:00

Run stopped - cave to be opened. Beam looks on when run was stopped.

Temps OK - attach

Leakage current stable - attach

Rates OK - attach

Merger OK - attach

Final spectra attached

09:30

Gas target shutter valve closed to save ring vacuum.

All checks OK

Stats at htis threshold with no beam attached.

Biased DSSD4 in steps of 5V from 60V since it has been stable since yesterday,

Was able to bias to 100V with no issues.

01:10

Gas target turned off via the shutter valve.

Run 49 started beam only background run.

Slow comparator threshold lowered to 0x14 (200 keV) in preparation for the energy change tomorrow morning.

Other than that no changes to the DAQ or to the experimental setup.

D+ beam remains at 0.5 MeV nominally. All four detectors positioned fully out and stationary,

I tried to re-bias detector #4 however was not able to bias past 70V. DSSD4 remains off and set to the MEC (0x1). (see attchement 1)

Ring cycle is every 10 seconds. Beam position unchanged, Beam position. Vertical =0.0mm , Horizontal=0.0 mm

Ring vacuum is now 3.16e-11 mbar. Before switching off the gas target density was 2e12 at/cm2

Data rate is 89 kB/sec

ADC data items stats remain largely unchanged at new threshold. (see attachment 2)

Aida01 has increased to several thousand. Tried check ASIC control on asic #4 of aida01->no effect on higher rates.

01:20

All checks OK.

After 20 minutes of running see energy histogram and xy histogram (attachments 3,4)

Interesting xy pattern (hydrogen? Injection noise?)

Note put aida13-aida16 slow comparator threshold back to 0x24 as we had some rates coming through (~1kHz) which is now back to zero. If we revive the detector in the morning, the thresholds should be lowered in line with other detectors.

03:00

All checks OK

04:30

All checks ok

7:20

All checks ok

Run stopped, final energy histogram and xy histogram attached.

Run 48 started. Everything is running again. We started at 3E13 at/cm2

D+ beam deuterium target. D+ beam energy is still 0.5 MeV/u. (beam calc calculation is 0.5143 MeV/u). See previous entry for beamcalc.

All four detectors positioned fully out and stationary, however we switched off detector #4.

Left potentiometer = -3.03mm (corresponds to x = 0, which is the more trustworthy value)

Right potentiometer = 1.74 mm (corresponds to y = -500, which is the more trustworthy value)

Ring cycle time is 10 seconds.

Cooler set value = 297.2 V, 8 mA. Read value = 296.7 V, 7 mA

All leakage currents look good (except dssd4, currently turned off)

Beam position. Vertical =0.0mm , Horizontal=0.0 mm

Data rate ~ 108kB/s

16:40  Change Gasjet target Y=-500 to Y=0
17:37  Change Gasjet target Y= 0 to Y= 500

20:30 We now take some time to optimize the areal density
20:30  Change Gasjet target Y= 500 to Y= 1000 (resulting in 2E12)
20:32  Change Gasjet target Y= 1000 to Y= 500 (resulting in 4E12)
20:33  Change Gasjet target Y= 500 to Y= 0 (resulting in 7E12)
20:35  Change Gasjet target Y= 0 to Y= -500 (resulting in 1.1E13)
20:37  Change Gasjet target Y= -500 to Y= -1000 (resulting in 1.8E13, still increasing and amazing for almost 1h)

21:48: Since approximately 20min its just going down systematically from a stable 2E13 to 6E12...) Lets try another round of optimization...
21:48  Change Gasjet target Y= -1000 to Y= -1500 (starting at 7E12 and resulting in 2E12)
21:49  Change Gasjet target Y= -1500 to Y= -1000 (starting at 2E12 and resulting in 6E12)
21:50  Change Gasjet target Y= -1000 to Y= -500 (starting at 6E12 and resulting in 9E12)
21:51  Change Gasjet target Y= -500 to Y= 0 (starting at 9E12 and resulting in 1.3E13 but dropping back to 7E12 within 3min)

21:54  Change Gasjet target. Leaving Y at 0, but moving X from 0 to -500 (starting at 6E12 and resulting in 3E12)
21:55  Change Gasjet target. Leaving Y at 0, but moving X from -500 to 0 (starting at 3E12 and resulting in 4E12)
21:56  Change Gasjet target. Leaving Y at 0, but moving X from 0 to +500 (starting at 4E12 and resulting in 6E12)

21:59  Change Gasjet target. Leaving X at 500, but moving Y from 0 to +500 (starting at 5E12 and resulting in 7E11...)
22:00  Change Gasjet target. Leaving X at 500, but moving Y from +500 to 0 (starting at 7E11 and resulting in 2E12)

Side comment: It seems no matter what we do, that there is a general decrease within the last 30min...

22:00  Change Gasjet target. Leaving X at 500, but moving Y from +500 to 0 (starting at 7E11 and resulting in 2E12)

Okay... No matter what we do... Its still decreasing...

22:03  Change Gasjet target. Leaving Y at 0, but moving X from 500  to 0 (starting at 1E12 and resulting in 2E12)
22:06  Change Gasjet target. Leaving X at 0, but moving Y = 0 from  to -500 (starting at 2E12 and resulting in 5E12
22:09  Change Gasjet target. Leaving X at 0, but moving Y = -500 from  to -1000 (starting at 5E12 and just randomly fluctuating within the next 15min... and more decreasing than increasing...)

22:25  Change Gasjet target. Leaving X at 0, but moving Y = -1000 from  to -1500 (starting at 1E12 and resulting in 2E12... )
22:31  Change Gasjet target. Leaving X at 0, but moving Y = -1500 from  to -2000 (starting at 1E12 and resulting in 8E11... ) Whaaaat????
22:32  Change Gasjet target. Leaving X at 0, but moving Y = -2000 from  to -1000 (starting at 9E11 and resulting in 4E12... ) Okaaaay lets wait and see...

01:00

Run stopped.

Final statistics very high. Over 10,000 counts for 3He and 3H, Over 5000 counts for proton.

Final energy histogram and xy plot on final attachments

Run 47 started. Target cooling down after water cooler failure, beam only background

D+ beam deuterium target. D+ beam energy is 0.5 MeV/u. (beam calc calculation is 0.5143 MeV/u). See previous entry for beamcalc.

All four detectors positioned fully out and stationary.

Left potentiometer = 18.86 mm

Right potentiometer = 19.8 mm

Ring cycle time is 10 seconds.

Cooler set value = 297.2 V, 8 mA. Read value = 296.477 V, 6.97 mA

All leakage currents look good (except dssd4, currently stable at V=40)

Beam position. Vertical =0.0mm , Horizontal=0.0 mm

Data rate ~ 25kB/s

13:00

Run stopped to allow tuning of parameters for 0.35 MeV/u

Run 45 started.

D+ beam deuterium target. D+ beam energy is 0.5 MeV/u. (beam calc calculation is 0.5143 MeV/u). See attachment for beamCalc

Target density is about 2e12 at/cm2

All four detectors positioned fully out and stationary.

Left potentiometer = 18.86 mm

Right potentiometer = 19.8 mm

Ring cycle time is 10 seconds. (optimized with calculation https://web-docs.gsi.de/~stoe_exp/web_programs/optimizer/index.php)

Target T1=29.9K, T2=31.6K.

Nozzle position was not touched since run 40 (not clear how to double check)

YR09-Etarget pressure = 1.33e-10 mbar.

Cooler set value = 297.2 V, 8 mA. Read value = 296.477 V, 6.97 mA

All leakage currents look good

Beam position. Vertical =0.0mm , Horizontal=0.0 mm

Beam intensity ~6e8 on bunched beam, unknown on coasting.

Data rate ~ 422kB/s

Attachements:

- beam cycle time optimzer results (https://web-docs.gsi.de/~stoe_exp/web_programs/optimizer/index.php)

- full paramodi export

- leackage current plot

- beam target overlap measurement

22:55 - all checks okay

23:00-00:00 atppc025 crashed, taking down the proxy to the internet and anydesk. Recovered remotely moving proxy to atppc022. Let Michael know, then move back to atppc025 (contact CB or JM). 22 seems to work fine, no rush

Tried to move InteractiveMotion.x screen on carme-gsi since it was on atppc025, which froze. Cannot ssh to carmemotorspi from carme-gsi, except if already ssh in. Must be a proxy issue. Motors are stationary, will fix tomorrow morning.

00:00 Found DSSD 4 unbiased. Strong spike in leakage current just before midnight. Correlated with atppc025 freezing? Maybe a power fluctuation? No storage. Attempting to re-bias. Beam and target appear to be fine. Merger appears to be fine.

Moved right arm slightly with servo. No effect on bias.

V = 50 -> 14 uA oscillating

V = 40 -> 7 uA oscillating

V = 30 -> 4uA stable

V = 35 -> 6.5 uA unstable

Cannot bias above 35 V. Will leave DSSD4 condition overnight. LEC-> MEC on DSSD 4.

Run 45 final histograms save. Started new run with same conditions except DSSD 4.

04:00

Temps OK

Rates OK (no dssd 4)

Merger OK (38 kb/s)

Histo attached

Could increase bias in 4 to around 70 V before the current got unstable. Ramped down to 30 V again. Need to try significantly slower, 10 V an hour or so -> morning shift.

07:10

Since 4:35 no electron cooler

7:15 electron cooler back

Temps OK

Rates OK (except dssd4)

Merger OK (38kB/s)

Histo attached

8:35

V=40  -> 8uA oscillating 

V=50 -> 8uA oscillating

V=40 -> 7uA oscillating 

V=30 -> 3.9uA oscillating 

Performed a V-I curve test of dssd 4

Turned bias OFF, went to 5V and then bias ON again 

V=5 -> 1.245uA stable 

V=10 -> 1.820uA stable 

V=15 -> 2.300uA stable 

V=20 -> 2.720uA stable 

V=25 -> 3.105uA stable 

V=30 -> 3.460uA stable 

V=35 -> 3.795uA stable 

V=40 -> 4.115uA stable 

V=45 -> 4.425uA stable

V=50 -> unstable 

Turned bias OFF again, then back on after few minutes

V=5 -> 1.240uA stable 

V=10 -> 1.820uA stable 

V=15 -> 2.295uA stable 

V=20 -> 2.715uA stable 

V=25 -> 3.100uA stable 

V=30 -> 3.450uA stable 

V=35 -> 3.790uA stable 

V=40 -> 4.110uA stable 

Leaving at 40 for a couple of hours 

10:55

Tried 0x1 for medium/low energy selection for aida 13,14,15,16 but rate was roughly 250000 across all 

11:30

Water coolers have gone down, moinitoring the FEE temperatures, stopped the run 

11:48

Water cooling back

Same settings are Run 43 but with coasting beam and scrapers set to:  30 / - 30 mm.

all checks ok, but WR timestamp error, see attached

19:28 the Run 44 has been stopped.

Same settings are Run 42 but bunched beam and scrapers set to:  30 / - 30 mm.

17:00

Scraper tests conducted. We tried moving in the scrapers both at a fixed position throughout and also moving with the injection cycle.

We were unable to find a good position with the scrapers that did not produce significant scattering in the detectors.

Therefore we have moved the scrapers back to the fully out position.

Run 42 started.

We have increased the storage time to 10 reps (1 minute) in order to investigate the shoulders on the 3He peaks online and whether it is likely from injection. I think it is likely just a calibration issue

D+ beam deuterium target. D+ beam energy is 0.75 MeV/u. (beam calc calculation is 0.7619 MeV/u). See previous entry for beamcalc.

Beam calc - Attachment 1

Target density is about 2e12 at/cm2

All four detectors positioned fully out and stationary.

Left potentiometer = 18.86 mm

Right potentiometer = 19.8 mm

Ring cycle time is 60 seconds. Note we see some hydrogen in in the spectrum, this disapears after a few seconds.

Target T1=30.0K, T2=31.6K.

Nozzle position x=-2.96, z=1.72 mm

YR09-Etarget pressure = 2.0e-10 mbar.

Cooler set value = 439 V, 15 mA. Read value = 439.81 V, 12.88 mA

All leakage currents look good

Beam position. Vertical =0.0mm , Horizontal=-1.5 mm

Beam intensity ~6e8 on bunched beam, 6e8 on coasting.

Data rate ~ 416kB/s

slow comparator threshold to 0x24 (360 keV)

Run 41 started.

D+ beam deuterium target. D+ beam energy is 0.75 MeV/u. (beam calc calculation is 0.7619 MeV/u). See previous entry for beamcalc.

Beam calc - Attachment 1

Target density is about 3e12 at/cm2

All four detectors positioned fully out and stationary.

Left potentiometer = 18.86 mm

Right potentiometer = 19.8 mm

Ring cycle time is 25 seconds. Note we see some hydrogen in in the spectrum, this disapears after a few seconds.

Target T1=30.0K, T2=31.9K.

Nozzle position x=-2.96, z=1.72 mm

YR09-Etarget pressure = 2.0e-10 mbar.

Cooler set value = 439 V, 15 mA. Read value = 439.81 V, 12.88 mA

All leakage currents look good

Beam position. Vertical =0.0mm , Horizontal=-1.5 mm

Beam intensity ~3e8 on bunched beam, 3e8 on coasting. Gleb has increased the intensity this morning.

Data rate ~ 403kB/s

Lowered slow comparator threshold to 0x24 (360 keV)

13:20 Run stopped

Wolfgang tuning next beam energy

All checks fine

Total stats: 7827,4085,1821

OFFLINE CHECK

I have check Run41 and applied the gain calibration from 2024 in addition to a tigher EyEx energy cut (600 keV from 3 MeV for the online script). We no longer see the larger hump to the side of the 3He peak in DSSD1. See final attachment for comparison.

Note no time cuts have been applied to this spectra.and a more rigourous gain calibration using the igher energy D+ runs will likely improve things further. 

16:30

Run 40 started.

D+ beam deuterium target. D+ beam energy is 0.75 MeV/u. (beam calc calculation is 0.7619 MeV/u)

Beam calc - Attachment 1

Target density is about 1e12 at/cm2

All four detectors positioned fully out and stationary.

Left potentiometer = 18.86 mm

Right potentiometer = 19.8 mm

Ring cycle time is 30 seconds. Note we see some hydrogen in in the spectrum, this disapears after a few seconds.

Target T1=30.1K, T2=31.9K.

Nozzle position x=-2.96, z=1.72 mm

YR09-Etarget pressure = 2.55e-10 mbar.

Cooler set value = 439 V, 15 mA. Read value = 439.81 V, 12.88 mA

All leakage currents look good

Beam position. Vertical =0.0mm , Horizontal=-1.5 mm

Beam intensity ~1e8 on bunched beam, 1e7 on coasting. This is less intensity than higher energies, may require an increase in the morning. 

Data rate ~ 403kB/s

Lowered slow comparator threshold to 0x24 (360 keV) since we decreased beam energy.

18:36

Temps OK - attached

Rates OK - attached

Merger OK - attached.

Spectra appear to have a flat background to the right of Rutherford that was not there at higher energies.

The xy plot also does not seem to be as centered.

21:17

Tems OK

Stats OK

Merger OK

Leakage current stable

Run continues OK

Ring vacuum 2E-10 mbar, likely getting less target.

02:00

Temps OK

Stats OK

Merger OK

Leakage current OK

Run continues - attached

Ring vacuum as before

04:20

Temps OK

Stats OK

Merger OK

L. current stable

Run continues

Ring vacuum as before

07:00

All checks OK

Leakage currents remain stable.

We have accumulated good statistics. 3He peak does seem a bit off. Cooling could be slightly off. Problem is not so bad looking at Ey compared to Ex. Online code uses pulser calibration only so may be a bit off depending on Ey/Ex.

Target density has been stable in the 1e12-2e12 at/cm2 range overnight. A bit more would be good.

Will ask on call operator to check cooling and try to increase intensity.

Run stopped gas target off.

07:30

Note during the tuning process we observed the same structure at 2.5 MeV in DSSD 1 as we did overnight that may overlap with the 3He peak. Perhaps it can be removed offline. See final attachment

08:45

Run 39 started.

D+ beam deuterium target. D+ beam energy is 1.0 MeV/u. (beam calc calculation is 1.0151 MeV/u)

Beam calc - Attachment 1

Target density is about 5e12 at/cm2

All four detectors positioned fully out and stationary.

Left potentiometer = 18.86 mm

Right potentiometer = 19.8 mm

Ring cycle time is 1 minute. Note we see some hydrogen in in the spectrum, this disapears after a few seconds.

Target T1=30.1K, T2=31.9K.

Nozzle position x=-2.96, z=1.72 mm

YR09-Etarget pressure = 2.55e-10 mbar.

Cooler set value = 575 V, 15 mA. Read value = 575.8 V, 12.9 mA

All leakage currents look good

Beam position. Vertical =0.0mm , Horizontal=-1.25 mm

Beam intensity ~1e8. We appear to lose intensity when reducing energy. It is still sufficient to for our purposes.

09.38

CRYRING vacuum and ambient temperature - attachments 2-3

09:58

All checks OK.

Target density is ~7e12 at/cm2

Data rate ~300kB/sec

All leakage currents look OK

After 1 hour we have 3671, 2515 and 1064 in each peak respectively. This is also logged on the google docs form in same tab as elog.

10:36

Temps OK

Data rate OK 326 kB/sec

Leakage currents stable

12:30

Temps ok - attach

Rates ok - attach

Merger ok - attach

14:20

Run stopped for energy change.

11.40 DAQ continues
      File G22-205/R38

      ASIC settings
       slow comparator 0x32 all FEE64s

      DSSSD bias & leakage current OK - attachments 1-2

      FEE64 temps OK - attachment 3

      ADC data item stats OK - attachment 4

      WR timestamps OK - attachment 5

      per FEE64 Rate spectra - attachment 6

      Merger & Tape Server - attachments 7-8
       filesystem /mnt/data1 4.7Tb remaining

      Online analysis - per DSSSD energy spectra - elastic peak max count / channel c. 250-300Hz - attachment 9

      CRYRING vacuum & temperature - attachments 10-12
       YR09 e-target gauge indicates vacuum transients from high e-11 to low e-9mbar presumably due to high density D2 target

11.42 All histograms & stats zero'd


17.36 DSSSD bias & leakage current OK - attachments 13-14

      FEE64 temps OK - attachment 15

      ADC data item stats OK - attachment 16

      per FEE64 Rate spectra - attachment 17

      per FEE64 1.8.L spectra - attachments 18-19
       aida11 p+n pulser peak width 63 ch FWHM 
       aida03 n+n pulser peak width 85 ch FWHM

      Merger - attachment 20

      Online analysis spectra - elastic peak max count / channel c. few Hz - attachment 21
       rates much lower than earlier - no beam and/or no target - alert JM

10:56

Run 38 started.

D+ beam deuterium target. D+ beam energy is 1.5 MeV/u. (beam calc calculation is 1.5160 MeV/u)

Beam calc - Attachment 1

Target density is about 8.5e12 at/cm2 after moving nozzle this morning.

All four detectors positioned fully out and stationary.

Left potentiometer = 18.86 mm

Right potentiometer = 19.8 mm

Ring cycle time is 1 minute. Note we see some hydrogen in in the spectrum, this disapears after a few seconds.

Target T1=30K, T2=31.9K.

Nozzle position x=-2.89, z=1.72 mm

YR09-Etarget pressure = 2.37e-10 mbar.

Cooler set value = 846V, 15 mA. Read value = 847.378V, 13.105mA

Detector 4 looks OK at the moment.

Beam position. Vertical =0.0mm , Horizontal=2.5mm

11:05

All checks OK

Data rate is ~300 kB/sec.

Leakage currents - attachments 2,3

17:56

Rates have dropped significantly. Do not see elastics peak. No beam?

18:23

Check in with HKR. The thunder and lightning storm appears to have knocked out the beam from 17:30 until 18:10.

Beam is now back with an intensity of 2e8 pps.

I have also adjusted the nozzle of the gas target slightly and recovered target pressure of 1e13 from 3e11 at/cm2. This has been stable for the last 15 minutes. I think during shifts we will require some nozzle modifications. It is not vital at higher energies but for energies during the week, we will need.

We again see the very nice elastic scattering pattern on our detector. I am concerned we may be some shadowing on our detector giving rise to the observed circle? Attachment 5

20:30

Checks all OK

Target density in last 30 mins ~1e13 at/cm2

DSSD4 still looking good and  stable

23:00

All checks OK.

Detectors all stable

Target density still in 1e13 range.

We have accumulated lots of stats! This run should provide an excellent run for energy calibration using elastics and reaction peaks.

We run overnight and change energy in the morning

01:00

All checks OK

Detectors stable

Target density stable 1e13.

05:00

All good still

07:05

Run stopped to change energy. Gas target off.

final statistics plot attached.

Leakage currents overnight also. DSSD4 had two transients during the night but recovered.

22:49

Run 37 started.

D+ beam deuterium target. D+ beam energy is 2 MeV/u. (beam calc calculation is 1.9211 MeV/u)

Target density is about 1.3e12 at/cm2. FLuctuations between 1e12 and 1e13 at/cm2.

All four detectors positioned fully out and stationary.

Left potentiometer = 18.86 mm

Right potentiometer = 19.8 mm

Ring cycle time is 1 minute. Note we see some hydrogen in in the spectrum, this disapears after a few seconds.

Target T1=30K, T2=31.9K.

Nozzle position x=-3.11, z=1.77 mm

YR09-Etarget pressure = 1.04e-10 mbar.

Cooler set value = 1126V, 15 mA. Read value = 1068V, 13.22 mA

Detector 4 is still a bit unstable in its leakage current but the data coming through looks good. Some crap is periodically written to disk when leakage current spikes. Attachment 1,2 for leakage currents.

23:30

Checks OK - high but managable rates from DSSD4

01:00

Checks OK - DSSD4 has settled down. Leakage current attachment 1

Ex energy histograms - attachment 2

X2go check on gas target shows density has dropped to 5e11 at/cm2 in last half an hour. 

03:56

Checks OK

DSSD had more issues but once more settled

Temps OK

Rates OK

DAQ continuing

06:00

Checks OK

08:00

We can now change to 1.5 MeV/u no storage mode enabled. 

21:47

Run 36 started.

D+ beam deuterium target. D+ beam energy is 2 MeV/u.

Target density is about 1.6e12 at/cm2. FLuctuations between 1e12 and 1e13 at/cm2.

Detectors are now IN with the servo motors only. Detectors are stationary.

Left potentiometer = 36.54 mm

Right potentiometer = 37.96 mm

Ring cycle time is 1 minute. Note we see some hydrogen in in the spectrum, this disapears after a few seconds.

Target T1=30K, T2=31.9K.

Nozzle position x=-3.12, z=1.72 mm

YR09-Etarget pressure = 2.29e-10 mbar.

Cooler set value = 1126V, 15 mA. Read value = 1068V, 13.22 mA

Detector 4 is still a bit unstable in its leakage current but the data coming through looks good. Some crap is periodically written to disk when leakage current spikes.

We will run like this for an hour then move detectors back out for overnight run.

after 1 hour of beamtime we stop.

Attachment 1 - xy plot

Attachment 2 - energy histogram NUCLEAR

21:00

Run 35 started.

D+ beam deuterium target. D+ beam energy is 2 MeV/u. (beam calc calculation is 1.9211 MeV/u -> may be wrong cooler voltage, need to check grafana)

Target density is about 4e12 at/cm2. FLuctuations between 1e12 and 1e13 at/cm2.

All four detectors positioned fully out and stationary.

Left potentiometer = 18.86 mm

Right potentiometer = 19.8 mm

Ring cycle time is 1 minute. Note we see some hydrogen in in the spectrum, this disapears after a few seconds.

Target T1=30K, T2=31.9K.

Nozzle position x=-3.06, z=1.72 mm

YR09-Etarget pressure = 2.29e-10 mbar.

Cooler set value = 1126V, 15 mA. Read value = 1068V, 13.22 mA

Detector 4 is still a bit unstable in its leakage current but the data coming through looks good. Some crap is periodically written to disk when leakage current spikes. Attachment 1,2 for leakage currents.

Attachment 3,4 data rate to disk and statistics tab for when detector 4 is behaving. When not data rate can spike to 4000 kb/sec. Looks OK at the moment.

Attachment 5 - xy plot. We observe a circular shape on the detector. We are unsure of what this is at the moment. Offline analysis required.

Attachment 6 - energy histogram including Rutherford.

Attachment 7 - energy histogram just nuclear peaks.

Attachment 8 - beam calc with read values. 

08:27

No run going.

Temperatures OK - attach

Attempting to bias channel 3 again. Slowly ramping up.

V = 60, I = 5.3

V = 70, I = 6.1

V = 80, I = 9.0 --> 6.2 (unstable). Decreasing bias.

V = 70, I = 6.0 (stable again)

Leaving at 70 V for a while to condition (?)

Resetting the gnuplot graph. Old caen_current.dat moved to G22-205-caen_current.dat and copied in /TapeServer/G22-205

10:10

Temperatures OK

Leakage current on channel 3 showed some issues, back to stable. See attached.

11:00

Temps OK

Leakage current stable.

Increased bias on channel 3 to 80 V. I = 6.2 uA stable. Leaving for a while.

12:45

Temps OK

Leakage current stable

Increased bias on channel 3 to 90 V. I = 6.3 stable. Leaving for a while.

13:30

Temps OK

Leakage current stable.

Increased bias on channel 3 to 100V. I = 6.3 stable. Hopefully it holds until the end of the beam time.

20:00

Leakage current on channel 3 had issues again and bias was reduced to 50 V. Remained stable. Turned to 60 V now. Still stable. See attachement.

FEEs on detector for -> MEC

Temps OK - attach

Checks as before - attach

Rates OK (four fees not counting as expected) - attach

Deuterium beam in the ring at 2 MeV/A approx 2E8 pps, significant H2+ contamination.

Deuterium target working, fluctuating around 5E12-1E13 atoms/cm2

Vacuum in YR09 - 3E-10 mbar

Beginning beam-target overlap measurements soon.

Oven temperature increased, current up to 3.5E7 pps.

Found beam-target overlap setting horizontal bump in RO9 to -2.5mm.

Target T1 30.5K, density increasing to 2.6E11 at/cm2.

19:08 Run 32 start

Moving left detectors (79.69->34.66mm).

Beam energy 1.85 MeV/u nominal

Electron cooler actual values: voltage 1.051 kV,  current 0.013215 uA, [voltage divider G35 1.0504 kV]

Stopped run, beam was still in bunch mode.

19:15 Run 33 start

All checks Ok.

Target at 3E11 at/cm2

Attachment 1-2 with rates and temperatures

20:20

Target density 3.4E11 at/cm2. Beam around 2.2-3.6E7 pps.

Checks ok! Spectra attached in att.3.

21:25

all good. Target density 4E11 at/cm^2

22:24

All checks are OK

Noted some variability in the injection intensity. For 15 minutes about half of shots were below 1e7. Perhaps some variability due to end of lithium in oven or increased temperture. 

Beam calc with read values - Attachment 4

01:30

All checks OK. Injection intensity has stabilised ~2E7

Target density is stable ~4e11 at/cm2

02:44

Suddenly see very high rates in DSSD4. Detector had tripped. Tried to re-bias but kept tripping.

Set to 70V, leakage current is about 17uA but fluctuates quite wildly. Set to 50V and leakage current is about 6uA but again has wild fluctuations. Not sure of the cause, this detector is not moving and is far from the beam.

Decided to turn detector off to try and protect it. We can  re-bias and monitor in the day tomorrow when we do not have beam on target.

This detector has tripped previously but was able to be re-biased at the time. See attachments 5 and 6 for the detector leakage currents.

New Run started R34.

Same conditions as before. DSSD4 turned off. To stop crap writing to disk I have set the corresponding FEEs to the MEC.

In principle we do not need this detector now as it is not moving to see the reaction.

Note I also observed in the system messages we semi regularly get a DHCP request from aida11. It seems to be functioning fine as I see the pulser signal in the spectrum browser. May be worth following up on at a later date. See attachment 7

All other checks OK

Data rate is now ~140 kB/sec

03:15

Tried to bias DSSD4 again. Leakage currents appear fine again.

Left for 5 minutes to gauge stability -> seems fine.

03:22

Have returned aida13, 14, 15, 16 back to LEC.  Maintaing the same run (34)

Scratch that. 03:27 detector tripped again. Will just leave it off tonight. Turned those FEEs back to MEC.

06:00

I have quickly looked at Run 33. We clearly see the 7Be again in both detectors. Locus on detector much smaller than at higher energies. 

All checks OK

07:07

Run stopped, switching to deuterium.

Detectors moved out

Shutter for gas target off.

Moved to next run -> no storage mode.

15:40

Waiting for Serge to come in to change beam energy.

Remaining at the same beam energy and settings as before, except RIGHT arm now moving.

Run 31

37.96 -> 83.69 mm

16:53

Serge arrived. Run ended. Motors out. No storage.

Temps OK

Rates OK

We start a new run with real data taking condititon: beam is ok, target density is 1e12 cm-2, detectors are moving in-out periodically.

Cooler voltage setpoint 1066.6 V. Read value 1068 V.

Current read = 0.01325 uA

Beam energy = 1.88 MeV/u (from HKR)

Attachment 1 - beamcalc with nominal values

Attachment 32 - beamcalc with actual values

Right arm at 19.80 mm

Left  arm IN at 77.56 mm (OUT 32.77 mm)

vertical beam position 0.0 mm

horizontal beam position  -3.0mm

Beam intensity ~1.8e+7 particles.

Target density ~1e12 at/cm2

Target temperatures: T1=31.4 K T2=35.1 K

17:48

aida01 fault      0x0 :      0x1 :      1  
FPGA Timestamp error counter test result: Passed 15, Failed 1

All checks OK.

The electron current from beamcalc is the setvalue.

18:51

aida01 fault      0x0 :      0x1 :      1  
FPGA Timestamp error counter test result: Passed 15, Failed 1

All checks OK.

20:20

aida01 fault      0x0 :      0x1 :      1  
FPGA Timestamp error counter test result: Passed 15, Failed 1

All checks OK.

22:02

         Base         Current         Difference
aida01 fault      0x0 :      0x1 :      1  
FPGA Timestamp error counter test result: Passed 15, Failed 1

All checks OK.

23:13

All checks OK. Target stabilized at ~6.7E11 at/cm^2

00:23

All checks good.

01:01

We are observing what seems to be a steady decrease of the target density, currently at around 5e11 at/cm2, whihc also seems to be following a decrease in the temperature T2.

1;40

All checks good. Spectra attached in att. 18. Target density still decreasing (3.7E11 at/vcm2)2

2:54

All checks ok. Attached rates and spectra in att. 19-20. target density decreased as continued, now around 2.5E11 at/cm^2.

We tried to move a bit around the nozzle/target, no effect.

Gone back to original value of x=1000, y=-4200.

Moreover, the screen with the program to move the detector seems to be bugged (gray background, a double window): however, the potentiometer value is chnaging and I see the usual effect of detector moving on the statistics, so i think it is fine

3:38

Checks Ok. Target 2.5E11 at/cm2

4:05

The bug disappeared

4:56

Target density is now 1.9E11 at/cm2. It is very low with respect to before, but our reasoning is that nothing can be done about it at night anyway (apart from moving the nozzle, which we tried without effect). O. pointed out that the beam lifetime is still such that the beam is gone before the next injection.

Checks ok. Attachments 21-22 spectra and xy plot. Some structure in top left?

06:00

All check ok. Target density 1.8E11 at/cm2

6:49

all goo, target 1.7E11 at/cm2

07:30

All checks ok, except timestamp (15 passed, 1 failed, see screenshot)

8:30

Tried moving the nozzle. Minor improvement in target density only. x=-1000 y=-4200

Stopped writing to disk while moving nozzle and stopped the motors. Restarted everything and moved to run 29 - no differences vs. 28.

09:11

Temps OK.

Nautilus does not respond to user commands. Attempint to make it work again without rebooting.

10:05

Stopped to reconsider which arm we are moving. Started to move arms around. Decided to stick with left arm.

Started run 30. Same as 28 and 29.

10:30

Temps OK - attach

Rates OK - attach

Stats OK (taken with arm in) - attach

Current histogram attached

11:40

Something happened to leakage currents. We see an increase in the top-right detector (which recovered) and a decrease in the bottom-right. Neither is moving.

No changes to left arm detectors, which are moving.

Temperature in the cave stable. No effects on the DAQ.

Temps OK

Rates in aida06 at 10k. Fast discriminator at 100k. Checkloaded. OK. Other rates fine.

Will keep monitoring.

11:50

aida06 fast discriminator over 100k. Checkloaded x2. OK now. Other rates fine.

No changes to leakage current.

13:20

Temps OK

Rates OK (aida 06 is no longer counting fast)

Leakage current stable

14:20

Run continues OK

Temps OK

Stats OK

Run 27 running

28/05/2025

(ignore 26 - in-between run)

We start a new run with real data taking condititon: beam is ok, target density is 9.6e11 cm-2, detectors are moving in-out periodically.

Cooler voltage setpoint 1128 V.

Beam energy = 1.99 MeV/u (from HKR) (same as run 25)

Left arm at 18.86 mm

Right  arm IN at 83.69 mm (OUT 37.96 mm)

vertical beam position 0.0 mm

horizontal beam position  -3.5mm

Beam intensity ~1e+7 particles.

Target density ~9.6e11 at/cm2

Target temperatures: T1=31.5 K T2=35.2 K

Beam cycle set to 10 seconds.

11;57

All checks OK.

Aida10's rates seems low now, but aida07 is instead jumping between 200 and 4000 following beam.

15:45

Root histograms refreshed.

Temps OK - attach

Stats OK - attach

All checks OK

Leakage OK - attach

             Base         Current         Difference
aida01 fault      0x0 :      0x1 :      1  
FPGA Timestamp error counter test result: Passed 15, Failed 1
If any of these counts are reported as in error
The ASIC readout system has detected a timeslip.
That is the timestamp read from the time FIFO is not younger than the last

23:20

JM thinks we cannot see 7Be locus on run 24. Possibly the right arm cannot get close enough.

Stopped moving right arm

Started moving left arm as previously: 32.52 mm -> 77.56 mm

Checked with bunched beam: not clipping. Possibly we could go further in - to be decided.

Started run 25

Target - 1.1E12 atoms/cm2

Beam - 1.2E7 pps

Root histograms refreshed.

Temps OK - attach

Stats OK - attach

All checks OK

Leakage OK - attach

Spectrum browser 1, 7, 8 attached

00:00

Run continues OK

Temps OK, Stats OK, Merger OK

01:15

Run continues OK

Temps OK - attached

Stats OK - attached

Merger OK

Rates OK - attached

Also attached current histograms

03:10

Motors now moving 32.77 -> 77.56 mm. Unclear why, should not affect results.

Target 1.1E12 atoms/cm2

Current 1.4E7 pps

Temps OK - attached

Rates OK - attached

All checks OK

Merger OK

03:37

7Be locus appears to be clearly visible. Attach 18

04:32

Temps OK

Rates OK

Merger OK

05:30

Temps OK

Rates - aida10 showes intermittently high rates around 10k. See attached. Seems to be linked to beam, already observed last night.

06:10

Temps OK

Rates OK - aida10 still counting 10k with beam, 300 without

Merger OK

Histograms attached

7:23- LB,PW

All checks OK, general behaviour consistent with previous observations. Beam current ~ 1E7 pps

8:40

All good, attachment 27 is the spectra. Beam current 1.3E7 pps.

9;50

All good, target very stable at 1E12 at/cm^2. Noticed also Aida01 and aida02 show same behaviour as aida10, but the maximum rate is between 1000-2000 (instead of the 10000-20000 of aida10)

Run 25 stopped 10:45, Run 26 started -> laser spectroscopy laser test

Run 24 running

27/05/2025

We start a new run with real data taking condititon: beam is ok, target density is 5e11 cm-2, detectors are moving in-out periodically.

Cooler voltage setpoint 1128.55 V.

Beam energy = 1.99 MeV/u (from HKR)

Attachment 1 - beamcalc with set values

Attachment 7 - beamcalc with actual values

Left arm at 18.86 mm

Right  arm IN at 83.69 mm (OUT 37.56 mm)

vertical beam position 0.0 mm

horizontal beam position  -3.5mm

Beam intensity ~2e+7 particles.

Target density ~5e11 at/cm2

Target temperatures: T1=31.5 K T2=35.1 K

Beam cycle set to 10 seconds.

17:32 all checks OK

17:35 target density jumped to at 9e11

19:30 all checks OK (spectra attached)

19:45 target density drops to 3.5E11

20:20 target density jumps to 7e11

21:30 all checks OK

22:50 all checks OK

Screenshots and ParamModi settings export attached.

1) Select 'No Storage' [workspace 4, display 1, browser tab 'TapeServer']
    If already in 'No Storage' mode please ignore this step

2) STOP DAQ [workspace 3, display 1, browser tab 'Run Control']
   all FEE64s should change status from 'going' to 'stopped' *except* whichever FEE64(s) have a problem - typically their status is 'going' or 'error'

3) Restart Merger by selecting the Merger icon [workspace 4, display 2]
    terminal window showing the startup will popup

4) Setup Merger by selecting 'SETUP' [workspace 4, display 1, browser tab 'NewMerger Control']

5) Start Merger by selecting 'GO' [workspace 4, display 1, browser tab 'NewMerger Control']
     all data links will be inactive (red)

6) Start DAQ by selecting 'GO' [workspace 3, display 1, browser tab 'Run Control']
     check that DAQ is *actually* going - if not repeat 'GO'

7) Check data is being transferred to Merger and TapeServer

    Select 'Reload' [workspace 4, display 1, browser tab 'NewMerger Control']
     you should see a non-zero 'current merged data rate' and all links should show as green at least some of the time (requires observation over several reloads)

    Select 'Reload' [workspace 4, display 1, browser tab 'TapeServer']
     you should see 'Blocks written' and 'kb written' counters increase

8) Unselect 'No Storage' [workspace 3, display 1, browser tab 'TapeServer']
    If already in 'No Storage' mode at the start of this procedure please ignore this step


   If you continue to have problems, please request expert assistance.

27/05/2025 ca. 6:00

We start a new run: beam is ok, target density ok, detectors are moving in-out periodically.

Cooler voltage setpoint  1105.7 V

Attachment 8 - beamcalc with actual values

Next entry - beamcalc with set values

Right arm at 19.80 mm

Left arm IN at 77.56 mm (OUT 32.53 mm)

vertical beam position 0.0 mm

horizontal beam position  -3.5mm

Beam intensity 1.7e+7 particles.

Target density ~6e11 at/cm2

Target temperatures: T1=31.5 K T2=35.2 K

Beam cycle set to 10 seconds.

All check are Ok!

6:30

Noticed a small spike in all leakage currents, see attachment 1

6:50

all checks ok!

07:40

All checks are Ok!

Aida 10 shows sometimes higher statistics.

09:02

All checks are Ok!

Aida 10 shows sometimes higher statistics.

10:00

Checks OK.

Compression works OK.

Moved to run 23. Now moving RIGHT hand side detectors instead of LEFT hand side.

Motion 37.96 mm -> 83.69 mm

Left arm stationary at 18.86 mm

Planning to change energy around lunch.

11:35

Parameters are OK! Tragte density dropped down a bit: ~6e11 at/cm2

12:35

Parameters are OK! Tragte density dropped down a bit: ~1e12 at/cm2

13:10

Starting beam energy change. Detectors OUT.

06:00

FEE modules power cycled.

No issues on power cycle restart.

All system check OK - clock status, ADC calibration etc.

ASIC settings loaded are the same as previous startup. Slow comparator thresholds 0x32 (500 keV) and all FEEs set to LEC.

Statistics (ADC data) - attachment 1. Note aida10 fluctuations between 10,000 and 300 which appears to be a physics effect (beam on target)

Spectrum browser - layout 1 - attachment 2

Merger - attachment 3

Tape server - attachment 4 Data rate is about 300 kB/sec.

FEE temperatures OK

Waveforms - attachments 4,5

All Lekagae currents appear normal

Online monitoring scropt started. Beam on target. Run 22 started. See nect elog for details.

Run 21 running

26/05/2025 19:42 p.m.

We start a new run with real data taking condititon: beam is ok, target density is 1.1e12 cm-2, detectors are moving in-out periodically.

Cooler voltage setpoint 1105.7 V.

Beam energy = 1.95 MeV/u

Right arm at 19.80 mm

Left arm IN at 77.56 mm (OUT 32.53 mm)

vertical beam position 0.0 mm

horizontal beam position  -3.5mm

Beam intensity 2.2e+7 particles.

Target density ~1.1e12 at/cm2

Target temperatures: T1=31.5 K T2=35.2 K

Beam cycle set to 10 seconds.

All check are Ok!

21:44

All check are Ok!

23:10

Data rate to disk ~300 kB/sec

All checks OK

ADC disk Items #6 and ADC data items screenshots - attachments 5 and 6

Target density has dropped slightly to 7e11 at/cm2. This is fine with lithium due to beam lifetime constraints.

00:43

All checks OK

01:52

All checks are OK,

Attached spectra (attachment 7 and 8).

target pressure seems to be back at ca. 1E12 at/cm2

3:27

All checks good.

target pressure went down to 5E11 at/cm2 for a while, then back up to ca. 9E11 at/cm2.

4:49

All checks good

Rates higher on aida10 and aida4 (see attachment 9), monitoring. It is not consistently high but for example aida10 goes 222->20000->300->11000. It seems to follow the detector movement (higher rates when detector are IN)

Data rate to disk ~370kB/s.

Spectra attached in 10-11.

5:11

Still flickering. Attachment 12 with rates.

Data rate to disk around ~400 kB/s

05:30

DAQ has crashed. All statistics on aida read zero. No data through the merger or tape server.

Stopped tape server and then Run control STOP. Most FEEs did not respond to the command and continued to read going and some undefined. Reset aida servers and reloaded webpages. Same status. Have to power cycle.

Run 20 running

We start a new run since the laser guys will do some measurements.

Zoran will increase the beam intensity

Detectors are out position

All checks are OK!

13:30

All checks are ok!

Summary: Target not running. Background runs written to disk, some with beam some without.

19:27 Data file R17  running

      DSSSD positions out. Nikos will work on the target.
      Started a new run just after changing the DSSSD position
      No storage enabled
      All the checks are ok!

At 20:30 after 2h there was possible to open the cave again and Nikos started to cool down the target. However, is not clear if they can close the ring again...

22:12  The beam is back again. Cave closed and we are cooling downg the target!

Data file R18 started now.

DSSSD positions out. 

No storage disabled.

All checks ok. See attached files Work on the target.

Sunday 25 May 2025

09:45 Data file R18 running

DSSSD positions out. 

All checks ok!

12:05 Data file R18 running

DSSSD positions out. 

All checks ok!

13:55 Data file R18 running

DSSSD positions out. 

All checks ok!

15:50 Data file R19 running

DSSSD positions out. 

Beam is off.

All checks ok!

21:50

All checks OK.

Monday 26.05.25 09:15

All checks OK.