run control = 56

run data =/onlineNEDA_00/xData/hil099/run_0056_11-03-2023_23h26m10s

RU = 7.3 MB/s

LF =   3.5 MB/s

plunger:

plunger run = 1445

actual distance =  262.7 um

micrometer =   266.2 um

position = 30 um

voltage =  3.05 V

Beam dump: 0.75 nA 

Colimator :  1.1 enA

stop:

RUN CONTROL = 37

Data = /onlineNEDA_00/xData/hil099/run_0037_04-03-2023_22h56m17s/needleRU_i37_0037_0106.caendat

RU = 8.65 MB/s

LF = 4.11 MB/s

Plunger ;

Planger run = 745

Supposed Dist=240 um

Micrometer = 187.5 um

Position = 241.1 um

Actual distance = 240.6 um

Voltage = 2.715 V

Beam dumb = 0.75 nA

Collimeter =0.65 nA

beam started 18:04.

run control = 51

run data =  /onlineNEDA_00/xData/hil099/run_0051_09-03-2023_16h25m16s/needleRU_i51_0051_0002.caendat

RU =  6.43MB/s

LF =   3.49 MB/s

plunger:

plunger run = 896

actual distance =  532.1 um

supposed distance = 532.7 um

micrometer =   532.9 um

position =  299.4 um

voltage =  1.659 V

Beam dump: 1 nA

Colimator :  0.6 enA

run control = 51

run data =  /onlineNEDA_00/xData/hil099/run_0051_09-03-2023_16h25m16s/needleRU_i51_0051_0002.caendat

RU =  6.43MB/s

LF =   3.49 MB/s

plunger:

plunger run = 896

actual distance =  532.1 um

supposed distance = 532.7 um

micrometer =   532.9 um

position =  299.4 um

voltage =  1.659 V

Beam dump: 1 nA

Colimator :  0.6 enA

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

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.

Issue described in #61 continues to persist.

Beam stopped from 19:20 to 19:32, run 36 ongoing; MP, GJ, BS entering the experimental hall. 

They changed the position of the grounding point on the chamber, moving it downstream after a fitting/joining part (A to B on the attached picture [artist: GJ]).

Run 37 stopped by itslelf at 15:43. This was noticed at about 16:10 by observing that grafana data rates do not change.

Stop at Run COntrol.  LF looks  disabled.

Attempt to restart normal way --> run 38  --> failed

Attempts to load topology failed.

Cannot any more refresh or load the Run COntrol web page (192.168.0.133:5000)

Grzes is trying to fix the problem remotely, while we are starting changing of the target....

No beam 05:10:00

9:20 to 9:50 am beam current stayed 2.5 nA . After 9:50 am decrease 1.5 nA

16:30 beam increased 5 mb/s to 9 mb/s and stayed 1 hour 9 mb/s

17:10 beam fixed. stable

9:08 local filter turned red. Both .caendat and   LF .adf files still incrementing. Stopped run 44, started run 45, looks OK.

after run 45 I reset all spectrums and number_Ge_15 dedector not taking data.

i check the fans_monitor_scaler (EAGLE_array_monitor) monitor and number 15 Ge, number ACS 5 never change the color just staying white there is a problem.