Wiki » History » Version 155

« Previous - Version 155/332 (diff) - Next » - Current version
Jason St. John, 04/16/2015 04:18 PM

MCenter Control Room (MC-CR) x3726 or x8871
  • Call the Main Control Room (x3721) at the start and at the end of shift. This is required, and pleasant.
  • If the beam goes away for more than a few spills, look for Accelerator Alarms in ACNET (a default window). If the problem persists a few minutes, and you see nothing about it in the MCR elog, (or you just really want to find out more), call the MCR. They're friendly, though they may be super-busy.

Shifter Stuff

Link summary

Important knowledge

Obsolete links


Any time day or night, please call experts if you are in need of help and the answer is not provided below.

Getting started

  • If you cannot ssh to FTBFLX machines: Get a kerberos ticket for yourself: kinit <yourKerberosPrincipal>, then ssh ftbf_user@ftbflx01 (or whichever machine...).
  • If your Kerberos username and password are good, but you can't log on to FTBFLX[NN] machines: Have someone who CAN log into those machines heck that your kerberos principal appears in ~ftbf_user/.k5login in the LArIAT section.

Trigger and DAQ system

  • If the trigger crate has been power cycled and the V1495 is not emitting triggers: Reset1495

Wire Chambers

  • If the wire chambers are acting strangely: mini-DAQ and telnet interface including remote power cycling instructions.
  • If the wire chamber system is skipping spill numbers, it may be a high trigger rate (> 30 k per spill). The wire chamber controller may still be reading out the hits from the last spill.

Hardware Connections and Configurations

Electronic Hardware Documentation

Diagnostic and Control Software

Test programs in the lariat-online/daq/src directory

Examining the WC mini DAQ ASCII data

The Processor makes TTrees from the ASCII files saved by
WC MiniDAQ Data Processor

Data Files from the year 2013

Data files for various beam conditions can be found in the DataFiles page.