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

<- Back to Run Coordination Meetings: Spring 2017 Run

• View Runplan google calendar
• Edit Runplan google calendar
• MCC white board

Thursday, February 9

1. Accelerator Status
   • Slew of difficulties over Owl shift, pathlength drift, electronics problems, BPM problems
2. Hall-D/GlueX items
   • Running last day
     • ABUs
     • Triggers
   • Coherent Peak Position difference
     • [1], [2]
   • 50 kHz running
     • Smooth running, hodoscope up to 5.7 GeV turned off. Occasional glitches in the DAQ rate due to Java garbage collection (adding a few percent to deadtime.) 900 MB/s
     • What is the data quality? (Normalized to trigger) Physics signals, (omega, rho: # per trigger, widths, backgrounds)
   • Monitoring
     • Monitoring coordinator (Thomas): Report every morning.
     • data monitoring shifts
     • data anomalies
   • Target IOC problem overnight
     • How to handle reboot (shift workers or experts?)
   • End run script and RCDB entries
3. Run Plan
   • Align coherent peaks?
   • Production
4. Offline Analysis?
5. Any Other Business?