Short Term Run Plan
- 1 Last updated
- 2 Current Experiment
- 3 Notes
- 4 Run conditions
- 5 Run plan
- 6 Shift duties
- 7 Special instructions
28 June, by Naomi Jarvis
Measuring the Charged Pion Polarizability in the γγ -> π+π- reaction
- Experiment number: E12-13-008 (use in BTA shift information)
- Proposal: PAC link
- Spokesperson: Rory Miskimen
- ST: not installed
- one quadrant is OFF (crate CDC1)
- Weather alarm, see https://logbooks.jlab.org/comment/38202#comment-38202
- Stop run
- Acknowledge alarm and document it
- Start new run
- DIRC: not in use
- Radiator JD70-103 45/135
- Collimator 3.4 mm
- TPOL converter Be 750 um
- Coherent edge see whiteboard
- Runs are no more than 2 hours - see whiteboard for production cycle
- setup: PHYSICS_CPP
- production: config FCAL_BCAL_PS_CPP_m9.conf
- (raw mode: config FCAL_BCAL_PS_CPP_m10.conf)
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
- 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)
- 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 shift, Shift_Checklist
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).
- 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
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.
Call the expert. In case they suggest that you restart the DAQ, find information at Data_Acquisition_Shift.
If there are any, please add firstname.lastname@example.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