TWiki> LHCb/RichOperations Web>RichReadout (revision 4)EditAttachPDF

The RICH readout system

Run control

Standard PVSS recipes

System Recipe Notes
TFC R2_2HLT Send MEPs to two farm nodes
TFC RICH2V3 Send MEPs to one farm node

Online monitoring

To start the presenter:

  • Check that an X-server (eXceed) is running where you want to see the display (e.g. lb016w)
  • Log in to the processor running the event builder (presently hlte0403).
  • export DISPLAY=lb016w:0
  • source /group/rich/sw/scripts/
  • HPDMonitor

For more details see here.

Data recording

ALERT! Please ensure that a unique run number is assigned to any data that is written to disk. The run number is set using the ODIN panel.

Data are written to /var/tmp/rich/data/rich{timestamp}.mdf

After completing a run, the script /group/rich/scripts/mdf-archive should be run in the directory where the data was written. The script magically creates subdirectories keyed by the run number and moves the MDF files there.

For permanent storage, data can be written to /data/rich. Files copied here are automatically copied to CASTOR as described here. Please try to organise your files in subdirectories. Data with a unique run number should be put in /data/rich/run/ after packaging with tar and compressing with gzip as required.

Special operating conditions for data-taking in ALICE mode:

  • MEP packing factor (UKL1 control and ODIN control) must be set to 1
  • L0 gap generator gap length (ODIN control) must be set to its maximum value (presently 15, for normal data taking the gap length should be 1).

Note that in ALICE mode, the throttle will be briefly asserted on every event. This is normal.


The ODIN crate, TFC switch crate and transmitter crate are required for clock and trigger distribution to the L0 and L1 electronics.

The ODIN partition 4 has been assigned to the RICH for the time being. The ODIN PVSS controls are available from the PVSS "ECS" project on the control room consoles.

The normal TFC recipe for running at IP8 is R2_2HLT. In this configuration, the ODIN MEP destination table contains both hlte0403 and hlte0404. To run with one destination only (hlte0403) you can use the recipe RICH2V3.

Basic, command-line control of the ODIN can be done by logging in to tfcodin04 and using the program /home/richard/bin/ctrl to read and write the ODIN registers.

For example, to set up periodic or single shot triggers:

  • ctrl -w1000 2020 # Set periodicity to 0x1000
  • ctrl -w1000 2024 # Set number of triggers to 0x1 and offset to 0x000
  • ctrl -w20 2004 # Enable periodic trigger generation
  • ctrl -w0 1000 # Start run
Alternatively do not enable periodic generation but do:
  • ctrl -w1 200c # Single shot trigger
after starting the run.
A complete description of the ODIN registers is available via the TFC web pages.


We are using hlte0403 and hlte0404 for RICH commissioning. See here for the authoritative list.

'putty' configuration instructions for log in to event builder can be found here

The environment to run the event builder suite can be set up as follows:

  • . /group/rich/sw/scripts/

Some of this environment setup will be migrated into the common or group login scripts or other convenience scripts later.

To start the event builder:

  • source /group/rich/scripts/
  • diskwr & if you want to write data to disk

DIM_DNS_NODE must be set first. If it is not set it to hlte04.

Running your own rich algorithms on mdf data offline on LXPLUS

for info click here

-- StephenWotton - 22 Nov 2007

Edit | Attach | Watch | Print version | History: r8 | r6 < r5 < r4 < r3 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r4 - 2007-11-26 - StephenWotton
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCb/RichOperations All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback