Difference between revisions of "Run Planning Meeting Notes, Feb 1-Feb 7, 2018"

Revision as of 09:12, 1 February 2018

Notes from the previous 24 hours:
- After empty target run, beam intermittent. Trouble setting up V-wire TAC run, due to lock on Active Collimator not providing consistent TAC rate.
- 8 PM start production TAC run with lock on Beam Profiler. TAC rate initially at ~200 kHz, but dropped to 100 kHz overnight.
- 5:30 AM stopped the TAC run and switch to production: target filled, beamline back in production configuration and production run started.
- 16.1 hours of CW beam. ABU: 14.4 hrs (4.9+3.5+6.0), BANU: 1.7 hrs (0.1+0.8+0.8)
- Spreadsheet: number of triggers.
- Low level monitoring
Issues:
Run plan for this week:
- Low intensity runs planned for tonight: what is the status of min-bias triggers?
Today's run plan:
- At 9 AM (or after run production run 41172):
  - Harp scans by MCC and Hall D (Hovanes on shift)
- Production running the rest of the day
Reports:
- Preliminary PS acceptance
- Statistics from RCDB
Standing issues:
- Rate evolution: Work ongoing to compare rho yields to PS flux before and after "step" in PS rate.
- Polarization status? Came up at MCC meeting, Eugene suggested to report next week.

@@ Line 6: / Line 6: @@
 #* 8 PM start production TAC run with lock on Beam Profiler.  TAC rate initially at ~200 kHz, but dropped to 100 kHz overnight.
 #* 5:30 AM stopped the TAC run and switch to production: target filled, beamline back in production configuration and production run started.
-#* ? hours of CW beam. BAU: ? hrs (?+?+?), BANU: ? hrs (?+?+?)
+#* 16.1 hours of CW beam. ABU: 14.4 hrs (4.9+3.5+6.0), BANU: 1.7 hrs (0.1+0.8+0.8)
 #* [https://docs.google.com/spreadsheets/d/1NffTc4-S5PbTMSuH_pp7ZYsGRH4JC_WSVo770_iJYt0/edit#gid=1635471172 Spreadsheet: number of triggers].
 #* [https://logbooks.jlab.org/entry/3525087 Low level monitoring]