AASPI Software Computational EnvironmentTim Kwiatkowski

Welcome Consortium MembersNovember 18, 2008

• Hardware• Clusters• Multiprocessor / Multi-core

• Software• Computational Environment

• Compilers• Libraries• Graphics

• Software Design• Directory Layout

• The Future

Overview

HardwareClusters

The AASPI Software was originallydesigned to run on U**X/Linux clusters using MPI (Message Passing Interface).

Large Granularity

No need for expensive interconnects.Gigabit Ethernet is sufficient.

Depending on the size of the cluster, can be difficult to administer.

HardwareMultiprocessor / Multi-core

•Newer multi-core processors have•become available

•Currently no explicit multi-threading.

•MPI using “Loopback” Communication

•Simpler to administer

•Can be grown into a cluster

HardwareOur Current Resources

Older Resourcesdiamond - Sun Enterprise 450,

2ea. Sun Blade 10002ea. Sun Blade 2000

corundum - Dual CPU 2.4GHz Xeon 5.2 TB storage

Newer ResourcesOpal - Dual Quad-core 3.0GHz Xeon 16 GB, 15 TB storageRuby – Quad Quad-core 1.6 GHz Xeon 32 GB, 1 TB storage

22 Windows XP 64bit PC/Workstations.

HardwareOur Current Resources – Cluster Resources

Muntu1 management node, 1 head node, 16 compute nodes. Each node: 3.06 GHz Dual processor , 4GB RAM. Total disk storage: ~2TB

OSCER (Oklahoma Supercomputing Center for Education & Research) As a whole: 531 User Accessible Nodes, 120TB Fast scratch storage, 34450 GFlop peak, 28030 GFlop sustained.

Our own dedicated OSCER nodes / storageDual Quad core (3 ea. 2.33 GHz, 3ea. 2.66 GHz) 16GB RAMStorage node - Dual Quad core 2.33GHz, 16GB RAM, 18TB disk storage.

www.oscer.ou.edu

HardwareRecommendations

What type of hardware do I need to run the AASPI software?

The short answer: It depends.

Entry level suggestion:Dual or Quad Quad-core 3.0GHz+2GB /core>2 TB disk capacity

SoftwareEnvironment − OS

Operating SystemAs shipped, we have chosen to pre-compile the AASPI software. This should work on most Redhat 4 Release 4 and higher installations.

Some needed packagesblas, lapack, libf2c, bzip2-libs,zlib, X11 packages for running the GUI, Mesa-libGL, Mesa-libGLU

SoftwareEnvironment − Compilers

We have chosen to pre-compile the AASPI software to make your life easier. However, IF you are compiling on your own…

Required: A good Fortran90 compiler such as the Portland Group Fortran compiler or the Intel Fortran 90/95 compiler. We use the Intel Fortran compiler.

Required: A good C/C++ compiler. GCC is fine.

Required: Patience!

Most of the compiling issues come from the 3rd party packages!

SoftwareEnvironment − Libraries

The software depends on several external libraries:

Seismic Unix (Center for Wave Phenomena - Colorado School of Mines)SEPlib (Stanford Exploration Project)

OpenMPI (We have used MPICH in the past)FFTW (Version 2 at the present time)Lapack & BLAS The FOX Toolkit (GUI interface and seismic data display)

SoftwareEnvironment − Graphics

Now we have a GUI interface.It’s X-Windows based.How do we use it?

Some SolutionsUse a desktop Linux workstation.Use a MacThinAnywhereVNCHummingbird ExceedXmingCygwin

SoftwareDesign Practices/Goals

• Use modern programming languages• Fortran 90/95• C/C++

• Modular Design• Maximize code re-use• Use Fortran 90/95 modules/interfaces• Use C++ classes/template programming

• Libraries• Organize processes/functions into logical, reusable libraries

SoftwareLayout

AASPI

ext_lib

ext_rpm

ext_src

Include

man

scripts

Precompiled binaries

Non-AASPI package compiled libraries

Non-AASPI RPMS

Non-AASPI packages - source

AASPI include files (along with others)

AASPI man pages

AASPI source code

Scripts – program wrappers and utilities

AASPI libraries & other shared libraries

The Future

Madagascar (RSF) – You’ve heard this one before.

MS Windows? – Perhaps… All of our core code should be multiplatform. MPI is available on Windows platforms via cluster services. The main issues are with our dependencies: Seismic UNIX and SEPlib.

AASPI Software Computational EnvironmentTim Kwiatkowski

Thank You!

Questions?