Run Planning Meeting Notes, October 20 - October 26, 2022

From GlueXWiki
Revision as of 08:35, 24 October 2022 by Aasatury (Talk | contribs) (→‎Past 24 hours)

Jump to: navigation, search

Meetings are via ZoomGov: connect (Meeting ID: 160 199 0060 / Passcode 8394)

MCC whiteboard

Hall D counting room white board

Hall D Logbook

Back to Run Coordination Meetings:Fall2022

Monday, October 24

Past 24 hours

  • ~1.7B triggers collected on He target at 200nA CW since yesterday update, overall after filling target collected ~11B events
  • Mostly beam was very stabile over the weekend
  • Monday early morning ~2:30am beam goes OFF, the reason was injector slit water flow interlock issue, at around 7am it was recovered and MCC started beam delivery
  • There was one FCAL base which is locked-up, shift crew reset it -> https://logbooks.jlab.org/entry/4067100
  • BCAL FADC occupancy plots -> https://logbooks.jlab.org/entry/4067264
  • No planned "Maintenance day" yet

Shift Summary


Issues

Plan

  • Continue taking production data at 200nA with FULL TGT.


Sunday, October 23

Past 24 hours

  • ~2.8B triggers collected on He target at 200nA CW since yesterday update (~11am)
  • Asked MCC for Rapid Access to change the broken FCal fADC (~1hrs down time)
  • Mostly beam was very stabile(Hall-A is not in business), except starting at ~5:30am-6:00am MCC is having some instabilities with 1L12 HV which is causing the instabilities for Halls D and C, but it is not a major issue for now, and MCC will continue beam delivery to halls

Shift Summary

Issues

Plan

  • Continue taking production data at 200nA with FULL TGT.

Saturday, October 22

Past 24 hours

  • past 24 hours we collected ~3.43B total triggers on the He4 target with 200nA beam.
  • Starting from run_num 111140 one of FCal fADC is broken
  • Beam was OFF from 16:37 till 19:58 issues with RF 1L10 HV
  • After Beam is back continued taking data at 200nA FULL target
  • ~00:15 DAQ rate dropped to 0kHz, Contacted to Sergey, 1st power cycled rocTOF2, which brings trigger rate to 12.5kHz, but still way far from nominal 50kHz
  • It turns out one of FCAL outer ring fADC is broken (trying to reach expert to replace it), will continue running with this condition until it's been replaced


Shift Summarys


Issues

Plan

  • Continue taking production data at 200nA with FULL LHe target over the weekend.


Friday, October 21

Past 24 hours

  • Continued taking data at 200nA with EMPTY Target Cell till ~15:00, collected ~0.65B events, overall collected data for past period 1.533B events
  • 15:00 Beam was OFF for ~2.5 hours for Injector Restoration
  • At 16:10 started filling the target with LHe
  • ~17:40 Beam was back, started collecting data with 200nA and FULL target
  • 17:58 FDC:hv:2:c3:3n channel HV tripped, tried to turn it ON, with different ways, but continuously it was tripping, contacted to Lubomir he changed the HV from 500V to 400V https://logbooks.jlab.org/entry/4064442
  • 19:20 Target alarm comes ON, the Pulse Tube Refrigerator(PTR) was switched off resulting in increase of the target cell temperatures from 4.27 to about 4.6 K
  • Same Target Issue happened at 20:50 again, switched back ON the PTR, and in both cases contacted to Chris Carlin, he will keep an eye on it
  • 22:10 asked for Rapid Access to let Chris Carlin take a look on the heater/cooler control box
  • The CDC Pressure Alarm is coming ON more frequently than it was
  • Collected data for LHe ~1.9B events

Shift Summary

Issues

Plan

Continue running on the FULL LHe target at 200nA

Thursday, October 20

Past 24 hours

  • Beam was Off most of the day starting from ~7:30am for "ARW Tour and Associated Maintenance" and VCG1L1210(SRF Insulating Vacuum)
    • During dawn time Mark and Malte replaced some Fcal bases (2?)
    • Vlad and Arshak did some alignment on the prototype
    • Kondo conducted some work on GEM-TRD
  • Restored Beam to the Hall-D at ~22:30, after 15 hours of downtime
  • After Beam restoration Harp Scan was performed and started run on the Empty LHe4 Cell target with 200nA
  • Collected for about 0.3B events
  • At 7:45 meeting informed MCC about beam position instability


Shift Summary

Issues

Plan

Continue running on the Empty target at 200nA

Retrieved from "https://halldweb1.jlab.org/wiki/index.php?title=Run_Planning_Meeting_Notes,_October_20_-_October_26,_2022&oldid=116734"