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.

Beam energy = 1.88 MeV/u (from HKR)

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.

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)

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

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.

Summary: Target not running. Some background files written to disk, some with beam some without. 

09.27 DAQ going
      Switch from 'no storage' mode - alpha background
      Data file R13 

      All histograms & stats zero'd

      ASIC settings 2025Apr08-13.45.30
       slow comparator 0x32

      Pulser ON

      DSSSD bias & leakage currents OK - attachment 1-2 
      FEE64 temps OK - attachment 3
      ADC data item stats - attachment 4
      per FEE64 Rate spectra - attachment 5
      WR timestamp OK - attachment 6
      System wide checks OK *except* WR decoder/FPGA error - attachments 7-8
      Merger & TapeServer - attachment 9-10
      CRYRING vacuum & temperature - attachment 11-12

10.07 Laser group have completed their work in the CRYRING area - will now request 7Li beam
      Tape Server to 'no storage' mode

10.45 Beam 7Li1+ c. 1e6 
      Switch from 'no storage' mode - alpha background
      Data file R14
      All histograms & stats zero'd; online analysis restarted

11.35 per FEE64 1.8.L spectra - attachments 13-14
       pulser peak width aida03 78 ch FWHM, aida11 63 ch FWHM

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

12.55 DSSSD bias & leakage currents OK - attachment 19-20
      FEE64 temps OK - attachment 21
      ADC data item stats - attachment 22

14.33 Switch Tape Server from 'no storage' mode
      Data file R15
      DSSSD positions Left 36.54mm, Right 64.60mm

16:22 Data file R15 still running

      DSSSD positions unchanged (Left 36.54mm, Right 64.60mm)
      All the checks are ok!


18:30 Data file R16  running

      DSSSD positions out. Nikos will work on the target.
      Started a new run just after changing the DSSSD position

      All the checks are ok!

10.12 DAQ, Merger & Tape Server running OK - no storage mode 

      DSSSD bias leakage current OK - attachments 9-10

      CRYRING vacuum & temperature - attachments 11-12

      FEE64 temps OK - attachment 8

      ADC & DISC data item stats OK - attachments 6-7

      per FEE64 Rate spectra - attachments 1 & 5
       before and after check ASIC load

      WR timestamps OK - attachment 4

      System wide checks OK *except* FPGA & WR status - attachments 2-3

10.33 All histograms & stats zero'd
      Online analysis restarted

13:56 Checks on temperature status, statistics status and power supply : OK 
      

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

15:30

Waiting for the target to cool down. ETA is 16:30 for cooling to be finished and then we need to try and make target.

While waiting we havve been running a background (R3). I noticed the rates on aida10 had increased (300k) and aida09 were slowlly creeping up too. Check load and shaking the detectors did not work. These FEEs correspond to the high leakage current detectors and showed similar rates to aida03 and aida04 which were turned to MEC.

Tried some tests. Lowered bias voltage to 50V. Rates increased on aida09 and aida10. Increased voltage to 110V and rates dropped to approx zero. Checked 105V and we get the same effect as at 110V. 

Then decided to try to increase the bias on DSSD1 as well. 110V no ffect but at 115V we see the rates drop to zero.

Data rates of ~300 kB/sec writing to disk.

Some increases in rates on aida12 have also been noticed. We have turned the fast discrimtor off for this FEE which has resolved the issue. We should keep an eye on the rates as we hope this is stable but may not be.

 Attachment 1 - current ADC data items rate with new settings. (still 0x32 slow comparator, all channels LEC)

Attachment 2 - aida12 discriminator settings.

Attachment 3 - current bias/leakage current values.

Started R4 - background we expect beam in the ring soon.

16:00

Beam is in the ring - we see the beam stripe on DSSD1

No change on data rate writing to disk or in ADC statistics rate.

Motors fully out. Left potentiometer = 18.86 mm, Right potentiometer = 19.80 mm

Beam energy = 2 MeV/u - 6Li1+

Cycle time is 25 seconds

Attachment 4 - CARME detectors xy plot

Attachment 5 - Total energy histograms (Ex)

17:56

Nikos requires access to the cave so beam is stopped and background run is going.

R5 started. Same settings as previous run.

21:45

All system checks OK - except white rabbit decoder and FPGA timestamps see attachments 6,7

Data rate had gone high again ~2 MB/sec. No difference on ADC data items. Large increase on aida06 for aida disc info #6.

Checked hit rate for aida06 and see ASIC 2 was misbehaving. ASIC check load on asic 2 -> problem sorted. This is not first time this has happened. We should keep an eye on the data rate.

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

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.

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.

DAQ quick manual

cabling documentation

MBS trigger inputs

scaler inputs

Proxy bridge enabling anydesk and generic Internet access dropped due to atppc025 being rebooted. Found it dropped again late today.

Restarted bridge inside a screen session.