PrimEx-eta Short Term Run Plan
Contents
Last updated
27 August, by Igal Jaegle
Current Experiment
Measure the η-meson radiative decay width (η -> γγ)
- Experiment number: E12-10-011 (use in BTA shift information)
- Proposal: PAC link
- Spokesperson: Ashot Gasparian
Notes
- All GlueX detectors except DIRC
- Plus, a calorimeter (CCAL) 4 m downstream FCAL to cover polar between 0.2 and 1 degree and measure Compton events in combination with FCAL.
Run conditions
Hall D counting room whiteboard
- Radiator (Amorphous) 10 µm Al (2 x 10-5 RL)
- Collimator 5 mm
- TPOL converter Be 750 µm
- Runs are no more than 2 hours - see whiteboard for the production cycle
- Targets, currently Empty Be target
- 4He target: cryogenic target
- Empty 4He target
- Be target
- Empty Be target
DAQ config
- setup:
- production:
- (raw mode: config )
Run plan
See the daily plan in Run Coordination Meetings:Summer2022 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, Pb target / no target, radiator & orientation, 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 >= 5 minutes must be reflected in the PCC value (else the aftermath doesnt work out for RC)
- BANU values < 5 minutes may be set to 0
- 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 myaPlot
- right-click on the blank space of the myaPlot screen and select "Clone in new LivePlot"
- right-click on the screen and select "Load a Configuration"
- the configuration "beam_conditions" provides the beam current and position information
- right-click on the screen and select "Make Elog Entry", make sure you do not log to ELOG but to HDLOG.
data monitoring plots
log per run, Online_Monitoring_Shift
screen shot of CSS GlueX Overview
log per run, Slow_Controls_Shift#EPICS_Control_Screens , also see screenshot tool for making E-log entries
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.
After beam restoration
- see Beam_Line_Detectors_Shift#Collimator_and_Radiators on how to move radiators and collimator
- 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
- use the harp scan extrapolation tool http://zeus.phys.uconn.edu/halld/cobrems/harptool.cgi and post screenshots of the plots into the logbook (eg https://logbooks.jlab.org/entry/3929556).
Target status
- check camera west-cam.jlab.org, select Target view, if necessary
- look for yellow (small) flag as in https://halldweb.jlab.org/hdops/wiki/images/3/34/Lead_target.gif
- yellow flag visible: target IN
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.
Timing problems
If there are any, please add sdobbs@jlab.org to the notifications in the logbook entry.
Example double timing peaks: https://logbooks.jlab.org/entry/3933110
Shoulders on timing peaks might be features and not problems: https://logbooks.jlab.org/entry/3933867