Project

General

Profile

Wiki » History » Version 184

« Previous - Version 184/370 (diff) - Next » - Current version
Matthew Toups, 10/06/2015 11:18 AM


Before you start your shift

  • Make sure you have a current Fermilab ID, Fermilab Kerberos account, and Fermilab Services account (and go to "Request New/Renew Accounts" or call 630-840-2345 - 24 hours a day).
  • 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.

Shift Procedure

Log on to the control room computers

  • On the mac, the user is ubooneshift, and the password is the same as the MicroBooNE DocDB password.
  • On the Linux boxes, there are two cases (You must be added to the .k5login file. Contact us to help):
    • Case 1. The screen has been locked. In this case enter your Kerberos password, followed by your Keberos principal (user name)
    • Case 2. You have been logged out. In this case first enter the user as "ubooneshift", then enter your Kerberos password, and finally enter your Keberos principal (user name).

REFRESH ALL OPEN BROWSERS and sign in to Elog, Google+

  • Browsers open with instructions may have been changed! Make sure you have the latest instructions.
  • Log on to the ubooneshift google account with the common DAQ password xxxxxxxxxxx (concatenate the MicroBooNE DocDB user name, the number two, and the first syllable in the word preceding "xxxxxxxxxxx" in this sentence), go to Google hangouts, and then open up the MicroBooNE DAQ conversation to communicate with DAQ experts.

Check for special run plans, else follow the routine shift procedure

  • NEW: At the beginning of the shift call MCR (x3721) and let them know that uboone shifters are in ROC West. We are in a 3 month shutdown now. This is not necessary.
  • At the beginning of shift, fill out the Beginning of Shift form on the Elog, and enter it under topic "Shift/Beginning of shift".
  • During shift:
    • Day/Evening/Owl shifts:
      • See Run Plan
      • Execute the noisy channel analysis script (see Getting the list of noisy channels) and post the list of very noisy and very quiet channels to the Elog under topic "Shift".
      • Look at the Online Monitor plots for the run you just took. See the prototype checklist here: OM - Checklist
      • Monitor the slow control display. Check for alarming or tripping Wiener power supplies (see here for instructions). Call the DAQ expert on call if this happens. Monitor the pressure in the cryostat. There is a saved plot "filling.plt". If you see the pressure rise to 15 psig and no corresponding e-log entry from the cryogenics team that they are working on the issue immediately page the cryo on-call expert (630-255-1324) and call the run coordinator. If you do not receive a response within 10 min, call cryogenics experts directly. Check the slow control for recent alarms (see instructions).
      • Monitor the 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 promptly update the Run Information Document (a Google Doc) with noise/pulser run information as the runs are taken during shift: [[https://docs.google.com/spreadsheets/d/1aVGAZrCYizhmduY4pqx5k29pVjyPRO7ydBJj95i0XfA/edit#gid=0]] 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 the commissioning process as it will be very helpful in helping us diagnose noise-related concerns. Please update this document during your shift and copy your updates into an elog 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 elog entry. Any operations-related items of interest must be noted in the elog, 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 elog entry using the Start of Detector Access form, and fill out the End of Detector Access form when the work is complete.
  • For ganglia, use user uboone and then the common DAQ password.

Run Control

Slow control

  • 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!)
  • SLC - Guide: What should I look at? How should it look like?

Online Monitoring

Data Management and PUBS

Laser System

Light Collection/PMT System

Beam Monitoring

Raspberry Pi Webcam

Cathode High Voltage

Readout Electronics

Time Projection Chamber (TPC)

  • TPC-Overview: This is a shifter guide to what are the relevant systems associated with the TPC
  • TPC-Guide: Here is a step-by-step guide to monitoring things related to the operation of the TPC
  • TPC-Troubleshooting: Quick guide to previously experienced problems with the TPC (When in doubt call the TPC expert)

Purity Monitors

MiniBooNE

Example System

  • Example - Overview: This is basically what should the shifter be looking at (not necessarily touching), try to be explicit about what give what information about what to the shifter.
  • Example - Guide: How should the shifter navigate through the different screens to retrieve the necessary information
  • 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.

Expert call list

Useful Links

Expert actions

  • k5login Adding shifters to the .k5login