Wed Mar 8 02:45:53 2023, KS, KSz, Other, , Beam, increase in Counting Rates
|
Since 2:32 increased counting rate observed:
Sinde 3:45 decrease to 1.5 kHz ch4.
run control = 48
/onlineNEDA_00/xData/hil099/run_0048_08-03-2023_01h08m57s/needleRU_i48_0048_0007.caendat
run data =
RU = 8.69 MB/s
LF = 3.79 MB/s
Eagle Rated ch4: around 2.3 kHz
plunger: (2:48)
plunger run = 514
actual distance = 382.7 um
supposed distance = 382.7 um
micrometer = 383.5 um
position = 149.8 um
voltage = 2.144 V
Beam dump = 1.5 nA
Collimater= 0.5 nA |
Wed Mar 1 11:52:48 2023, MP, Runs, , , first beam
|
Operators tune beam on the target, collecting run 0023, trigger gg. |
Tue Mar 7 03:21:33 2023, JD, DW, Problem Fixed, , General, daq crash
|
daq crashed at 02:59:00, resolved at 03:16:00
|
Sat Mar 11 09:29:48 2023, EG, Other, , , current exeriment parameters as requested in the manual for shifters
|
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?
|
Thu Mar 2 16:40:45 2023, MP, Runs, , General, changing the plunger distance to minimum.
|
Run 31 was stopped, because plunger distance is reduced to the mininimal one.
It takes time, in the meantime, after some break, run 32 was started, with no beam. |
Sun Mar 5 22:32:56 2023, MP, Other, , , change of the target 6x
|
See pictures in the attachment:
1) stopper seen from the back (upstream view)
2) stopper seen from the front (downstream view)
Mind the two small off-center dots. It is clear that the beam hits the edge of the frame. This is possible because the 5 mm collimator has two small dots outside the 5 mm hole (the collimator can be seen in the beam tube).
3) old target, upstream view
4) new target, upstream view, after the stopper drove into it
5) new target, before it was mounted
6) the stopper, after the collision with the target. One of the visible rings is probably due to this collision, other traces probably reflect its complicated history earlier.
|
Mon Feb 27 02:49:10 2023, GJ, Runs, , General, calibs - 2x 152Eu - run 0
|
Run number: 0
Trigger: g
Start time: Mon Feb 27 02:43:50 2023
Stop time: Mon Feb 27 03:21:01 2023
Two Eu sources hanging in more or less focus points of two partially open halves of EAGLE. |
Sun Mar 12 00:09:35 2023, AF, Problem Fixed, , Software, caen_shifted correction in spy & greware
|
neda_psdcaen_positions.txt had weird values for three first detectors, especially neda_02.
It was:
NEDA_00_position_psdcaen 0
NEDA_01_position_psdcaen 0.22
NEDA_02_position_psdcaen 40
I (AF) make it:
NEDA_00_position_psdcaen 0.2
NEDA_01_position_psdcaen 0.2
NEDA_02_position_psdcaen 0.2 |
Fri Mar 3 02:23:45 2023, GJ, Problems, , Software, builder gate, TS offsets
|
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. |
Fri Mar 10 08:02:39 2023, AM, Problems, , Beam, bigger data rate
|
rate of ch4 above 2kHz, too big beam intesivity, highier data rate from: 07:51
|
Mon Mar 6 17:19:24 2023, OST, Problems, , Beam, beam unstable and a little high
|
16:30 beam increased 5 mb/s to 9 mb/s and stayed 1 hour 9 mb/s
17:10 beam fixed. stable |
Tue Mar 7 20:42:03 2023, IP, Problems, , Beam, beam unstable
|
There was a problem with the beam from 20:19 to 20:30.
Now it is fine. |
Wed Mar 8 07:30:15 2023, KS, KSz, Problems, , Beam, beam unstable
|
The beam was unstable from 7:18 to 7:25. |
Wed Mar 8 07:57:05 2023, IK, Problems, , Beam, beam unstable
|
The beam was unstable from 7:55. Stabilized around 8:03.
Counting rates are higher, EAGLE det4 went to ~2.5kHZ from ~2kHz (attached).
According to the operator, a bit of a tuning was done, current is 1nA.
run control = 48
run data = /onlineNEDA_00/xData/hil099/run_0048_08-03-2023_01h08m57s/needleRU_i48_0048_0041.caendat
RU = 10.4 MB/s
LF = 4.3 MB/s
|
Wed Mar 8 14:47:34 2023, AM, Runs, , Beam, beam unstable
|
two drops in beam intesitivity at 14:33, 14:37 and 14:51 |
Wed Mar 8 12:11:59 2023, IK, Problem Fixed, , General, beam tuned
|
Beam tuning was made, focusing significantly improved.
Intensity:
beam dump: 0.9-1 nA,
collimator: 0.5 nA.
Rates:
RU = 8.2 MB/s
LF = 4.03 MB/s
EAGLE det4: 2.2 kHz
|
Thu Mar 2 15:15:40 2023, mgb, Runs, , General, beam stopped. eagle is opened and run 30 continues
|
Data
Position = 522.6
Supposed = 520
Plunger run = 32
Micrometer = 525.3
Run Data = /onlineNEDA_00/xData/hil099/run_0030_02-03-2023_11h18m31s/needleRU_i30_0030_0011.caendat
RU = 3.53 Mb/s
LF = 2.40 Mb/s
beam off and on and off. eagle is opened and run 30 continues
new cable is stucked
Cable test is going on |
Thu Mar 9 13:22:37 2023, OST, Other, , Beam, beam stopped 13:21-13:24 for control
|
| |
Fri Mar 3 11:48:29 2023, IP, Runs, , General, beam stopped
|
The beam is gone. |
Fri Mar 10 21:29:28 2023, IP, Runs, , Beam, beam start
|
the beam starts at 21:27.
But the operators are still working on focusing the beam. |
|