You are here: Home Documentation How-To LifeV @ epfl (malc1)

LifeV @ epfl (malc1)

In this page we try to give short hints on how to start compiling the LifeV library and run a simple test on a cluster

# connect to cluster malc1
ssh -X -l fgelsomi malc1


# Only once
#==========

# allow rsh connections inside the cluster:
# create a file ~/.rhosts


cd LIFEV/

# exctract lifev sources, release "lifev-parallel "
# into directory "lifev-parallel"
cvs -d :ext:fgelsomi@cmcsforge.epfl.ch:/cvsroot/lifev co \
-d lifev-parallel -r lifev-parallel lifev



# Only when major changes in the library:
#========================================
cd ~/LIFEV/lifev-parallel
make -f Makefile.cvs


# Create directory for binaries.
# for example optimized versions:
mkdir opt3
cd opt3
../configure --prefix=/home/fgelsomi/local/opt3/lifev-parallel --with-trilinos=/home/deparis/local/opt3/trilinos-8 --disable-shared --enable-static --enable-opt3 GCC=gcc GXX=g++ F77=gfortran


# Compiling the library:
#=======================
cd ~/LIFEV/lifev-parallel/opt3/life
# -j4 means: use 4 processes, since this computer has many CPUs
make -j4


# Compiling one first example in the testsuite
#=============================================

cd ~/LIFEV/lifev-parallel/opt3/testsuite/test_ethiersteinman

make -j4 check
make link
# Hint: use emacs, open the directory test_ethiersteinman and run compile:
# ESC-x compile
# and give the command: make -j4 check


# modify the data file according to your needs

# then submit a job:
====================
# get a template file for job submitting, e.g.: runTest.sh
# modify it to your needs

qsub runTest.sh
qstat -a

# kill a job:
qdel "job number"





### examples of postprocessing:

# total iteration time
grep "Total iteration time" runTest.16x16.P1P1.8.out

# time to compute stabilizing terms
grep "myFaces" runTest.16x16.P1P1.8.out

# time to compute the preconditioner
grep "Computing the precond" runTest.16x16.P1P1.8.out

# Estimated condition number
grep "Estimated condition number" runTest.16x16.P1P1.8.out

#total numer of iterations iterations:
grep "total iterations:" runTest.16x16.P1P1.8.out
Document Actions
« August 2010 »
August
MoTuWeThFrSaSu
1
2345678
9101112131415
16171819202122
23242526272829
3031