Wiki » History » Version 242

« Previous - Version 242/332 (diff) - Next » - Current version
Jason St. John, 04/07/2016 05:30 PM

ROC West x5413
MCenter Control Room (MC-CR) x3726 or x8871
Internationally: prefix +1 630 840 to the above

  • 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 ( quick start )

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.

Trouble getting started

  • If you cannot ssh to FTBFLX machines: Get a kerberos ticket for yourself: kinit <yourKerberosPrincipal>, then ssh ftbf_user@ftbflx18 (or ssh ftbf_user@ftbflx15 or ssh ftbf_user@ftbf-cr-03).
  • 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 check that your kerberos principal appears in ~ftbf_user/.k5login in the LArIAT section (email the Run Co-ordinator at ).
  • The same ssh errors may also apply to computers at ROC West. Troubleshoot using the above methods.

Trigger and DAQ system

When the DAQ crashes, please post the relevant information to DAQerrors for experts to study.

Common failures:

  • DAQ fails with ERROR: ReadRegisgter ACQUISITION_STATUS CAEN_DGTZ_CommError BoardId 0 wait 2 minutes, then try to start again.
    • Try issuing the command lariatReset 0 1 waiting more then 5 seconds, and trying again.
      This command is appropriate when one sees any type of "CAEN_DGTZ" error. This command will NOT help the persistent ports error.
  • DAQ fails with Found persistent communication port still open
    • Wait 8 minutes for the ports to clear, then try again.
  • DAQ fails with "An exception occurred when trying to send a message to ..."
    • Check that the terminal you are running the DAQ from is indeed lariat-daq00 (or a screen within it). Output from klist should show the default principal as "" or similar if running from a screen off lariat-daq00 from the ROC-West station.
    • Run number failed increment or has reset to a low number such as 1: Stop the run and then on the DAQ terminal edit /opt/lariat-online/config/runNumber.dat to correct the run number. Start new run after.

Other failures:

  • If the DAQ is having trouble talking to the crates, try issuing the command lariatReset 0 1 waiting more then 5 seconds, and trying again.
    This command is appropriate when one sees any type of "CAEN_DGTZ" error. This command will NOT help the persistent ports error.
  • No triggers at all If the trigger crate has been power cycled and the V1495 is not emitting triggers: Reset1495
  • Run Status page not updating
    • Try refreshing the page.
    • If the ACNET node has gone down (as in a power loss) may need to re-start the tomcat servlet: ssh, then kitty. (Yep, "kitty.")

Wire Chambers

Nominal Voltages:
WC1 -2425
WC2 -2400
WC3 -2425
WC4 -2450
  • If the wire chambers HV trips: instructions for controls via Synoptic
  • If the wire chambers are acting strangely: remote power cycling instructions including mini-DAQ and telnet interface.
  • 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.

High voltage for the wire chambers, TPC wireplane bias, cryo PMTs

Important! Follow instructions in link below if cathode HV trips off due to LAr level interlock.
Drift HV TPC Cathode Voltage

Instructions for controls via Synoptic

Also valid for some of the muon range stack paddles (1-8), the halo veto and 1 aerogel PMT.

ONLY IF SYNOPTIC DOESN'T WORK Instructions for controls via ACNET

  • The readback voltage doesn't make any sense, is of the wrong polarity and/or is way above the nominal value, but just for a fraction of time.
    This is most likely just a glitch in the readout, please ignore if it happens once or twice. If it happens too frequently, set voltage to 0, turn off the power supply and report it.
  • The readback voltage doesn't make any sense, is of the wrong polarity and is way above the nominal value, and the value is stable~ish (you might see small fluctuations over time)
    This is a typical symptom of a bad power supply. Try to set it back to 0, turn it off and disconnect the SHV cable. If the readout values remain the same, it confirms there is a hardware problem. Please contact Brian Fellenz for repairs if we don't have a spare for that unit.

FYI, the power supplies have a given voltage rating and cannot physically deliver voltages beyond that range. Also, their polarities cannot be swapped so if you see the wrong sign on the readout ie a positive voltage on a negative power supply or vice versa, then you can be sure the unit is broken or you have a problem somewhere else in the system.
- Bias voltage rating: - 500 V for the shield and induction planes, + 500 V for the collection plane.
- ELT and Hamamatsu PMTs: +2000 V
- All of the other units: -2000 V

  • Something went wrong during a ramp, I need to turn off the supply!
    There is an interlock that prevents you from using the normal fast controls on the power supply when a ramp is on-going. First, stop the ramp by clicking on the STOP button. This will stop the ramp and clear the interlock. If you need to go back to 0 quickly, use the fast controls to set the voltage to 0 and don't forget to turn off the supply!

Even if the controls appear not to respond, set the voltage to 0 and turn the supply off. Contact Charlie Briegel first and describe the problem in detail. If you can and if it's safe, disconnect the SHV cable from the power supply. If the readback values remain the same, then the power supply is broken.

Event Viewer

  • If the event viewer stops cycling through the events and the terminal from which it is running shows a list of lines saying something like "event XX in file, but on event 0" with XX any number,
    • ctrl+z
    • ps -def to look at the processes list. Look for the job ID of the process "python /lariat/app/users/EventViewer/..."
    • kill -9 JobID to kill the event viewer
    • open a new event viewer
  • If the problem persists and/or become more frequent, exit the session you are in and try to connect from a different gpvm machine

Power Cycle the ASICs (TPC Wire Noise)

  • Anecdotal evidence has shown that analog noise on the TPC wire readout channels can be
    alleviated by power cycling the TPC electronics: ASICs and Warm Receiver/Drivers
  • You can remotely power cycle the TPC electronics. Log onto with X-forwarding enabled, type "firefox", and go to Usename "ftbf" (password posted on whiteboard in MC7). Choose the CYCLE option, which will automatically give a 60
    second powerless interlude.
  • Further important informations can be found on the white board in MC-CR.
  • This mechanism is controlled by a smart power distribution unit (PDU) located under the
    TPC electronics power supply near the cryostat in the enclosure. Due to electrical safety
    rules you must NOT use any of the other outlets on this PDU. Do NOT remove the protective
    outlet covers at any time.

Recover from a LAr level interlock

Assuming the LAr Level dropped low enough to trip off the TPC Cathode power supply, and maybe you even powered down the PMTs.

  1. Be sure HV is set to zero for these: Cathode Drift, Wire Bias, cryo-PMTs
    How to control the Drift HV
  2. Power down the ASICs. (They should be off when TPC voltages change.)
  3. Bring up the Cathode
  4. Bring up the Wire Bias
  5. Bring up the ASICs
  6. Bring up the PMTs

Synoptic troubleshooting

Synoptic Troubleshooting

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.