Difference between revisions of "Run Planning Meeting Notes, Feb 06-Feb 12, 2020"

From GlueXWiki
Jump to: navigation, search
(Monday, February 10)
Line 11: Line 11:
 
#** Found high rates in high photon tagger counter (see issues)
 
#** Found high rates in high photon tagger counter (see issues)
 
#** Had to request beam tune -> Unusal tagger rates + ION chamber trips (see: [https://logbooks.jlab.org/entry/3780300])
 
#** Had to request beam tune -> Unusal tagger rates + ION chamber trips (see: [https://logbooks.jlab.org/entry/3780300])
#** PSC coin.rates < 6khz (issue did not occur during next shift [https://logbooks.jlab.org/entry/3780554])
 
 
#* Sunday
 
#* Sunday
 
#** Prodcution runs @350nA
 
#** Prodcution runs @350nA
 
#** Harp scans
 
#** Harp scans
 
# Issues
 
# Issues
#* Variation in PS and main trigger rates over the weekend ([https://logbooks.jlab.org/entry/3779952],[https://logbooks.jlab.org/entry/3780684])
+
#* Variation in PS and main trigger rates over the weekend ([https://logbooks.jlab.org/entry/3779952],[https://logbooks.jlab.org/entry/3780684],[https://logbooks.jlab.org/entry/3780554])
 
#* High rates in high photon tagger counters ([https://logbooks.jlab.org/entry/3780065 energy distribution], [https://logbooks.jlab.org/entry/3780267 harp scan electron], [https://logbooks.jlab.org/entry/3780269 harp scan gamma], [https://logbooks.jlab.org/entry/3780295 epics after tune])
 
#* High rates in high photon tagger counters ([https://logbooks.jlab.org/entry/3780065 energy distribution], [https://logbooks.jlab.org/entry/3780267 harp scan electron], [https://logbooks.jlab.org/entry/3780269 harp scan gamma], [https://logbooks.jlab.org/entry/3780295 epics after tune])
 
# Reports
 
# Reports

Revision as of 21:09, 9 February 2020

Monday, February 10

  1. Last 72 hours
    • Friday
      • Beam sent to hall around 08:30
      • Harp scans
      • Prodcution runs @350nA until 23:50 -> no beam until the next morning
    • Saturday
      • Beam sent to hall around 12:00
      • Harp scans (requested by MCC)
      • Prodcution runs @350nA
      • Found high rates in high photon tagger counter (see issues)
      • Had to request beam tune -> Unusal tagger rates + ION chamber trips (see: [1])
    • Sunday
      • Prodcution runs @350nA
      • Harp scans
  2. Issues
  3. Reports
  4. Plans for today

Friday, February 7

  1. Last 24 hours
    • Production runs @350nA until 14:00
    • Hovanes worked on diamond position for JD70-105 0/90 (see reports)
    • Continued data taking until 18:15
    • Connection issues with rocDIRC -> Bill, Sergey and network expert on call had to work until late night to fix the problem
    • Accelerator crew was having network issues too
    • Hall went into beam permit around 1:15am
    • Accelerator crew having trouble with control system (see issues)
  2. Issues
    • DIRC cart leaking (see: [9])
    • Problems with 1L12 and 2L24 (see: [10])
    • Accelerator site having problems with IOCs in alarm handler (see: [11])
  3. Reports
    • New diamond position for JD70-105 0/90 (see: [12],[13])
    • Communication problems with rocDIRC (see: [14],[15],[16])
    • Network problems on accelerator site (see: [17],[18])
  4. Plans for today
    • Production runs
    • Access to hall ?
  5. Plan(s) for next week
    • Monday: Hall A will change setup for pol. meas. -> No beam from ~ 8:00 on (see: [19])
  6. No meeting this weekend -> Next meeting: Monday, Feb 10

Thursday, February 6

  1. Last 24 hours
    • Beam was sent to hall at 19:51
    • Harp scans (see reports for details)
    • Production runs @ 350nA
    • Collected 1.8B events
  2. Issues
    • DIRC temperature alarm (resolved, see: [20])
    • Swing shift reported coherent peak for JD70-105 0/90 PARA to be unusually wide -> No such observations for other settings
  3. Reports
  4. Plans for today
    • Production runs