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

From GlueXWiki
Jump to: navigation, search
(Created page with "<- Back to Run Coordination Meetings:Fall2017 Spring2018 Run == Thursday, February 1 == # Notes from the previous 24 hours: #* After empty target run, trouble setting up...")
 
(Thursday, February 1)
Line 3: Line 3:
 
== Thursday, February 1 ==
 
== Thursday, February 1 ==
 
# Notes from the previous 24 hours:
 
# Notes from the previous 24 hours:
#* After empty target run, trouble setting up V-wire TAC run.  Lock on Active Collimator not providing consistent TAC rate.
+
#* 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.
 
#* 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.
 
#* 5:30 AM stopped the TAC run and switch to production: target filled, beamline back in production configuration and production run started.

Revision as of 08:10, 1 February 2018

<- Back to Run Coordination Meetings:Fall2017 Spring2018 Run

Thursday, February 1

  1. 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.
    •  ? hours of CW beam. BAU: ? hrs (?+?+?), BANU: ? hrs (?+?+?)
    • Spreadsheet: number of triggers.
    • Low level monitoring
  2. Issues:
  3. Run plan for this week:
    • Low intensity runs planned for tonight: what is the status of min-bias triggers?
  4. 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
  5. Reports:
  6. Standing issues:
    • Rate evolution
    • Polarization status? Came up at MCC meeting, Eugene suggested to report next week.