16/03/2023

Plunger chamber closed, some dummy target and stopper probably inside

run 72    eagle closed

run 73    right half of EAGLE completely opened

Three screenshots are attached:

Run 72  EAGLE closed

1)  Three rings.  There is significantly more 511 in ring 143 than in 117, 101

2) 5 detectors of ring 143. They all look similar to each other.

Run 73  right half of EAGLE opened

3) 5 detectors of ring 143.  The 3 detectors in the opened half hardly see 511 keV, the other 2 do.

Check with Colibri and a gamma scintillator probe ws done: largest activity is visible close to the target chamber, in the region starting at the edge of the chamber, end ending about 6 cm upstream.

About 80 gamma counts/s are seen there. The count rate decreases further upstream.

Background rate:  20 to 30 counts/s, 25 counts/s in Sala Fizykow.

Radioactivity line seen in the spectra,  with the same behaviour as 511:   743.5,  936 keV, 1434 keV.  These are lines from 52Cr, fed by beta+ decay of 52Mn.

Confirmed by Michain gamma-gamma.

52Mn can be produced in the a2pn channel in  the reaction 32S+27Al

Attached are the lists of files copied to the two 4 TB Bahadir's disks.

run 66 started, radiocativity (background)

At about 12:00, 13/03/2023 (about  17 hours after the beam was stopped), a measurement of activity of the beam line was performed using  FH 40G-L10 meter.

Radioctivity run 65 stopped before the measurement, radioactivity run  66 started after the measurement

Background level 120 ns/h

Target, stopper, the forward half of the target chamber - dismounted.

Approximate distance from the target position (upstream), approximate activity

10 cm    500 ns/h

25 cm    420 ns/h

35          350 ns/h

40          350 ns/h

50          200 ns/h

75          170 ns/h

Plunger run files for later to calculate error in the distance

started

source in the target position, as precisely as possible

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

Run 59 collected data using gg trigger radioactivty

Run 60 trigger changed fropm gg to single g.

Just in the beginning a few minutes gg data could have been collected.

18:54 Run 58 stopped and 18:55 Run 59 started.

BEAM STOPPED.

END of EXPERIMENT.

Run 59 collects radioactivity.

-rw-rw-r-- 1 xdaq xdaq 295178920 Mar 12 18:59 needleLF_i58_0059_0000.adf
-rw-rw-r-- 1 xdaq xdaq 802293316 Mar 12 18:59 needleRU_i59_0059_0000.caendat

run control = 58

run data =xdaq  471656980 Mar 12 18:47 needleRU_i58_0058_0095.caendat

RU = 7.35 MB/s

LF =   3.50 MB/s

plunger:

plunger run = 1638

actual distance =  262.6 um

micrometer =   266.9 um

position = 29.8 um

voltage =  3.308 V

Beam dump: 0.7 nA 

Colimator :  0.5 nA

run control = 58

run data =xdaq 1111949504 Mar 12 17:01 needleRU_i58_0058_0083.caendat

RU = 7.14 MB/s

LF =   3.46 MB/s

plunger:

plunger run = 1620

actual distance =  262.5 um

micrometer =   266.7 um

position = 29.8 um

voltage =  3.31 V

Beam dump: 0.7 nA 

Colimator :  0.5 nA

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.

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.

run control = 58

run data = xdaq 3303602776 Mar 12 08:01 needleRU_i58_0058_0024.caendat

RU = 7.88 MB/s

LF =   3.70 MB/s

plunger:

plunger run = 1530

actual distance =  262.6 um

micrometer =   266.8 um

position = 29.9 um

voltage =  3.308 V

Beam dump: 1 nA 

Colimator :  0.5 nA

run control = 58

run data =xdaq 2254808224 Mar 12 06:59 needleRU_i58_0058_0017.caendat

RU = 8.10 MB/s

LF =   3.79 MB/s

plunger:

plunger run = 1520

actual distance =  262.7 um

micrometer =   266.7 um

position = 30 um

voltage =  3.306 V

Beam dump: 1 nA 

Colimator :  0.5 nA

run control = 57

run data =/onlineNEDA_00/xData/hil099/run_0057_12-03-2023_03h10m10s/

RU = 8.1 MB/s

LF =   3.8 MB/s

plunger:

plunger run = 1484

actual distance =  262.7 um

micrometer =   266.9 um

position = 30 um

voltage =  3.306 V

Beam dump: 0.75 nA 

Colimator :  1.1 enA

stop:

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