Difference between revisions of "Run Planning Meeting Notes, Feb 9-Feb 15, 2017"
From GlueXWiki
(→Friday, February 10) |
(→Friday, February 10) |
||
Line 19: | Line 19: | ||
# Monitoring | # Monitoring | ||
#* Low level | #* Low level | ||
− | #** New channel out in FCAL | + | #** New channel out in FCAL; occupancy drift in single PS channel; LED signals still in some histograms, cuts coming; new statistics on some histograms (nice) |
#* High level | #* High level | ||
− | #** Rho https://logbooks.jlab.org/entry/3456928 | + | #** Rho analysis (30 kHz) |
+ | #*** https://logbooks.jlab.org/entry/3456928 | ||
+ | #*** timing calibration seems out, polarizations might not be good because of lack of accidental subtraction, signal to background looks great, | ||
# Run Plan | # Run Plan | ||
#* Production | #* Production |
Revision as of 10:19, 10 February 2017
<- Back to Run Coordination Meetings: Spring 2017 Run
Friday, February 10
- Accelerator Status
- Difficulties on Day Shift and into Swing. Owl smooth
- Hall-D/GlueX items
- Running last 24 hours
- ABUs 9 hours
- Triggers
- Coherent Peak Position
- Harp scans
- https://logbooks.jlab.org/entry/3457200
- If the beam returns from a down or if it's beam 2 days since the last scan.
- Running last 24 hours
- Monitoring
- Low level
- New channel out in FCAL; occupancy drift in single PS channel; LED signals still in some histograms, cuts coming; new statistics on some histograms (nice)
- High level
- Rho analysis (30 kHz)
- https://logbooks.jlab.org/entry/3456928
- timing calibration seems out, polarizations might not be good because of lack of accidental subtraction, signal to background looks great,
- Rho analysis (30 kHz)
- Low level
- Run Plan
- Production
- Offline Analysis?
- Any Other Business?
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
- Low level monitoring coordinator (Thomas): Report every morning.
- High level monitoring coordinator (Alex): Report every morning.
- Cut on triggers for monitoring
- Run DAQ when beam is gone
- Threshold for alerting experts?
- Run coordinator should be called for problems that limit data taking
- Target IOC problem overnight
- Reboot should be done by shift crew if they know how, otherwise call Deur, then cal Ito.
- End run script and RCDB entries
- Running last day
- Run Plan
- Align coherent peaks?
- Production
- Offline Analysis?
- Any Other Business?