Difference between revisions of "Short Term Run Plan"

From Hall D Ops Wiki
Jump to: navigation, search
(→‎After beam restoration)
(→‎DAQ issues)
 
(134 intermediate revisions by 6 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)
 +
* Experiment number: E12-12-002 (use in BTA shift information)
 +
* [https://misportal.jlab.org/mis/physics/experiments/viewProposal.cfm?paperId=834 Proposal]
 +
* Spokesperson: C. A. Meyer
  
−
PrimEx-eta: A Precision Measurement of the η Radiative Decay Width via the Primakoff Effect
+
== Notes ==
−
* Experiment number: E12-10-011 (use in BTA shift information)
+
* All GlueX detectors (including DIRC)
−
* Proposal: [https://www.jlab.org/exp_prog/proposals/10/PR12-10-011.pdf PAC link]
+
  
 
== Run conditions ==
 
== Run conditions ==
 +
[https://halldweb.jlab.org/online/whiteboard/ Hall D counting room whiteboard]
  
−
Production runs at 200nA with full LHe4 target.
+
* Radiator: JD70-103 50 um diamond (4 orientations: 0, 90, 45, -45)
−
<!-- empty (He4) -->
+
* Collimator: 5.0 mm
−
(Solenoid and drift chambers on).
+
* 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 name: PHYSICS_PRIMEX
+
DAQ configuration
−
* Trigger file: CCAL_FCAL_PS_m9.conf
+
* Setup: FCAL_BCAL_PS_m9
−
* Keep the runs to 2h or less.
+
* Production: PHYSICS_DIRC
 +
* (Raw mode: PHYSICS_DIRC_RAW)
  
−
== Shift leader  ==
+
== Run plan ==
 +
See the daily plan in [https://halldweb.jlab.org/wiki/index.php/Run_Coordination_Meetings:Spring2023 Run Coordination Meetings:Spring2023] and also the [https://halldweb.jlab.org/online/whiteboard/ counting house whiteboard]
  
−
Guidelines are at [[Shift_Guidelines_for_Shift_Leader]]
+
== Shift duties  ==
  
−
=== AI for CDC HV ===
+
[[Shift_Guidelines_for_Shift_Leader|Shift Leader]]
  
−
For FULL target runs only, set the CDC HV before the start of each run using the value suggested by the AI. 
+
[[Guidelines_for_Remote_Worker_Shift|Shift Worker]]
−
* There are instructions here https://wiki.jlab.org/epsciwiki/index.php/PrimEx_instructions   
+
−
* The AI uses measurements from epics averaged over the last minute, so the AI should be used just before starting a run, when the beam current is at its target value and has been steady for the past minute. 
+
−
* If for any reason this proves to be problematic, please revert to the nominal HV, 2125V, and contact Naomi.
+
  
−
* for '''full target''' runs set the '''CDC HV''' before the start of each run using the value suggested by the AI. (see below [[Short_Term_Run_Plan#AI_for_CDC_HV]] for more info)
+
== Special instructions ==
−
* for '''empty target''' runs, keep the CDC HV at 2125V'''
+
  
−
=== run comment ===
+
=== Hall Delta ===
  
−
Put a comment, eg "production 200nA LHe4", in the run comment window of the DAQ. This comment is needed for RCDB.
+
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.
  
−
The run comment window should appear automatically after a run has been started. Enter the comment and SAVE, do not exit.
+
=== Screenshot tool ===
  
−
=== list of production runs ===
+
"Alt L" brings up the [[Logbook_Screenshot_Tool | screenshot tool for making E-log entries]]
  
−
* Include a separate list of the runs taken during the shift at the end of the summary (for example, see https://logbooks.jlab.org/entry/3936066)
+
=== FCAL Base lockup ===
  
−
=== strip charts ===
+
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
  
−
* Log the '''strip charts''' of beam current and position, see [[Slow_Controls_Shift#MYA_Archiver]], make sure you do not log to ELOG but to '''HDLOG'''.
+
=== CDC Weather alarm ===
−
** on a gluon machine type myaPlot
+
−
** right-click on the blank space of the myaPlot screen and select "Clone in new LivePlot"
+
−
** right-click on the blank space of the myaPlot screen and select "Load a Configuration"
+
−
** the configuration "beam_conditions" provides the beam current and position information
+
  
−
=== BTA sheet ===
+
aka Alarm on HD:coda:cdc:p_diff.
−
 
+
See https://logbooks.jlab.org/entry/4117725
−
* The '''BTA''' guidelines are at [[BTA_guidelines]]. <br> After loading the EPICS values, you may change the values, eg round them up or down.
+
* Stop run - Acknowledge alarm and document it - Start new run
−
** '''BANU values''' >= 5 minutes must be reflected in the PCC value (else the aftermath doesnt work out for RC)
+
We are temporarily using Hall B sensor for our alarm, see [https://logbooks.jlab.org/entry/4117725 Alternative Barometric Pressure Measurement]  
−
** '''BANU values''' < 5 minutes may be set to 0
+
<!--The alarm has been disabled, see logbook entries [https://logbooks.jlab.org/entry/4114344 4114344], [https://logbooks.jlab.org/entry/4114307 4114307]-->
−
 
+
−
== Shift worker ==
+
−
 
+
−
Guidelines are at [[Guidelines_for_Remote_Worker_Shift]]
+
−
+
−
'''Duties:'''
+
−
 
+
−
=== shift checklist ===
+
−
 
+
−
log per shift, [[Shift_Checklist]]
+
−
 
+
−
=== data monitoring plots ===
+
−
 
+
−
log per run, [[Online_Monitoring_Shift]]
+
  
−
=== screen shot of CSS GlueX Overview ===
+
=== DIRC Communication Error at Run Start ===
  
−
log per run, [[Slow_Controls_Shift#EPICS_Control_Screens]]
+
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.
  
−
== After beam restoration ==
+
=== After beam restoration ===
  
−
* [[Beam_Line_Detectors_Shift#Collimator_and_Radiators]]
+
* See [[Beam_Line_Detectors_Shift#Collimator_and_Radiators]] on how to move radiators and collimator
  
−
* check the '''radiation levels''' without a radiator and then with the radiator  
+
* 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
 
** see the whiteboard (bottom RHS corner of the RH board) - there are columns of values expected without and with the radiator
 
* '''retract the radiator'''
 
* '''retract the radiator'''
−
* after that,make sure that the '''collimator is in blocking position'''.
+
* '''collimator in blocking position'''
 
* ask MCC to do their harp scan
 
* ask MCC to do their harp scan
−
* follow the instructions in [[Beam_Line_Detectors_Shift#Radiator_Harp_Scan]] to do our '''harp scans''' 
+
* our '''harp scans''': follow the instructions in [[Beam_Line_Detectors_Shift#Radiator_Harp_Scan]]
−
* use the '''harp scan extrapolation''' tool and post screenshots of the plots into the logbook (eg https://logbooks.jlab.org/entry/3929556).
+
−
 
+
−
== Special instructions ==
+
  
 
=== rootspy  ===  
 
=== rootspy  ===  
Line 93: Line 78:
 
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]].
  
−
=== timing problems ===
+
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.
  
−
If there are any, please add sdobbs@jlab.org to the notifications in the logbook entry.
+
=== BTA sheet ===
  
−
Example double timing peaks: https://logbooks.jlab.org/entry/3933110
+
* 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).
  
−
Shoulders on timing peaks might be features and not problems: https://logbooks.jlab.org/entry/3933867
+
=== Bottom Alcohol Bubbler ===
  
−
=== PS and/or PSC scalers freezing ===
+
*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]
−
 
+
−
Keep an eye out for the PS and/or PSC scalers freezing.  If it happens, then step 2+3 of the instructions 'Run PS Scalers' at [[Pair_Spectrometer_Shift]]  can be followed to reset them, it has to be done on gluon100.
+
−
 
+
−
=== 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.
+

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
Retrieved from "https://halldweb.jlab.org/hdops/wiki/index.php?title=Short_Term_Run_Plan&oldid=4671"