Difference between revisions of "Short Term Run Plan"

From Hall D Ops Wiki
Jump to: navigation, search
(Run conditions)
Line 14: Line 14:
 
[https://halldweb.jlab.org/online/whiteboard/ Hall D counting room whiteboard]
 
[https://halldweb.jlab.org/online/whiteboard/ Hall D counting room whiteboard]
  
* Radiator (Amorphous) 10 µm Al (1 x 10-4 RL)
+
* Radiator:
* Collimator 5 mm
+
* Collimator:
* TPOL converter Be 750 µm
+
* TPOL converter:
  
 
* Runs are no more than 2 hours - see whiteboard for the production cycle
 
* Runs are no more than 2 hours - see whiteboard for the production cycle
  
* Targets:
+
* Target:
** 4He target: cryogenic target
+
*** FULL if supply pressure at < 23psi
+
*** EMPTY if supply pressure at > 27psi
+
** Be target
+
** Empty Be target
+
  
 
DAQ config
 
DAQ config
* Setup: PHYSICS_PRIMEX
+
* Setup:
* Production: CCAL_FCAL_PS_m9
+
* Production:  
 
* (Raw mode: config TBA)
 
* (Raw mode: config TBA)
  

Revision as of 10:55, 5 January 2023

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

Run conditions

Hall D counting room whiteboard

  • Radiator:
  • Collimator:
  • TPOL converter:
  • Runs are no more than 2 hours - see whiteboard for the production cycle
  • Target:

DAQ config

  • Setup:
  • Production:
  • (Raw mode: config TBA)

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 25 nA Pb", 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 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.

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, beam current, Be or He4 target / no target/empty target, radiator, daq configuration, daq event rate, daq livetime, 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 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

"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

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

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

Target status

  • Check camera west-cam.jlab.org, select Target view, if necessary

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.