Skip to main content


Versions and Availability


Module Names for wq on smic
Machine Version Module Name
smic 264 wq/264
smic 272 wq/272

▶ Module FAQ?

The information here is applicable to LSU HPC and LONI systems.



A user may choose between using /bin/bash and /bin/tcsh. Details about each shell follows.


System resource file: /etc/profile

When one access the shell, the following user files are read in if they exist (in order):

  1. ~/.bash_profile (anything sent to STDOUT or STDERR will cause things like rsync to break)
  2. ~/.bashrc (interactive login only)
  3. ~/.profile

When a user logs out of an interactive session, the file ~/.bash_logout is executed if it exists.

The default value of the environmental variable, PATH, is set automatically using Modules. See below for more information.


The file ~/.cshrc is used to customize the user's environment if his login shell is /bin/tcsh.


Modules is a utility which helps users manage the complex business of setting up their shell environment in the face of potentially conflicting application versions and libraries.

Default Setup

When a user logs in, the system looks for a file named .modules in their home directory. This file contains module commands to set up the initial shell environment.

Viewing Available Modules

The command

$ module avail

displays a list of all the modules available. The list will look something like:

--- some stuff deleted ---

---------------- /usr/local/packages/Modules/modulefiles/admin -----------------
EasyBuild/1.11.1       GCC/4.9.0              INTEL-140-MPICH/3.1.1
EasyBuild/1.13.0       INTEL/14.0.2           INTEL-140-MVAPICH2/2.0
--- some stuff deleted ---

The module names take the form appname/version/compiler, providing the application name, the version, and information about how it was compiled (if needed).

Managing Modules

Besides avail, there are other basic module commands to use for manipulating the environment. These include:

add/load mod1 mod2 ... modn . . . Add modules
rm/unload mod1 mod2 ... modn  . . Remove modules
switch/swap mod . . . . . . . . . Switch or swap one module for another
display/show  . . . . . . . . . . List modules loaded in the environment
avail . . . . . . . . . . . . . . List available module names
whatis mod1 mod2 ... modn . . . . Describe listed modules

The -h option to module will list all available commands.

About the Software

WQ is a support tool that creates supports a dispatcher/worker model of distributed computing. Serial, multi-thread OpenMP, and small multi-process MPI are supported. Tasks are defined by input file names, or other command line strings, contained in an input file - one line per task. To use, you'll need the PBS template ($WQ_PBS_TEMPLATE). Make a copy and edit to fit your application needs. A sample task script ($WQ_EXAMPLE_TASK) and user documention ($WQ_DOC) are also available.


  • Create a file with each line defining a file name, command line, or whatever the task script/program requires.
  • Create a task script, or command, that runs correctly when given a line from the above file. The variable WQ_EXAMPLE_TASK points to a sample script file.
  • Test the task script manually, just to be sure.
  • Make a copy of the file pointed to by WQ_PBS_TEMPLATE, and update the settings to suite your needs (user name, allocation code, other options.)
  • Submit the PBS script as usual.


  • WQ_DOCS environment variable that points to the full user manual in PDF form.


  • WQ_DOCS environment variable that points to the full user manual in PDF form.

Last modified: September 10 2020 11:58:50.