Software/Geant4/Installation/CLHEP - Revision history

JamesChappell at 09:56, 20 October 2017

2017-10-20T09:56:15Z

← Older revision		Revision as of 09:56, 20 October 2017
Line 15:		Line 15:
	; Website : http://proj-clhep.web.cern.ch/proj-clhep/		; Website : http://proj-clhep.web.cern.ch/proj-clhep/
	; Source URL : http://proj-clhep.web.cern.ch/proj-clhep/DISTRIBUTION/		; Source URL : http://proj-clhep.web.cern.ch/proj-clhep/DISTRIBUTION/
	; Installed version : 2.3.1.1 (15 Mar 2016)		; Installed Production version : 2.3.1.1 (15 Mar 2016)
	; Source code : <code>src/geant4-prerequisites/clhep/2.3.1.1</code>		; Source code : <code>src/geant4-prerequisites/clhep/2.3.1.1</code>
			; Installed Development version : 2.3.4.5 (20 October 2017)
			; Central Repository : https://gitlab.cern.ch/CLHEP/CLHEP

	== Installation Notes ==		== Installation Notes ==
Line 28:		Line 30:
	When downloading software, the downloaded tarball (or other <code>Zip</code> archive) should be placed in an appropriately named directory in <code>/unix/pbt/software/src</code>: the instructions below assume that the directory is <code>/unix/pbt/software/src/clhep</code>. The tarball should then be extracted into the same subdirectory.		When downloading software, the downloaded tarball (or other <code>Zip</code> archive) should be placed in an appropriately named directory in <code>/unix/pbt/software/src</code>: the instructions below assume that the directory is <code>/unix/pbt/software/src/clhep</code>. The tarball should then be extracted into the same subdirectory.

	For CLHEP, the tarball is named <code>clhep-2.3.1.1.tgz</code>. When extracted, this produces a directory called <code>2.3.1.1</code>. Therefore, you will end up with a directory called <code>/unix/pbt/software/src/clhep/2.3.1.1</code> containing the CLHEP source code:		For CLHEP, the tarball is named <code>clhep-2.3.1.1.tgz</code>. When extracted, this produces a directory called <code>2.3.1.1</code>. Therefore, you will end up with a directory called <code>/unix/pbt/software/src/clhep/2.3.1.1</code> containing the CLHEP source code.

	=== Source Code Extraction ===		=== Installation from Central Repository ===

			Once the latest version of CLHEP has been pulled from its [https://gitlab.cern.ch/CLHEP/CLHEP central repository] and placed within <code>/unix/pbt/software/src/clhep/</code>, create a build directory within the PBT Software directory from which you can compile <code>CLHEP</code>:

			<pre>
			cd /unix/pbt/software/build/
			mkdir clhep-2.3.4.5
			cd clhep-2.3.4.5
			</pre>

			<code>CMake</code> can then be used to compile <code>CLHEP</code>:

			<pre>
			cmake ../../src/clhep/
			ccmake .
			</pre>

			The command <code>ccmake .</code> opens an interactive GUI that can be used to specify installation options. From within this you can define your installation directory and configure any other options as required. On the PBT cluster it is required that the software is installed to the development directory, and so the <code>CMAKE_INSTALL_PREFIX</code> is defined as follows:

			<pre>
			CMAKE_INSTALL_PREFIX /unix/pbt/software/dev/clhep-2.3.4.5/
			</pre>

			* ''c'' to configure
			* ''g'' to generate and exit

			The software can then be installed using the usual commands:

			<pre>
			make
			make install
			</pre>

			=== Installation from the Source Code ===

			==== Source Code Extraction ====

	<pre>		<pre>
Line 37:		Line 74:
	</pre>		</pre>

	=== Build And Install ===		==== Build And Install ====

	==== Development Environment ====		===== Development Environment =====

	<pre>		<pre>
Line 50:		Line 87:
	</pre>		</pre>

	==== Production Environment ====		===== Production Environment =====

	It may be possible to install in the production environment by running cmake again and changing the install prefix, then running make install:		It may be possible to install in the production environment by running cmake again and changing the install prefix, then running make install:

SimonJolly at 11:39, 3 June 2016

2016-06-03T11:39:24Z

← Older revision		Revision as of 11:39, 3 June 2016
Line 45:		Line 45:
	mkdir -pv clhep/clhep-2.3.1.1		mkdir -pv clhep/clhep-2.3.1.1
	cd clhep/clhep-2.3.1.1		cd clhep/clhep-2.3.1.1
	cmake -DCMAKE_INSTALL_PREFIX=/unix/pbt/software/dev/clhep-2.3.1.1 /unix/pbt/software/src/clhep/2.3.1.1/CLHEP		cmake -DCMAKE_INSTALL_PREFIX=/unix/pbt/software/dev/clhep-2.3.1.1 /unix/pbt/software/src/geant4-prerequisites/clhep/2.3.1.1/CLHEP
	make		make
	make install		make install

LawrenceDeacon at 10:56, 3 June 2016

2016-06-03T10:56:22Z

← Older revision		Revision as of 10:56, 3 June 2016
Line 23:		Line 23:

	According to the release notes, http://geant4.web.cern.ch/geant4/support/ReleaseNotes4.10.2.html, the supported version of CLHEP for <code>Geant4.10.2.p01</code> is 2.3.1.1. Using other versions of <code>CLHEP</code> may produce incorrect simulation results.		According to the release notes, http://geant4.web.cern.ch/geant4/support/ReleaseNotes4.10.2.html, the supported version of CLHEP for <code>Geant4.10.2.p01</code> is 2.3.1.1. Using other versions of <code>CLHEP</code> may produce incorrect simulation results.

	For installation, <code>CLHEP</code> does not support installation into a sandbox directory (i.e. there are no options <code>prefix</code> or <code>DESTDIR</code> defined for command <code>make install</code>) and must be given the installation directory with the <code>-prefix</code> option.
	As such, to recompile <code>CLHEP</code> for different target directories, the <code>configure</code> script must be rerun with a modified <code>-prefix /path/to/dest</code> option. This has to be managed manually as can be seen in the installation commands below.

	== Installation ==		== Installation ==

	When downloading software, the downloaded tarball (or other <code>Zip</code> archive) should be placed in an appropriately named directory in <code>/unix/pbt/software/src</code>: the instructions below assume that the directory is <code>/unix/pbt/software/src/clhep</code>.		When downloading software, the downloaded tarball (or other <code>Zip</code> archive) should be placed in an appropriately named directory in <code>/unix/pbt/software/src</code>: the instructions below assume that the directory is <code>/unix/pbt/software/src/clhep</code>. The tarball should then be extracted into the same subdirectory.

	~~The source~~ code ~~should then be~~ extracted ~~into~~ a ~~suitable subdirectory in~~ <code>/unix/pbt/software/~~build~~</code>~~. The extracted~~ source code ~~directory can only be deleted once the software has been built and installed.~~		For CLHEP, the tarball is named <code>clhep-2.3.1.1.tgz</code>. When extracted, this produces a directory called <code>2.3.1.1</code>. Therefore, you will end up with a directory called <code>/unix/pbt/software/src/clhep/2.3.1.1</code> containing the CLHEP source code:

	=== Source Code Extraction ===		=== Source Code Extraction ===

	<pre>		<pre>
	cd /unix/pbt/software/src/~~geant4-prerequisites/qt~~		cd /unix/pbt/software/src/clhep
	tar -~~xvz -f qtbase-opensource-src-5.6.0.tar.gz~~		tar -xvzf clhep-2.3.1.1.tgz
	~~mv qtbase-opensource~~-~~src-5~~.6.~~0 qt-5~~.6.0
	</pre>		</pre>

	=== Build And Install ===		=== Build And Install ===

	These instructions assume the code has already been built for the '''Development''' environment before building for the '''Production''' environment, so some of the commands for the '''Production''' install are omitted.
	Although it is highly discouraged to install straight to the '''Production''' environment without first compiling a '''Development''' version, it is possible to do so by adding in the directory creation commands at the start.

	==== Development Environment ====		==== Development Environment ====
Line 50:		Line 43:
	<pre>		<pre>
	cd /unix/pbt/software/build		cd /unix/pbt/software/build
	mkdir -pv qt/qt-5.6.0		mkdir -pv clhep/clhep-2.3.1.1
	cd qt/qt-5.6.0		cd clhep/clhep-2.3.1.1
	../../../~~src~~/~~geant4-prerequisites/qt~~/qt-5.6.~~0/configure -prefix~~ /unix/pbt/software/~~dev~~/~~qt-5~~.6.~~0 -release -opensource -confirm-licence -nomake tests -nomake examples -optimized-qmake -opengl -qt-xcb~~		cmake -DCMAKE_INSTALL_PREFIX=/unix/pbt/software/dev/clhep-2.3.1.1 /unix/pbt/software/src/clhep/2.3.1.1/CLHEP
	make		make
	make install		make install
Line 58:		Line 51:

	==== Production Environment ====		==== Production Environment ====

			It may be possible to install in the production environment by running cmake again and changing the install prefix, then running make install:

	<pre>		<pre>
	cd /unix/pbt/software/build/qt/qt-5.6.0		cd /unix/pbt/software/build/clhep/clhep-2.3.1.1
	../../../~~src~~/~~geant4~~-~~prerequisites~~/qt/qt-5.6.~~0/configure~~ -~~prefix~~ /unix/pbt/software/prod~~-sl6 -release -opensource -confirm-licence -nomake tests -nomake examples -optimized-qmake -opengl -qt-xcb~~		cmake -DCMAKE_INSTALL_PREFIX=/unix/pbt/software/prod .
			make install
			</pre>

			This will save having to compile the code again. If this does not work, the compilation steps for the development environment (above) will need to be repeated in another build directory:

			<pre>
			cd /unix/pbt/software/build
			mkdir -pv clhep/clhep-2.3.1.1-prod
			cd clhep/clhep-2.3.1.1-prod
			cmake -DCMAKE_INSTALL_PREFIX=/unix/pbt/software/prod /unix/pbt/software/src/clhep/2.3.1.1/CLHEP
	make		make
	make install		make install
	</pre>		</pre>

LawrenceDeacon at 10:33, 3 June 2016

2016-06-03T10:33:14Z

← Older revision		Revision as of 10:33, 3 June 2016
Line 22:		Line 22:
	The [http://proj-clhep.web.cern.ch/proj-clhep/ CLHEP website] provides some documentation on building and installing standalone <code>CLHEP</code> libraries at http://proj-clhep.web.cern.ch/proj-clhep/INSTALLATION/clhep-2.0.html .		The [http://proj-clhep.web.cern.ch/proj-clhep/ CLHEP website] provides some documentation on building and installing standalone <code>CLHEP</code> libraries at http://proj-clhep.web.cern.ch/proj-clhep/INSTALLATION/clhep-2.0.html .

	<code>Geant4.10.2.p01</code> ~~has been tested with <code>CLHEP~~ 2.3.1.1~~</code>~~.		According to the release notes, http://geant4.web.cern.ch/geant4/support/ReleaseNotes4.10.2.html, the supported version of CLHEP for <code>Geant4.10.2.p01</code> is 2.3.1.1. Using other versions of <code>CLHEP</code> may produce incorrect simulation results.
	<code>CLHEP ~~2.3.2.2~~</code> ~~is available but <code>Geant4.10.2.p01</code> would not compile with this version, so the previous version is installed~~.

	For installation, <code>CLHEP</code> does not support installation into a sandbox directory (i.e. there are no options <code>prefix</code> or <code>DESTDIR</code> defined for command <code>make install</code>) and must be given the installation directory with the <code>-prefix</code> option.		For installation, <code>CLHEP</code> does not support installation into a sandbox directory (i.e. there are no options <code>prefix</code> or <code>DESTDIR</code> defined for command <code>make install</code>) and must be given the installation directory with the <code>-prefix</code> option.

SimonJolly at 12:02, 1 June 2016

2016-06-01T12:02:12Z

← Older revision		Revision as of 12:02, 1 June 2016
Line 22:		Line 22:
	The [http://proj-clhep.web.cern.ch/proj-clhep/ CLHEP website] provides some documentation on building and installing standalone <code>CLHEP</code> libraries at http://proj-clhep.web.cern.ch/proj-clhep/INSTALLATION/clhep-2.0.html .		The [http://proj-clhep.web.cern.ch/proj-clhep/ CLHEP website] provides some documentation on building and installing standalone <code>CLHEP</code> libraries at http://proj-clhep.web.cern.ch/proj-clhep/INSTALLATION/clhep-2.0.html .

	<code>Geant4</code> ~~supports~~ <code>~~Qt 4~~.6</code> ~~or higher (~~<code>~~Qt 4~~.8</code> ~~or higher on Mac)~~.		<code>Geant4.10.2.p01</code> has been tested with <code>CLHEP 2.3.1.1</code>.
			<code>CLHEP 2.3.2.2</code> is available but <code>Geant4.10.2.p01</code> would not compile with this version, so the previous version is installed.

	<code>Qt</code> is available in a number of different versions and with a vast array of submodules. Only the "qtbase" submodule is required to compile all the elements required for <code>Geant4</code>. The various different installer and source code options can be found at: http://www.qt.io/download-open-source/		For installation, <code>CLHEP</code> does not support installation into a sandbox directory (i.e. there are no options <code>prefix</code> or <code>DESTDIR</code> defined for command <code>make install</code>) and must be given the installation directory with the <code>-prefix</code> option.
			As such, to recompile <code>CLHEP</code> for different target directories, the <code>configure</code> script must be rerun with a modified <code>-prefix /path/to/dest</code> option. This has to be managed manually as can be seen in the installation commands below.
	For installation, <code>Qt</code> does not support installation into a sandbox directory (i.e. there are no options <code>prefix</code> or <code>DESTDIR</code> defined for command <code>make install</code>) and must be given the installation directory with the <code>-prefix</code> option. As such, to recompile <code>Qt</code> for different target directories, the <code>configure</code> script must be rerun with a modified <code>-prefix /path/to/dest</code> option. This has to be managed manually as can be seen in the installation commands below.

	~~The tarball extracts to a rather long folder name. To follow the installation commands below, rename this to <code>src/qt-5.6.0</code>.~~

	~~Some instructions on the correct package to download and the various compilation flags were provided by Ben Morgan at Warwick, along with this configuration script:~~

	~~https://github.com/SuperNEMO-DBD/homebrew-cadfael/blob/master/Formula/qt5-base.rb~~

	== Installation ==		== Installation ==

	When downloading software, the downloaded tarball (or other <code>Zip</code> archive) should be placed in an appropriately named directory in <code>/unix/pbt/software/src</code>: the instructions below assume that the directory is <code>/unix/pbt/software/src/qt</code>.		When downloading software, the downloaded tarball (or other <code>Zip</code> archive) should be placed in an appropriately named directory in <code>/unix/pbt/software/src</code>: the instructions below assume that the directory is <code>/unix/pbt/software/src/clhep</code>.

	The source code should then be extracted into a suitable subdirectory in <code>/unix/pbt/software/build</code>. The extracted source code directory can only be deleted once the software has been built and installed		The source code should then be extracted into a suitable subdirectory in <code>/unix/pbt/software/build</code>. The extracted source code directory can only be deleted once the software has been built and installed.

	=== Source Code Extraction ===		=== Source Code Extraction ===

SimonJolly at 08:06, 27 May 2016

2016-05-27T08:06:10Z

← Older revision		Revision as of 08:06, 27 May 2016
Line 8:		Line 8:
	This internal version of the CLHEP library is built and used by default, so having an external install of CLHEP is no longer a prerequisite for Geant4.		This internal version of the CLHEP library is built and used by default, so having an external install of CLHEP is no longer a prerequisite for Geant4.

	However, the [[Software/BDSIM\|BDSIM]] accelerator simulation toolkit, uses Geant4 for particle-matter interactions, requires a standalone version of <code>CLHEP</code> to be compiled separately from <code>Geant4</code>.		However, the [[Software/BDSIM\|BDSIM]] accelerator simulation toolkit, which uses Geant4 for particle-matter interactions, requires a standalone version of <code>CLHEP</code> to be compiled separately from <code>Geant4</code>.
	As such, the instructions below relate to the standalone version of <code>CLHEP</code>.		As such, the instructions below relate to the standalone version of <code>CLHEP</code>.

SimonJolly at 14:50, 24 May 2016

2016-05-24T14:50:22Z

← Older revision		Revision as of 14:50, 24 May 2016
Line 8:		Line 8:
	This internal version of the CLHEP library is built and used by default, so having an external install of CLHEP is no longer a prerequisite for Geant4.		This internal version of the CLHEP library is built and used by default, so having an external install of CLHEP is no longer a prerequisite for Geant4.

	However, the [[/Software/BDSIM\|BDSIM]] accelerator simulation toolkit, uses Geant4 for particle-matter interactions, requires a standalone version of <code>CLHEP</code> to be compiled separately from <code>Geant4</code>.		However, the [[Software/BDSIM\|BDSIM]] accelerator simulation toolkit, uses Geant4 for particle-matter interactions, requires a standalone version of <code>CLHEP</code> to be compiled separately from <code>Geant4</code>.
	As such, the instructions below relate to the standalone version of <code>CLHEP</code>.		As such, the instructions below relate to the standalone version of <code>CLHEP</code>.

SimonJolly at 14:49, 24 May 2016

2016-05-24T14:49:59Z

← Older revision		Revision as of 14:49, 24 May 2016
Line 8:		Line 8:
	This internal version of the CLHEP library is built and used by default, so having an external install of CLHEP is no longer a prerequisite for Geant4.		This internal version of the CLHEP library is built and used by default, so having an external install of CLHEP is no longer a prerequisite for Geant4.

	However, the [[/Software/BDSIM BDSIM]] accelerator simulation toolkit, uses Geant4 for particle-matter interactions, requires a standalone version of <code>CLHEP</code> to be compiled separately from <code>Geant4</code>.		However, the [[/Software/BDSIM\|BDSIM]] accelerator simulation toolkit, uses Geant4 for particle-matter interactions, requires a standalone version of <code>CLHEP</code> to be compiled separately from <code>Geant4</code>.
	As such, the instructions below relate to the standalone version of <code>CLHEP</code>.		As such, the instructions below relate to the standalone version of <code>CLHEP</code>.

SimonJolly at 14:49, 24 May 2016

2016-05-24T14:49:32Z

← Older revision		Revision as of 14:49, 24 May 2016
Line 19:		Line 19:

	== Installation Notes ==		== Installation Notes ==

			The [http://proj-clhep.web.cern.ch/proj-clhep/ CLHEP website] provides some documentation on building and installing standalone <code>CLHEP</code> libraries at http://proj-clhep.web.cern.ch/proj-clhep/INSTALLATION/clhep-2.0.html .

	<code>Geant4</code> supports <code>Qt 4.6</code> or higher (<code>Qt 4.8</code> or higher on Mac).		<code>Geant4</code> supports <code>Qt 4.6</code> or higher (<code>Qt 4.8</code> or higher on Mac).

SimonJolly: Created page with "== Introduction == `CLHEP` is intended to be a set of HEP-specific foundation and utility classes such as random generators, physics vectors, geometry and linear alge..."

2016-05-24T14:48:08Z

Created page with "== Introduction == <code>CLHEP</code> is intended to be a set of HEP-specific foundation and utility classes such as random generators, physics vectors, geometry and linear alge..."

New page

== Introduction ==

<code>CLHEP</code> is intended to be a set of HEP-specific foundation and utility classes such as random generators, physics vectors, geometry and linear algebra.
<code>CLHEP</code> is structured in a set of packages independent of any external package.

<code>Geant4</code> requires the <code>CLHEP</code> libraries in order to compile simulations.
By default <code>Geant4</code> distributes a minimal version of the <code>CLHEP</code> library sources with the toolkit to help cross-platform usage.
This internal version of the CLHEP library is built and used by default, so having an external install of CLHEP is no longer a prerequisite for Geant4.

However, the [[/Software/BDSIM BDSIM]] accelerator simulation toolkit, uses Geant4 for particle-matter interactions, requires a standalone version of <code>CLHEP</code> to be compiled separately from <code>Geant4</code>.
As such, the instructions below relate to the standalone version of <code>CLHEP</code>.

== Details ==

; Website : http://proj-clhep.web.cern.ch/proj-clhep/
; Source URL : http://proj-clhep.web.cern.ch/proj-clhep/DISTRIBUTION/
; Installed version : 2.3.1.1 (15 Mar 2016)
; Source code : <code>src/geant4-prerequisites/clhep/2.3.1.1</code>

== Installation Notes ==

<code>Geant4</code> supports <code>Qt 4.6</code> or higher (<code>Qt 4.8</code> or higher on Mac).

<code>Qt</code> is available in a number of different versions and with a vast array of submodules. Only the "qtbase" submodule is required to compile all the elements required for <code>Geant4</code>. The various different installer and source code options can be found at: http://www.qt.io/download-open-source/

For installation, <code>Qt</code> does not support installation into a sandbox directory (i.e. there are no options <code>prefix</code> or <code>DESTDIR</code> defined for command <code>make install</code>) and must be given the installation directory with the <code>-prefix</code> option. As such, to recompile <code>Qt</code> for different target directories, the <code>configure</code> script must be rerun with a modified <code>-prefix /path/to/dest</code> option. This has to be managed manually as can be seen in the installation commands below.

The tarball extracts to a rather long folder name. To follow the installation commands below, rename this to <code>src/qt-5.6.0</code>.

Some instructions on the correct package to download and the various compilation flags were provided by Ben Morgan at Warwick, along with this configuration script:

https://github.com/SuperNEMO-DBD/homebrew-cadfael/blob/master/Formula/qt5-base.rb

== Installation ==

When downloading software, the downloaded tarball (or other <code>Zip</code> archive) should be placed in an appropriately named directory in <code>/unix/pbt/software/src</code>: the instructions below assume that the directory is <code>/unix/pbt/software/src/qt</code>.

The source code should then be extracted into a suitable subdirectory in <code>/unix/pbt/software/build</code>. The extracted source code directory can only be deleted once the software has been built and installed

=== Source Code Extraction ===

<pre>
cd /unix/pbt/software/src/geant4-prerequisites/qt
tar -xvz -f qtbase-opensource-src-5.6.0.tar.gz
mv qtbase-opensource-src-5.6.0 qt-5.6.0
</pre>

=== Build And Install ===

These instructions assume the code has already been built for the '''Development''' environment before building for the '''Production''' environment, so some of the commands for the '''Production''' install are omitted.
Although it is highly discouraged to install straight to the '''Production''' environment without first compiling a '''Development''' version, it is possible to do so by adding in the directory creation commands at the start.

==== Development Environment ====

<pre>
cd /unix/pbt/software/build
mkdir -pv qt/qt-5.6.0
cd qt/qt-5.6.0
../../../src/geant4-prerequisites/qt/qt-5.6.0/configure -prefix /unix/pbt/software/dev/qt-5.6.0 -release -opensource -confirm-licence -nomake tests -nomake examples -optimized-qmake -opengl -qt-xcb
make
make install
</pre>

==== Production Environment ====

<pre>
cd /unix/pbt/software/build/qt/qt-5.6.0
../../../src/geant4-prerequisites/qt/qt-5.6.0/configure -prefix /unix/pbt/software/prod-sl6 -release -opensource -confirm-licence -nomake tests -nomake examples -optimized-qmake -opengl -qt-xcb
make
make install
</pre>

Software/Geant4/Installation/CLHEP - Revision history

JamesChappell at 09:56, 20 October 2017

SimonJolly at 11:39, 3 June 2016

LawrenceDeacon at 10:56, 3 June 2016

LawrenceDeacon at 10:33, 3 June 2016

SimonJolly at 12:02, 1 June 2016

SimonJolly at 08:06, 27 May 2016

SimonJolly at 14:50, 24 May 2016

SimonJolly at 14:49, 24 May 2016

SimonJolly at 14:49, 24 May 2016

SimonJolly: Created page with "== Introduction == CLHEP is intended to be a set of HEP-specific foundation and utility classes such as random generators, physics vectors, geometry and linear alge..."

SimonJolly: Created page with "== Introduction == `CLHEP` is intended to be a set of HEP-specific foundation and utility classes such as random generators, physics vectors, geometry and linear alge..."