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