Difference: RichDaq (1 vs. 13)

Revision 132007-10-29 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="RichOperations"

DAQ Infrastructure

Revision 122007-08-11 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="RichOperations"

DAQ Infrastructure

Line: 17 to 17
  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.
Changed:
<
<
Alternatively, basic 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.
>
>
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

Revision 112007-07-27 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="RichOperations"

DAQ Infrastructure

Line: 64 to 64
  Data are written to /var/tmp/rich/data/rich{timestamp}.mdf
Added:
>
>
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

Revision 102007-07-04 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="RichOperations"

DAQ Infrastructure

Deleted:
<
<

Login environment

Access to the computing infrastructure is via the gateways. Direct connection to online systems from outside the IP8 network is not permitted.

Users have personal logins. Request one from lhcb-online-admins@cernNOSPAMPLEASE.ch. The login is common across both linux (including CCPCs) and windows systems.

There is an area set aside for common Rich software at /group/rich/.

This area is organised as follows:

  • /group/rich/pvss/ RICH PVSS components.
  • /group/rich/sw/ Other software.
  • /group/rich/sw/cmtuser/ CMT managed software (user release area).

There is a group-wide login profile for the linux systems at /group/rich/profile. Please source this from your personal profile (it is not yet done by default).

We are currently experimenting with ACLs on the filesystem which provide better control over file access than standard UNIX permissions. Directories with ACLs contain a special ACL file (appears as an exclamation point in the file listing) and the directory access mode appears with a plus character appended. Bear this in mind if you are having difficulties with file permissions. To view or manipulate ACLs from Linux, use the commands getfacl and setfacl.

 

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/.
Line: 28 to 13
 Programs can be cross-compiled for the CCPCs on these machines. See the makefile in /group/rich/L1/src/ukl1cfg for examples.

TFC

Deleted:
<
<
ALERT!Due to lack of cooling and monitoring the TFC equipment (in D3) should only be powered when needed.
 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.

Line: 49 to 32
 The UKL1 network parameters can be found here.

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

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

Line: 79 to 62
  DIM_DNS_NODE must be set first. If it is not set it to hlte04.
Changed:
<
<
Data are written to /tmp/rich{timestamp}.mdf
>
>
Data are written to /var/tmp/rich/data/rich{timestamp}.mdf
  More details of the software environment can be found on the RICH online monitoring page.

Revision 92007-06-24 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="RichOperations"

DAQ Infrastructure

Login environment

Line: 74 to 74
 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:

Changed:
<
<
  • . $User_release_area/Online_v3r3/Online/OnlineTasks/v1r4/job/hltrx.sh
>
>
  • source /group/rich/scripts/hltrx.sh
  • diskwr & if you want to write data to disk
 
Changed:
<
<
DIM_DNS_NODE must be set first. If it is not set it to localhost.
>
>
DIM_DNS_NODE must be set first. If it is not set it to hlte04.

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

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

Revision 82007-06-18 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="RichOperations"

DAQ Infrastructure

Login environment

Line: 49 to 49
 The UKL1 network parameters can be found here.

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

Changed:
<
<
  • r2ukl101: 192.168.1.1
  • [r2ukl102]: 192.168.1.2
>
>
  • 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

Revision 72007-06-13 - unknown

Line: 1 to 1
 
META TOPICPARENT name="RichOperations"

DAQ Infrastructure

Login environment

Line: 66 to 66
 

HLT

We are using hlte0403 and hlte0404 for RICH commissioning. See here for the authoritative list.
Added:
>
>
'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

Revision 62007-06-12 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="RichOperations"

DAQ Infrastructure

Login environment

Line: 67 to 67
 We are using hlte0403 and hlte0404 for RICH commissioning. See here for the authoritative list.

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

Changed:
<
<
  • . /group/rich/sw/scripts/setup.sh
  • setenvOnline
  • . $User_release_area/Online_v3r1/Online/OnlineTasks/v1r3/cmt/setup.sh
>
>
  • . /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:

Changed:
<
<
  • . $User_release_area/Online_v3r1/Online/OnlineTasks/v1r3/job/hltrx.sh
>
>
  • . $User_release_area/Online_v3r3/Online/OnlineTasks/v1r4/job/hltrx.sh
  DIM_DNS_NODE must be set first. If it is not set it to localhost.

Revision 52007-06-11 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="RichOperations"

DAQ Infrastructure

Login environment

Line: 58 to 58
 
  • [r2ukl107]: 192.169.1.7
  • r2ukl108: 192.169.1.8
  • r2ukl109: 192.169.1.9
Changed:
<
<
  • r2ukl110: 192.169.1.10
>
>
  • [r2ukl110]: 192.169.1.10
 
  • r2ukl111: 192.169.1.11
  • r2ukl112: 192.169.1.12
Added:
>
>
Those in [] are not installed at IP8.
 

HLT

Changed:
<
<
We are using hlte0403 and hlte0404 for RICH commissioning.
>
>
We are using hlte0403 and hlte0404 for RICH commissioning. See here for the authoritative list.
  The environment to run the event builder suite can be set up as follows:
  • . /group/rich/sw/scripts/setup.sh

Revision 42007-06-11 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="RichOperations"

DAQ Infrastructure

Login environment

Line: 49 to 49
 The UKL1 network parameters can be found here.

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

Changed:
<
<
  • r2ukl103: 192.169.1.3
>
>
  • r2ukl101: 192.168.1.1
  • [r2ukl102]: 192.168.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
 

HLT

Changed:
<
<
We are using hlt00102 for RICH commissioning.
>
>
We are using hlte0403 and hlte0404 for RICH commissioning.
  The environment to run the event builder suite can be set up as follows:
  • . /group/rich/sw/scripts/setup.sh

Revision 32007-04-21 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="RichOperations"

DAQ Infrastructure

Login environment

Line: 8 to 8
  There is an area set aside for common Rich software at /group/rich/.
Changed:
<
<
RICH PVSS components are under /group/rich/pvss/.
>
>
This area is organised as follows:
  • /group/rich/pvss/ RICH PVSS components.
  • /group/rich/sw/ Other software.
  • /group/rich/sw/cmtuser/ CMT managed software (user release area).
 
Changed:
<
<
There is a group-wide login profile for the linux systems at /group/rich/profile. Please source this from your personal profile (it is not done by default).
>
>
There is a group-wide login profile for the linux systems at /group/rich/profile. Please source this from your personal profile (it is not yet done by default).

We are currently experimenting with ACLs on the filesystem which provide better control over file access than standard UNIX permissions. Directories with ACLs contain a special ACL file (appears as an exclamation point in the file listing) and the directory access mode appears with a plus character appended. Bear this in mind if you are having difficulties with file permissions. To view or manipulate ACLs from Linux, use the commands getfacl and setfacl.

 

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/.
Added:
>
>
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

Changed:
<
<
The UKL1 CCPC servers for RICH1 and RICH2 are r1daq01 and r2daq01 respectively. The CCPCs themselves are called r1ukl1nn and r2ukl1nn.
>
>
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

ALERT!Due to lack of cooling and monitoring the TFC equipment (in D3) should only be powered when needed.
Changed:
<
<

The ODIN crate, TFC switch crate and transmitter crate are required for clock and trigger distribution to the L0 and L1 electronics.
Until the TFC controls project is available, basic control of the ODIN can be done by logging in to tfcodin09 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:
>
>
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.

Alternatively, basic 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
Line: 34 to 46
 after starting the run.
A complete description of the ODIN registers is available via the TFC web pages.

Readout network

Changed:
<
<
The UKL1 network parameters are:
  • Destination IP address: 192.168.188.1 (but temporarily using 192.168.60.1)
  • Destination MAC address: 00:01:e8:22:4b:bb (aggregation switch)
  • Source IP addresses: 192.169.1.1-192.169.1.254
  • Source MAC address: Not yet allocated.
>
>
The UKL1 network parameters can be found here.
  The UKL1s are assigned the following source IP addresses from the range indicated above:
Changed:
<
<
  • r2ukl101: 192.169.1.128 (old prototype)
>
>
  • r2ukl103: 192.169.1.3
 

HLT

Added:
>
>
We are using hlt00102 for RICH commissioning.

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

  • . /group/rich/sw/scripts/setup.sh
  • setenvOnline
  • . $User_release_area/Online_v3r1/Online/OnlineTasks/v1r3/cmt/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:

  • . $User_release_area/Online_v3r1/Online/OnlineTasks/v1r3/job/hltrx.sh

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

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

  -- Steve Wotton - 04 Apr 2007 \ No newline at end of file

Revision 22007-04-04 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="RichOperations"

DAQ Infrastructure

Login environment

Access to the computing infrastructure is via the gateways. Direct connection to online systems from outside the IP8 network is not permitted.
Changed:
<
<
Users have personal logins. Request one from lhcb-online-admins@cernNOSPAMPLEASE.ch. The login is common across both linux and windows systems.
>
>
Users have personal logins. Request one from lhcb-online-admins@cernNOSPAMPLEASE.ch. The login is common across both linux (including CCPCs) and windows systems.
 
Changed:
<
<
There is an area set aside for common Rich software at /group/rich/.
>
>
There is an area set aside for common Rich software at /group/rich/.
 
Changed:
<
<
RICH PVSS components are under /group/rich/pvss/.
>
>
RICH PVSS components are under /group/rich/pvss/.
 
Changed:
<
<
There is a group-wide login profile for the linux systems at /group/rich/profile. Please source this from your personal profile (it is not done by default).
>
>
There is a group-wide login profile for the linux systems at /group/rich/profile. Please source this from your personal profile (it is not done by default).
 

PVSS

Changed:
<
<
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/.
>
>
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/.

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

ALERT!Due to lack of cooling and monitoring the TFC equipment (in D3) should only be powered when needed.

Revision 12007-04-04 - StephenWotton

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="RichOperations"

DAQ Infrastructure

Login environment

Access to the computing infrastructure is via the gateways. Direct connection to online systems from outside the IP8 network is not permitted.

Users have personal logins. Request one from lhcb-online-admins@cernNOSPAMPLEASE.ch. The login is common across both linux and windows systems.

There is an area set aside for common Rich software at /group/rich/.

RICH PVSS components are under /group/rich/pvss/.

There is a group-wide login profile for the linux systems at /group/rich/profile. Please source this from your personal profile (it is not done by default).

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

TFC

ALERT!Due to lack of cooling and monitoring the TFC equipment (in D3) should only be powered when needed.
The ODIN crate, TFC switch crate and transmitter crate are required for clock and trigger distribution to the L0 and L1 electronics.
Until the TFC controls project is available, basic control of the ODIN can be done by logging in to tfcodin09 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 are:
  • Destination IP address: 192.168.188.1 (but temporarily using 192.168.60.1)
  • Destination MAC address: 00:01:e8:22:4b:bb (aggregation switch)
  • Source IP addresses: 192.169.1.1-192.169.1.254
  • Source MAC address: Not yet allocated.

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

  • r2ukl101: 192.169.1.128 (old prototype)

HLT

-- Steve Wotton - 04 Apr 2007

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