Run Coordinator report: fall 2022 w12

From GlueXWiki
Revision as of 18:44, 16 November 2022 by Deurpam (Talk | contribs) (Created page with "The week started with no beam for 14 hours due to beam tuning and cryomodule issues. When the beam was back we did a harp scan and saw that the sigmas of x, y and u positions...")

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

The week started with no beam for 14 hours due to beam tuning and cryomodule issues. When the beam was back we did a harp scan and saw that the sigmas of x, y and u positions from harp scan results at radiator were out of preferred range and the harp scan extrapolation results showed that they don’t converge at primary collimator location. We then checked the PSC rate and saw that it was 8.1 kHz, while we expected it to be 8.3 at 200 nA. We decided to closely monitor the PSC rate for further changes while taking production data with full LHe target, and on Thursday morning asked MCC to tune Hall D beam optics to improve beam convergence. This was helpful and new harp scan results showed convergence at collimator, but the sigmas of u and y positions still were outside of the preferred range and PSC rate was still low. On friday around 16:19 pm MC took away the beam for ~ 8.5 hours due to fire issues in HallB and vacuum issues in north LINAC. We switched to empty target while the beam was away. When the beam was back we did a harp scan and saw that the sigmas of x, u and y positions were in preferred range and PSC rate was back to normal ~8.3 kHz. During owl shift DAQ event rate dropped because FADC250 in Slot 3 of the rocfcal4 crate was dead. Sergey disconnect FCALRoc4 from trigger to recover event rate to 17 kHz. Sasha replaced the FADC module in the morning (took around ~1h) and connected FCALRoc4 to the trigger but didn't succeed in running the script to include BCAL LED triggers, so he asked Mark to do it.This wasn't critical for PrimEx since the this slot is at the edge of FCAL. We continued production data taking throughout Saturday. On Sunday beam was very unstable, there were RF and orbit instabilities. We didn't have beam for few hours. Also beam positions were oscillating during owl and early riser shifts, particularly AC inner Y and we informed MCC about this. This was related with MCC trying to deliver haigh current to Hall C (70 uA). BCAL LED triggers were turned on during owl shift. On Monday beam was very unstable, beam AC position was changing a lot. We let MCC know, they turned on the orbit locks and the position at AC became more stable, but beam stayed very trippy till owl shift. On Tuesday we had multiple people working in the hall during accelerator maintenance from 6:45 am -2:45pm. The beam was back at 23:50 pm, we did a harp scan, which gave a satisfactory results and continued with production data taking with full target. Sasha found some issues with BCAL LED trigger. He mentioned that level translation board has a problem that results in producing some extraneous trigger pulses for the downstream led trigger and will need to be replaced when there are spare modules.