14/04/25

Arrived at GSI in the afternoon.

Found that the coolant loop on aida08 had popped out which resulted in the high FEE temperatures observed (see attachment 1). Female swagelock connector on FEE suggested to be the cause as this connector has the locking mechanism. FEE dismounted and female swagelock connector removed. No obvious defect in the connector (see attachment 2).

Turning on detectors we observe ~4uA in DSSD2 and DSSD4 (right hand side detectors) and ~15uA in DSSD1 and DSSD3 (left detectors). Leakage currents in left hand side detectors is down from ~17uA seen at the end of last week and ~19uA at start of last week. Temperatures in the cave do not appear to have changed sufficiently to explain this change. VI curve completed to test diode response (attachment 3+4).

Motors turned on to again see if it changes the leakage currents in any way. Both arms homed. Left arm moved in with pneumatic and servo (10mm). No change in leakage currents during movement or when fully in. Same procedure with the right arm. No change in leakage currents in either. I doubt this is a light affect. If some light was incident on the left hand detectors, moving the detectors should have changed the amount of light on them in some way, reducing the leakage current. Similarly if light can hit the detector when fully in for the left arm, some should be hitting the right arm when it is fully in too, but no change observed on the right arm either. No light sources found on interaction chamber, baking jackets covers all ports.

Movement for several repeptitions with the pneumatic tried to see if this had any affect -> no change

Bias lines for DSSD1 and DSSD2 swapped around on the caen bias module. No change in leakage current for DSSD1 or 2. Channel on bias module not to blame.

Tried turning ion pumps off, no change on leakage currents.

Tried reverse biasing the detectors. Polarity for channels 0 (DSSD1) and 2 (DSSD3) swapped from -ve to +ve on bias module. Core and braid swapped on adaptor card. Completed VI curve when reverse biased for these detectrors. Obtain the same curve as with -ve polarity. Left at 100V for 10-15 minutes. Put polarities back to -ve, no change in leakage currents observed.

Opended up one of the diamond windows with bias off. Shone my phone light through the window for ~30 seconds. Closed window off again, biased, no change observed. Left detectors biased overnight. CH0 - 15.4 uA, CH2-14.7uA.

15/04/25

No change in leakage currents overnight. From gnuplot they look pretty flat overnight. Perhaps slight decrease.

Checked attaching LK2 jumper to aida09 (nn DSSD3). Could not reach other nn adaptor card. No effect on leakage current. Dismounted jumper.

New female connector mounted on aida08 and FEE remounted.

Restarted AIDA system by closing all windows and servers. Error on starup, could not connect to relay16 for FEE power.

Issue related to dew point interlock. Dew point sensor is very sensitive and any movement can cause it to trip. Sensor was not well supported on the coolant pipe. Sensor remounted with plastic zip ties. Issue resolved. Investigate some noise issues in the afternoon

After lunch I have noticed the leakage current have increased slightly. See attachment 5. CH3 is higher and appears to be fluctuating by 1-2uA. Turning off bias and going to cave to investigate.

Bias still higher and fluctating on CH3. Konstantin is in the ring, but he has not started any works yet, some grossmontage are also in the ring and are working on the new source. Could this be affecting us? Either way, will startup daq to check rates/noise etc.

Previous settings applied (i.e all channels back to LEC). Have lost the dew point interlock again!

I have suspended the dew point sensor in the air for the time being -> need to put a dummy in.

Grossmontage working on ion source have left and leakage current on DSSD3 is no longer fluctuating -> coincidence? (attachment 6)

AIDA started again. Rates appear OK except for on 3,4 and 15. (see attachement 7,8,9)  Note the rates on 9,10 are reduced compared to previous elog entry. Note pulser off. Note on aida startup aida16 clock status fail and ADC calibration fail for aida 6,14 and 16

16:00

We again see DSSD3 leakage current fluctuating. I will head back to the cave to check if anyone is working again? Nikos and davide working on the target but can't see how they would impact the leakage current (they were only installing a support for the new turbo)

DSSD3 remains fluctuating even now they have stopped working.

Pulser on. Same settings as elog 664 -> freq = 10 Hz

Overall pulser widths look bad, rates (ADC data items) look okay (~1000) for all except aida03 and aida04 (>250,000). Again rates on aida09 and aida10 are good although the widths are poor. One change I did make was to ground the FEEs to the CRYRING ground wheras previously they were grounded to the coolant pipe. I may try putting them back onto the coolant loop to see if there are any changes. Note grounds all around have not been examined yet.  Attachments 10-17 with pulser on.

Moved grounds back onto the coolant pipe -> no effect on ADC rates.

Also tried lowing slow comparator theshold down to 150 keV (0xf) for most channels (except aida3 and 4). See rates attachment 18.

FEE power off, bias remains on

09:00

Leakage currents this morning again appear to have lowered during the night. Current plot shows a day/night variation but I think the minimum is decreasing ever so slightly.

This morning DSSD1=15.1uA and DSSD3=14.4uA, this is ~0.3-0.4 uA lower than yesterday. DSSD4 is still fluctuating in its leakage current and looks to have been all night. See attachment 1.

Will now proceed to systematically check all grounds before restarting AIDA.

Several cables have been re-routed this morning to clean up the area, allow us to see clear what cable goes where, and are avoid any unwanted interference. E.g. ion pump cables have been re-routed to not be near the bias cables, one ion pump cable was running between the power and hdmi on one of the FEEs, this was been sorted.

All grounds have been checked, some loose cables have been tightend up. Current ground configuration has all the adaptor cards (nn and pn) on a single detector connected together. One grounding cable then goes from each detector to the right coolant pipe which all the other detectors are also grounded to. This was the configuration for the previous beamtime. Will start pulser tests after lunch. Bias back on, leakage current slowly increasing again, DSSD3 current no longer fluctuating.

13:00

Ground config 1 - attachments 2-7 (described above)

Ground config 2 - attachments 8-10 (grounds now go to the CRYRING ground cable not the coolant pipe and jumper removed form bias module)

pulser widths 1.8L worse pretty much across the board. No sig impact on rates

Ground config 3 - attachments 11-14 (grounds returned to coolant pipe)

pulser widths 1.8L better than config 2 but still worse than config1

Ground configuration returned to first configuration. Pulser widths consistent with that seen before.

Additional bias tests.

Disconnected the pn bias cable (core) from DSSD1 but left nn bias cable connected. Biased. Observed bias ramp up but no leakage current was seen.

Reconnected pn bias cable but now disconnected nn bias cable. Biased. Observed bias ramp up, leakage current was seen to increase during ramp to ~8uA. Once fully ramped, leakage current started to slowly decrease and eventually went to zero.

Repeated same tests with DSSD2. Same behaviour observed as with DSSD1.

Have removed motors pins and tried some movement again. No effect on leakage current. Checked pulser widths before movement and after movement (with pnuematic IN). No change in pulser widths.

End of day status FEEs off, bias on and monitoring. Motor pins out to allow for last movement check, motors code running in screen session.

09:00

Came in to see the bias for DSSD4 which has been fluctuating for the past few days had tripped during the night. From the gnuplot it looks like it was fluctuating all night and just after midnight it went above 20uA and tripped.

Other leakage currents are around the value they have been recently, day night cycle still observed. Again perhaps the leakage current of DSSD1 and DSSD3 is slowly decreasing and reaching a lower minimum value. Reset the module, DSSD4 does bias back up and is currently around 10uA. See attachments 1+2.

I have also noticed a small spike in current when starting up the FEE power, see the small spikes in attachment 2.

Continuing with different ground configurations from yesterday.

Ground config 5: I have now removed the grounding cables between non-bias FEE modules. So grounding cable goes between pn and nn bias FEEs and then one grounding cable to the coolant pipe. No grounding on any other FEEs. (attachments 3-8). Effect on pulser widths is hard to discern, some widths have decreased i.e 5 and 6 wheras others have increased such as 11. One interesting note is that the rates on aida03 have decreased by just over a factor 2 so now read ~100k. Whether this is the result of different grounding or maybe similar to what was seen for DSSD3 where rates decreased on there own over time? Attachment 8 shows the rates for each ASIC and most have now reached similar level to the other FEEs (note log scale).

Ground config 6: Have kept grounds to only pn or nn bias FEEs. Have now also included a ground cable from the body of the FEE module into the grounding connection. The ADC data items rate increase from 100k to 150k in aida03, no other impact on rates. Pulser widths remain largely unchanged, although some widths saw increases in the pulser widths. (attachments 9-13)

Ground config 7: Wanted to check impact of having no grounds at all. No impact on leakage currents. Rates look pretty similar for all FEEs, aida03 and aida04 200k and 350k respectively. Pulser widths and waveforms significantly worse than grounded case. See attachments 14-18

Ground config 8: Have reattached all ground cables (back to config1). In addition I have added a ground cable from the coolant pipe to effectively the CARME chamber. Rates appear pretty unchanged. Pulser widths better than no grounding but worse than original configuration. Attachments 19-23

Note since after lunch DSSD4 leakage current no longer fluctuating. Nothing has been changed. As I write that currents start fluctuating again. Maybe some ongoing work in the cave is affecting this?

Removed groud cable going to the chamber.

I wanted to rule out any affect from the test inputs. Have removed all test inputs. Only input is directly from pulser to DSSD3 as this previously had best pulser widths. All other cables removed. See attachments 24-26. Still see very high rates in aida03 and aida04 (250k and 350k). Pulser widths in DSSD3 seem worse now for some reason? While pulser detattched decided to lower slow comparator to 0x32 (500keV) and 0x24 (360 keV) to see rates in all FEEs. Rates still look pretty good, other than aida03 and 04. See attachments 27,29. Putting test inputs back.

Test inputs all back. Ground configuration back to configuration 1. Pulser tests, widths are best so far - will upload them later from all tests.Rates good in all except aida03 and aida04 still.

FEEs off, bias on and monitoring. Have put pins back in motors.

20:50

Bias has tripped again on DSSD4. It had remiained stable with noi fluctuations ~20 mins before leaving.

09:10

Arrived at GSI. Leakage currents status same as before, DSSD4 is still fluctuating. DSSD1 and DSSD3 currents are definitely lower again compared to previous days. I am convinced they are decreasing over time, whether this will be enough for our measurement....

While in the cave I again removed the motors pins so that the detectors can can be shook in an attempt to perform magic. While in the cave I also connected the CRYRING ground cable to the coolant pipe (ground config 11). Will see effect on rates / pulser.

Ground config 11 - see attachments 1-8. Rates in aida03 are massively down by a factor 10! Rates now ~20k. Aida04 still around 300k. On attachment 4 we can see the noise from zero energy on aida03 is massively down and we can now see the pulser, although the peak is double. Similar low energy noise is now appearing on aida15 and aida16 of DSSD4. Is this the early phase of what happended to DSSD1 and DSSD3?

Note the waveforms shown in attachments 7 and 8 change quite alot when updating the spectrum browser. Wave structure very visible in 7 but after updating a few times this disappears before coming back again a bit later.

20 minutes later ...

DAQ continued for about 20 minutes, noticed the leakage current in DSSD4 was no longer fluctuating. Zero'd stats and histograms to look again.

Stats in aida03 have increased back to ~100k, still less than before but back up from ~20k. Check of the pulser widths shows they have decreased across the board from the previous test 20 mins ago.

Leaving DAQ to run for a bit longer, the rates in aida03 continue to increase and are now back ~200k (back where it was).

I am currently trying to cycle motors. No effect on leakage current when cycling pneumatic motor. Note when using single commands such as 'l p in' I have no problems. But when trying a longer command where I ask the code to wait before pulling the pneumatic out again the code crashes. ??? Crash not repeated by Carlo remotely, Perhaps it is my laptop, or a bug relating to windows. Will investigate back in Edinburgh.

Have performed the same bias test for DDSD4 as #1 and #2 in previous elogs. Same behaviour observed. No (0.01uA) leakage current with only nn and current ramps up and falls to zero with only pn. I did notice that the ion pumps were arcing, I have not noticed this in prevous days. They have now been turned off, I think we can leave them off as they do little for the vacuum anyway unless using heavy gas taget gas. VI bias curve looks identical to one performed at the start of the week.

I have moved the PC power to the 19 inch rack. Power cycled the FEEs. I noticed the leakage current on DSSD4 was fine during VI test but after starting the FEEs power cycle they started to fluctuate again. After about 5 minutes after the startup, DSSD4 leakage current returned to a normal stable level. I have seen spikes in leakage current for all detectors during power cycle but perhaps it could also cause the fluctuations in #4. Overnight I have left FEEs off due to uncertainty over the swagelock on aida08 and the fact I was changing ground a lot so a background didn't make sense. Perhaps leaving FEE power on will stabilise DSSD4? I will leave system to stabilise a bit now (after seeing rates and pulser widths change in previosu test) and check pulser widths. Going for an awful GSI coffee.

New configuration: See attachments 9-13. Rates on aida03 and aida04 still remain very high >200k. Pulser widths across the board look pretty good. All have reduced since moving the PC on same power supply as 19 inch rack. DSSD4 leakage current has been stable the last hour since FEE power on. Waveforms look improved too. No longer see such high amplitude oscillations. Updated several times, see no change in waveforms like previous test.

Attachment 14 for pulser widrths from tests this week. Note x means no value. This could be because the width was so very big, or the test input wasn't connected. These values aren't too bad. DSSD2 and 3 have avergae pulser width (1.8L only) of ~60 keV.

Tried ground cable to NIM bin, had no effect / maybe negative effect. Disconnected cable.

D+D tests in next elog

Finally a pulser walkthrough was completed. Run8 has pulser settings unchanged, slow comparator at 0x64, aida03 and aida04 set to MEC. Pulser amplitudes 9000,8000,7000,6000,5000,4000,3000,2000,1000

A second walkthrough (Run9) was done with slow comparator set to 0x14, aida03 and aida04 set to MEC. Pulser amplitudes 9000,8000,7000,6000,5000,4000,3000,2000,1000,700,400 (so that we can check ~BBN energies) - attachment 15

During second walkthrough, DSSD4 starting fluctuating in leakage current again. No-one was in the ring. No observable change. FEEs were ON and were currently acquiring. ?? See noise which in attachment 15 on aida15/16 that only started when current was fluctuating.

FEEs off. Bias on and monitoring. Pins re-inserted into motors. Compressed air off.

D+D minimum energy Ecm = 150 keV which corresponds to Ed=150 keV/u or Ed=300 keV. Therefore we need a threshold below this.

Test 1 - Current status

Current slow comparator threshold is 0x64 (1 MeV). ADC data items rate in all FEEs is essentially zero with this threshold. (except aida03 and aida04). Aida15 and 16 also show ~1k rates when DSSD4 current is fluctuating.

Pulser was set to find point it is cut off by the threshold. Attachments 1,2,3 show 1.8L for nn channels with the pulser set to 570,550 and 530. Over this range pulser disappears. Estimate 550 is equal to ~1 MeV.

Test 2 - Noise level at lower threshold 200 keV

Threshold set to 0x14 (200 keV). Pulser kept at 550 for the time being to gauge location of noise compared to pulser. Attachments 4,5 show 1.8L for nn and pn channels respectively. Some noise observable at low energy.

Note zero energy is around 32500 channels. In nn channels (attachment 4) pulser is to the right of the noise peak, wheras in pn channels (attachment 5) pulser is to the left of noise peak.

Attachment 6 shows data rates with pulser off. Rates okay, only aida15 has very high rate (80k), rest of channels <5k.

Test 3 - Noise level at lower threshold 100 keV

Threshold set to 0xa (100 keV). Pulser kept at 550 for the time being. Attachment 7 shows data rates with pulser off. Rates significantly higher all round. Half of channels >50k, some >100k.

Attachments 8,9 show 1.8L for pn and nn channels respectively. A lot more noise observable at low energy. Pulser peaks generally overshadowed by noise. 100 keV probably too low to set threshold.

Test 4 - Noise level at lower threshold 150 keV

Threshold set to 0xf (150 keV). Pulser kept at 550 for the time being. Attachment 10 shows data rates with pulser off. In general rates are pretty low. Most channels <1k. Aida15 and 16 pretty high.

Attachments 11,12 show 1.8L for nn and pn channels respectively. Noise observable at low energy but in general less than that of the pulser peaks.

Test 5 - D+D pulser peak at lower threshold 150 keV

Theshold kept at 0xf (150 keV). Pulser set to 180 (should be about 300 keV based on Test 1). This should be the level of d+d at our lowest beam energy.

Attachments 13,14 show 1.8L for pn and nn channels respectively.

Test 6 - D+D pulser peak at lower threshold 200 keV

Theshold increased to 0x14 (200 keV). Pulser kept at 180 (should be about 300 keV based on Test 1). This should be the level of d+d at our lowest beam energy.

Attachments 15,16 show 1.8L for nn and pn channels respectively.

CARME_Sort histogramming has been updated to aid our understanding online.

> XY plots have been updated to reflect the true position of the beam relative to each detector. Online we will be able to layout in a grid to reflect looking downstream in YR09 (see attachment 1)

> Angle vs Energy plots have been created (see attachment 2). For this the position of the detectors has to hardcoded in the EventClustering header file of the code. This has been done using the detector positions from the 426 keV/u 15N measurement in 2024 which is the reference position. To reflect the true state during the beamtime a correction to these positions is required in the EventClustering regular file (e.g x_position + 30 mm). Correction can be applied using difference between potentiometer value and reference potentiometer values. 

Ref potentiometer value LEFT = 36.54 mm

Ref potentiometer value RIGHT = 64.60 mm

> An additional condition based on the cluster y position has been added for an event to be added to the histograms. This can be used to remove edge strips affected by the beam stripe (if beam stripe can't be removed via scrapers). This allows angle vs energy and regular energy histograms to be of use online. Currently this option is set to zero, can be enabled if beam stripe persists.

> Histograms not immediately useful (such as high energy XY etc) have been commented out. This makes the histogram browser cleaner and should ease use for online shifters. (see attachment 3)

> Corrections to CARME_Sort found during analysis of 15N data have been added to the code. These include Event timing cutoffs in the EventBuilder and a corrreciton to the BuildTimestamp function in DataItems file which was causing timewarps.

> Previous CARME_Sort versions have been saved and will be uploaded to github in due time.

EMERGENCY SHUTDOWNS

1. CARME motors: Q key on keyboard while on workspace 1 of appc218 (right of this double-monitor setup)

2. Internal target:

ELOG

The shift should put all information relating to the current run in ONE elog entry. If a significant change occurs during the shift i.e beam off, target off, run change, detectors out etc, start a new run and add a new elog entry.

Elog entry should be named by the current run number.

At the start of each new elog entry please state current detector positions, beam energy and run type (e.g. beam on target, background etc).

TO DO FOR THE SHIFTERS - CHECK EVERY HOUR AND POST TO ELOG WITH SCREENSHOTS. ELOG should be updated with current beam energy, injection beam intensity, system checks OK/not, FEE temperature OK/not, Statistics OK/not, Merger OK/not, tape server data rate, Motors OK/not and min/max motors potentiometer value. The time of each update should be noted in the elog. Screenshots of important screens (detailed below) should also be uploaded to the elog regularly (not required every hour).

CARME DAQ

CARME computer has 6 workspaces (WS), two monitors for each WS.

WS1 : left monitor - fee power

          right monitor - Detector Bias control, fee power server (just a terminal, do not close). Check detector bias is stable. If any detector current levels become unstable contact Jordan or Carlo and note time in the elog.

WS2 : left monitor - DAQ controls

          right monitor - DAQ server (just a terminal, do not close)

          Most important tabs (DAQ controls)

• Run control : shows daq status, stopped / going
• Fee temperatures : temperatures of fees labelled aida01, aida02, aida03, aida04, aida05, aida06, aida07, aida08, aida09, aida10, aida11, aida12, aida13, aida14, aida15, aida16. Hit reload, temperatures will update and should all be green. 1-2 C above safe limit (top) is OK. More than that - warn expert shifter immediately.
• Statistics : shows the statistics for each fee. Make sure ADC Data Items is selected in the left hand menu. Hit update all  (SCREENSHOT once, if no changes record OK in elog)
• System wide checks : checks for the setup. Click on 'Check Clock Status', 'Check ADC Calibration' and 'Check the White rabbit decoder status' to run checks. (SCREENSHOT once, if no changes record OK in elog)
• Spectrum browser : loads histograms for fees and fee channels from preset layouts. select layout from 'layout ID' then restore layout from 'Arrange functions' drop down menu. Check layout 1, Select log scale and change xmax as 128 . This displays the data rate per strip. If any strips are a lot higher than the others, or very different from previous entry, make a note in the ELOG. (SCREENSHOT once, if no changes record OK in elog)
• Asic control : sets asic parameters

WS3 : left monitor - Merge control, Tape server

          right monitor - servers (just terminals, do not close) , data being written to file

• Check NewMerger tab. Hit reload button and see if 'current links with data' and 'current merged data rate' are updating. All links should go green, but not necessarily at the same time. Keep hitting refresh until you see all of them going green at least once.
• Data rate, hit reload should be around 100,000. Record data rate in elog
• Check tapeService tab. Hit reload button. Check data rate in Kbytes/sec box. Record data rate to elog. This is where the current run number is displayed
• On the right-hand monitor, bottom right terminal, check the current run fragment (sub-run) is being written and is slowly increasing in size. It refreshed automatically every 5 seconds.

WS4 : Leakage current plot

• Check leakage current plot is stable. Transients will occur during motors movement but baseline current should remain consistent. Make sure it is updating and time is correct. (SCREENSHOT once, record OK in elog if no changes) Check present values on WS2, CAEN window

WS5 : Online data monitoring

• Check the following plots are updating for each DSSD
  • LowEnergyXY (right click - col - colz). This shows the total number of events, per pixel, since the code was started / re-started.
  • LowEnergyAngleE. This shows the angle vs energy plot of all detected events. Can be used to observed elastic scattering / 7Be from lithium measurement
  • LowEnergyXYRate (right click - col - colz). This shows the rate over the last 20 seconds.
  • LowEnergyExRate (double left click. Right click on y axis - Log scale on y). Rate over the last 20 seconds
  • LowEnergyExTotal (double left click. Right click on y axis - Log scale on y). This shows the total energy deposited on all X strips since code restart.
  • LowEnergyEyTotall (as above). as above, Y strips. (SCREENSHOT of each per DSSD per shift. If significant changes are observed screenshot again)

• During the shift, shifters should try to integrate peaks of interest. Area to integrate will be given in spreadsheet in same workspace as monitoring code. This is particularly important for D+D where peaks from each detectors for reaction products should be integrated every hour to determine how much time before moving to the next datapoint. For lithium beamtime this should also be done in the angle vs energy plot. Note the number of counts in the spreadsheet in the same workspace.

WS6 : Browser, ELOG

-->IMPORTANT NOTE: MIDAS DAQ can respond slowly. DO NOT try to change tab or give new command while the previous one is being executed. Check activity in right-hand part of tab currently in use. Do not double click on buttons.

Motors computer (Computer to the right)

• Check motors cycle is running. The code will cycle through the loaded motors instructions. When an instruction is being done it is highlighted in bold. Check the bold highlighting cycles through entire set of instructions.
• Check potentiometer is reproducing same max/min values for each cycle of instructions.
• Detectors are on LEFT and RIGHT arm.
• No need for screenshots, but record in the ELOG you checked this.

19:00

Arrived at GSI.

We have 6Li1+ beam in the ring at 2 MeV/u. Injection is about 2.5e7 pps and lifetime with no target is about 40 seconds. We have injection every 25 seconds.

DSSD bias situation remains unchanged from previous elogs. See attachment 1.

AIDA started - all looks OK. All FEE temps OK - coolant pipe must still be fine.

Set aida03 and aida04 to MEC (0x1) and slow comparator thresholds for all FEEs to 0x32 (500 keV).

Attachment 2 shows ADC data items rate for 1 MeV threshold. Attachment 3 shows the same but at 500 keV threshold with aida03 and aida04 set to MEC.

DAQ go rates look OK.

Setting up tape server and merger. I notice a strange occurance. NetVar options is set to 3 on loading. I set this equal to 1 so we can write to disk.... but this turns off the enable output to data storage off on the merger. By enabling output to data storage again the neVar options variable returns to 3 and we cannot write data to disk. I have tried reloading the servers for the merger/tape server and rebooting the FEEs -> still have this issue. It is pretty late so have turned FEEs off but left DSSDs biased at 100V.

Note the proxy is back up

09:45

Started up AIDA DAQ.

Started merger and tape server as yesterday. Today I have had no issues (same procedure was used last night?!). We are currently writing data to disk G22-205/R1

All FEEs set to 0x32 thresholds, with aida03 and aida04 set to MEC.

All sytem checks OK - no faults.

Temps OK

Merger running between 100k and 400k. Tape server writing ~300 kb/sec to disk.

Beam is ON. 6Li1+ at 2 MeV/u. Gleb is currently running machine tests.

Motors are not homed yet, waiting until beam is off and access to the cave to double check pins are out, Potentiometers read left=21.45mm and right=19.8mm

Attachment 4 - ADC data rates

Attachment 5 - Merger

Attachment 6 - Tape server

11:00

Safety meeting , beam off and access to the cave

Pins removed from motors and compressed air on. Motors homed.

Started background run (no beam) R3

13:30

We are now waiing for the target before we can begin tests today.

ASIC settings checked. We are using APR2025 settings. Only chnages made are aida03 and aida04 to MEC and slow comparator threshold lowered to 500 keV (0x32)

Fast comparator threshold is 0xff

14:00

Motors movement tested with signals from CRYRING. Dummy test signals sent through number 16 on the control room to CRYRING touch panel. This sent an injection signal followed by a dump signal 5 seconds later. Motors moved according to this pattern.

Command used on CARME motors code for future reference

l t in

l p in

l t out

l p out

l r 20

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.

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.

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.

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

11:55

beam intensity at injection: 8e7 ions

Temperature setpoint = 110 k

Rutherford rates shaky, peak max at ~ 3x10^2

Merger OK

Data rate ~ 1600 kb/sec

Ring avg pressure ~ 2.7E-10 mbar

Temperatures OK

System checks OK - wr fail attached

Leakage current ~ 3.22 uA

12.20 CARME IE514 4.1e-11mbar, ambient temperature 16.7 deg C

      FEE64 cabling complete

      WR source - VETAR2 borrowed from Nik Kurz and opwerating standalone ( no BuTIS reference )
      All MACBs mode 0x3


15.20 Power ON FEE64s #1 - #15

      aida02 did not boot - /etc/dhcp/dhcpd.conf typo - fixed

      aida04 did not boot - AIDA FEE64 PSU output #4 fuses open circuit - fuses replaced from AIDA FEE64 PSU spare channel ( aida16 not connected yet ) - fixed

      aida07 did not boot - power OK - FEE64 comfort LEDs OK - network switch link LED OK - network config?

      aida08 boots - power OK - comfort LEDs OK - network switch link LED OK - requests RFS / but does not request RFS MIDAS - can ping aida08 OK, cannot telnet aida08 'connection refused'

      aida09 did not boot - FEE64 comfort LEDS OFF - swap FEE64 #9 & #10 power cables - aida09 boots OK, aida10 does not boot
      Restore #9 & #10 power cables - swap AIDA FEE64 outputs #1 & #2 ( aida09 & aida10 ) - aida09 boots OK
      Conclude AIDA FEE64 PSU ( no label ) output #1 is faulty. Replace AIDA FEE64 PSU ( label ISOL3 ). aida09 & aida10 boot OK

      aida15/aida16 MAC addresses were swapped in https://elog.ph.ed.ac.uk/CARME/467 - fixed

      aida01-aida06, aida09-aida15 boot OK - aida07 does not boot, aida08 does not complete boot

16.25 Configure MIDAS DEE64 servers aida01 - aida06, aida10 - aida15 

      FEE64 temperatures - attachment 1
      aida06 looks low ( c. 25 deg C cf. c. 40 deg C )

      System wide checks - attachments 2-8
       aida02 fails WR decoder

      WR timestamps ( attachments 7 & 8 ) look odd/low - values always c. 0x2???


17.30 CARME IE514 OFF

      WR NIM emulator SMA cables to root MACB ( rear panel ) disconnected at front panel

      Power cycle FEE64s

      System wide checks & WR timestamp control - attachments 9-14
       no change

17.45 Detector bias -20, -100 & 150V - attachments 15-17
      CAEN N1419ET non-floating outputs ( to be checked ), HV cable SHV - 2x Lemo 00.250, LK1 not fitted 

18.40 Detector bias -150V attachment 18




To Do
Check ASIC settings
Configure HV
Check LKs
Ground cabling
      

Courtesy Nik Kurz, JG has installed a PEXARIA5 PCIe card adjacent to CARME - BuTIS single-mode fibre input
and HDMI output to root MACB input for distribution to the other MACBs and FEE64s.

The PEXARIA5 card provides equivalent functionality to the VETAR2 VME module that we have used to date. 

Further information https://www.gsi.de/fileadmin/EE/Module/EXPLODER/pexaria5_14.pdf 

Cooling water ON 

Via Anydesk startup MIDAS and FEE64s

Power ON
DSSSD HV OFF ( not required for WR test )

FEE64 temperatures OK - attachment 1

All system wide checks OK

Info code 4 & 5 stats OK - attachments 2 & 3

10:48:46 WR timestamps OK - attachment 4

         Timestamp (ns) converted to (s) corresponds to 09.49.22 GMT 6.3.24 which appears to be correct

11.00 Power OFF

07.00 

JG found target off (target data stopped c. 02.30 this morning) and beam off (not re-enabled from previous CRYRNG area entry - target related?) JG re-enables beam 

07.37 

Run R5 stopped Run R6 started - switch to no storage mode 

07.44 

DSSSD bias and leakage currents - attachments 1 
FEE64 Rate spectra OK - attachment 2 
ADC data item stats OK - attachment 3 
FEE64 temps OK - attachment 4 
WR timestamps OK - attachment 5 
Merger and Tape Server - attachments 6 
DSSSD x-y hit patterns - attachment 8 
Per JM instructions will move detectors toward beam axis by 30mm and investigate effect of e-target scrapers 

08.45 

Run R7 JG has setup e-target scrapers (YR09DS1HA and YR09DS1HI) both scrapers are set to move with the beam cycle. They move in with the start of the 'target' period 
(SC3). They move out with the start of the 'intermediate' period (SC4). The movement is rather slow (~1sec) so there is still some unblocked time during 'target' period. 
The positions are YR09DS1HA (outside): 10mm (SC3) and 30mm (SC4) YR09DS1HI (inside): -0.5mm (SC3) and -20mm (SC4) 


11:50 

Jan has been playing with the scraper settings so that we can take a run with the scrapers  and without. 

Since he has been playing. We see the beam halo. This is when scrapers were in and beam was moved to the inside of the ring by 5mm. See attachment 10

Moving the beam to the putside of the ring by 5mm we see halo on the left now. See attachment 11

We believe this is scattering from the edge of the scrapers. See attachment 12 for the energy spectrum which corresponds to attachment 11. It is consistent with 
scattering.

We will now take a run with and without the scrapers in and with the left detector moving in with every cycle via the pneumatic motor.  

12:20 

R8 started. Scrapers in. Left arm moving in synchronous with the ring cycle, potentiometer when IN = 62.71 mm. Right arm stationary and OUT, potentiometer = 19.8 mm

13:00

Run 9 started. Same condition as run 8 except no scrapers.

13:35 

Run 9 stopped, R10 started -> no storage 

13.37 Merger - attachment 13

      per FEE64 n+n Ohmic 1.8.W spectra - 20us, 200us, 2ms, 20ms FSR - attachments 14-18
      per FEE64 p+n junction 1.8.W spectra - 20ms, 2ms, 200us, 20us FSR - attachments 19-22

      per FEE64 Rate spectra - attachment 23

      WR timestamp OK - attachment 24

      ADC, DISC, PAUSE  RESUME data item stats - attachment 25-28

      FEE64 temps OK - attachment 29

      DSSSD bias & leakage current OK - attachment 30


14:00

R11 Pulser walkthrough 
    See attachments 31-32

Following pulser walkthrough R12 started with no beam and no target in the ring. Cave is accessible while we switch to 7Li

20:15

System checks OK

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.

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.

Beam is still beeing tuned. Target is off.

There is a problem with ADC calibration of aida5: see entry https://elog.ph.ed.ac.uk/CARME/268

- Motor on manual

SW3

- Merger OK

- Screenshot uploaded

- Data rate : ??? kbytes/s

SW4

- current plot uploaded

SW2

- T OK

- system wide check OK (ADC calibration test for AIDA5 failed, see above)

- Statistics ok

- Spectra ok

SW5

4 plots uploaded