Difference: WebHome (15 vs. 16)

Revision 162012-08-14 - ThomasDoherty

Line: 1 to 1
 

Linear Collider activities in Glasgow

<-- img style="width: 222; float: right" alt="ild.gif" src="https://ppes8.physics.gla.ac.uk/twiki/pub/LinearCollider/WebHome/ild.gif" title="ild.gif" height="169" -->
clic_event.gif
Line: 24 to 24
  https://svnsrv.desy.de/viewvc/ilctools/ilcinstall/tags/?view=tar
Changed:
<
<
into the temporary directory(soon to be replaced by an afs area)
>
>
into the afs area
 
Changed:
<
<
/data/atlas01/ILC
>
>
/afs/phas.gla.ac.uk/data/ilc/software
 
Added:
>
>
 I then untarred the file:
tar xvfz ilctools-tags.tar.gz
Line: 35 to 36
  I then went into the directory:
Changed:
<
<
/data/atlas01/ILC/tags
>
>
/afs/phas.gla.ac.uk/data/ilc/software/tags
 
Added:
>
>
 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!)

Line: 50 to 52
 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:

Changed:
<
<
/data/atlas01/ILC
>
>
/afs/phas.gla.ac.uk/data/ilc/software
 directory. For xerces-c I did the following:
mkdir xerces-c
Line: 61 to 63
 
wget http://apache.mirror.rbftpnetworks.com//xerces/c/3/binaries/xerces-c-3.1.1-x86_64-linux-gcc-3.4.tar.gz
Added:
>
>
 for 64 bit. And untarred.
Changed:
<
<
For Cernlib I realised that the installation here (/usr/lib64/cernlib) did not have the inlcude directories needed so I also went to /data/atlas01/ILC and created directory 2006b/ and in this directory I downloaded:
>
>
For Cernlib I realised that the installation here ( /usr/lib64/cernlib) did not have the inlcude directories needed so I also went to /afs/phas.gla.ac.uk/data/ilc/software

and downloaded:

 
wget http://wwwasd.web.cern.ch/wwwasd/cernlib/download/2006b_x86_64-slc5-gcc41-opt/tar/cernlib.tar.gz
wget http://wwwasd.web.cern.ch/wwwasd/cernlib/download/2006b_x86_64-slc5-gcc41-opt/tar/include.tar.gz
Line: 74 to 78
 

Preparing release version file

Changed:
<
<
First of all I created a directory where the ilcsoft software packages will actually be installed into. This is called /data/atlas01/ILC/ilcsoft
>
>
First of all I created a directory where the ilcsoft software packages will actually be installed into. This is called /data/atlas01/ILC/ilcsoft
 
Changed:
<
<
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:
>
>
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:
 
Changed:
<
<
/data/atlas01/ILC/v01-14/releases/v01-14/release-versions.py
>
>
/afs/phas.gla.ac.uk/data/ilc/software/tags/v01-14/releases/v01-14/release-versions.py
 

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

Changed:
<
<
ilcsoft_install_prefix = "/data/atlas01/ILC/ilcsoft/"
>
>
ilcsoft_install_prefix = "/afs/phas.gla.ac.uk/data/ilc/software/ilcsoft/"
 
Added:
>
>
 I then added:
MySQL_path = "/usr/"
Line: 91 to 94
 
MySQL_path = "/usr/"
Java_path = "/usr/java/latest/"
Changed:
<
<
CERNLIB_path = "/data/atlas01/ILC/2006b/" XERCESC_ROOT_DIR = "/data/atlas01/ILC/xerces-c/xerces-c-3.1.1-x86_64-linux-gcc-3.4/"
>
>
CERNLIB_path = "/afs/phas.gla.ac.uk/data/ilc/software/2006b" XERCESC_ROOT_DIR = "/afs/phas.gla.ac.uk/data/ilc/software/xcerces-c/xerces-c-3.1.1-x86_64-linux-gcc-3.4"
 
Added:
>
>
 to this file

Starting a full build for all packages

Line: 98 to 102
 

Starting a full build for all packages

Changed:
<
<
The file at the centre of this build is called 'release-scratch.cfg' which can be found in the same directory as the release-versions.py: /data/atlas01/ILC/v01-14/releases/v01-14/
>
>
The file at the centre of this build is called 'release-scratch.cfg' which can be found in the same directory as the release-versions.py: /afs/phas.gla.ac.uk/data/ilc/software/tags/v01-14/releases/v01-14/
  This file has the list and order in which all packages must be installed. First of all it is necessary to point to the release-version.py file from within this file:
Line: 115 to 119
 
LCIO compilation problems
Changed:
<
<
(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:
>
>
(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"
Line: 125 to 129
 /data/atlas01/ILC/ilcsoft/lcio/v02-01-02/CMakeLists.txt
Changed:
<
<
(2) We don't want Fortran examples - and they cause problems in compilation anyway - so I commented out:
>
>
(2) We don't want Fortran examples - and they cause problems in compilation anyway - so I commented out:
 
#MESSAGE( STATUS "BUILD_F77_TESTJOBS = ${BUILD_F77_TESTJOBS}" )
Line: 150 to 155
 
Building Root Dict manually for certain packages
Changed:
<
<
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:
>
>
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:
  KALTEST:
Line: 280 to 289
 export MARLIN_DLL=$PWD/lib/libExampleDSTAnalysis.so
Changed:
<
<
(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:
>
>
(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:
 
Changed:
<
<
Marlin -x > mysteer.xml
>
>
Marlin -x > mysteer.xml
 
Changed:
<
<
(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.
>
>
(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

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback