Run Coordinator report: spring 2019 w12

From GlueXWiki
Revision as of 14:11, 17 April 2019 by Deurpam (Talk | contribs) (Created page with "During the last week of the spring 2019 run, Hall D was scheduled for 119 hours of beam. Of that schedule, the accelerator was able to deliver 88.9 (75%) hours of beam. We u...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

During the last week of the spring 2019 run, Hall D was scheduled for 119 hours of beam. Of that schedule, the accelerator was able to deliver 88.9 (75%) hours of beam. We utilized (ABU) 84.7 hours which is 71% of the scheduled beam time. The BANU for this period totals 10.5 hours, this breaks down with seven hours being allocated to accesses made to changes to the CompCal and the 3x3 prototype, two hours were spent in making changes to the DAQ configurations to allow the 3x3 prototype to be calibrated as well as the inclusion of other triggers for the 100nA run. The remaining hour were typical DAQ start stop procedures between runs and occasional crashes. At the end of the run we have collected 132% of the expected data schedule. This was due in part to the accelerator efficacy exceeded our predictions. However there is also the issue of the beam energy change to 11.168GeV, so this will not account to the lower figure of merit. The Detector hardware performance was normal during the week. One HV board for the ComCal lost communication and was replaced quickly on Wednesday. Two FCal bases were observed to begin to have problems by the end of the run period, but were not replaced as they were not in the central region of the detector. Beam conditions were good after the odd decrease in the rate on Wednesday. That issue did not reappear, and as of this point there is still no definitive explanation for what caused it.