Difference between revisions of "Run Planning Meeting Notes, Mar 2 - Mar 8, 2017"

From GlueXWiki
Jump to: navigation, search
(Friday, March 3)
(Saturday, March 4)
Line 129: Line 129:
 
#* Empty target run accomplished
 
#* Empty target run accomplished
 
#* fADC250 Compressed Mode Study
 
#* fADC250 Compressed Mode Study
#* [https://logbooks.jlab.org/entry/3464181 MO phase drift] (Elton)
+
#* Better downtime tracking in elog
 
#* In the last 24 hours:  
 
#* In the last 24 hours:  
#** Total triggers collected during last period:
+
#** Total triggers collected during last period: 1771M
 
#** Run Statistics [https://docs.google.com/spreadsheets/d/1NffTc4-S5PbTMSuH_pp7ZYsGRH4JC_WSVo770_iJYt0/edit#gid=1113040681 Spread Sheet]
 
#** Run Statistics [https://docs.google.com/spreadsheets/d/1NffTc4-S5PbTMSuH_pp7ZYsGRH4JC_WSVo770_iJYt0/edit#gid=1113040681 Spread Sheet]
 
#** Current Total: B
 
#** Current Total: B

Revision as of 13:18, 4 March 2017

<- Back to Run Coordination Meetings: Spring 2017 Run

Thursday, March 2

Shift ABU BNA BANU
Day 6.49 0.63 0.88
Swing 6.97 0.32 0.71
Owl 7.09 0.11 0.80
Total 20.55 1.06 2.39


  1. Accelerator Status over the last 24 hrs
  2. Hall-D/GlueX items
    • In the last 24 hours:
      • Production data taken after 10:30 AM Weds.
      • Long mode run
      • Black spots on diamonds
      • Total triggers collected during last period: 3099M
      • Run Statistics Spread Sheet
      • Current Total: 40.05B
  3. Issues
    • Problems with FCAL crate 9
    • FCAL red light issue
    • TRD gas issue
    • DAQ issues:
      • 5:42 - The DAQ keeps giving us "SEBO: Client has not reported for xx sec." errors, but then recovers after a minute. This happens every ~20mins or so. We will restart the DAQ again after the current run finishes.
      • ~22:00 - Monitoring stops working, have to start/stop runs several times to get events flowing through secondary ET
  4. Monitoring
  5. Run Plan
    • Production
    • Triggers: In-time random? Min-bias? FCAL+BCAL+ST?
  6. Offline Analysis
    • TAC runs?
  7. AOB

Friday, March 3

Shift ABU BNA BANU
Day 0.79 0.00 7.21
Swing 4.75 0.75 2.50
Owl 6.83 0.08 1.09
Total 12.37 0.83 10.80


  1. Accelerator Status over the last 24 hrs
    • Vacuum issues [~8 hours down]
    • 1630 - Beam back
    • 1730 - Attempt at trigger & DAQ studies
      • 1800 to 1840 - ACC access to replace controller
      • 1900 to 1930 - FSD Card swap
    • 2000 - Start of production
      • 500 - 20 min down due to cryomodule problems
    • Strip charts: 1 2
  2. Hall-D/GlueX items
  3. Issues
    • Red lines on run control GUI?
    • Front-panel triggers off for 30920-2
    • Firefox problems
  4. Monitoring
  5. Run Plan
    • Tagger/SC trigger
    • Hall A Bleed-through?
    • Empty target run?
    • fADC250 Compressed Mode?
    • Production
    • Next week:
      • High rate run [500 nA]
      • Low rate run [50 nA + 2x10^-5 RL Al]
  6. Offline Analysis
    • TAC runs?
  7. AOB


Saturday, March 4

Shift ABU BNA BANU
Day 6.79 0.03 1.18
Swing 6.17 1.12 0.71
Owl 7.29 0.07 0.64
Total 20.25 1.22 2.53
  1. Accelerator Status over the last 24 hrs
    • Steady beam delivery
    • New slow lock status display logbook entry
    • Strip charts: 1 2 3
  2. Hall-D/GlueX items
    • Tagger/SC trigger studies
    • Hall A Bleed-through study: 1 2
    • Empty target run accomplished
    • fADC250 Compressed Mode Study
    • Better downtime tracking in elog
    • In the last 24 hours:
      • Total triggers collected during last period: 1771M
      • Run Statistics Spread Sheet
      • Current Total: B
  3. Issues
    • ~2hrs lost to DAQ problems on Fri. morning
  4. Monitoring
  5. Run Plan
    • Production + Afternoon harp scan
    • Next week:
      • High rate run [500 nA]
      • Low rate run [50 nA + 2x10^-5 RL Al]
  6. Offline Analysis
  7. AOB