Skip to Content.
Sympa Menu

forum - Re: [abinit-forum] parallel tune

forum@abinit.org

Subject: The ABINIT Users Mailing List ( CLOSED )

List archive

Re: [abinit-forum] parallel tune


Chronological Thread 
  • From: Alain Jacques <ajs.jacques@gmail.com>
  • To: forum@abinit.org
  • Subject: Re: [abinit-forum] parallel tune
  • Date: Fri, 26 Dec 2008 16:40:18 +0100
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding:from; b=MvIKtNFO6TcsvJh8aG5we7xe5xbB6kZoGQaa5BYp7/kE4nl2N6SLcwU8zvZ+MZUrrs 5Yrm/NVbhTJoZxCCqPc8GHHblDMzdciHZvQndI4+6QZ82pjEk5Y46wvTeK06qNZafhO4 Sfvlx3lTguFj23bdP2NCrkzQylOCpZGpC8dqA=


Hello again,

Physics fany wrote:
281680.34637.qm@web59901.mail.ac4.yahoo.com" type="cite">


1. opensuse comes with gcc-4.3.2 (?) yes, it does.
2. but what kind of MPI implementation are you using? openmpi-1.2.8

Nice. It is the system I am using for development - abinit 5.6.4 builds nicely on it, including parallelization. I realized that you work with version 5.4.4. 5.6.4 is out and is the recommended production release. But 5.4.4 should work

281680.34637.qm@web59901.mail.ac4.yahoo.com" type="cite">
3. A copy of your abinit configure or the head of the config.log would be useful. Please find it below.
281680.34637.qm@web59901.mail.ac4.yahoo.com" type="cite">
4. Maybe you need to specify a transport with mpirun suitable for your hardware setup. in abinit 5.4.4 I made the abinip by manually enabling mpi and some libraries, I did the same for some libraries, still the made abinip does not work!
Check with a "ldd abinip" that the exec links to the correct libraries; you should see references to /usr/local/lib/libmpi... right? Abinit's configure picks a mpi implementation you probably build yourself and install in /usr/local. If ldd finds unreferenced libraries you may have to add an "export  LD_LIBRARY_PATH=/usr/local/lib" i.e. where the libmpi reside.
Lets try a test. Make a test directory, cd to it, copy the content of the abinit distribution tests/paral/Input/ directory in it. Copy tests/Psps_for_tests/26fe.pspnc in your test directory. Make a test.files containing the following lines:

t_kpt+spin.int_kpt+spin.out
t.i
t.o
t
26fe.pspnc

and run it with "mpirun --mca btl sm,self -np 2 abinip < test.files >& log_mpi"
You may have to replace abinip with the full path to the exec. Follow the log_mpi output; this test takes a few minutes to  run. I assume you have at least a dual core CPU system therefore asking for 2 processes. From another terminal window, "top" should display 2 abinip tasks and plenty of CPU use :-) Does it work or do you have errors in the log?
If it doesn't, please show the error ... and the configure invocation line.

Kind regards,

Alain




Archive powered by MHonArc 2.6.15.

Top of Page