00.33 DSSSD bias & leakage currents OK - see attachments 1 & 2
FEE64 temperatures OK - see attachment 3
00.34 DAQ continues (RIBF03R1/R10)
ASIC settings 2016Nov17-10.50.10
BNC PB-4 pulser
Amplitude 90,000
x5 attenuator IN
frequency 25Hz range
t_r 50ns, tau_d 50us
polarity -, tail pulse, delay MIN, INT ref
good events - see attachment 4
N.B. 5x FEE64s > 100k data items/s - intrinsic/extrinsic noise has changed cf. 0x FEE64s previously
00.50 SyncCheck - see attachment 5
Two peaks for RIBF-AIDA, one peak for BRIKEN-AIDA => RIBF issue?
Merge statistics - see attachments 6-11
00.56 All system-wide checks OK - except clock status - see attachment 12
Note - clock status fails show bit 2 set
01.02 Visual scaler - see attachment 13
03.00 Beam stopped temporarily.
File R10_142 @ ~ 1.5Gb.
Beam returned ~03.06. Near end of file R10_147.
05.57 Bias and leakage currents ok (attachments 14+15).
06.25 R10 (@R10_211) stopped in anticipation of LN2 fill.
07.11 Successfully restarted DAQ after LN2 fill.
Started run R11.
07.18 Beam stopped to change stripper foil.
End of R11_1.
DAQ also stopped as I typed this.
07.53 Beam returned.
08.01 R12 started on 1GeV setting to look at suspicious data in high LEC/low HEC ranges.
Will run this for ~30mins.
(NB: Threshold of 0x20 was not changed so...)
(DK arrives on shift)
08.21 Data size of R12 very small, but maybe to be expected as the low gain usually contains ~10k counts which
is now suppressed?
Offline analysis show no implants, even in the low gain portion. Strange!
Redo this test again later today if possible
08.50 Stop R12
Change the medium energy back to low energy
08.55 Start R13 with low and high energy modes
The data stops writing to disk for some reason
09.05 Switch the degrader condition: was degraders 2 & 3, now degraders 1 & 2
Liu and Alfredo had found one 40Mg event (it seems we have about 1 such event per hour)
However, it was only implanted into DSSD #1, so we want to implant 40Mg deeper (N=1 statistics, woohoo)
So now, 0.5 mm W (+1 mm Al) and 0.3 mm W (+1 mm Al)
09.14 Run takes a moment to begin (data transfer links on FEE 3 and 4 dropped out briefly). R14 now.
09.39 Data writing stopped. We re-sequence the merger (toggle data transfer on all FEE64s), and start run R15.
09.43 R15 stops writing to disc. All system checks still passed, but not writing.
Restart merger but lose contact with nnaida14.
09.50 Power cycle FEEs.
10.20 Start run R16 -- garbage
nnaida13 refuses to calibrate ADCs
Maybe miscommunication with BRIKEN team?
When we restart, they need to reload parameters, and then they cannot see our sync (or we are actually not
sending it?)
10.25 Start run R17
Still the time stamp from AIDA is not visible on the sync check?
One of the Check ASIC Control tests returned something other than OK
(sorry, we did not copy it)
But trying it again (w/o other changes), then it returned the default OK values.
BRIKEN is not synced with BigRIPS? They don't know if it gets syncs from AIDA or not
All AIDA sync checks appear as normal, however
10.36 BRIKEN and AIDA seem to now be synchronized (we did nothing on the AIDA side)
It is unclear if we are sync'd with BigRIPS.
Stop this run to get aligned with BRIKEN
10.41 Start R18. Checks on ASICs and SYNC come back good.
Degrader settings (not changed): 3 mm Pb,; 0.5 mm W (+1 mm Al); 0.3 mm W (+1 mm Al)
F11 plastic rate 8 cps
BigRIPS run 1026; started 10:27
(CG leaves shift)
(TD arrives)
12.28: BigRIPS run number 1028
12.58 Checking the synchronization, and it is not correct.
R18_28: BRIKEN issues a new synchronization signal
13.25 Merger stops
Merger error messages for Q 23 (nnaida24) - see attachment 16
nnaida24 reboots c. 13:31 - see attachment 17
Request DAQ STOP, restart Merger
DAQ stops OK
Request DAQ RESET & SETUP
R19 started for AIDA, but we never get the full data links (junk)
13.54 nnaida15 did not show data transfer -> merger restarted
Now R20_0, DAQs look good, BRIKEN issued resync
BigRIPS run 1028 still
14.00 SyncCheck see attachment 18
good events statistics - see attachment 19 - rates lower than observed yesterday, not clear why
|