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).
- Make sure your Fermilab training is up to date and that you have LArTF Hazard Awareness training.
- 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.
REFRESH ALL OPEN BROWSERS (instruction might have been updated) and SIGN INTO ELog WITH YOUR ACCOUNT¶
- Log on to the uboonedaq google account with 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.
- At the beginning of shift, fill out the "Beginning of Shift" form on the Elog, and enter it under topic "Shift/Beginning of shift".
- Open "Run Plan" page to see what the Run Coordinators plan for the day is!
- During shift:
- Day/Evening/Owl shifts:
- Take a 30-minute data run every 2 hours (see Running the Console DAQ). In the event that the run terminates unexpected, if the run lasts for longer than 20 minutes it does not need to be retaken.
- At the beginning of the run, copy the "DAQ RUN START MESSAGE" from the console DAQ screen output into an Elog entry under topic "Shift".
- 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".
- 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 cooldown temperature. There is a saved plot "cooldown-temp.plt". If you see unusual warm-up and no corresponding e-log entry from the cryogenics team that they are working on the issue within an hour of the problem occuring, call the run coordinator (or call cryogenics experts directly if no answer). Similarly, monitor the liquid nitrogen flow in the plot "PressureValveTag.plt". If the flow drops to 0 and there is not corresponding e-log entry from the cryogenics team that they are working on the issue within an hour of the problem occuring, call the run coordinator (or call cryogenics experts directly if no answer). There is also a slow control alarm (for variable FVC805) ff this happens. Check the slow control for recent alarms (see instructions).
- Day shifts only:
- Visit LArTF once per shift, fill out the "LArTF checklist" form on the Elog, and enter it under topic "Shift/LArTF checklist"
- Day/Evening/Owl shifts:
On the mac, the user is ubooneshift, and the password is the same as the MicroBooNE DocDB password.
On the Linux boxes, the user is ubooneshift, the password is your Kerberos password, and then the principal is your Kerberos user name. You must be added to the .k5login file. Contact us to help
On the Linux boxes, the user is uboonedaq, the password is your Kerberos password, and then the principal is your Kerberos user name. You must be added to the .k5login file. Contact us to help
For ganglia, use user uboone and then the common DAQ password.
- RC - Overview: How your run control screen should look like
- RC - Guide: How to start and stop a run
- RC - Troubleshooting: What should I do if... ?
- RC - Experts Only: Expert Documentation
- SLC - Overview: An Introduction to the slow control screen
- SLC - Guide: What should I look at? How should it look like?
- SLC - Troubleshooting: What should I do if... ?
- SLC - Experts Only: Expert Documentation
- OM - Overview: An Introduction to the online monitoring screen
- OM - Guide: Access and technical information.
- OM - Troubleshooting: What should I do if... ?
- OM - Experts Only: Expert Documentation
Light Collection/PMT 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 - Troubleshooting: What issues will the shifter experience and how do they fix them
- 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.
- Shift calender : Look who is on shift or sign up for shifts