Difference between revisions of "Run Planning Meeting Notes, Apr 26-May 2, 2018"

From GlueXWiki
Jump to: navigation, search
m
m
Line 13: Line 13:
 
#Issues:
 
#Issues:
 
#* Rootspy crashes and recovery [https://logbooks.jlab.org/entry/3567623][https://logbooks.jlab.org/entry/3567838]
 
#* Rootspy crashes and recovery [https://logbooks.jlab.org/entry/3567623][https://logbooks.jlab.org/entry/3567838]
 +
#* Time differences in monitoring plots [https://logbooks.jlab.org/entry/3567859]
 
# Reports:
 
# Reports:
 
#* Running with 750 um converter
 
#* Running with 750 um converter

Revision as of 08:36, 27 April 2018

<- Back to Run Coordination Meetings:Fall2017 Spring2018 Run

Friday, April 27 at 08:45

  1. Notes from the previous 24 hours:
  2. Issues:
    • Rootspy crashes and recovery [7][8]
    • Time differences in monitoring plots [9]
  3. Reports:
    • Running with 750 um converter
  4. Run Plan
    • Friday
      • High rate DAQ tests (9.30 am)
      • Injector recovery (MCC, possible beam down ~1hr)
      • TAC Run (2 pm)
    • Saturday
      • Production Running
    • Sunday
      • Production Running
    • Longer term run plan/Other items
      • Resumption of raster scan studies
      • Level 1 trigger studies
    • End of run preparation
      • Be prepared to switch everything off after last beam at 6 am, SUNDAY May 6
  5. AOB

Thursday, April 26 at 08:45

  1. Notes from the previous 24 hours:
    • Replacement of TAGH FDC module [10]
    • Production running
    • High rate trigger tests
  2. Issues:
    • Resuming DAQ after Wednesday tour [11]
    • Running with 750 um converter
    • Hot Channels, delta t offsets [12]
  3. Reports:
  4. Run Plan
    • Thursday
      • Level 1 trigger test
      • High rate trigger test part II(?)
      • Low current BPM lock test (afternoon)
    • Friday
      • High rate DAQ tests (9.30 am)
      • TAC Run (2 pm)
    • Saturday
    • Longer term run plan
  5. AOB