General info

This is a general DAQ/HLT-I release which is intended to be used for the ATLAS detector commissioning starting from M6 runs in March 2008.

Since tdaq-01-08-03 the externals were slightly changed, in order to get latest patches for LCG packages: it is compatible with LCG53f s/w and coming offline-13.0.36/13.1.x release branch.

The release is compatible with previous 1.8.x releases: the public API is not changed, users need to recompile the code agains the new release without changes. Most of the changes are bug-fixes and all new features are internal to TDAQ, it is assumed that migration to the new release is transparent for end users.
The same is true for tdaq-common and dqm-common releases.

Supported platforms and compilers

NB: the only supported platform is SLC4. SLC3 support is dropped, since this platform is no longer maintained in CERN.

System and compiler
 CMTCONFIG
Compatibility list
Linux 2.6.9 (SLC4), gcc-3.4.x i686-slc4-gcc34-opt
SLC4.x, RHEL4
Linux 2.6.9 (SLC4), gcc-3.4.x i686-slc4-gcc34-dbg - ~ -

External s/w and run-time environment tuning.

 external package & version
 tdaq-common-01-08-00 (new eformat)
 dqm-common-00-03-02
 LCG 53f (POOL 2.6.2, COOL 2.2.2, CORAL 1.9.2, ROOT 5.14.00i and their dependencies)
 Java Runtime Environment 1.6.0

Release distribution

This release is distributed in RPM format, along with all required dependencies.

Development environment

Versions and paths of used external s/w are defined in TDAQExternal package.

Tools needed for development:

The default compiler is gcc-3.4 on SLC4, no need to install it additionally.
CMT v1r20p20070720 (installed with RPM in <inst_root>/CMT/v1r20p20070720)
JDK 1.6.0 (installed with RPM in <inst_root>/sw/lcg/external/Java/JDK/1.6.0)

Important changes (valid since tdaq-01-08-01):

* CMTPATH is no longer needed. Instead, CMTPROJECTPATH should contain path to the tdaq, tdaq-common, dqm-common and LCG 'CMT projects'. On afs, the value is
/afs/cern.ch/atlas/offline/external:/afs/cern.ch/atlas/project/tdaq/cmt
* When release is installed locally with RPMs, all projects are put in one location and CMTPROJECTPATH needs to be set to the installation root directory.

* The user's working area shall be also organized as 'CMT project'. This is done be creating cmt/project.cmt directory/file in the working area, with content like 'use tdaq tdaq-01-08-03'. After that, CMTPATH and all environment will be set according to the used chain of projects. See TDAQ CMT development guide for more details.

When changing your development area from release to release, do not forget to update cmt/project.cmt file! It is essential

CMT projects are explained in more details in CMT manual.

Changes overview

There are no changes which directly affect end users. However user's code must be recomiled.