Ask a control room expert or the Run Coordinator to add your Kerberos principal to the .k5login files for the uboonedaq and ubooneshift users on uboone-cr-01, uboone-cr-02, uboone-cr-03, and uboone-cr04.
Changes in shift procedure and important notices for shifters are listed by date in the Operations Wiki Updates page. Please review this list at the beginning of every shift and contact the relevant subsystem expert or Run Coordinator if you are not clear on new procedures.
Be sure to reread parts of the Operations Wiki that have been updated (or are new) since the last shift you took. The Operations Wiki Updates page should make it very simple to determine which material should be reviewed.
If your last shift was before October 14th, 2015 (the date the Operations Wiki Update page was created), please read the entire Operations Wiki. Ideally this should be done before the beginning of your shift.
At the beginning of the shift call MCR (x3721) and let them know that the new MicroBooNE shifters are in ROC West.
At the beginning of shift, fill out the Beginning of Shift form on the E-log, and enter it under topic "Shift/Beginning of shift".
Take runs according to the Run Plan, referencing RC - Guide for instructions about the run control. Contact DAQ on-call expert if there are any problems in data-taking - try gchat first and give the expert a phone call if they don't respond within a minute.
Monitor the BNB status display (see Beam - Overview for instructions) and follow the directions in Beam - Guide about alarms or significant changes in beam conditions.
Monitor the slow control display for recent alarms (see SLC - Shifters). Check for alarming/tripping power supplies and call the relevant subsystem expert if you see major alarms. Acknowledge previously understood alarms, and new major alarms after contacting the relevant subsystem expert. In either case fill out the Alarm Acknowledged form on the E-log. For minor alarms, send an email to the relevant subsystem expert instead.
Look at the Online Monitor plots for the runs you take while on shift. See the prototype checklist here: OM - Checklist.
Monitor data processing, a.k.a. PUBS. Make sure PUBS is running and that the computers on which PUBS is running are not overloaded. See the specific instructions at DM - Shifters.
This document includes ASIC configuration settings as well as information about activity at LArTF during the collection of data. Please continue to update this document during early operations as it will be very helpful in helping us diagnose noise-related concerns, for instance. Please update this document during your shift and copy your updates into an E-log entry at the end of your shift.
Also note that noting operations-related items in the Run Information Document or making a note in the shifter Google chat window is not a replacement for an E-log entry. Any operations-related items of interest must be noted in the E-log, both promptly and with specific information (such as which alarms went into a bad state).
Shifters need to notify Run Coordinator when experts are going to work in LArTF and also when the shifters are asked to help the experts in LArTF.
Shifters must also fill out an E-log entry using the Start of Detector Access form, and fill out the End of Detector Access form when the work is complete.
At the end of shift, fill out the End of Shift form on the E-log, and enter it under topic "Shift/End of shift". Communicate with the incoming shifters (who should arrive at least 10 minutes before the end of the shift) the events of the shift, anything unusual they should be monitoring, and changes in the Run Plan communicated to you by the Run Coordinator or DAQ experts.
SLC - Shifters: SHIFTER INSTRUCTIONS (Shifters are strongly instructed to ONLY follow instructions in this link. Ignore any other instructions you might see in the slow monitoring tabs below, you are welcome to read them for informative purposes ONLY!)
Example - Experts Only: This is where the "Expert Documentation" should live, but only for the time being, we will want to move this behind a password wall. For the time being please start to build the documentation here now but be mindful that it is public viewable.