HPC/Module naming scheme, 2008 edition - Revision history

Stern: /* Module conventions on Carbon */

2017-06-21T15:43:56Z

Module conventions on Carbon

@@ Line 27: / Line 27: @@
   	http://jmol.sourceforge.net/
   	http://wiki.jmol.org/
 === Environment variable for package home directory ===
@@ Line 62: / Line 54: @@
   LDFLAGS += -L'''$(FFTW3_HOME)'''/lib
   …
 === Package-specific sample job ===

2016-11-17T23:00:43Z

Environment variable for package home directory

2016-11-17T23:00:14Z

Environment variable for package home directory

← Older revision		Revision as of 23:00, November 17, 2016
Line 53:		Line 53:
	Doc/ atomic_doc/ examples/		Doc/ atomic_doc/ examples/

	; ~~Specifcy link~~ paths in makefiles:		; Specify paths in makefiles:
	$ '''module load fftw3'''		$ '''module load fftw3'''
	$ cat Makefile		$ cat Makefile
			…
			CPPFLAGS += -I$(FFTW3_HOME)/include
			FPPFLAGS += -I$(FFTW3_HOME)/include
	…		…
	LDFLAGS += -L$(FFTW3_HOME)/lib		LDFLAGS += -L$(FFTW3_HOME)/lib

2016-11-17T22:57:27Z

Default modules being loaded

← Older revision		Revision as of 22:57, November 17, 2016
Line 11:		Line 11:
	2) ifort/11/11.1.073 5) profile/user/1.0		2) ifort/11/11.1.073 5) profile/user/1.0
	3) mkl/10.3.10		3) mkl/10.3.10
	: '''Note''': ~~This~~ is done ''before'' <code>.bashrc</code> ~~processing~~.		: '''Note''': These is done by the system ''before'' processing <code>.bashrc</code>.

	== Module conventions on Carbon ==		== Module conventions on Carbon ==

2016-11-17T22:56:16Z

Default modules being loaded

← Older revision		Revision as of 22:56, November 17, 2016
Line 11:		Line 11:
	2) ifort/11/11.1.073 5) profile/user/1.0		2) ifort/11/11.1.073 5) profile/user/1.0
	3) mkl/10.3.10		3) mkl/10.3.10
	: ~~Internally, this~~ is done ''before'' <code>.bashrc</code> processing~~, by the module <code>profile/user</code>~~.		: '''Note''': This is done ''before'' <code>.bashrc</code> processing.

	== Module conventions on Carbon ==		== Module conventions on Carbon ==

2016-11-17T22:54:20Z

@@ Line 3: / Line 3: @@
 * Package directories are named <code>''' ''name-version-build'' '''</code>, e.g. <code>/opt/soft/jmol-12.1.37-1</code>.
 * Module names are organized by a mostly version-less name, with the version following after a slash: <code>''' ''name/version-build'' '''</code>. Using the <code>''name''</code> component alone is possible and will select a default version for <code>module ''subcommand''</code> to act upon. Some packages do carry a major version number in their name, notably fftw3 and vasp5.
-* <code>module help</code> briefly describes a package, gives its version number (in the module path) and will usually contain a link to its home page.
   $ '''module help jmol'''
@@ Line 16: / Line 28: @@
   	http://wiki.jmol.org/
 === Package home directory organization ===
 A package directory usually contains Unix-style subdirectories for the various files, which the modulefile usually automatically integrates into your user environment by means of standard environment variables.
@@ Line 35: / Line 37: @@
 === Environment variable for package home directory ===
 Most modules will set a convenience variable <code>''' $''NAME''_HOME'''</code> which points to the package's toplevel directory.
 Dashes in the package name are converted to underscores in the environment variable.

2016-11-17T22:52:36Z

← Older revision		Revision as of 22:52, November 17, 2016
Line 16:		Line 16:
	http://wiki.jmol.org/		http://wiki.jmol.org/

	~~== Conventions on Carbon ==~~
	=== Default modules being loaded ===		=== Default modules being loaded ===
	The following ~~default~~ modules are loaded:		The following modules are loaded by default for all users:
	$ '''module list'''		$ '''module list'''
	Currently Loaded Modulefiles:		Currently Loaded Modulefiles:
Line 26:		Line 25:
	: Internally, this is done ''before'' <code>.bashrc</code> processing, by the module <code>profile/user</code>.		: Internally, this is done ''before'' <code>.bashrc</code> processing, by the module <code>profile/user</code>.

			== Module conventions on Carbon ==
	=== Package home directory organization ===		=== Package home directory organization ===
	A package directory usually contains Unix-style subdirectories for the various files, which the modulefile usually automatically integrates into your user environment by means of standard environment variables.		A package directory usually contains Unix-style subdirectories for the various files, which the modulefile usually automatically integrates into your user environment by means of standard environment variables.

2016-11-17T22:51:20Z

Conventions on Carbon

← Older revision		Revision as of 22:51, November 17, 2016
Line 17:		Line 17:

	== Conventions on Carbon ==		== Conventions on Carbon ==
			=== Default modules being loaded ===
			The following default modules are loaded:
			$ '''module list'''
			Currently Loaded Modulefiles:
			1) icc/11/11.1.073 4) openmpi/1.4.5-intel11-2
			2) ifort/11/11.1.073 5) profile/user/1.0
			3) mkl/10.3.10
			: Internally, this is done ''before'' <code>.bashrc</code> processing, by the module <code>profile/user</code>.

	=== Package home directory organization ===		=== Package home directory organization ===
	A package directory usually contains Unix-style subdirectories for the various files, which the modulefile usually automatically integrates into your user environment by means of standard environment variables.		A package directory usually contains Unix-style subdirectories for the various files, which the modulefile usually automatically integrates into your user environment by means of standard environment variables.

2016-11-17T22:46:01Z

Module naming scheme

@@ Line 15: / Line 15: @@
   	http://jmol.sourceforge.net/
   	http://wiki.jmol.org/
 == Conventions on Carbon ==

2016-11-17T22:44:37Z

← Older revision		Revision as of 22:44, November 17, 2016
Line 1:		Line 1:
	== Module naming ==		== Module naming scheme ==
	* Most application software is installed under <code>'''/opt/soft'''</code>		* Most application software is installed under <code>'''/opt/soft'''</code>
	* Package directories are named <code>''' ''name-version-build'' '''</code>, e.g. <code>/opt/soft/jmol-12.1.37-1</code>.		* Package directories are named <code>''' ''name-version-build'' '''</code>, e.g. <code>/opt/soft/jmol-12.1.37-1</code>.