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

From GlueXWiki
Jump to: navigation, search
(Friday, February 2)
(Friday, February 2)
Line 23: Line 23:
 
#* [https://logbooks.jlab.org/entry/3524060 Rate evolution]: Work ongoing to compare rho yields to PS flux before and after "step" in PS rate.
 
#* [https://logbooks.jlab.org/entry/3524060 Rate evolution]: Work ongoing to compare rho yields to PS flux before and after "step" in PS rate.
 
#* Polarization status?
 
#* Polarization status?
 +
# Beam Time Accounting (BTA):
 +
#* 3 possible conditions:
 +
#** ABU:  Available Beam Used
 +
#** BANU:  Beam Available [to the Hall] but Not Used [by the Hall]
 +
#** BNA: Beam Not Available [to the Hall]
 +
#* Automated procedure in MCC for populating BTA have not been very reliable
 +
#* Proposal from Mark D.
 +
#** Shift leader should record when we request no beam (for example changing the radiator.)  When submitting the Beam Time Accounting, the shift leader should check that the BANU and BNA numbers are correct.  If they are not correct, the shift leader should move all the time that is listed under BANU into the BNA column unless they specifically requested no beam from MCC.
  
 
== Thursday, February 1 ==
 
== Thursday, February 1 ==

Revision as of 09:28, 2 February 2018

<- Back to Run Coordination Meetings:Fall2017 Spring2018 Run

Friday, February 2

  1. Notes from the previous 24 hours:
    • Harp scans around 2 pm found the beam was significantly over-focused in y. Around the same time MCC decided to retune the beam.
    • After beam tuning in the afternoon, harp scans around 8 pm showed convergence at the collimator is better
    • 12.6 hours of CW beam. ABU: 10.9 hrs (3.2+1.7+6.0), BANU: 1.7 hrs (0.3+0.7+0.7), BNA: 11.3 hrs (4.5+5.6+1.2)
    • Spreadsheet: number of triggers.
    • Low level monitoring
  2. Issues:
  3. Today's run plan Google Calendar:
    • Production running
    • 10 am: Min-bias trigger setup (Sasha)
    • 11:30 am: High intensity test (Sergey)
  4. Reports:
  5. Standing issues:
    • Rate evolution: Work ongoing to compare rho yields to PS flux before and after "step" in PS rate.
    • Polarization status?
  6. Beam Time Accounting (BTA):
    • 3 possible conditions:
      • ABU: Available Beam Used
      • BANU: Beam Available [to the Hall] but Not Used [by the Hall]
      • BNA: Beam Not Available [to the Hall]
    • Automated procedure in MCC for populating BTA have not been very reliable
    • Proposal from Mark D.
      • Shift leader should record when we request no beam (for example changing the radiator.) When submitting the Beam Time Accounting, the shift leader should check that the BANU and BNA numbers are correct. If they are not correct, the shift leader should move all the time that is listed under BANU into the BNA column unless they specifically requested no beam from MCC.

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.
    • 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
  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: 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.