Software/Geant4/Installation - Revision history

JamesChappell at 10:48, 20 October 2017

2017-10-20T10:48:14Z

@@ Line 68: / Line 68: @@
 ; Website : http://geant4.web.cern.ch/geant4/
 ; Source URL : http://geant4.web.cern.ch/geant4/support/download.shtml
-; Latest version : 10.2.p01 (26 Feb 2016)
+; Latest Production version : 10.2.p01 (26 Feb 2016)
 ; Source tarball : <code>src/geant4/geant4.10.02.p01.tar.gz</code>
 == Installation Instructions ==
@@ Line 82: / Line 84: @@
 # Configure, build and install <code>Geant4</code> from within the build folder.
-=== Download and Extract <code>Geant4</code> Source Code ===
+=== Configure, Build and Install <code>Geant4</code> ===
 The <code>Geant4</code> source code can be downloaded from the [http://geant4.web.cern.ch/geant4/support/download.shtml Geant4 Download Page] of the [http://geant4.web.cern.ch/geant4/ Geant4 website] given above.
@@ Line 100: / Line 166: @@
 This will extract the <code>Geant4</code> source code into a directory alongside the <code>tar</code>-file.
 This directory can be renamed: it does not need to be kept the same for the installation described below to work, although the correct directory name should be substituted for the default name used below.
 Once the source code has been extracted, a <code>build</code> directory should be created alongside the <code>src</code> to hold the compiled <code>Geant4</code> files before they are moved to their final installation location.

SimonJolly at 14:53, 24 June 2016

2016-06-24T14:53:26Z

← Older revision		Revision as of 14:53, 24 June 2016
Line 48:		Line 48:
	** The [[/Coin3D#SoXt\|<code>SoXt</code>]] open source InventorXt library, which is a GUI binding for using Open Inventor with Xt/Motif. <code>SoXt</code> must be installed after <code>Coin3D</code>.		** The [[/Coin3D#SoXt\|<code>SoXt</code>]] open source InventorXt library, which is a GUI binding for using Open Inventor with Xt/Motif. <code>SoXt</code> must be installed after <code>Coin3D</code>.
	** [[/Coin3D#SoQt\|<code>SoQt</code>]] open source <code>Qt</code> GUI component toolkit library for <code>Coin3D</code>. <code>SoQt</code> must be installed after <code>Coin3D</code>.		** [[/Coin3D#SoQt\|<code>SoQt</code>]] open source <code>Qt</code> GUI component toolkit library for <code>Coin3D</code>. <code>SoQt</code> must be installed after <code>Coin3D</code>.

			By default some of these will ship pre-installed with most modern Linux distributions: however the <code>expat</code> and <code>mesa</code> generally need to be installed alongside the software listed above.

	=== Add Ons ===		=== Add Ons ===
Line 62:		Line 64:
	* The [[/gMocren\|<code>gMocren</code>]] volume visualiser for <code>Geant4</code> medical simulations.		* The [[/gMocren\|<code>gMocren</code>]] volume visualiser for <code>Geant4</code> medical simulations.

	== ~~Geant4 Installation~~ ==		== Details ==

	; Website : http://geant4.web.cern.ch/geant4/		; Website : http://geant4.web.cern.ch/geant4/
	; Latest version : 10.0.2 (~~13 June 2014~~)		; Source URL : http://geant4.web.cern.ch/geant4/support/download.shtml
	; Source tarball : <code>src/geant4/geant4.10.00.~~p02~~.tar.gz</code>		; Latest version : 10.2.p01 (26 Feb 2016)
			; Source tarball : <code>src/geant4/geant4.10.02.p01.tar.gz</code>

			== Installation Instructions ==

			The installation process follows the general process described on the [[Software/Geant4/UCL HEP Cluster\|UCL HEP Linux Cluster]] page.
			The basic method used is as follows:

			# Check that all the prerequisites for building <code>Geant4</code> are installed (see above);
			# Download the latest version of the source code;
			# Extract the source code from the downloaded tarball;
			# Create a build folder;
			# Configure, build and install <code>Geant4</code> from within the build folder.

	~~All the required software has now been installed,~~ and <code>~~GEANT4~~</code> ~~itself can finally be installed.~~		=== Download and Extract <code>Geant4</code> Source Code ===

	~~Notes~~:		The <code>Geant4</code> source code can be downloaded from the [http://geant4.web.cern.ch/geant4/support/download.shtml Geant4 Download Page] of the [http://geant4.web.cern.ch/geant4/ Geant4 website] given above.
	* There are a number of ways to configure the software before building. Using the <code>ccmake</code> command, each configuration option can be set interactively. Alternatively, the cmake command below configures with the recommended options.
			Unless there is a '''very''' good reason for not doing so, it is always recommended to use the latest version: each version features incremental improvements and bug fixes over earlier version and normally also features superior physics modelling.

			Alongside the <code>Geant4</code> download, there are also a number of data files available for modelling particular processes.
			These do not need to be downloaded separately as they can be added during <code>Geant4</code> installation by setting the <code>-DGEANT4_INSTALL_DATA=ON</code> compilation flag when running <code>cmake</code> (see below).

			The <code>Geant4</code> source code is normally downloaded as a single gzipped <code>tar</code>-file.
			This needs to be extracted with the following command:

			<pre>
			tar -xvz -f geant4.10.02.p01.tar.gz
			</pre>

			This will extract the <code>Geant4</code> source code into a directory alongside the <code>tar</code>-file.
			This directory can be renamed: it does not need to be kept the same for the installation described below to work, although the correct directory name should be substituted for the default name used below.

			=== Configure, Build and Install <code>Geant4</code> ===

			Once the source code has been extracted, a <code>build</code> directory should be created alongside the <code>src</code> to hold the compiled <code>Geant4</code> files before they are moved to their final installation location.

			On the [[Software/Geant4/UCL HEP Cluster\|UCL HEP Linux Cluster]], the <code>build</code> directory should be created in <code>/unix/pbt/software/build</code>:

			<pre>
			cd /unix/pbt/software/build
			mkdir geant4
			cd geant4
			mkdir geant4.10.02.p01-build
			cd geant4.10.02.p01-build
			</pre>

			Unlike other software installed on the [[Software/Geant4/UCL HEP Cluster\|UCL HEP Linux Cluster]], there are a number of ways to configure the software before building.
			Using the <code>ccmake</code> command, each configuration option can be set interactively.
			Alternatively, the <code>cmake</code> command below configures with the recommended options.

			Note that the <code>-DCMAKE_INSTALL_PREFIX="/unix/pbt/software/prod-sl6"</code> flag specifies that the resulting <code>Geant4</code> should be installed in the directory <code>/unix/pbt/software/prod-sl6</code> after compilation: this should be changed to suit the particular installation in question.

	Installation commands:		Installation commands:
Line 104:		Line 152:
	make		make
	make install		make install

	</pre>		</pre>

Line 132:		Line 179:
	* Cannot find <code>GCCXML</code> These packages are optional, but some of the examples are designed to demonstrate the connection with these packages. Note that some filetypes, such as <code>AIDA</code> and <code>HBOOK</code>, do in fact have viewers installed in the PBT environments, but these are not available to the <code>GEANT4</code> system. This what the errors are reporting.		* Cannot find <code>GCCXML</code> These packages are optional, but some of the examples are designed to demonstrate the connection with these packages. Note that some filetypes, such as <code>AIDA</code> and <code>HBOOK</code>, do in fact have viewers installed in the PBT environments, but these are not available to the <code>GEANT4</code> system. This what the errors are reporting.

	==== Basic examples ====		=== Basic examples ===

	===== B1 =====		==== B1 ====

	<pre>		<pre>
Line 152:		Line 199:
	This is due to the fact that the results depend on the initial state of the random number generator. The random seed used to generate the example output is unknown.		This is due to the fact that the results depend on the initial state of the random number generator. The random seed used to generate the example output is unknown.

	====== B1 visualisation ======		==== B1 visualisation ====

	The example, when run without arguments, opens in interactive mode using the visualisation driver selected in the file vis.mac:		The example, when run without arguments, opens in interactive mode using the visualisation driver selected in the file vis.mac:

LawrenceDeacon: /* B1 */

2016-06-07T02:32:16Z

← Older revision		Revision as of 02:32, 7 June 2016
Line 149:		Line 149:
	</pre>		</pre>

	~~There are significant differences in the~~ simulation results ~~compared~~ to the included <code>exampleB1.out</code> file.		The newly generated simulation results contain similar but not identical values to those in the included <code>exampleB1.out</code> file.
	This is due to the fact that the results depend on the initial state of the random number generator. The random seed used to generate the example output is unknown.		This is due to the fact that the results depend on the initial state of the random number generator. The random seed used to generate the example output is unknown.

LawrenceDeacon: /* B1 visualisation */

2016-06-07T02:28:46Z

B1 visualisation

← Older revision		Revision as of 02:28, 7 June 2016
Line 160:		Line 160:
	</pre>		</pre>

	The various visualisation packages can be tested by editing vis.mac to select the appropriate package. Some drivers create an interactive view of the simulation geometry. Others write to a file which can be viewed using an external software package e.g. DAWN - see the [http://geant4.web.cern.ch/geant4/G4UsersDocuments/UsersGuides/ForApplicationDeveloper/html/Visualization/introduction.html geant manual] for details.		The various visualisation packages can be tested by editing vis.mac to select the appropriate package. Some drivers create an interactive view of the simulation geometry. Others write to a file which can be viewed using an external software package e.g. DAWN - see the [http://geant4.web.cern.ch/geant4/G4UsersDocuments/UsersGuides/ForApplicationDeveloper/html/Visualization/introduction.html geant manual] for details.

	Most packages are listed in the file in lines beginning <code>/vis/open</code> and can be uncommented to select, e.g.		Most packages are listed in the file in lines beginning <code>/vis/open</code> and can be uncommented to select, e.g.

LawrenceDeacon: /* B1 visualisation */

2016-06-07T02:28:20Z

B1 visualisation

← Older revision		Revision as of 02:28, 7 June 2016
Line 154:		Line 154:
	====== B1 visualisation ======		====== B1 visualisation ======

	The example, when run without arguments, opens in interactive mode using the visualisation driver selected in the file vis.mac. The various visualisation packages can be tested by editing vis.mac to select the appropriate package. Some drivers create an interactive view of the simulation geometry. Others write to a file which can be viewed using an external software package e.g. DAWN - see the [http://geant4.web.cern.ch/geant4/G4UsersDocuments/UsersGuides/ForApplicationDeveloper/html/Visualization/introduction.html geant manual] for details.		The example, when run without arguments, opens in interactive mode using the visualisation driver selected in the file vis.mac:

			<pre>
			./exampleB1
			</pre>

			The various visualisation packages can be tested by editing vis.mac to select the appropriate package. Some drivers create an interactive view of the simulation geometry. Others write to a file which can be viewed using an external software package e.g. DAWN - see the [http://geant4.web.cern.ch/geant4/G4UsersDocuments/UsersGuides/ForApplicationDeveloper/html/Visualization/introduction.html geant manual] for details.

	Most packages are listed in the file in lines beginning <code>/vis/open</code> and can be uncommented to select, e.g.		Most packages are listed in the file in lines beginning <code>/vis/open</code> and can be uncommented to select, e.g.

LawrenceDeacon: /* B1 */

2016-06-07T02:27:35Z

← Older revision		Revision as of 02:27, 7 June 2016
Line 150:		Line 150:

	There are significant differences in the simulation results compared to the included <code>exampleB1.out</code> file.		There are significant differences in the simulation results compared to the included <code>exampleB1.out</code> file.
	This is due to the fact that the results depend on the initial state of the random number generator~~. To generate identical results the random seeds would need to be the same~~. The random seed used to generate the example output is unknown.		This is due to the fact that the results depend on the initial state of the random number generator. The random seed used to generate the example output is unknown.

	====== B1 visualisation ======		====== B1 visualisation ======

LawrenceDeacon: /* B1 visualisation */

2016-06-07T02:26:57Z

B1 visualisation

← Older revision		Revision as of 02:26, 7 June 2016
Line 156:		Line 156:
	The example, when run without arguments, opens in interactive mode using the visualisation driver selected in the file vis.mac. The various visualisation packages can be tested by editing vis.mac to select the appropriate package. Some drivers create an interactive view of the simulation geometry. Others write to a file which can be viewed using an external software package e.g. DAWN - see the [http://geant4.web.cern.ch/geant4/G4UsersDocuments/UsersGuides/ForApplicationDeveloper/html/Visualization/introduction.html geant manual] for details.		The example, when run without arguments, opens in interactive mode using the visualisation driver selected in the file vis.mac. The various visualisation packages can be tested by editing vis.mac to select the appropriate package. Some drivers create an interactive view of the simulation geometry. Others write to a file which can be viewed using an external software package e.g. DAWN - see the [http://geant4.web.cern.ch/geant4/G4UsersDocuments/UsersGuides/ForApplicationDeveloper/html/Visualization/introduction.html geant manual] for details.

	Most packages are listed in the file in lines beginning /vis/open and can be uncommented to select, e.g.		Most packages are listed in the file in lines beginning <code>/vis/open</code> and can be uncommented to select, e.g.

	<pre>		<pre>

LawrenceDeacon: /* B1 visualisation */

2016-06-07T02:26:19Z

B1 visualisation

← Older revision		Revision as of 02:26, 7 June 2016
Line 154:		Line 154:
	====== B1 visualisation ======		====== B1 visualisation ======

	The example, when run without arguments, opens in interactive mode using the visualisation driver selected in the file vis.mac. The various visualisation packages can be tested by editing vis.mac to select the appropriate package.		The example, when run without arguments, opens in interactive mode using the visualisation driver selected in the file vis.mac. The various visualisation packages can be tested by editing vis.mac to select the appropriate package. Some drivers create an interactive view of the simulation geometry. Others write to a file which can be viewed using an external software package e.g. DAWN - see the [http://geant4.web.cern.ch/geant4/G4UsersDocuments/UsersGuides/ForApplicationDeveloper/html/Visualization/introduction.html geant manual] for details.

	Most packages are listed in the file in lines beginning /vis/open and can be uncommented to select, e.g.		Most packages are listed in the file in lines beginning /vis/open and can be uncommented to select, e.g.

LawrenceDeacon: /* Testing */

2016-06-07T02:21:44Z

Testing

← Older revision		Revision as of 02:21, 7 June 2016
Line 151:		Line 151:
	There are significant differences in the simulation results compared to the included <code>exampleB1.out</code> file.		There are significant differences in the simulation results compared to the included <code>exampleB1.out</code> file.
	This is due to the fact that the results depend on the initial state of the random number generator. To generate identical results the random seeds would need to be the same. The random seed used to generate the example output is unknown.		This is due to the fact that the results depend on the initial state of the random number generator. To generate identical results the random seeds would need to be the same. The random seed used to generate the example output is unknown.

			====== B1 visualisation ======

			The example, when run without arguments, opens in interactive mode using the visualisation driver selected in the file vis.mac. The various visualisation packages can be tested by editing vis.mac to select the appropriate package.
			Most packages are listed in the file in lines beginning /vis/open and can be uncommented to select, e.g.

			<pre>
			/vis/open OGL 600x600-0+0
			</pre>

			RayTracerX is not listed in the file but can be enabled by uncommenting the other /vis/open lines and adding the following line:

			<pre>
			/vis/open RayTracerX
			</pre>

LawrenceDeacon: /* B1 */

2016-06-07T02:15:06Z

← Older revision		Revision as of 02:15, 7 June 2016
Line 149:		Line 149:
	</pre>		</pre>

	There ~~seem to be~~ significant differences in the simulation results compared to the included <code>exampleB1.out</code> file.		There are significant differences in the simulation results compared to the included <code>exampleB1.out</code> file.
	The ~~reason for these differences~~ is ~~unclear~~.		This is due to the fact that the results depend on the initial state of the random number generator. To generate identical results the random seeds would need to be the same. The random seed used to generate the example output is unknown.