Difference between revisions of "Run Planning Meeting Notes, Mar 14 - Mar 20, 2019"

From GlueXWiki
Jump to: navigation, search
(Monday, Mar. 18 at 08:45)
(Monday, Mar. 18 at 08:45)
Line 13: Line 13:
 
#* Production running
 
#* Production running
 
#* [https://logbooks.jlab.org/entry/3669217 Emptied target at 3:30pm Sunday]
 
#* [https://logbooks.jlab.org/entry/3669217 Emptied target at 3:30pm Sunday]
#* [https://logbooks.jlab.org/entry/3669252 Attempted TAC run but beam position was too unstable]
+
#* [https://logbooks.jlab.org/entry/3669252 Attempted TAC run but beam position was too unstable][https://logbooks.jlab.org/entry/3669283].
 
# Issues
 
# Issues
 
#* [https://logbooks.jlab.org/entry/3668424 Short access Friday evening due to PS/ST problems. Vlad saw 2 of these alarms yesterday evening.]  
 
#* [https://logbooks.jlab.org/entry/3668424 Short access Friday evening due to PS/ST problems. Vlad saw 2 of these alarms yesterday evening.]  
Line 19: Line 19:
 
#* [https://logbooks.jlab.org/entry/3669341 Target temperature continues to rise over 100K.]
 
#* [https://logbooks.jlab.org/entry/3669341 Target temperature continues to rise over 100K.]
 
# Reports
 
# Reports
#*
+
#* Daily FCAL update
 +
#* Daily compcal RF timing discussion
 +
#Today
 +
#* Halls B and D only halls at 5 pass. We're both at low current and MCC can not see the beam in the machine, only when it enters our halls. Beam trips may take a little longer to recover, so they asked for us to be patient.
 +
#* MCC looking into noisy BPMs (calibration issue?). They're looking into this now.
 +
 
 +
#Run Plan
 +
#* Empty target running with standard production setup.
 +
#* What else can be done about the beam position to ensure a successful TAC run?
  
 
== Friday, Mar. 15 at 08:45 ==
 
== Friday, Mar. 15 at 08:45 ==

Revision as of 08:34, 18 March 2019


Monday, Mar. 18 at 08:45

  1. Past 48 hours:
  2. Issues
  3. Reports
    • Daily FCAL update
    • Daily compcal RF timing discussion
  4. Today
    • Halls B and D only halls at 5 pass. We're both at low current and MCC can not see the beam in the machine, only when it enters our halls. Beam trips may take a little longer to recover, so they asked for us to be patient.
    • MCC looking into noisy BPMs (calibration issue?). They're looking into this now.
  1. Run Plan
    • Empty target running with standard production setup.
    • What else can be done about the beam position to ensure a successful TAC run?

Friday, Mar. 15 at 08:45

  1. Past 24 hours:
    • Short access after meeting
    • gluon01 is back with a new kernel and graphics driver
    • Production running
  2. Issues
    • Problematic FCAL channels near beamline
      • One base lost connection and was recovered by power cycling the power supply. This happens 1-2 times per week. Right now I (Colin) am the only one capable of doing this. Need to train more people how to spot and fix these errors. It is a relatively simple process, but one that should not be left to the shift crew.
      • One base lost HV near beam line.Follow up. Access to replace after morning meeting. Friendly reminder: please do not call Colin at night about base problems. Emails and texts are fine.
  3. Reports
  4. Today:
    • Production: 200nA, Al 10-4
  5. Run Plan
    • Production running
    • TAC run
    • Hall A performing beam modulation studies Tuesday owl shift. Will cause 1 MeV fluctuations in beam energy. They will do a test Monday morning from 8-9am.

Thursday, Mar. 14 at 08:45

  1. Past 24 hours:
    • Production running
  2. Issues
  3. Reports
  4. Today:
    • Production: 200nA, Al 10-4
  5. Run Plan
    • Production running
    • Hall C goes down Sunday at 4pm. Postpone TAC run until Monday unless there are objections.
      • There are parity quality beam testes (PQB) scheduled for Hall A Monday and Tuesday, but this should not affect the beam delivered to us.
    • RF Recovery scheduled for Wednesday