Difference between revisions of "Short Term Run Plan"

From Hall D Ops Wiki
Jump to: navigation, search
(Run comments)
(Run comments)
Line 33: Line 33:
 
=== Run comments ===
 
=== Run comments ===
  
Put information, eg "production ...nA <target>", in the run comments window of the DAQ. The comments are needed for RCDB.
+
Put information, eg "production ...nA <target>", in the run comments window of the DAQ. The comments are needed for RCDB. <br>
 
+
The run comments window should appear automatically after a run has been started. Enter comments and SAVE, do not exit. <br>
The run comments window should appear automatically after a run has been started. Enter comments and SAVE, do not exit.
+
 
If you do not see the run comments window, check first whether it is hiding eg on the upper workspace.
 
If you do not see the run comments window, check first whether it is hiding eg on the upper workspace.
 
If it is not up, restart the DAQ before start of the next run.
 
If it is not up, restart the DAQ before start of the next run.

Revision as of 06:46, 23 January 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 - see whiteboard for the production cycle
  • Target: Liquid Hydrogen

DAQ config

  • Setup: TBA (prelim: 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

GlueX Guidelines are at Shift_Guidelines_for_Shift_Leader and Guidelines_for_Remote_Worker_Shift

Run comments

Put information, eg "production ...nA <target>", in the run comments window of the DAQ. The comments are needed for RCDB.
The run comments window should appear automatically after a run has been started. Enter comments and SAVE, do not exit.
If you do not see the run comments window, check first whether it is hiding eg on the upper workspace. If it is not up, restart the DAQ before start of the next run.

List of production runs

  • 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.
    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 per shift, 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 "Make Elog Entry", make sure you do not log to ELOG but to HDLOG.
  • make sure the time span of your trip chart covers your shift

The following are suitable for the (remote) shift worker:

CSS GlueX Overview

Log per run, Slow_Controls_Shift#EPICS_Control_Screens

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

Online Monitoring Plots

Log per run, Online_Monitoring_Shift

Shift Checklist

Log per shift, Shift_Checklist and https://halldweb.jlab.org/hdops/wiki/index.php/Primer_for_shift_takers for more information.

Note that remote shift workers can look at the white board https://halldweb.jlab.org/online/whiteboard/ or at RCDB for information on DAQ/trigger configurations.

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.

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

Note: the alarm has been disabled, see logbook entries 4114344, 4114307

( 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 )

Screenshot tool

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

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.