Project

General

Profile

History

Operations Configuration Wiki

{{last_modified}}

Overview

Some configuration items are needed outside of the SRT (SoftRelTools) system, prior to any setup of software releases. These are handled through a plain text configuration file with simple key-value pairs. This system is used by the novadaq_setup.sh script.

Requirements

  • The simplicity of the system imposes constraints on the names of keys. Since the tools that currently exist to extract values associated with keys use simple grep commands, no key should be a substring of another.
  • All keys and values should be single strings.

Keys

Currently implemented keys are
  • DEFAULT_BASE_RELEASE - the base release to use
  • DEFAULT_TEST_RELEASE_PATH - the full path to the test release to use.
  • PEDESTAL_OUTPUT_DIR - tells various utilities where to find Pedestal Scan results.
  • MASTER_TDU_HOST - the name of the master TDU to use. (This key is an inappropriate use of this facility - the TDU should be associated in the database with the timing input chain on the DCMs (0 or 1).)

Implementation

Configuration file

The configuration file name is daq-operations.cfg. An example is

DEFAULT_BASE_RELEASE FD02_02_00
DEFAULT_TEST_RELEASE_PATH /home/novadaq/testRelForOperations_FD02_02_02
PEDESTAL_OUTPUT_DIR /data-a
MASTER_TDU_HOST TDU-Master-ARM-02

Directory structure

The default configuration file is
/nova/config/<detector environment name>/daq-operations.cfg.

Specific partitions may override the defaults with a configuration file
/nova/config/<detector environment name>/Partition<partition number>/daq-operations.cfg.
Only key-value pairs that differ from the default need to be included in the partition-dependent configuration file.

Utilities

DAQOperationsTools/setup/grepInPath.sh <key> searches the directory hierarchy described above, first at Partition level and then the default, and returns the value found associated with the first occurrence of <key> in a daq-operations.cfg file.