Run Planning Meeting Notes, Feb 9-Feb 15, 2017
From GlueXWiki
<- Back to Run Coordination Meetings: Spring 2017 Run
Saturday, February 11
- Accelerator Status
- 2 hour down overnight for RF problem
- Hall-D/GlueX items
- Running last 24 hours
- ABUs 15.4 hours
- Triggers
- Solenoid power supply transistor
- Harps scans show divergence in Y https://logbooks.jlab.org/entry/3457448
- Ask MCC to run Todd's script?
- Running last 24 hours
- Monitoring
- Low level
- Daily
- Beam properties histogram: the issue was a change in the analysis cuts which applied to the new diamond but needed a new AMO reference
- High level
- Low level
- Calibration
- Run Plan
- Production
- Harp scan Sunday
- QS Utility scan? Used for matching optics, 12 harp scans per plane, per harp
- Empty target run?
- Offline Analysis?
- Any Other Business?
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 data before beam focus was tuned
- 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; 30% lower rho/trigger compared to Spring 2016(should improve with calibration); omega width 50% larger and yield lower by half
- Rho analysis, 30 kHz data before beam focus was tuned
- Low level
- Calibration
- Calibration jobs are on the farm right now, hopefully ready by Sunday/Monday.
- 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?