Difference between revisions of "Run Planning Meeting Notes, Feb. 14-Fev 21, 2019"

From GlueXWiki
Jump to: navigation, search
(Created page with "== Wednesday, Feb. 13 at 08:45 == # Notes from the past 24 hours: #*Investigations of SSP problem #**40 min access for SSP issue. Sergei also looked at TOF RF problem, and Lu...")
 
(→‎Friday, Feb. 15 at 08:45)
 
(14 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
== Wednesday, Feb. 13 at 08:45 ==
+
== Thursday, Feb. 14 at 08:45 ==
−
# Notes from the past 24 hours:
+
# Past 24 hours:
−
#*Investigations of SSP problem
+
#* Acceptable quality beam established early morning around 11:00 am.
−
#**40 min access for SSP issue. Sergei also looked at TOF RF problem, and Lubomir worked on TRD.
+
#** Beam profile and convergence by Jay:https://logbooks.jlab.org/entry/3652506
−
#**[https://logbooks.jlab.org/entry/3652012 Some success in identifying issue and partly fixing it]
+
#* DIRC data taking.
−
#**[https://logbooks.jlab.org/entry/3652330 Only one instance of lifetime dropping to zero after the fix]
+
#*# DIRC analysis is on-going.
−
#*DIRC data taking.
+
 
# Issues
 
# Issues
−
#*Beam stirring issue. MCC cannot deliver more than 65 nA.  
+
#* Cryo Water Temperature jump to 72F (limit 70F).
−
#** Only ran on amo since last evening.
+
#** Due to pump switch: https://logbooks.jlab.org/entry/3652512
−
#** [https://logbooks.jlab.org/entry/3652433 Beam transmission look fine]
+
#* IOC lost communication
−
#*[https://logbooks.jlab.org/entry/3651965 Beam convergence]
+
#** 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
−
#*SSP problem
+
#* DIRC SSP problem:
−
#*[https://logbooks.jlab.org/entry/3651748], [https://logbooks.jlab.org/entry/3651772] Target control problem. [https://logbooks.jlab.org/entry/3651725 Target alarms were not enabled].
+
#** DAQ stopped twice due to the out of sync issue.
−
#*TOF RF status?
+
#* Tagger RF time: https://logbooks.jlab.org/entry/3652533
−
#*Beam current can drift by have been drifting by up to 15 MeV the last 24h
+
#* hdview2 is work working
−
#Today's plan (changed this morning at the 8:00am MCC meeting)
+
#Today:
−
#*Beam scheduled for all day: DIRC commissioning+Thr. scan (LED&dark runs done) + data taking overnight.
+
#* No planned access
−
#*[https://cebaf.jlab.org/files/ops/accboard/ MCC white board]
+
#* Opportunistic access requested by Kenoe to work on GEM.
−
#*[https://halldweb.jlab.org/wiki/images/6/64/Spring19_week1.jpg This week time chart]
+
#* DIRC nominal running (MOROC threshold scan?)
−
#*[https://halldweb.jlab.org/online/whiteboard/ Hall D white board]
+
 
 +
== 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

Latest revision as of 10:09, 15 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
Retrieved from "https://halldweb.jlab.org/wiki/index.php?title=Run_Planning_Meeting_Notes,_Feb._14-Fev_21,_2019&oldid=91302"