Difference between revisions of "Run Planning Meeting Notes, Mar 12-Mar 18, 2020"

From GlueXWiki
Jump to: navigation, search
(Monday, March 16)
(Monday, March 16)
Line 32: Line 32:
 
== Monday, March 16 ==
 
== Monday, March 16 ==
 
# Last 72 hours
 
# Last 72 hours
#* [https://logbooks.jlab.org/entry/3803258 fadc250 data corruption issue?] -- Beni
 
#** [https://logbooks.jlab.org/entry/3804492 problem narrowed down to one fadc250 module]
 
 
#* [https://logbooks.jlab.org/entry/3803296 TAGH hv adjustments, recovery of failed channel] -- Beni
 
#* [https://logbooks.jlab.org/entry/3803296 TAGH hv adjustments, recovery of failed channel] -- Beni
 
#* [https://logbooks.jlab.org/entry/3803578 TAC run impossible, bleed-through from Hall A?] -- Sasha
 
#* [https://logbooks.jlab.org/entry/3803578 TAC run impossible, bleed-through from Hall A?] -- Sasha
Line 44: Line 42:
 
#** [https://logbooks.jlab.org/entry/3804017 gradual recovery within 23 hours]
 
#** [https://logbooks.jlab.org/entry/3804017 gradual recovery within 23 hours]
 
# Reports/Issues
 
# Reports/Issues
#*  
+
#* [https://logbooks.jlab.org/entry/3803258 fadc250 data corruption issue?] -- Beni
 +
#** [https://logbooks.jlab.org/entry/3804492 problem narrowed down to one fadc250 module]
 +
#* [https://logbooks.jlab.org/entry/3804573 unable to reproduce notch structure around coinc peak in TAGM timing monitoring plot] -- Richard
 
# Run Plan
 
# Run Plan
 
#* ...
 
#* ...
 
#* Production
 
#* Production

Revision as of 07:14, 16 March 2020

Thursday, March 12

  1. Last 24 hours
  2. Reports/Issues
  3. Run Plan
    • Production

Friday, March 13

  1. Last 24 hours
  2. Reports/Issues
  3. Run Plan

For the period starting evening of Tuesday, March 17

Tentative Revised Shift Schedule -- Viral Edition

Monday, March 16

  1. Last 72 hours
  2. Reports/Issues
  3. Run Plan
    • ...
    • Production