Download DMT Release

Before You Start

The DMT libraries are available to the entire GW community. The primary purpose for the DMT libraries are to provide a toolkit for developing LIGO data monitors. The toolkit will evolve as necessary to support this activity. Although I will try to maintain backwards compatibility, this may not be possible. Please read the release notes and change file when loading new versions.

Rauha Rahkola has documented the step-by-step procedures used to install v2.0.0 of the DMT software on a Solaris workstation (Solaris Installation updated 04/04/02) and I have added some notes on installing v2.8.1 on a RedHat Linux 9 platform (Linux Installation updated 05/17/04). If anyone is willing to do the same for other versions and platforms, I will link them here also.

Suggestions and inquiries are welcome and may be sent to me at zweizig_j'at'ligo.caltech.edu.

Required Software

The packages listed below are necessary for the proper installation of the DMT software.

Software development tools

C++ compiler and standard library (gcc-2.95.3 or later - preferably after gcc-3.2 - or Solaris CC 6.0)
Binary utilities (e.g. gnu binutils-2.11.2 or later)
gzip - File compression/decompression utility (gzip-1.2.4 or later).
autoconf - automatic source configuration (autoconf-2.57 or later).
automake - Automatic make file generation (automake-1.6.3 or later).
libtool - shared library development and maintenance (libtool-1.4.3 or later)
m4 - macro processor (m4-1.4 or later).
make - Gnu make (make-3.79.1 or later)
perl - Perl language interpreter (perl-5.005_03 or later)
doc++ - C++ documentation generator (only needed to build documentation)
latex - Document preparation system (only needed to build documentation)

Public Domain Libraries

zlib - gzip compression library (zlib-1.1.4 or later)

libbz2 - bzip compression library (bzip2-1.0.2). Note: bzlib.h can be found in bzip2-devel if it isn't included on your linux system.

Other software

root - Object-oriented data analysis system (version 3.05-06 or later)

ligotools - Ligo toolbox

Installing GDS from the DASWG Repository

To install the GDS software at you home institution you may install a native binary package from the Daswg repository package for the supported systems (currently SL6 and debian squeeze).

Building the software from SVN

For other operating systems you will probably have to compile the gds package from the sources. The source files are available as tar files (linked to the version names in the table below) or from svn. The current versions are listed below with the SVN tag in square braces:

GDS version	CVS Tag	Comments
gds-2.15.7	gds_2_15_7	Backup version [old]
gds-2.16.3	gds_2_16_3	ER2 production version [pro]
gds-2.16.5	gds_2_16_5	Current testing version. [new]

The procedure for installing any of the above versions is:

Verify that all the packages named in the "Required Software" list are installed.
Download the gds package from svn repository as follows:

svn co https://redoubt.ligo-wa.caltech.edu/svn/gds/tags/<gdstag> gds

Configure the build

cd gds
./configure --prefix=<target> --enable-online --enable-dtt --enable python

Compile the GDS software

make

Install the compiled packages into a tree based at <target-dir>

make install

Building the Documentation Tree

The DMT online documentation is built from the source distribution as follows:

Build the documentation:

cd doc
doxygen

Copy the documentation to the an appropriate web directory:

mkdir ~/public_html/dmt
cp html/* ~/public_html/dmt/

Installation Scripts

I have written two scripts to build ROOT and GDS/DMT, respectively on the standard DMT platforms. These scripts seem to work, but have not been extensively tested. In each case you must replace the target directory names that are defined at the top of the scripts. The scripts download the full source from cvs into "<target>/cvs/" and
then compile and install the results into "<target>/<revision>/". Once the installation is completed, you can leave the cvs directory or delete it as you see fit.

Setting the User Environment

To use your new GDS installation you should set up a few environment variables. If you use tcsh, type:

setenv DMTHOME
<target-dir>

setenv DMTVERSION pro

source $DMTHOME/$DMTVERSION/bin/setup



root-setup

If you use bash, type:

export
DMTHOME=<target-dir>

export DMTVERSION=pro

source $DMTHOME/$DMTVERSION/bin/setupb



root-setupb

root-setup[b] should print out where everything is installed. You can then run any of the pre-compiled monitors on local frame files, use DMT classes in root, develop new DMT monitors, etc.

Last Update: Sep 6, 2012
Please send questions, comments or suggestions to: John Zweizig