Difference between revisions of "Modules"

Jump to navigation Jump to search
Line 5: Line 5:
==Basic usage==
==Basic usage==
Please see [[Modules Basic Usage]] for a practical introduction to using ''modules'' at the UF HPC Center.
Please see ''[[Modules Basic Usage]]'' for a practical introduction to using ''modules'' at the UF HPC Center.
==Personal modules==
==Personal modules==

Revision as of 16:41, 10 August 2012


Setting and maintaining your environment while running a large number of diverse software applications with different requirements can be a daunting task. The UF HPC Center is adopting the modules system developed by Robert McLay at the Texas Advanced Computing Center (TACC) in order to ease the complexity of this process and relieve users of this burden.

Basic usage

Please see Modules Basic Usage for a practical introduction to using modules at the UF HPC Center.

Personal modules

You can write and use your own modulefiles. The procedure for making them available is very simple. Load the "personal" module to have a "$HOME/.modules" directory automatically created and the environment set up for using it to house your personal modulefile sub-directories. For example, once the "personal" module is loaded you can create a "myapp" sub-directory under "$HOME/.modules" and put a modulefile named version.lua, like "1.0.lua" for instance, into that directory to make the "myapp/1.0" module available.

Mpi-selector Command Deprecated

With the introduction of modules, mpi-selector has been deprecated. If you have been using mpi-selector to set up your MPI environment, please see From mpi-selector to environment modules for more information.


To request help with using modules or installation of new module enabled application please file a support request or if necessary please send us an email.

Upstream Documentation

Those who would like to learn as much as possible about lmod can use the documentation written by the Lmod author.