Send an email to firstname.lastname@example.org to request access be granted to LArTF, once you have completed the Hazard Awareness training
Ask the Run Coordinator or other expert 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. To add a principal to the .k5login, they must push the change to the ubooneops repository k5login file, which will automatically update the .k5login file for ubooneshift and uboonedaq. There is a copy of the repository on ws01 at ~ubooneshift/uboone-shift-tools/uboone-operations-ubooneops/.
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.
Please note that you are required to check in to your shift ten minutes before the official start of your shift, as listed on the elog. Otherwise, follow these procedures for communicating with the outgoing shifter: Shift Turnover Procedures
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 (first following the recommendations in RC - Guide) - try Google Chat first and give the expert a phone call if they don't respond within a minute.
Every four hours (two hours into the shift and six hours into the shift), fill out the Checklist form on the E-log, and enter it under topic "Shift/Checklist".
This checklist is used to ensure shifters are focusing on the right things during their shifts, to help track our noise issues as they develop over time, to catch things that "slip between the cracks" of our slow monitoring alarms, and to provide a summary of who to contact in case problems come up.
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.
Occasionally (every hour or so) check the MCR E-log for updates about the status of the BNB.
Monitor the slow control display for recent alarms (see SLC - Guide). 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.
For cryo-related alarms in the slow control display, before contacting anyone you should first verify that the cryo IFIX display is also showing an alarm. The cryo IFIX display is located on the opposite side of the NOvA shifter station (by the white boards along the side of the room). The machine with the IFIX display is the one closest to the door (but not the one facing the door that is used to control the displays on the walls). Use the default username; the password is "2Run@TheSho$". If the IFIX display is not showing an alarm as well, contact the Run Coordinator (phone call for major alarm, email for minor alarm) instead of MC-1 (as instructed in SLC - Guide).
Look at the Online Monitor plots for the runs you take while on shift. See an example of things to monitor 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.
Please check the quality of a data run using the Run Catalogue once a run finishes. Add in any comments about occurrences during the run.
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.
We have a DEDICATED form for the weekly cryo walk-through. You do NOT have to inform the RC about these.
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.
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.