GlueX 2023

EPICS overview - change the dates to suit

Same, with temperature

DAQ status in EPICS

HV scan instructions

RC meeting page

Shift leader instructions & desperate logbook entry on prestarts

wish list Remaining items are EPICS gathering (Thomas) & move to Prestart (David in Jan, or ask Sergey)

The default GCF in CCDB for runs 120,000+ is 0.1491. This is good. Summer 2020 runs 72075 and 72766 started at close to 350nA and w pressure close to (and on either side of) 100kPa, have GCFs 0.148 and 0.150.

Run starts Jan 12

Naomi out Jan 3-23.

Initialization?

source $HOSS_VENV/bin/activate.csh
python3 /group/halld/AIEC/AIEC_CDC.py -c /group/halld/AIEC/AIEC_CDC.cfg -I 15

Jan 12 RoboCDC control off, because the pressure sensor was not working reliably for most of January. Jan 24 logbook entry describing pressure sensor issues

Feb 16 120739-120745 RoboCDC control on. According to EPICS, the AI switch was on from 120718, but the HV was fixed at 2125V until 120739. This is because RoboCDC was unable to change the HV because it was running on a gluon without EPICS ChannelAccess, Hovanes fixed this early on Feb 16.

Feb 20 120746-120750 10am - 3pm RoboCDC control switched off for the duration of MCC's BCM recalibration (which was found to be unnecessary)

Feb 20 120751-120821 RoboCDC control on.

Feb 23 4pm ish 120818? Changed the current input to fixed because it was causing so many badepics

Feb 24 120822-120830 switched the control off because the script was running so late and setting the HV after the run started.

Feb 25 120831-120832 Control switched back on for two runs and then off again afterwards.

Feb 25 120833-120920 control off

Mar 1 120921-120931 Late evening control switched back on, HV set to 2123V during tests, script failed and HV remained at 2123 overnight.

Mar 2 120932 10:30am HV set back to 2125V manually. Control still on. Beam off.

Mar 2 120933-121007 Resumed operation correctly later that day (there was a long beam outage).

Mar 6 121008-121009 Control switched off for high current tests.

Mar 6 121010-121022 Control switched on when maintenance day was announced instead.

Mar 7 121023-121025 Control switched off during high current tests.

Mar 7 121026-121035 Control on

Mar 8 121036-121042 Control switched off during high current tests.

Mar 8 121043-121106 Control on

Mar 10 121076-121105 HV remained at 2121V, looks suspicious as the pressure is not constant.

Mar 12 121106-121121 HV returned to 2125V

Mar 13 121122-121147 Looks like control was on again

Mar 15 121148-121155 Control off for high current tests

Mar 16 121156-121214 Control on

Summarizing the above, control was on but problematic for runs up to 121121. Best run period is production runs during 121122-121214.

There were two periods when a script was altered but left buggy, and the HV was stuck once at 2123V and once at 2121V. For some of the runs the recommended HV was slightly off due to a bug in the HVB current scaling. For some of the runs the HV changed up to 1 minute(?) after the run started.

Naomi thinks that the HVBi fix was the cause of the first stuck HV period, and moving the HV-setting from prestart to go caused the 2nd, but is not totally sure of this. If this is correct, then runs 120933-121076 should be OK for analysis provided that Alex used the files after the start of the run as requested.