Difference between revisions of "Run Planning Meeting Notes, Mar 2 - Mar 8, 2017"
From GlueXWiki
(→Wednesday, March 1) |
(→Wednesday, March 1) |
||
Line 39: | Line 39: | ||
#** 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. | #** 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 | #** ~22:00 - Monitoring stops working, have to start/stop runs several times to get events flowing through secondary ET | ||
− | |||
# Monitoring | # Monitoring | ||
# Run Plan | # Run Plan |
Revision as of 07:46, 2 March 2017
<- Back to Run Coordination Meetings: Spring 2017 Run
Wednesday, March 1
Shift | ABU | BNA | BANU |
---|---|---|---|
Day | |||
Swing | |||
Owl | |||
Total |
- Accelerator Status over the last 24 hrs
- Smooth sailing
- Strip charts: 1 2
- AC position drift
- Hall-D/GlueX items
- In the last 24 hours:
- Production data taken after 10:30 AM Weds.
- Long mode run
- Black spots on diamonds
- Total triggers collected during last period: ~2600M
- Run Statistics Spread Sheet
- Current Total: B
- In the last 24 hours:
- Issues
- Problems with FCAL crate 9
- FCAL red light issue
- 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
- Monitoring
- Run Plan
- Production
- TAC run?
- Triggers: In-time random? Min-bias? FCAL+BCAL+ST?
- Offline Analysis
- AOB