Difference between revisions of "Run Planning Meeting Notes, Feb 14 - Feb 20, 2019"

From GlueXWiki
Jump to: navigation, search
(Wednesday, Feb. 18 at 08:45)
Line 1: Line 1:
 +
 +
== Thursday, Feb. 14 at 08:45 ==
 +
# Past 24 hours:
 +
#* Acceptable quality beam established early morning around 11:00 am.
 +
#** Beam profile and convergence by Jay:https://logbooks.jlab.org/entry/3652506
 +
#* DIRC data taking.
 +
#*# DIRC analysis is on-going.
 +
# Issues
 +
#* Cryo Water Temperature jump to 72F (limit 70F).
 +
#** Due to pump switch: https://logbooks.jlab.org/entry/3652512
 +
#* IOC lost communication
 +
#** IOCHDCOL failed at 21:30. Reported to us by MCC at 0:00. Reset at 1:50 am. Hovanes verified things are ok at 3am.  https://logbooks.jlab.org/entry/3652920
 +
#* DIRC SSP problem:
 +
#** DAQ stopped twice due to the out of sync issue.
 +
#* Tagger RF time: https://logbooks.jlab.org/entry/3652533
 +
#* hdview2 is work working
 +
#Today:
 +
#* No planned access
 +
#* Opportunistic access requested by Kenoe to work on GEM.
 +
#* DIRC nominal running (MOROC threshold scan?)
 +
 +
== Friday, Feb. 15 at 08:45 ==
 +
# Past 24 hours:
 +
#* Nominal DIRC setting collected 1B triggers
 +
#** Switched to the higher MOROC threshold (200)
 +
#* Smooth overnight running at 180nA, coming back to the desired 225nA this morning.
 +
#* Both opportunistic accesses happened during the accelerator down time due to the bulk power supply failure.
 +
# Issues:
 +
#* Beam steered to the wrong BCM, therefore constrained the maximum beam delivered to 180nA
 +
#**Detailed log: https://logbooks.jlab.org/entry/3653554
 +
#* Goni camera, wrong angle, did something move? https://logbooks.jlab.org/entry/3653437
 +
#* root spy crash: https://logbooks.jlab.org/entry/3653678
 +
#* DIRC SSP
 +
#** Runs at MOROC threshold of 50 not possible due to the out of sync issue, need to be looked into
 +
#** Out of sync over night (after switching the MOROC threshold).
 +
#* hdview2 and monitoring email working?
 +
# Plan for today:
 +
#* keep collecting higher MOROC threshold data (up to 1B triggers).
 +
#* When beam is not available, 15 min LED runs with different pulsing and trigger conditions.
 +
#* No planned and opportunistic access
 +
 
== Wednesday, Feb. 18 at 08:45 ==
 
== Wednesday, Feb. 18 at 08:45 ==
 
# Over the weekend summary:
 
# Over the weekend summary:

Revision as of 11:38, 18 February 2019

Thursday, Feb. 14 at 08:45

  1. Past 24 hours:
  2. Issues
  3. Today:
    • No planned access
    • Opportunistic access requested by Kenoe to work on GEM.
    • DIRC nominal running (MOROC threshold scan?)

Friday, Feb. 15 at 08:45

  1. Past 24 hours:
    • Nominal DIRC setting collected 1B triggers
      • Switched to the higher MOROC threshold (200)
    • Smooth overnight running at 180nA, coming back to the desired 225nA this morning.
    • Both opportunistic accesses happened during the accelerator down time due to the bulk power supply failure.
  2. Issues:
  3. Plan for today:
    • keep collecting higher MOROC threshold data (up to 1B triggers).
    • When beam is not available, 15 min LED runs with different pulsing and trigger conditions.
    • No planned and opportunistic access

Wednesday, Feb. 18 at 08:45

  1. Over the weekend summary:
    • Quote by Eugine: "All the problems landed on other ppl's court".
    • DIRC SSP firmware on Friday (thanks to Ben and Sasha)
    • Low intensity program completed.
    • HV scan: two more settings remains
    • HI test on Sunday: for most of the day, we were the only hall up.
      • ToF inner layer off, DC HV reduced, Tpol excluded from the trigger.
      • DIRC and DAQ passed the test!
    • Overnight: smooth 425nA scanning operation.
  2. Monitoring
  3. Plan for today:
    • Hall A, B and C are down, another HI test? @900nA?
  4. Issues:
    • hdview2: hang on the 1st event
    • DAQ: Randy factor cant be set and BCALroc.
    • Any update on the RF issue?
  5. Transition to the CPP