Run Coordinator report: Spring 2020 w9

Feb 26-Mar 4:

we had a successful week of running! According to the numbers, we were scheduled for 155 hours of running with 57% of CW on target (88.7 hours). In total, we lost about 5 hours due to diamond/radiator orientation change, start/stop DAQ and Harp scan.

Recall we started the week with a major issue with the Hall A bleed-through hitting AD00 (tagger) BLM, causing as much as 21 trips per hour and long down time. This issue was resolved in Sunday day shift, we gained serious momentum (3-4 great owl shifts with less than 10 trips per hour) which allowed us to surpass the projected 3B triggers per day goal! According to the integrated trigger plot, the data collection curve starts to cross deep into the 3B trigger projection line. All credit to the accelerator crews. However, next time when MCC change the tagger magnet field for a more stable accelerator performance, we must be informed at the counting house and with an elog entry to the hdlog.

In terms of detector and magnet performances, there were only minimum issues: 1. FCal board failed on Sunday owl shift; 2. One DIRC LV group tripped during a DAQ stop action. Both issues were addressed quickly by experts and no beam time were lost.

Remaining/pending issues: 1. we still have an issue with the Gluon05 monitor situation, it is operating on 0-1 monitor. The sooner we can have the video card driver updated the better. 2. The 2ns timing shift is still not calibrated/collected for the recent runs, therefore the beta vs momentum plots and few other timing plots are still incorrect.