DAQ Infrastructure

PVSS

RICH PVSS packages should be stored at /group/rich/pvss/. For performance reasons the projects themselves should be installed onto the machine where they will run. For example the UKL1 project would be installed on r2daq01:/localdisk/pvss/.

Two projects are installed on the RICH console. The project "ECS" is intended to evolve into a centrally managed project that is the same on all consoles in the control room so customisation is discouraged (any changes might be lost if the project is updated centrally). A second project "RICH" has been installed which can be customised for RICH operations, for example, to add things that have not yet migrated to the centrally managed project.

CCPC

The UKL1 CCPC servers for RICH1 and RICH2 are r1daq01 and r2daq01 respectively. The CCPCs themselves are called r1ukl1nn and r2ukl1nn.

Programs can be cross-compiled for the CCPCs on these machines. See the makefile in /group/rich/L1/src/ukl1cfg for examples.

TFC

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.

Readout network

The UKL1 network parameters can be found here.

The UKL1s are assigned the following source IP addresses from the range indicated above:

r2ukl101	192.169.1.1
[r2ukl102]	192.169.1.2
[r2ukl103]	192.169.1.3
r2ukl104	192.169.1.4
r2ukl105	192.169.1.5
r2ukl106	192.169.1.6
[r2ukl107]	192.169.1.7
r2ukl108	192.169.1.8
r2ukl109	192.169.1.9
[r2ukl110]	192.169.1.10
r2ukl111	192.169.1.11
r2ukl112	192.169.1.12

Those in [] are not installed at IP8.

HLT

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/Online_v3r3_Setup.sh

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/hltrx.sh
• diskwr & if you want to write data to disk

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

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

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.

More details of the software environment can be found on the RICH online monitoring page.

-- Steve Wotton - 04 Apr 2007