Summary

The EAS x86 cluster is a 9 node cluster of Athlon 2.166 Mhz nodes for parallel and serial computation. The front end to this cluster is bora.eas.slu.edu.

E-mail support eas slu edu

EAS PC Cluster User Guide

News:

  • No news is good news...


This page is a bare-bones user manual for the PCP cluster. Please send comments about missing, incorrect or confusing information to support eas slu edu /P>

General Overview

The EAS cluster1 is a 9-node PC cluster for parallel (MPI) and serial (task-farm) computation. The front end, bora.eas.slu.edu, is used for interactive work (e.g., editing, compiling, and submitting jobs). The compute nodes (b01, b02, ..., b08) are managed through the Portable Batch System (PBS) and you should not log into them.

Login access to bora should be through ssh. Insecure access through telnet or rsh is not allowed. Security is an important concern on the x86 cluster (as it is on all EAS systems) so please be careful. Please read the EAS policy on passwords. Login access to the compute nodes should be through PBS only.

The default login shell is bash.

The standard environment setup is in /home/defaults/bashrc. Your .bashrc file should already include this file. This should allow you to do everything described here without modifying your environment. All man pages should also be accessible by default. When software changes on the cluster, we will automatically update the global bashrc to reflect the changes. If you don't source the global file, your programs may stop working. If you find that we missed something that should be in the global file, please let us know rather than changing just your own environment.


The cluster is running the PGI CDK Cluster Development Kit It includes pghpf, pgf90, pgf77, pgc++, pgcc, pgdbg, and pgprof.

Online documentation is available via netscape

under the URL file:/usr/pgi/doc/index.htm



Compiling Code with MPICH

We do not provide the mpi(compiler) scripts. There are too many ways that these can cause confusion. There is an installed version on mpich

that was provided with the PGI CDK. To use that you add the library name to the compile line or the makefile library line.

An example from the mpihello program:

pgf77 -o mpihello mpihello.f -lfmpich -lmpich



The fmpich library provides the fortran hooks to the mpich library.


Description of node attributes

Node attributes on the EAS cluster are all the same:

512 MB RAM

1200 MB swap

1 GB/sec Ethernet




Software available on the cluster:

This rest of this page provides a brief introduction to the software available on the cluster. Some of this software is part of the Cluster Development Kit (CDK) and some is specific to the EAS cluster. EAS-specific software is labelled (EAS).

Unless otherwise noted, the software can be accessed by adding /usr/local/pkg/[package-name]/bin to your $PATH variable. Source code, if any, can be found in /usr/local/src/[package-name].

For packages available in multiple versions, /usr/local/{src,pkg}/[package-name] is usually a symbolic link to the most recent version. Other versions can usually be accessed directly using the package name with the appropriate version number appended (e.g. /usr/local/pkg/package-3.1).

Terms of use on the cluster

Users are guaranteed no level of service on this cluster. This cluster is a development system. We cannot make any guarantees to cluster availability. We use this cluster to test device drivers and operating system software, so you should expect it to be a bit unstable. We do, occasionally, lose user data and user jobs. We will sometimes shut the cluster down without notification. If you need results for a conference tomorrow, or need your data backed up nightly, you should use another system. Last modified: 30 Sep 2002
Questions/comments to: support eas slu edu