Difference between revisions of "Run Planning Meeting Notes, Feb 9-Feb 15, 2017"
From GlueXWiki
| Line 20: | Line 20: | ||
#* Monitoring | #* Monitoring | ||
#** Monitoring coordinator (Thomas): Report every morning. | #** Monitoring coordinator (Thomas): Report every morning. | ||
| + | #** Cut on trigger 1 | ||
#** data monitoring shifts | #** data monitoring shifts | ||
#** data anomalies | #** data anomalies | ||
Revision as of 10:08, 9 February 2017
<- Back to Run Coordination Meetings: Spring 2017 Run
Thursday, February 9
- Accelerator Status
- Slew of difficulties over Owl shift, pathlength drift, electronics problems, BPM problems
- Hall-D/GlueX items
- Running last day
- ABUs
- Triggers
- Coherent Peak Position difference
- 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.
- Cut on trigger 1
- data monitoring shifts
- data anomalies
- Target IOC problem overnight
- How to handle reboot (shift workers or experts?)
- End run script and RCDB entries
- Running last day
- Run Plan
- Align coherent peaks?
- Production
- Offline Analysis?
- Any Other Business?
