- Version: version number of software
- Path: path of the software
- Variables: Relevant shell variables that are pre-set or need to be set
- Documentation: Location of documentation
- Function: Description of the software's purpose/function
PVM
- 3.4.5
- Standard system paths
- Set automatically: PVM_ROOT=/usr/share/pvm3
Set automatically: PVM_ARCH=`$PVM_ROOT/lib/pvmgetarch`
Set automatically: PVM_RSH=/usr/bin/ssh - /usr/share/doc/pvm-3.4.5
- PVM3 (Parallel Virtual Machine) is a library and daemon that allows distributed processing environments to be constructed on heterogeneous machines and architectures.
- 1.2.5
- /usr/bin/xpvm
- Help files are available from within the gui
http://www.netlib.org/utk/icl/xpvm/xpvm.html - Xpvm is a TCL/TK based tool that allows full manageability of the PVM cluster as well as the ability to monitor cluster performance.
- 7.1.2
- Binaries are in system paths; Libraries are in /usr/lib64/lam ; Include files are in /usr/include/lam and /usr/include/lam/64
- Set automatically: LAMRSH=/usr/bin/ssh
- /usr/share/doc/lam-7.1.2
http://www.lam-mpi.org/ - LAM (Local Area Multicomputer) is an Message-Passing Interface (MPI)
programming environment and development system for heterogeneous
computers on a network. With LAM/MPI, a dedicated cluster or an
existing network computing infrastructure can act as one parallel
computer to solve one problem. LAM/MPI is considered to be "cluster
friendly" because it offers daemon-based process startup/control as
well as fast client-to-client message passing protocols. LAM/MPI can
use TCP/IP and/or shared memory for message passing (different RPMs
are supplied for this -- see the main LAM website at
http://www.lam-mpi.org/ for details).
LAM features a full implementation of MPI version 1 (with the exception that LAM does not support cancelling of sends), and much of version 2. Compliant applications are source code portable between LAM and any other implementation of MPI. In addition to meeting the standard, LAM/MPI offers extensive monitoring capabilities to support debugging. Monitoring happens on two levels: On one level, LAM/MPI has the hooks to allow a snapshot of a process and message status to be taken at any time during an application run. The status includes all aspects of synchronization plus datatype map/signature, communicator group membership and message contents (see the XMPI application on the main LAM website). On the second level, the MPI library can produce a cumulative record of communication, which can be visualized either at runtime or post-mortem.
- 1.2.6
- /opt/mpich/
- User set: PATH=/opt/mpich/ch-p4/bin:$PATH
User set: LD_LIBRARY_PATH=/opt/mpich/ch-p4/lib:$LD_LIBRARY_PATH
User set: You have to link the libraries in the above path via -L/opt/mpich/ch-p4/lib - /opt/share/doc/mpich
/opt/share/doc/mpich-1.2.6
/opt/share/doc/mpich-devel-1.2.6
http://www-unix.mcs.anl.gov/mpi/mpich/ - MPICH is a freely available, portable implementation of MPI, the Standard for message-passing libraries.
- 9.1
- /cluster/intel_cc_x86_64
-
Set automatically: PATH=$PATH:/cluster/intel_cc_x86_64/bin
Set automatically: IA32ROOT=/cluster/intel_cc_x86_64 - /cluster/intel_cc_x86_64/doc
- C/C++ Compiler
- 9.1
- /cluster/intel_cc_386
-
User set: PATH=$PATH:/cluster/intel_cc_386/bin
User set: IA32ROOT=/cluster/intel_cc_386 - /cluster/intel_cc_386/doc
- C/C++ Compiler
- 9.1
- /cluster/intel_fc_x86_64
-
Set automatically: PATH=$PATH:/cluster/intel_fc_x86_64/bin
Set automatically: FPATH=/cluster/intel_fc_x86_64/include
LD_LIBRARY_PATH=/cluster/intel_fc_x86_64/lib - /cluster/intel_fc_x86_64/doc
- Fortran Compiler
- 9.1
- /cluster/intel_fc_386
-
User set: PATH=$PATH:/cluster/intel_fc_386/bin
User set: FPATH=/cluster/intel_fc_386/include
User set: LD_LIBRARY_PATH=/cluster/intel_fc_386/lib - /cluster/intel_fc_386/doc
- Fortran Compiler
- 9.1
- /cluster/intel_idb_x86_64
- Set automatically: PATH=$PATH:/cluster/intel_idb_x86_64/bin
- /cluster/intel_idb_x86_64/doc
- The debugger provides support (at various levels, depending on the compiler version) for debugging programs written in C, C++, and Fortran (77, 90 and 95).
- 1.5
- /usr/java/jdk1.5.0_11
-
At the least, the PATH will need to be set, the other variables that may need to be set will
be dependent on the software using them (JAVA_HOME is a common one).
User set: PATH=/usr/java/jdk1.5.0_11/bin:$PATH - http://java.sun.com/docs/index.html
- This is the Sun Java Software Development Kit for 1.5
- 6.6.10
- /cluster/condor
- Still investigating
- Manual
- Condor is a cluster job processing suite. It is used as a job engine for the grid software. Reading the manual is probably your best bet for understanding what it does.
- 2.4.1
- /usr/bin/R
- Automatically set: R_LIBS=/cluster/statsoft/Rlibs64
Automatically set: PATH="$PATH:/cluster/statsoft/bin" - /usr/share/doc/R-2.4.1
/usr/share/doc/R-devel-2.4.1
- R is a free software environment for statistical computing and graphics.
- 3.40
- /usr/bin/oxl
/usr/local/lib/ox-3.40 - None that I am aware of
- Please see http://www.doornik.com/ox/index.html for documentation
- Ox is an object-oriented matrix programming language with a comprehensive mathematical and statistical function library.The Console (command line) versions may be used freely for academic research and teaching purposes only...Failure to cite the use of Ox in published work may result in loss of the right to use the free version, and an invoice at the full commercial price. Please see http://www.doornik.com/ox/index.html?content=/ox/oxcite.html for further requirements.
- TeX (Web2C 7.4.5) 3.14159
kpathsea version 3.4.5 - System paths
- No custom environment variables are needed for running the installed TeX/LaTeX environment
- There are a variety of sources for learning/using TeX/LaTex
- TeX, and associated programs such as LaTeX, form a system for computer typesetting, for placing text on a page. (Pronounce the name "tech".) It is well known for its abilities with the most difficult typesetting jobs: mathematical and scientific text, long and intricate documents, and multilingual works.
- 1.1
- LAM: /cluster/blacs-lam-1.1_x86_64/lib
PVM: /cluster/blacs-pvm-1.1_x86_64/lib
MPICH: /cluster/blacs-mpich-1.1_x86_64/lib - When compiling code you'll need to use -L followed by the path above which is dependent on your choice of parallel machine software.
- http://www.netlib.org/blacs/
- The BLACS (Basic Linear Algebra Communication Subprograms) project is an ongoing investigation whose purpose is to create a linear algebra oriented message passing interface that may be implemented efficiently and uniformly across a large range of distributed memory platforms.
- 1.1
- LAM: /cluster/scalapack-lam-1.7.4_x86_64/lib
PVM: /cluster/scalapack-pvm-1.7.4_x86_64/lib
MPICH: /cluster/scalapack-mpich-1.7.4_x86_64/lib - When compiling code you'll need to use -L followed by the path above which is dependent on your choice of parallel machine software.
- http://www.netlib.org/scalapack/
- The ScaLAPACK (or Scalable LAPACK) library includes a subset of LAPACK routines redesigned
for distributed memory MIMD parallel computers. It is currently written in a
Single-Program-Multiple-Data style using explicit message
passing for interprocessor communication. It assumes
matrices are laid out in a two-dimensional block cyclic
decomposition.
ScaLAPACK is designed for heterogeneous computing and is portable on any computer that supports MPI or PVM.
Like LAPACK, the ScaLAPACK routines are based on block-partitioned algorithms in order to minimize the frequency of data movement between different levels of the memory hierarchy. (For such machines, the memory hierarchy includes the off-processor memory of other processors, in addition to the hierarchy of registers, cache, and local memory on each processor.) The fundamental building blocks of the ScaLAPACK library are distributed memory versions (PBLAS) of the Level 1, 2 and 3 BLAS, and a set of Basic Linear Algebra Communication Subprograms (BLACS) for communication tasks that arise frequently in parallel linear algebra computations. In the ScaLAPACK routines, all interprocessor communication occurs within the PBLAS and the BLACS. One of the design goals of ScaLAPACK was to have the ScaLAPACK routines resemble their LAPACK equivalents as much as possible.
