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

Revision as of 10:03, 9 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
  - Monitoring coordinator (Thomas): Report every morning.
  - data monitoring shifts
  - data anomalies
- Target IOC problem overnight
  - How to handle reboot (shift workers or experts?)
- End run script and RCDB entries
Run Plan
- Align coherent peaks?
- Production
Offline Analysis?
Any Other Business?

@@ Line 15: / Line 15: @@
 #* Coherent Peak Position difference
 #** [https://logbooks.jlab.org/entry/3456939], [https://logbooks.jlab.org/entry/3456924]
+#* 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
-#** Analysis coordinator, data monitoring shifts
+#** Monitoring coordinator (Thomas):  Report every morning.
+#** data monitoring shifts
+#** data anomalies
 #* Target IOC problem overnight
 #** How to handle reboot (shift workers or experts?)