Wiki » History » Version 203

« Previous - Version 203/332 (diff) - Next » - Current version
Will Foreman, 02/18/2016 12:00 PM

Run II Preparations <<-- click there.

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 ( 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@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

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.

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.
  • 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: 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.

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

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.