Run Coordinator report: spring 2019 w4

I am happy to report we had a fantastic running week to complete the DIRC commissioning. According to Justin, we completed 95% of the commissioning objective. Initial DIRC performance was demonstrated and we collected data at variety of running parameters/conditions (MOROC threshold, HVs and beam intensities) to help understand this new detector. The DIRC readout (after firmware update) capability was also tested up to 900nA. The Hall is currently setting up for the CPP trigger study and PrimEx.

We lost 7-8 hours of beam time, it was caused by the following issues:

1. DAQ and DIRC readout.

2. iochdcol lost connectivity.

3. ROCs refuse to come online after reboot.

4. Configuration change and detector maintenance.

Thanks to the experts, rootspy/hdvew2 issues are being looked into, and the mysterious RF issued was finally identified.

To close up, I would like to draw attention to two rare issues we have encountered, interestingly, both happened about two years ago:

1. iochdcol lost connection. Symptom: MCC lost control to the Hall D Active Colimator and requested a physical reset. Both iochdcol and iochdmag are both beamline components and physically located in Hall D (MCC has no idea where they are located and refuse to reset them), therefore its difficult to assign responsibility. Currently, we donot get any alarm or heartbeat to these IOCs. MCC promised to looked into this problem and establish appropriate alarm (to us and them) to check IOC connectivity, and we will setup reset buttons for these IOCs in the counting house.

2. CSS unresponsive. Symptom: the all gluon machines will react slow for opening the CSS control window (5-10 mins to open one window). Once the window is opened, the functionality are normal. Apparently it was related to the issue from the JLab printing service server. We are the only hall who is sensitive to this problem. If it happens again, one need to contact the Jlab IT division and request them to look into the printing service servers.