Software/Geant4/UCL HEP Cluster - Revision history

SimonJolly at 02:39, 26 June 2024

2024-06-26T02:39:48Z

← Older revision		Revision as of 02:39, 26 June 2024
Line 75:		Line 75:
	## Set specific environment variables with locations of compiler, Geant4 etc.		## Set specific environment variables with locations of compiler, Geant4 etc.
	## Add locations to path variables and remove duplicates (calls <code>setpaths.sh</code> script);		## Add locations to path variables and remove duplicates (calls <code>setpaths.sh</code> script);
	## Define colours for scripts, prompt, etc (calls <code>definecolours.sh<code> script);		## Define colours for scripts, prompt, etc (calls <code>definecolours.sh</code> script);
	## Check versions of installed software and display results (calls <code>checkversions.sh</code> script);		## Check versions of installed software and display results (calls <code>checkversions.sh</code> script);
	## Modify prompt to show environment name;		## Modify prompt to show environment name;

RaffaellaRadogna: /* Scripts */

2019-03-14T15:16:09Z

Scripts

← Older revision		Revision as of 15:16, 14 March 2019
Line 81:		Line 81:

	Adding the <code>-v</code> flag enables the scripts to run in verbose mode, which displays the full paths when checking the versions of the installed software.		Adding the <code>-v</code> flag enables the scripts to run in verbose mode, which displays the full paths when checking the versions of the installed software.
	The <code>-b<code> flag sources the BDSIM PBT environment: this is only available on CentOS7 machines and using the script version available for EasyBuild modules (stored in <code>/unix/pbt/software/scripts/eb-centos7</code>).		The <code>-b</code> flag sources the BDSIM PBT environment: this is only available on CentOS7 machines and using the script version available for EasyBuild modules (stored in <code>/unix/pbt/software/scripts/eb-centos7</code>).
	Adding the <code>-d</code> flag enables the '''Development''' environment to allow new software to be built without changing the '''Production''' setup needed by most users: this is only available on SL6 machines.		Adding the <code>-d</code> flag enables the '''Development''' environment to allow new software to be built without changing the '''Production''' setup needed by most users: this is only available on SL6 machines.

RaffaellaRadogna: /* Software Matrix */

2019-03-14T13:14:26Z

Software Matrix

← Older revision		Revision as of 13:14, 14 March 2019
Line 149:		Line 149:
	== Software Matrix ==		== Software Matrix ==

	The following software is installed on the HEP Linux cluster. Starting from CentOS7, the supported procedure requires EasyBuild ~~installation~~.		The following software is installed on the HEP Linux cluster. Starting from CentOS7, the supported procedure requires EasyBuild.

	CentOS7 Machines: (not supported)		CentOS7 Machines: (not supported)

RaffaellaRadogna: /* Installations */

2019-03-14T13:14:02Z

Installations

← Older revision		Revision as of 13:14, 14 March 2019
Line 128:		Line 128:

	== Installations ==		== Installations ==
	For CentOS7 machines, ~~the~~ software ~~installation~~ is ~~made~~ using EasyBuild.		For CentOS7 machines, each software is installed using EasyBuild.

	For SL6 and SL5 machines, the installation procedure for each software package is listed below.		For SL6 and SL5 machines, the installation procedure for each software package is listed below.

RaffaellaRadogna: /* Installations */

2019-03-14T13:13:26Z

Installations

← Older revision		Revision as of 13:13, 14 March 2019
Line 129:		Line 129:
	== Installations ==		== Installations ==
	For CentOS7 machines, the software installation is made using EasyBuild.		For CentOS7 machines, the software installation is made using EasyBuild.

	For SL6 and SL5 machines, the installation procedure for each software package is listed below.		For SL6 and SL5 machines, the installation procedure for each software package is listed below.
	The basic method used is as follows:		The basic method used is as follows:

RaffaellaRadogna: /* Installations */

2019-03-14T13:13:09Z

Installations

← Older revision		Revision as of 13:13, 14 March 2019
Line 128:		Line 128:

	== Installations ==		== Installations ==
			For CentOS7 machines, the software installation is made using EasyBuild.
	For each software package~~, the installation information~~ is listed below.		For SL6 and SL5 machines, the installation procedure for each software package is listed below.
	The basic method used is as follows:		The basic method used is as follows:
	# Download the source tarball latest version to the <code>/unix/pbt/software/src</code> folder.		# Download the source tarball latest version to the <code>/unix/pbt/software/src</code> folder.

RaffaellaRadogna: /* Software Matrix */

2019-03-13T19:17:37Z

Software Matrix

← Older revision		Revision as of 19:17, 13 March 2019
Line 148:		Line 148:
	== Software Matrix ==		== Software Matrix ==

	The following software is installed on the HEP Linux cluster.		The following software is installed on the HEP Linux cluster. Starting from CentOS7, the supported procedure requires EasyBuild installation.

	CentOS7 Machines (not supported):		CentOS7 Machines: (not supported)

	{\| class="wikitable"		{\| class="wikitable"

RaffaellaRadogna: /* Software Matrix */

2019-03-13T19:14:56Z

Software Matrix

← Older revision		Revision as of 19:14, 13 March 2019
Line 150:		Line 150:
	The following software is installed on the HEP Linux cluster.		The following software is installed on the HEP Linux cluster.

	CentOS7 Machines:		CentOS7 Machines (not supported):

	{\| class="wikitable"		{\| class="wikitable"

RaffaellaRadogna: /* Scripts */

2019-03-13T19:13:56Z

Scripts

← Older revision		Revision as of 19:13, 13 March 2019
Line 99:		Line 99:

	The first 3 directories contain scripts that are almost identical, with small modifications to suit each environment.		The first 3 directories contain scripts that are almost identical, with small modifications to suit each environment.
	~~The <code>eb-centos7</code> directory contains a modified version of these scripts and the shared scripts to account for the EasyBuild modules.~~
	Along with the shared scripts, these are described below: substitute <code>xxx</code> for the particular environment.		Along with the shared scripts, these are described below: substitute <code>xxx</code> for the particular environment.
			The <code>eb-centos7</code> directory contains a version of all these scripts modified to work with EasyBuild modules.

	=== <code>/unix/pbt/software/scripts/xxx/pbt-xxx.sh</code> ===		=== <code>/unix/pbt/software/scripts/xxx/pbt-xxx.sh</code> ===

RaffaellaRadogna: /* Scripts */

2019-03-13T19:11:02Z

Scripts

← Older revision		Revision as of 19:11, 13 March 2019
Line 86:		Line 86:
	When <code>pbt.sh</code> is called, its first action after selecting the right environment is to launch a new <code>bash</code> shell that provides a degree of isolation for setting up the desired PBT environment.		When <code>pbt.sh</code> is called, its first action after selecting the right environment is to launch a new <code>bash</code> shell that provides a degree of isolation for setting up the desired PBT environment.
	Once the user has finished with the PBT environment, exiting the shell will deposit the user back into their previous environment.		Once the user has finished with the PBT environment, exiting the shell will deposit the user back into their previous environment.
	Launching a new shell also provides access to the correct Scientific Linux Developer Toolset: on SL6 this is <code>devtoolset-3</code>, whereas SLC5 uses the older <code>devtoolset-2</code>.		Launching a new shell also provides access to the correct Scientific Linux Developer Toolset: on CentOS7 this is <code>devtoolset-7</code>, on SL6 this is <code>devtoolset-3</code>, whereas SLC5 uses the older <code>devtoolset-2</code>.
	In either case, the Developer Toolset is a Linux software collection providing various tools for developers, including more up-to-date versions of software required by <code>Geant4</code>, most notably including a newer version of <code>GCC</code> (the '''GNU Compiler Collection''').		In either case, the Developer Toolset is a Linux software collection providing various tools for developers, including more up-to-date versions of software required by <code>Geant4</code>, most notably including a newer version of <code>GCC</code> (the '''GNU Compiler Collection''').

	The following sub-directories are present within the <code>scripts</code> directory:		The following sub-directories are present within the <code>scripts</code> directory:

	* <code>dev</code> — contains scripts for setting up '''Development''' environment;		* <code>dev</code> — contains scripts for setting up '''Development''' environment on SL6 machines;
	* <code>prod-sl6</code> — contains scripts for setting up '''Production''' environment on SL6 machines;		* <code>prod-sl6</code> — contains scripts for setting up '''Production''' environment on SL6 machines;
	* <code>prod-slc5</code> — contains scripts for setting up '''Production''' environment on SLC5 machines;		* <code>prod-slc5</code> — contains scripts for setting up '''Production''' environment on SLC5 machines;
	* <code>shared</code> — shared scripts used in the setup of all environments (see below);		* <code>shared</code> — shared scripts used in the setup of all environments (see below);
			* <code>eb-centos7</code> — contains scripts for setting up PBT environment on CentOS7 machines using EasyBuild modules;
	* <code>old</code> — legacy scripts used in previous environment setup on SLC5.		* <code>old</code> — legacy scripts used in previous environment setup on SLC5.

	The first 3 directories contain scripts that are almost identical, with small modifications to suit each environment.		The first 3 directories contain scripts that are almost identical, with small modifications to suit each environment.
			The <code>eb-centos7</code> directory contains a modified version of these scripts and the shared scripts to account for the EasyBuild modules.
	Along with the shared scripts, these are described below: substitute <code>xxx</code> for the particular environment.		Along with the shared scripts, these are described below: substitute <code>xxx</code> for the particular environment.