Research:SalsaBuildInstructions

From Astronomy Facility Wiki

Specific instructions for Research:Salsa builds on various parallel architectures are documented below. Prefered Charm++ build options are noted. If the machine corresponds to a NSF Teragrid facility, the particular machine will be noted.

Contents 1 SGI Altix (sharks at UW) 2 Cray XT3 (Bigben at PSC) 3 Dell Dual Core Linux cluster (lonestar at TACC) 3.1 mpi-linux-amd64 3.1.1 Running

SGI Altix (sharks at UW)

Note that charm++ has to be built with "build charm++ net-linux-ia64 -O2". Don't use a higher optimization level because of a bug in the GNU C compiler, gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-47).

Cray XT3 (Bigben at PSC)

Unfortunately, the XT3 does not support python, because the OS on the nodes don't support dynamic libraries.

Dell Dual Core Linux cluster (lonestar at TACC)

mpi-linux-amd64

Charm should be built with MPICC=mpicc MPICXX=mpiCC build charm++ mpi-linux-amd64 -O3 -xT

When building the xerces-c library, "autoconf" complains about not being able to lock a file. Ignore this and proceed with the "runConfigure" command.

Otherwise, the build of Salsa is straightforward.

• However, as with Research:ChaNGa, an FPE error occurs unless the system memory allocator is used. Edit the Makefile to add -memory os to the LDFLAGS definition (but before the '#', which is a comment character).

Running

TACC uses LSF, so a typical job script looks like:

bsub -q normal -n $NPROC -W 0:30 << EOF
#!/bin/sh -x
ibrun $HOME/bin/ResolutionServer ++server ++server-port 16512 +stacksize 1000000 simlist
EOF

Note that you are not allowed to run in interactive mode. So to find out the IP address of the head node in order to connect (and yes, you need to set up a tunnel to forward connections, see the Robert help in Research:Salsa for details) you need to use bpeek.