Introduction

This package contains several utilities to startup the DAQ, archive run parameters to COOL, send command to the Run Control, etc.
In addition this package contains the run control plugin for the web based monitoring (WMI).

General changes

Utilities

setup_daq <-h>: script to launch the DAQ. Note that the <-i> option is not supported anymore.

rc_print_partition_env <-h>: extracts the main partition environment from a database. It also constructs the environment necessary to launch the RootController. From within a bash script the function get_partition_env ${TDAQ_PARTITION} can be used after having sourced the file ${TDAQ_INST_PATH}/share/bin/setup_functions: this function requires ${TDAQ_DB_DATA} to be set.
rc_commander: simple graphical tool to send commands to a Controller.
rc_sendcommand <-h>: sends commands to a Controller.
rc_isread <-h>: reads the RC state of a controller from IS.
rc_waitstate <-h>: waits for a controller to reach a particular RC state.
rc_timetest <-h>: sends a series of commands to a Controller and measures the duration of each transition.
rc_decode_detectormask <-h> : decodes a numerical detector mask into human readable TTC pastition names.
rc_print_root <-h>: prints the name of the root controller and the top segment.
rc_print_tree <-h>: prints the tree of controllers for a partition.
rc_getrunnumber <-h>: gets the current run number for a partition from IS.
 rc_checkapps <-h>: dumps a tabular view of the applications in a partition with their basic properties.
rc_print_partition_env <-h>: extracts form the database the basic environment for the partition.
rc_is2cool_archive <-h>: inserts basic run information into COOL.

Changes in API

No APIs.

Plugins – wmiccplugin

Run status web page appearance has changed under a few aspects:
- color schema that is used is about the same with the one used by the other plugins: dark blue header background, light blue label cells background, white information cells background, critical information cells – white fonts on red background
- page is organized on blocks separated by titles:
Run Status block – available for all partitions
Busy Information block –available for the partitions that publish this information
  Trigger Information block – available for the partitions that publish this information in IS
Message from white board commission – available when the file /det/tdaq/RunComWhiteBoard/last_white_board_message.txt exists
Data Quality Monitoring Frame block – available for ATLAS partition only
Trigger rates block – available when the rates are available in the is
  Trigger Information block – available for the partitions that publish this information in IS
Useful Links block – links to data quality page (except for ATLAS partition), logs archives and oks archives

Note: the data quality base name (without the name of the partition) can be set in the configuration file using the parameter “DQPage”.
Ex.: <parameters name=”DQPage” value=”http://pcatdwww.cern.ch/atlas-point1/wmi/tdq201/Data%20Quality%20Monitoring_wmi/”/>

Known bugs, problems and limitations

None.