Run Planning Meeting Notes, Mar 9 - Mar 15, 2017

From GlueXWiki
Revision as of 08:12, 10 March 2017 by Jonesrt (Talk | contribs)

Jump to: navigation, search

<- Back to Run Coordination Meetings: Spring 2017 Run

Thursday, March 9

Shift ABU BNA BANU
Day 0:40 7:18 0:02
Swing 0:0 8:0 0.0
Owl 0:24 6:55 0:41
Total 1:04 22:13 0:43


  1. Accelerator Status over the last 24 hrs
    • Accelerator busy with Hall C until 05:00
    • Hall D first given beam at 05:20
    • Data collection at 50nA started at 08:00
  2. Hall-D/GlueX items
    • In the last 24 hours:
      • Low-intensity production started at 08:00
      • Long mode run (10 minutes) done at
      • Current Total: 40.05B
  3. Issues
    • DAQ issues:
      • 5:42 - The DAQ keeps giving us "SEBO: Client has not reported for xx sec." errors, but then recovers after a minute. This happens every ~20mins or so. We will restart the DAQ again after the current run finishes.
      • ~22:00 - Monitoring stops working, have to start/stop runs several times to get events flowing through secondary ET
  2. Monitoring
    • low-level report
  3. Run Plan
    • Production
    • Triggers: In-time random? Min-bias? FCAL+BCAL+ST?
  4. Offline Analysis
    • TAC runs?
  5. AOB

Friday, March 10

Shift ABU BNA BANU
Day 0:23 6:55 0:41
Swing 4:05 3:27 0:27
Owl 5:26 2:32 0:02
Total 9:54 12:55 1:10


  1. Accelerator Status over the last 24 hrs
    • Accelerator busy with Hall C until 05:00
    • Hall D first given beam at 05:20
    • Data collection at 50nA started at 08:00
  2. Hall-D/GlueX items
    • In the last 24 hours:
      • Low-intensity production started at 08:00
      • Long mode run (10 minutes) done at
      • Current Total: 40.05B
  3. Issues
    • DAQ issues:
      • 5:42 - The DAQ keeps giving us "SEBO: Client has not reported for xx sec." errors, but then recovers after a minute. This happens every ~20mins or so. We will restart the DAQ again after the current run finishes.
      • ~22:00 - Monitoring stops working, have to start/stop runs several times to get events flowing through secondary ET
  2. Monitoring
    • low-level report
  3. Run Plan
    • Production
    • Triggers: In-time random? Min-bias? FCAL+BCAL+ST?
  4. Offline Analysis
    • TAC runs?
  5. AOB
Retrieved from "https://halldweb1.jlab.org/wiki/index.php?title=Run_Planning_Meeting_Notes,_Mar_9_-_Mar_15,_2017&oldid=81281"