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
GDS Distributions
We hope to be able to distribute DMT code using one or more package
installation systems (e.g. rpm, apt, etc.). Until these are available I
have tarred the directories that gds and root are installed in. These
can only be expected to work on the same system as they were compiled
on. It is hoped that this will be useful, but no guarantess can be made.
The installation directory names have been stored in several places in
the installation (some compiled in) so regardless of where you install
these you will have to link the installations to the nominal target
directory. For example you can install the gds code anywhere you want,
e.g. a directory called '/home/gds_stuff
'
and link it to the target directory (e.g. '/opt'
)
like:
mkdir -p /home/gds_stuff
download the selected file to the new directory by clicking on the
desired version ID while pressing shift, and then completing the
download dialog for your web browser. Do the following to untar the
installation.
cd /home/gds_stuff
tar -xvzf <file-name>
ln -s . dmt/Linux_i686 # This allows
multi-platform support
ln -s . CERN/Linux_i686
su
ln -s /home/gds_stuff/CERN /opt/CERN
ln -s /home/gds_stuff/dmt /opt/dmt
^D
Multiple version of the DMT should be able to coexist in a single
installation directory. By convention, the current default version
should be symlinked to "pro" as follows:
cd /opt/dmt/.
ln -s rev_2.8 pro
See "Setting the User Environment" below for instructions on how to
start using the DMT.
Building the software from CVS
To install the GDS software at you home institution you must down-load
the source files from cvs or use the tar files provided below (linked
to
version names). The current versions are listed below with the CVS tag
in square braces:
GDS
version
|
CVS
Tag
|
Comments
|
gds-2.6.2
|
gds_2_6_2
|
Backup version [old]
|
gds-2.7.2
|
gds_2_7_2
|
S3 production version [pro]
|
gds-2.8.0
|
gds_2_8_now
|
Current development 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.
- Log into the cvs repository. This needs only to be done once as
follows:
- Get the readonly password from me
- setenv CVSROOT
:pserver:readonly@ldas-sw.ligo.caltech.edu:/ldcg_server/common/repository_gds
- cvs login
- supply the CVS password
- Get the sources into a local directory (replace <gdstag>
with one of the tags listed above.
- mkdir cvs
- cd cvs
- cvs get -r <gdstag> gds
- Configure the build
- Choose the architecture that best matches the platform you are
going to install the GDS software onto. The most commonly used
architectures are:
- linux - Linux with gcc compiler
- solaris - Sun Solaris using the sub
compiler
- solarisgcc - Sun solaris using the gcc
compiler
- Set GDSBUILD to specify one or more of
the following
options.
- debug - Generate debug symbol table
- framecpp - Compile packages that
require FrameCPP.
- test - Build miscellaneous test
programs.
- cd gds
- ./configure <architecture>
- Compile the external packages
- Compile the GDS software
- Install the compiled packages into a tree based at <target-dir>
- make prefix=<target-dir> install
Building the Documentation Tree
The DMT online documentation is built from the source distribution as
follows:
- Build the documentation:
- Copy the documentation to the an appropriate web directory:
mkdir ~/public_html/dmt
cp doc/* ~/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: June 28, 2004
Please send questions, comments or suggestions to: John Zweizig