Using modules

From HP-SEE Wiki

You do not have permission to edit this page, for the following reason:

You can view and copy the source of this page:

'' Section contributed by IICT-BAS '' Setting up better software environment can be done with modules, which are user interface to the Module packages, because they perform dynamic modification of user’s environment via modulefiles. The module alias or function executes the modulecmd program and has the shell evaluate the command's output. The first argument to modulecmd specifies the type of shell. Modulefiles are written in the Tcl and are interpreted by the modulecmd program via the module user interface. Each modulefile contains the information needed to configure the shell for an application. A typical modulefile is a simple bit of code that set or add entries to the PATH, MANPATH, or other environment variables, etc. modulefiles may be shared by many users on a system and users may have their own collection to supplement or replace the shared modulefiles. Modulefiles can be loaded, unloaded, or switched on-the-fly while the user is working; and can be used to implement site policies regarding the access and use of applications. The modulefiles are added to and removed from the current environment by the user. The environment changes contained in a modulefile can be summarized through the module command as well. If no arguments are given, a summary of the module usage and sub-commands are shown. The action for the module command to take is described by the sub-command and its associated arguments. Users of HP-SEE project can start by loading the hpsee module. All modules that were specifically tuned to the needs of HP-SEE project also start with hpsee, for example hpsee-blas etc. '''For more information:''' http://wiki.hp-see.eu/index.php/Module_framework ''' Resources ''' http://modules.sourceforge.net/index.html

Return to Using modules.