Difference between revisions of "Run Planning Meeting Notes, Feb 9-Feb 15, 2017"

Revision as of 10:01, 10 February 2017

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
  - [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
  - 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
Run Plan
- Align coherent peaks?
- Production
Offline Analysis?
Any Other Business?

@@ Line 5: / Line 5: @@
 * [https://cebaf.jlab.org/files/ops/accboard/ MCC white board]
+==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
+#** https://logbooks.jlab.org/entry/3457349
+#* Harp scans
+#** If the beam returns from a down or if it's beam 2 days since the last scan.
+# Run Plan
+#* Production
+# Offline Analysis?
+# Any Other Business?
 ==Thursday, February  9==