As in the title, see below. The data are still being constantly written on the disks with usual rate (also visible on grafena). Greware is also seeing data. beeper output: no new data about the growth for 37 s !!! Noticed at Sun Mar 12 02:50:42 2023 and weirdo scream followed. LF output: write: Broken pipe 0-LF_neda_2: 98 ev ( 107153)*30 Tot=26234475 2253/s write: Broken pipe 0-LF_eagle_1: 881 ev ( 120281)*31 Tot=295856141 24268/s write: Broken pipe write: Broken pipe 0-LF_neda_3: 3 ev ( 3909)*5980 Tot=375647125 30917/s write: Broken pipe 0-LF_neda_1: 92 ev ( 92962)*40 Tot=32523205 2820/s write: Broken pipe write: Broken pipe 0-LF_neda_0: 104 ev ( 117997)*33 Tot=38078515 3323/s 0-LF_eagle_0: 720 ev ( 63994)*31 Tot=268339966 22243/s write: Broken pipe write: Broken pipe write: Broken pipe write: Broken pipe write: Broken pipe write: Broken pipe 0-LF_neda_2: 72 ev ( 87376)*31 Tot=26236761 2274/s write: Broken pipe 0-LF_eagle_1: 714 ev ( 104681)*35 Tot=295880265 23988/s write: Broken pipe write: Broken pipe 0-LF_neda_3: 9 ev ( 3988)*5870 Tot=375677518 30545/s write: Broken pipe 0-LF_neda_1: 93 ev ( 98610)*34 Tot=32525919 2698/s
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
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 = 55
run data = /onlineNEDA_00/xData/hil099/run_0055_11-03-2023_00h33m38s/needleRU_i55_0055_0137.caendat
RU = 4.17 MB/s
LF = 3.11 MB/s
plunger run = 1439
actual distance = 515 um
micrometer = 578.2 um
position = 282.3 um
voltage = 1.372 V
stop: 11.15 pm -> new plunger distance
run data = /onlineNEDA_00/xData/hil099/run_0055_11-03-2023_00h33m38s/needleRU_i55_0055_0129.caendat
RU = 6.45 MB/s
LF = 3.46 MB/s
plunger run = 1424
supposed distance = 435 um
Beam dump: 1 nA
Colimator : 0.5 nA
Run files /onlineNEDA_00/xData/hil099/run_0055_11-03-2023_00h33m38s/needleRU_i55_0055_0114.caendat
Beam Dump = 0.7 nA
Run number 55
Plunger Distance = 500 um + offset
Plunger run 1402
Voltage 1.369 V
run data = /onlineNEDA_00/xData/hil099/run_0055_11-03-2023_00h33m38s/needleRU_i55_0055_0114.caendat
RU = 5.72 MB/s
LF = 3.27 MB/s
plunger run = 1392
actual distance = 512.2 um
position = 279.5 um
voltage = 1.37 V
Beam dump: 0.9 nA
beam started 18:04.
beam stopped 17:54.
run data = /onlineNEDA_00/xData/hil099/run_0055_11-03-2023_00h33m38s/needleRU_i55_0055_0103.caendat
RU = 8.23 MB/s
LF = 4 MB/s
plunger run = 1374
actual distance = 520.8 um
position = 288.1 um
voltage = 1.377 V
Colimator : 0.6 nA
Again beam intensity to high. Reduced to 2 kHz on ch4 GE
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.
14:12 beam intensity instability. Rapid increase of beam intensity - twice the previous value. Returned to normal after 4 minutes.
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.
at 11:34:50 sek on 11 march a spike in counting rate of some Ge detectors is observed. Buffers not cleared properly?
ch4 in total rate EGALE_) reached 2.4 kHz, beam intensity has been reduced to fit the required 2kHz.
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?
Run 55 Started New Distance 500 um
run 54 - stopped due to change the distance in plunger