TWiki> LinearCollider Web>WebHome (revision 17)EditAttach

Linear Collider activities in Glasgow



Installation of ILC software at Glasgow

Getting the latest version

Two choices for downloading the software is through svn or via a tarball. For the first attempt I opted for the latter. To do this I

went to:

and downloaded the tar file accessible here:

into the afs area


I then untarred the file:

tar xvfz ilctools-tags.tar.gz

I then went into the directory:


and removed all other tags except for the latest v01-14.

(Using svn to check out this tag would have been a more sensible way - will do next time!)

Preparing for build - separate packages to install

First we must prepare four packages that don't come automatically with the ilcsoft installation.

They are MySQL, Java, xerces-c and cernlib. MySQL was installed by sysadmin (Andy) as root

privileges are necessary. Java is already installed on our network. So it was necessary to install

xerces-c and Cernlib. I installed them in the:


directory. For xerces-c I did the following:

mkdir xerces-c

And in this directory I:


for 64 bit. And untarred.

For Cernlib I realised that the installation here ( /usr/lib64/cernlib) did not have the inlcude directories needed so I also went to /afs/

and downloaded:


and untarred them.

Preparing release version file

First of all I created a directory where the ilcsoft software packages will actually be installed into. This is called /data/atlas01/ILC/ilcsoft

It is now necessary to point to the above installations (MySQL etc.) in the release file that comes with the ilcsoft installer. To do this I went to file:


But I first tell this file where the ilcsoft install directory is by setting:

ilcsoft_install_prefix = "/afs/"

I then added:

MySQL_path = "/usr/"
Java_path = "/usr/java/latest/"
CERNLIB_path = "/afs/"

to this file

Starting a full build for all packages

The file at the centre of this build is called 'release-scratch.cfg' which can be found in the same directory as the /afs/

This file has the list and order in which all packages must be installed. First of all it is necessary to point to the file from within this file:

path_where_this_file_lives = "/afs/"

Then do:

./ilcsoft-install -p releases/v01-14/release-scratch.cfg -p (to check all is ok)
./ilcsoft-install -p releases/v01-14/release-scratch.cfg -I (to install)

Problems to expect and fix:

LCIO compilation problems

(1) Failed to find tools required to build lcio user manual - to fix this just turn off documentation installation. I did this for all pacakages by changing:

ilcsoft.envcmake["INSTALL_DOC"]="ON" to ilcsoft.envcmake["INSTALL_DOC"]="OFF"

in /data/atlas01/ILC/v01-14/releases/v01-14/release-scratch.cfg, but it could be done at just a package level here:


(2) We don't want Fortran examples - and they cause problems in compilation anyway - so I commented out:



# fortran examples
#OPTION( BUILD_F77_TESTJOBS "Set to ON to build LCIO F77 testjobs" OFF )
# ADD_SUBDIRECTORY( ./src/f77 f77 )

again in: /data/atlas01/ILC/ilcsoft/lcio/v02-01-02/CMakeLists.txt

(3) I also turned off the optional root dict build for LCIO


in /data/atlas01/ILC/v01-14/releases/v01-14/release-scratch.cfg.

Building Root Dict manually for certain packages

The Root Dict compilation does not work for some packages when building using the main compilation script so it is necessary to do the following:


Comment out of /data/atlas01/ILC/tags/v01-14/releases/v01-14/release-scratch.cfg

cd /data/atlas01/ILC/ilcsoft/KalTest/v01-05/build
# set up root (installed with ilcsoft)
source ../../../root/5.28.00f/bin/
cmake -DILCUTIL_DIR=../../../ilcutil/ -DROOT_DIR=$ROOTSYS ..
make install

When installed – can uncomment in release-scratch.cfg again.


Comment out of /data/atlas01/ILC/tags/v01-14/releases/v01-14/release-scratch.cfg

cd /data/atlas01/ILC/ilcsoft/KalDet/v01-09/build
source ../../../root/5.28.00f/bin/
cmake -DILCUTIL_DIR=../../../ilcutil/ -DROOT_DIR=$ROOTSYS ..
make install

When installed – can uncomment in release-scratch.cfg


Comment out of /data/atlas01/ILC/tags/v01-14/releases/v01-14/release-scratch.cfg

cd /data/atlas01/ILC/ilcsoft/LCFIPlus/v00-05/build
source ../../../root/5.28.00f/bin/
cmake -DILCUTIL_DIR=../../../ilcutil/ -DROOT_DIR=$ROOTSYS ..
make install

When installed – can uncomment in release-scratch.cfg but make sure not to reinstall.


Comment out of /data/atlas01/ILC/tags/v01-14/releases/v01-14/release-scratch.cfg

cd /data/atlas01/ILC/ilcsoft/bbq/v00-01-02/build
source ../../../root/5.28.00f/bin/
cmake -DILCUTIL_DIR=../../../ilcutil/ -DROOT_DIR=$ROOTSYS ..

When installed – can uncomment in release-scratch.cfg but make sure not to reinstall.

Installing a new tag for one package within ilcsoft suite

ALERT! STILL TO BE COMPLETED: Mokka needs to be reinstalled because of problem:

Running a validation test for Mokka and Marlin installations


Running a Marlin processor example in your home area

Preparing the home area

In this example we are building and running a Marlin processor called ExampleDSTAnalysis.

(1) Make the directory named as you wish - for example: /home/tdoherty/ILCWork/Marlin/ExampleDSTAnalysis

(2) In the ExampleDSTAnalysis directory create build, src, include and lib directories - like:

[tdoherty@ppepc144 ExampleDSTAnalysis]$ ls -lart
total 908
drwxr-xr-x 3 tdoherty grid 77 Aug 3 15:12 include
drwxr-xr-x 2 tdoherty grid 66 Aug 3 15:14 src
drwxr-xr-x 3 tdoherty grid 121 Aug 3 15:17 lib
drwxr-xr-x 5 tdoherty grid 4096 Aug 3 15:26 build

(3) Place the source ( code for your processor in the src directory and the header ( ExampleDSTAnalysis.h) file in the include/ directory

(4) Copy the CMakeLists.txt file from the mymarlin example given with Marlin into the ExampleDSTAnalysis folder:

cp /data/atlas01/ILC/ilcsoft/Marlin/v01-03/examples/mymarlin/CMakeLists.txt .

(5) Open up this file and just change the name of the project from mymarlin to ExampleDSTAnalysis: from PROJECT(mymarlin) to PROJECT(ExampleDSTAnalysis).

(6) If your processor code requires ROOT then add:



 IF( ${pkg}_FOUND )

to CMakeLists.txt so that your C++ code can pull in ROOT header files.

Building the processor

(1) First set up the ilcsoft software by running this script


(2) cd into the build directory of this processor in your home area

cd build

(3) Then:

cmake -C $ILCSOFT/ILCSoft.cmake ..

(4) And:

make install

This should create library: lib/

Loading the processor into Marlin

(1) Point to the .so file

export MARLIN_DLL=$PWD/lib/

(2) Create the steering file. This steering file is used to tell Marlin in what order to run your processor with other standard processors. It is used to set some global variables aswell as the input stdio file and the output file name. You also need to point to the gear (geometry) file that was used to create your input stdio file. Marlin automatically creates this file for you but you must edit the input/output files at least. The global variables will be taken from your C++ code. To create the file just do:

Marlin -x > mysteer.xml

(3) As mentioned you must edit the steering file to point to the input .stdio and gear.xml file you are using for your analysis.

Running Marlin processor

Simply do:

Marlin mysteer.xml


Useful Links

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng ILD-LDC-SWF.png r1 manage 144.5 K 2012-08-08 - 15:28 DanProtopopescu SW framework overview
PDFpdf gaede_ildsoft_chep09.pdf r1 manage 2139.7 K 2012-08-08 - 15:23 DanProtopopescu ILC Software Framework - Frank Gaede's CHEP 2009 talk
Edit | Attach | Watch | Print version | History: r57 | r19 < r18 < r17 < r16 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r17 - 2012-08-14 - ThomasDoherty
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback