HPC/Module naming scheme 2016

Configuration files used

You have files: .bashrc and …		Remark	CentOS-5 uses		CentOS-6 uses
			module names	files	module names	files
–	–	Current situation	old	.bashrc only	new	.bashrc only
–	.modules-carbon-6	Switch over, recommended	new	.modules-carbon-6 and .bashrc		.modules-carbon-6 and .bashrc
.modules-carbon-5	–	Avoid!	old	.modules-carbon-5 and .bashrc		.bashrc only (.*-5 file is ignored)
.modules-carbon-5	.modules-carbon-6	For advanced users	old	.modules-carbon-5 and .bashrc		.modules-carbon-6 and .bashrc

Configuration steps

CentOS-independent module selection (recommended)

To switch over to new hierarchical module names on both CentOS releases it's easiest to continue making all your module choices in ~/.bashrc, but you have to signal on the older platform to use the new module style:

1. Create a customization file for new names, but leave it empty (you'll configure your choices in the next step). Use the command:

   touch ~/.modules-carbon-6
   

2. Edit your .bashrc file and update your module selections as follows:
   • Remove version numbers from module names of the old-style packagename/version, leaving only packagename. This is the recommended approach, as you will automatically benefit from future versions.
   • To insist on a specific version for a pacakge affected by the new-style names, use the form packagename/compilername/version or packagename/mpiname/compilername/version as appropriate. To see available flavors and versions, separately run the command module avail packagename.

CentOS-dependent module selection

If you encounter difficulties with making your module selection work in both CentOS-5 and CentOS-6, use separate configurations:

1. Move all your previous module commands from .bashrc to ~/.modules-carbon-5, where they will apply only on CentOS-5.
2. Place all your module selections for CentOS-6 in ~/.modules-carbon-6. Get started using the contents of the .*-5 version.