Skip to main content


Versions and Availability


Module Names for paraview on qb2
Machine Version Module Name
qb2 4.3.1 paraview/4.3.1/INTEL-140-MVAPICH2-2.0

▶ 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

ParaView is an open-source, multi-platform data analysis and visualization application.


Sample usage for remote visualization:

  1. Start ParaView server pvserver on the cluster using compute node, do *not* start pvserver from the head node, e.g.:
    qsub -I -l nodes=1:ppn=20,walltime=1:00:00 -q workq -A your_allocation_name
    After you get the interactive session, start your pvserver from the *compute node*, e.g. smicXXX:
    module load paraview/4.3.1/INTEL-140-MVAPICH2-2.0
    mpirun -np 8 pvserver --server-port=11111
    *For unknown reason you might need to limit the number of pvserver process to 8
  2. Establish an SSH tunnel:
    Use the following command from your *local* terminal, note that the compute node number smicXXX should be the name of your compute node:
    ssh -L11111:smicXXX:11111 -N
    Type your password and leave the terminal open.
  3. Connect to the remote server using ParaView on your desktop:
    Start the same version of paraview as installed on cluster, e.g. Pavaview 4.3.1 from your *local* terminal and use File > Connect to the forwarded localhost port.

Please refer to Resources section for more detailed usage information.


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