Skip to main content



parpack, or Parallel ARPACK, is a library of routines for solving large-scale eigenvalue problems.

Version and Availability

Softenv Keys for parpack on painter
Machine Version Softenv Key
painter 96 +parpack-96-intel-11.1-mvapich-1.1
painter 96 +parpack-96-intel-11.1-mvapich2-1.4
▶ Display Softenv Keys for parpack all clusters
Machine Version Softenv Key
eric 96 +parpack-96-intel-11.1-mvapich-1.1
eric 96 +parpack-96-intel-11.1-mvapich2-1.4
qb 96 +parpack-96-intel-11.1-mvapich-1.1
qb 96 +parpack-96-intel-11.1-mvapich2-1.4
oliver 96 +parpack-96-intel-11.1-mvapich-1.1
oliver 96 +parpack-96-intel-11.1-mvapich2-1.4
louie 96 +parpack-96-intel-11.1-mvapich-1.1
louie 96 +parpack-96-intel-11.1-mvapich2-1.4
poseidon 96 +parpack-96-intel-11.1-mvapich-1.1
poseidon 96 +parpack-96-intel-11.1-mvapich2-1.4
painter 96 +parpack-96-intel-11.1-mvapich-1.1
painter 96 +parpack-96-intel-11.1-mvapich2-1.4
philip 96 +parpack-96-intel-11.1-mpich-1.2.7p1
▶ Softenv FAQ?

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


SoftEnv is a utility that is supposed to help users manage complex user environments with potentially conflicting application versions and libraries.

System Default Path

When a user logs in, the system /etc/profile or /etc/csh.cshrc (depending on login shell, and mirrored from csm:/cfmroot/etc/profile) calls /usr/local/packages/softenv-1.6.2/bin/ to set up the default path via the SoftEnv database.

SoftEnv looks for a user's ~/.soft file and updates the variables and paths accordingly.

Viewing Available Packages

Using the softenv command, a user may view the list of available packages. Currently, it can not be ensured that the packages shown are actually available or working on the particular machine. Every attempt is made to present an identical environment on all of the LONI clusters, but sometimes this is not the case.


$ softenv
These are the macros available:
*   @default
These are the keywords explicitly available:
+amber-8                       Applications: 'Amber', version: 8 Amber is a
+apache-ant-1.6.5              Ant, Java based XML make system version: 1.6.
+charm-5.9                     Applications: 'Charm++', version: 5.9 Charm++
+default                       this is the default environment...nukes /etc/
+essl-4.2                      Libraries: 'ESSL', version: 4.2 ESSL is a sta
+gaussian-03                   Applications: 'Gaussian', version: 03 Gaussia
Listing of Available Packages

See Packages Available via SoftEnv on LSU HPC and LONI.

For a more accurate, up to date list, use the softenv command.


Currently there are some caveats to using this tool.

  1. packages might be out of sync between what is listed and what is actually available
  2. resoft and soft utilities are not; to update the environment for now, log out and login after modifying the ~/.soft file.

softenv is available on all LSU HPC and LONI clusters to all users in both interactive login sessions (i.e., just logging into the machine) and the batch environment created by the PBS job scheduler on Linux clusters and by loadleveler on AIX clusters..

Packages Availability

This information can be viewed using the softenv command:

% softenv
Managing Environment with SoftEnv

The file ~/.soft in the user's home directory is where the different packages are managed. Add the +keyword into your .soft file. For instance, ff one wants to add the Amber Molecular Dynamics package into their environment, the end of the .soft file should look like this:



To update the environment after modifying this file, one simply uses the resoft command:

% resoft


The installations include example source files under:


There may be versions compiled with different MPI libraries, so adjust the above accordingly. The makefiles should be modified to point to the right locations:


include ../../


 /usr/local/packages/parpack/96/intel-11.1-mvapich-1.1/lib/parpack_MPI-LINUX.a \
 /home/packages/arpack/96/intel-11.1/lib/libarpack_LINUX.a \
 -L/home/packages/lapack/3.2/intel-11.1-mvapich-1.1/lib -lblas -llapack 

This also gives you an idea of the libraries you'll need to link in.


  • The ARPACK User Manual Except for running in parallel, there should be no difference between the two libraries.

Last modified: March 07 2013 12:30:04.