« Previous -
( diff) -
Next » -
Mark Ross-lonergan, 03/26/2019 11:42 AM
Run Plan - last updated Mar 26th 11:40am CDT
All shifters are required to be very familiar with this page. In case of questions, do not hesitate to contact the Run Co's. ¶
1 (937) 582-6663
1 (978) 822-2582
9788 BACK UB
RunCo (Mark) ON-CALL: 630-854-5306
Deputy RunCo (Kres) ON-CALL: 859-699-8711
Refresh this page Now. Click here: Run plan ¶
Link to which experts to call in case of other alarms
Please note there has been a change in the standard DAQ configuration ID, if runs crash please start back up in
DAQ Config ID 809 for the usual 420 minutes.
Chris Barnes will be covering as Slow-Control expert from Thurs 28th to Sun 31st march
The uB_DAQStatus_DAQX/sn_read_lag_multiplicity alarm sometime gets latched on. If it has a
green OK status box you can acknowledge it.
SN RunCat is down so you can ignore all checklist questions about this.
uB_RackTemps_TPC2_1_2/temperature is known and understood if it is minor alarm, you can acknowledge it.
Notes on current operations
General procedure: some troubleshooting instructions advocate to stop and restart the run to fix a problem. It is good to do so only once. If stopping and restarting didn't work at the first try, please get in touch with the relevant experts (or the Run Co) and wait for their clearance before stopping and restarting again.
Before resetting the PUBS, please ensure there are no PUBS errors being displayed - if there are, please report this to the Data Management expert (via email) before resetting.
If you make an elog entry about online monitor or runcat checks failing, upload a screenshot of the plot with the entry.
Additional Shifter Requirements:
Please inform the Run Coordinator(s) if
you see any DAQ instabilities, or
the mean run duration gets smaller than 2h, or
if you receive any information from MCR about the beam.
Please do not forget to check your runs in the RunCat.
Please fill out the Offline Production Checklist at 9am and 9pm every day. There are instruction on how to fill this out on this page: https://cdcvs.fnal.gov/redmine/projects/uboone-operations/wiki/Offline_Production_Checklist_-_Shifters
Please note that the offline production checklist has been modified. The content is essentially the same, but if you've done it before, it will look different now. Also, now you email the checklist itself to the offline production listserv rather than composing a separate email.
During access to the detector:
Make sure the Run Co's were informed of the access (google chat or call).
Detector platform access must be cleared by Run Co's.
Please fill out a Beginning of Detector Access and End of Detector Access Form.
If the "keytree" alarm occurs, and the persons accessing the platform have not called the shifter first, then call LArTF to find out who is accessing the detector. If no one answers, call the runco.
Please remind to the people making the access to call you back when they are done with their work in the pit.
At the end of detector access, please acknowledge the keybank incomplete alarm.
What should I do if I see alarms during my shift?
Have a look at this wiki page:
What to do in case of alarms during a shift