Difference between revisions of "Short Term Run Plan"

From Hall D Ops Wiki
Jump to: navigation, search
(Special instructions)
(DAQ issues)
 
(37 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
Do reload this page, it gets updated frequently.
 +
 
== Current Experiment ==
 
== Current Experiment ==
 
Rare Eta Decay & GlueX II (with DIRC)
 
Rare Eta Decay & GlueX II (with DIRC)
Line 7: Line 9:
 
== Notes ==
 
== Notes ==
 
* All GlueX detectors (including DIRC)
 
* All GlueX detectors (including DIRC)
* CDC Weather alarm, aka Alarm on HD:coda:cdc:p_diff, see https://logbooks.jlab.org/entry/4001862
 
** Stop run - Acknowledge alarm and document it - Start new run
 
  
 
== Run conditions ==
 
== Run conditions ==
Line 16: Line 16:
 
* Collimator: 5.0 mm
 
* Collimator: 5.0 mm
 
* TPOL converter: Be 75 um
 
* TPOL converter: Be 75 um
* Runs are no more than 2 hours - see whiteboard for the production cycle
+
* Runs are no more than 2 hours (~400M triggers)- see whiteboard for the production cycle
 
* Target: Liquid Hydrogen
 
* Target: Liquid Hydrogen
  
DAQ config
+
DAQ configuration
* Setup: TBA
+
* Setup: FCAL_BCAL_PS_m9
* Production: TBA
+
* Production: PHYSICS_DIRC
* (Raw mode: config TBA)
+
* (Raw mode: PHYSICS_DIRC_RAW)
  
 
== Run plan ==
 
== Run plan ==
Line 29: Line 29:
 
== Shift duties  ==
 
== Shift duties  ==
  
GlueX Guidelines are at [[Shift_Guidelines_for_Shift_Leader]] and [[Guidelines_for_Remote_Worker_Shift]]
+
[[Shift_Guidelines_for_Shift_Leader|Shift Leader]]  
  
=== Run comments ===
+
[[Guidelines_for_Remote_Worker_Shift|Shift Worker]]
  
Put information, eg "production ...nA <target>", in the run comments window of the DAQ. The comments are needed for RCDB.
+
== Special instructions ==
  
The run comments window should appear automatically after a run has been started. Enter comments and SAVE, do not exit. If the run comments window is visible, check first whether it is hiding eg on the upper workspcace. If it is not up, restart the DAQ before start of the next run.
+
=== Hall Delta ===
  
=== List of production runs ===
+
It's good practice to refer to our hall as Delta when talking to MCC, to make sure that there is no acoustic confusion between us and Hall B.
 
+
* Include a separate list of the runs taken during the shift at the end of the shift leader summary
+
* Please include the following:
+
*:run number,    start & stop times,  number of events,  production/test/junk/any_other_comment
+
 
+
=== BTA sheet ===
+
 
+
* The '''BTA''' guidelines are at [[BTA_guidelines]]. <br> After loading the EPICS values, you may change the values, eg round them up or down.
+
** '''BANU values''' should be reflected in the PCC (or UED) value (else the aftermath doesnt work out for RC), put a comment for > 5minutes.
+
** '''UED:''' unplanned experiment down (hardware failure).
+
 
+
=== Strip Charts ===
+
 
+
* Log the '''strip charts''' of beam current and position, see [[Slow_Controls_Shift#MYA_Archiver]]
+
** on a gluon machine type LivePlot
+
** right-click on the screen and select "Load a Configuration"
+
** the configuration "'''beam_psc'''" provides the currently desired information
+
** right-click on the screen and select '''"Make Elog Entry"''', make sure you do not log to ELOG but to '''HDLOG'''.
+
 
+
=== CSS GlueX Overview ===
+
  
Log per run, [[Slow_Controls_Shift#EPICS_Control_Screens]]
+
=== Screenshot tool ===
  
 
"Alt L" brings up the [[Logbook_Screenshot_Tool | screenshot tool for making E-log entries]]
 
"Alt L" brings up the [[Logbook_Screenshot_Tool | screenshot tool for making E-log entries]]
  
=== Online Monitoring Plots ===
+
=== FCAL Base lockup ===  
  
Log per run, [[Online_Monitoring_Shift]]
+
If FCAL HV bases lose communication and stop providing high voltage, refer to https://halldweb.jlab.org/hdops/wiki/index.php/Forward_Calorimeter_Shift#FCAL_Base_lockup
  
=== Shift Checklist ===
+
=== CDC Weather alarm ===
  
Log per shift, [[Shift_Checklist]]
+
aka Alarm on HD:coda:cdc:p_diff.
 +
See https://logbooks.jlab.org/entry/4117725
 +
* Stop run - Acknowledge alarm and document it - Start new run
 +
We are temporarily using Hall B sensor for our alarm, see [https://logbooks.jlab.org/entry/4117725 Alternative Barometric Pressure Measurement]
 +
<!--The alarm has been disabled, see logbook entries [https://logbooks.jlab.org/entry/4114344 4114344], [https://logbooks.jlab.org/entry/4114307 4114307]-->
  
== Special instructions ==
+
=== DIRC Communication Error at Run Start ===
  
=== Hall Delta ===
+
When starting a new run, one of the DIRC FPGA boards may lose communication resulting in a Magenta communication error in the Alarm Tree, refer to [https://halldweb.jlab.org/hdops/wiki/index.php/DIRC_Shift#DIRC_Communication_Error_at_run_start this page] for a fix.
 
+
It's good practice to refer to our hall as Delta when talking to MCC, to make sure that there is no acoustic confusion between us and Hall B.
+
 
+
=== Screenshot Tool ===
+
 
+
"Alt L" brings up the [[Logbook_Screenshot_Tool | screenshot tool for making E-log entries]]
+
  
 
=== After beam restoration ===
 
=== After beam restoration ===
Line 91: Line 69:
 
* ask MCC to do their harp scan
 
* ask MCC to do their harp scan
 
* our '''harp scans''': follow the instructions in [[Beam_Line_Detectors_Shift#Radiator_Harp_Scan]]
 
* our '''harp scans''': follow the instructions in [[Beam_Line_Detectors_Shift#Radiator_Harp_Scan]]
 
<!--
 
=== Target status ===
 
 
* Check camera west-cam.jlab.org, select Target view, if necessary
 
-->
 
  
 
=== rootspy  ===  
 
=== rootspy  ===  
Line 105: Line 77:
  
 
Call the expert. In case they suggest that you restart the DAQ, find information at [[Data_Acquisition_Shift]].
 
Call the expert. In case they suggest that you restart the DAQ, find information at [[Data_Acquisition_Shift]].
 +
 +
In case the DAQ issue is '''low lifetime''':
 +
* In case there is time (eg beam down), call the expert so that he can track down the problem.
 +
* Restart the DAQ, if that does not help, call the expert.
 +
 +
=== BTA sheet ===
 +
 +
* The '''BTA''' guidelines are at [[BTA_guidelines]]. <br> After loading the EPICS values, you may change the values, eg round them up or down.
 +
** '''BANU values''' should be reflected in the PCC (or UED) value (else the aftermath doesnt work out for RC), put a comment for > 5minutes.
 +
** '''UED:''' unplanned experiment down (hardware failure).
 +
 +
=== Bottom Alcohol Bubbler ===
 +
 +
*We are not using the bottom alcohol bubbler. It is expected that its level is "ADD" and that it is not bubbling [https://logbooks.jlab.org/entry/4108449 log entry]

Latest revision as of 04:49, 13 February 2023

Do reload this page, it gets updated frequently.

Current Experiment

Rare Eta Decay & GlueX II (with DIRC)

  • Experiment number: E12-12-002 (use in BTA shift information)
  • Proposal
  • Spokesperson: C. A. Meyer

Notes

  • All GlueX detectors (including DIRC)

Run conditions

Hall D counting room whiteboard

  • Radiator: JD70-103 50 um diamond (4 orientations: 0, 90, 45, -45)
  • Collimator: 5.0 mm
  • TPOL converter: Be 75 um
  • Runs are no more than 2 hours (~400M triggers)- see whiteboard for the production cycle
  • Target: Liquid Hydrogen

DAQ configuration

  • Setup: FCAL_BCAL_PS_m9
  • Production: PHYSICS_DIRC
  • (Raw mode: PHYSICS_DIRC_RAW)

Run plan

See the daily plan in Run Coordination Meetings:Spring2023 and also the counting house whiteboard

Shift duties

Shift Leader

Shift Worker

Special instructions

Hall Delta

It's good practice to refer to our hall as Delta when talking to MCC, to make sure that there is no acoustic confusion between us and Hall B.

Screenshot tool

"Alt L" brings up the screenshot tool for making E-log entries

FCAL Base lockup

If FCAL HV bases lose communication and stop providing high voltage, refer to https://halldweb.jlab.org/hdops/wiki/index.php/Forward_Calorimeter_Shift#FCAL_Base_lockup

CDC Weather alarm

aka Alarm on HD:coda:cdc:p_diff. See https://logbooks.jlab.org/entry/4117725

  • Stop run - Acknowledge alarm and document it - Start new run

We are temporarily using Hall B sensor for our alarm, see Alternative Barometric Pressure Measurement

DIRC Communication Error at Run Start

When starting a new run, one of the DIRC FPGA boards may lose communication resulting in a Magenta communication error in the Alarm Tree, refer to this page for a fix.

After beam restoration

  • check the radiation levels without radiator and then with the radiator
    • see the whiteboard (bottom RHS corner of the RH board) - there are columns of values expected without and with the radiator
  • retract the radiator
  • collimator in blocking position
  • ask MCC to do their harp scan
  • our harp scans: follow the instructions in Beam_Line_Detectors_Shift#Radiator_Harp_Scan

rootspy

If you have to restart rootspy, Online_Monitoring_Shift#Routine_Operation, and it crashes, you might have to restart the monitoring process, find help at Online_Monitoring_Shift#Starting_and_stopping_the_Monitoring_System.

DAQ issues

Call the expert. In case they suggest that you restart the DAQ, find information at Data_Acquisition_Shift.

In case the DAQ issue is low lifetime:

  • In case there is time (eg beam down), call the expert so that he can track down the problem.
  • Restart the DAQ, if that does not help, call the expert.

BTA sheet

  • The BTA guidelines are at BTA_guidelines.
    After loading the EPICS values, you may change the values, eg round them up or down.
    • BANU values should be reflected in the PCC (or UED) value (else the aftermath doesnt work out for RC), put a comment for > 5minutes.
    • UED: unplanned experiment down (hardware failure).

Bottom Alcohol Bubbler

  • We are not using the bottom alcohol bubbler. It is expected that its level is "ADD" and that it is not bubbling log entry