Objective log on perceived issues. (As a benchmark, I enumerated 17 such issues on my previous RIB experiment March 2017.)
In no particular order...
1) Sun PC:
Cannot properly connect to internet, disallowing SSH access
Important for external monitoring
Better to control DAQ from ISOLDE data room in case of ISOLDE issues
Connecting to CERN network screwed with DNS, borking local DNS hence DAQ
Double mouse clicking often skipped run numbers
2) Vacuum:
Barely acceptable, and manual gate valve leaked!
Keep in mind, interlock system showed higher than true values
44Ti requires a gas cell and vacuum load may increase considerably
(Chamber needs gas-feedthrough lines and gas-flow control system)
Cooling lines are known to leak badly
3) SSDs:
HI detector leak current increased considerably during the run
Noisy n-n sides
To be discussed
4) Scalers
Scalers were made with noisy n-n sides, making interpretation confusing
We lacked LEMO cables to provided summed p-n scalers
5) Decay halflife
A simple handheld monitor turned out to be effective for 59Cu
That won't work for 44Ti ...
6) Unused aparatus should be minimized
(Time & money)
Photodiodes
ZnS screen / camera
Manual gate valve (see above)
7) Shift plan/schedule
No definitive plan -- need pre exp. meeting
Shift schedule became arbitrary, w/ several flip/flops
RP requirements limited access to chamber
8) Shift work
Run log was made with short notice
Style may not be ideal for data analyst
Copy/paste errors et al were observed
Deadtime log was suggested to be added
(Other issues might be circumvented w/ SSH access to Sun PC)
9) Purpose
Detail & motivation of exp. was not clear to all members
10) Faraday Cup
Data taken by TIMBER system, which is better to integrate w/ our DAQ
Strange non-physical fluctuations which we like ISOLDE team to resolve
Timestamp differences of Sun PC and TIMBER PC?
11) Silena HV module
Module was found to falsely report applied bias
12) Alpha calibration / pulser walkthrough
Lacking prior to experiment owing to manpower and technical difficulties
13) Sort codes and simulations
It was common to discuss received vs. expected data w/o fast clear answer |