Data from current run - 35, with limited beam current and rates - see a recent post by Güray.
BU level, so what we see in Greware (both online & nearline).
Attached is the fold of Germaniums.
It seems way too large to me.
We are summing up the events and then, not surprisingly, having rubbish gamma-gamma matrices.
The gate is 1500 ns, while Ge are not so far away from each other.

Any fixed time differences should be corrected with LF configuration.
Having all Ge, ACS, and Neda TS-aligned at LF level, BU will do a good job with a reasonable short gate.

We need channel-by-channel TS differences.

The data we took and we are taking now can be recovered in terms of this correction later on.

Marcin can build the events correctly from LF level.
Let's try to do so with as short gates as possible and see again the gamma-gamma matrix and neutron-gated g-g 
matrix.

Since we were observing jumps of 16 ns in timings of all channels of whole boards, the assumption was that the 
signals from logical FIFO arrive at different times to S-IN inputs to zero the TS counters.
6 originally placed cables of quite the same length were replaced with 6 cables of declared 3-ns length, same 
producer, borrowed from NW's equipment.

target and stopper and beam dump dismounted.
only the constructional elements of the plunger remained. 

pure background, g trigger only.

Michal says the"bg" spectrum did not change...

41_ge_single_theta 101,117,143 looks ok. No peakdeformation of 511, other gammas FWHM around half of that of511 - ok

ch4 in total rate EAGLE_0 arouns 2.1 kHz - ok

planger tollerace limits (green and blue horizontal markers) set far of the current distance, intantionally?

ch4 in total rate EGALE_) reached 2.4 kHz, beam intensity has been reduced to fit the required 2kHz.

at 11:34:50 sek on 11 march a spike in counting rate of some Ge detectors is observed. Buffers not cleared properly?

Again beam intensity gradually increased reaching 2.4 kHz ontotal rate EAGLE_0 ch4.  Beam intensity reduction requested. 1.8 kHz on ch4 after reduction.

14:12 beam intensity instability. Rapid increase of beam intensity - twice the previous value. Returned to normal after 4 minutes.

Large beam intensity instabilities from 14:10 till 14:40.  Beam intensity reduction requested. CH4 on Total rate EAGLE_0 returned to 1.9kHz. Intensity became stable.

Again beam intensity to high. Reduced to 2 kHz on ch4 GE

Beam stable, counting rate within limits, plunger distance within the given tollerance, gamma spectra ok, everything looks good but....

(yes there must be some "but"), refreshing of EAGLE_array_monitor.mat and NEDA_array_monitor.mat are out of sync. Mostly pure red colour is dysplayed. Not very usefull and (I suppose) missleading information.

For a split second a red "NO DATA" notification appeared in the top right corner of Counting rates dashboard.

It looks like it did not change anything in data collection.

Run 27 with single gamma trigger

Plunger feedback system is not conected.

Data

Position = 522.6

Supposed = 520

Plunger run = 32

Micrometer = 525.3

Run Data = /onlineNEDA_00/xData/currentRun/needleRU_i27_0027_0027.caendat

RU = 5.10 Mb/s

LF = 3.75 Mb/s

Nothing really to report. The data rates are slowly decreasing from around 3 am. Still observing the frequent sharp minima in the data rates.

Using  the data which we've sorted to date, I looked into the gamma-gamma coincidences and have identified a number of nuclei e.g. 50Cr, 52Mn, 55Fe which would be consistent with fusion-evaporation reactions involving the sulphur-32 projectiles and aluminium-27. Such reactions would yield a 59Cu comound system and these channels would be populated as a result of the evaporation of a combination of alphas, protons and neutrons.

These lines are intense and the conicdences are very clear and clean. I think this suggests that the beam is hitting some aluminium components within the plunger chamber. This could be the plunger vessel itself or the target frame perhaps.

There is another interesting observation: some of the identified transitions are emitted from levels which have sub-ps lifetimes. At this plunger distance, we might expect these lines to be fully Doppler shifted as they would decay in-flight well in advance of reaching the stopper. Yet, we observe these lines with their non-Doppler shifted energies suggesting that they are not being emitted in-flight but rather at rest. This might suggest that the 32S+27Al reactions are taking place within some thick piece of aluminium. Some of the lines show signs of having been shifted in energy to some extent which might indicate that not all of the ions are completely stopped. The observed lineshapes seem to be consistent with the short-lived states showing evidence of Doppler shift while the decay of the "longer-lived" states (~9 ps) are very sharp.

I haven't slept for about 24 hours so I may be talking absolute sh*te (famous Scottish word).

Plunger run files for later to calculate error in the distance

Before this run TSs were moved on the LF level, so the BU has easier job to do and everything is more stable.

BU gate was changed from 1500 to 500 ns, this stay valid from now on.

Run 40 Started.

New target

Offset 100 um

RUN CONTROL = 40

Data = /onlineNEDA_00/xData/hil099/run_0040_06-03-2023_00h38m10s/needleRU_i40_0040_0000.caendat

RU = 7.21 MB/s

LF = 3.55 MB/s

Plunger ;

Planger run = 8

0-Point = 232, 7 um

Supposed Distance = 234,7 um

Micrometer = 187.5 um

Position = 241.1 um

Actual Distance = 234,5 um

Voltage =4,106V

Beam dumb =

Collimeter =

Run 26 is going on but not much for the moment in terms of any useful data.

And half of the EAGLE is opened.

20:50 EAGLE closed.

Run 27 with single gamma trigger

Plunger feedback system is not conected.

Data

Position = 522.6

Supposed = 520

Plunger run = 32

Micrometer = 525.3

Run Data = /onlineNEDA_00/xData/currentRun/needleRU_i27_0027_0011.caendat

RU = 5.58 Mb/s

LF = 3.72 Mb/s

Support of Target = 1.5 mg/cm2 Ta
Target            = 1.0 mg/cm2 Cd-106
Stopper           = 10 mg/cm2 Au
Beam Dump         = ~60 mg/cm2 Au