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

From GlueXWiki
Jump to: navigation, search
Line 44: Line 44:
 
#* beam [AD]
 
#* beam [AD]
 
#* CDC pressure alarm [https://logbooks.jlab.org/entry/3541040] [CG]
 
#* CDC pressure alarm [https://logbooks.jlab.org/entry/3541040] [CG]
#* Muon Chamber noise [https://logbooks.jlab.org/entry/3539241][https://logbooks.jlab.org/entry/3536388][https://logbooks.jlab.org/entry/3541376] [DL]
+
#* Muon Chamber noise [https://logbooks.jlab.org/entry/3536388][https://logbooks.jlab.org/entry/3539241][https://logbooks.jlab.org/entry/3541376] [DL]
 
# Planning:
 
# Planning:
 
#* updated run time chart [https://halldweb1.jlab.org/wiki/index.php/File:Spring18_week8.jpg]
 
#* updated run time chart [https://halldweb1.jlab.org/wiki/index.php/File:Spring18_week8.jpg]

Revision as of 09:21, 2 March 2018

<- Back to Run Coordination Meetings:Fall2017 Spring2018 Run

Thursday, March 1

  1. Notes from the previous 24 hours:
    • MCC reports
    • Production Data with 58um JD70-100 diamond in the early afternoon
    • At about 6pm, we started low intensity scan as proposed in Justin's google sheet
    • For these runs: (i) Hovanes reverted the collimator position to the same value used in the previous current scan, (ii) We reverted to the previous value of the CDC window offset
    • [Beam Position Strip Chart, AC, PS Coincidence Monitoring https://logbooks.jlab.org/entry/3540484] (small interruption from 9pm-10pm)
  2. Issues:
    • (fixed) Sean updated the CDC timing for the low intensity scan, see [1]. This has to be switched it back in production (see also this entry). How to restore production running (by Elton) [2].
    • Hall D BEM stopped reporting yesterday near 6pm [3] [AD]
  3. Reports (some of these shown at the AWG yesterday):
    • Production vertex position before/after collimator shift (runs 40496 and 40509) [AA]
    • Pedestals Monitor FCAL, BCAL (run 41546 - production) [4] [SF]
    • Beam Trip map updated in CCDB [5] [DL]
    • low level monitoring [6] [TB]
    • yesterday AWG meeting [7]
    • Slope of the coherent peak high energy edge [8] [JS]
  4. Planning:
    • updated run time chart [9]
  5. Today's run plan Run Plan Google Calendar Accel. Run Plan Google Calendar:
    • morning: harp scan [10],[11],[12]
    • Production
    • Hall D low-current orbit lock test for TAC runs
    • Production: back 4 more

Friday, March 2

  1. Notes from the previous 24 hours:
    • Hall D low-current orbit lock test for TAC runs: succeeded in good horizontal orbit lock down to a few nA [13]
    • Production runs: JD70-100 150nA and AMO, 180nA; Day: [14], Swing: [15], Owl: [16]
  2. Issues:
    • DAQ crashes at go (Sasha fixed it) ~40 mins banu https://logbooks.jlab.org/entry/3540927
    • downtime - issue with one of the cavities ~1.5h (2L15-4 dropping zone from HV; Cavity bypassed; still dropping zone. EES-RF contacted.)
    • FDC trips during owl shift [17] [SF, VC]
  3. Reports
    • cdc rates during current scan 41343-41347 [18] [BZ]
    • low level monitoring [19] [TB]
    • beam [AD]
    • CDC pressure alarm [20] [CG]
    • Muon Chamber noise [21][22][23] [DL]
  4. Planning:
    • updated run time chart [24]
  5. Today's run plan (TBD) Run Plan Google Calendar Accel. Run Plan Google Calendar:
    • harp scan
    • Sasha planning ~30 min run using the thicker 750 um thick converter. Goals: data sample for Sebastian to evaluate possible pile-up in the TPOL and pre-scale for PS trigger
    • Production running