Page 1 of 1

Testing Abinit with MPI - runtests.py: structure of mpi.cfg

Posted: Fri Nov 22, 2013 9:06 am
by hsatzger
Hi,

I managed to compile abinit 7.4.3 on SLES11.1 and want to run the test suite through LoadLeveler for an IBM machine (x86, Intel SandyBridge EP).
However, I cannot find the documentation on how to set up the 'mpi.cfg' file.
The script runtests.py tells me to use
runtests.py paral -n4 -c mpi.cfg
and in the directory ~abinit-7.4.3/tests/doc/howto I found the file 'testsuite_howto.rst'
However, in this file I find this

runtests.py -n 2 -c mpi.cfg

$ cat mpi.cfg

[mpi]
mpi_prefix = /usr/local/openmpi-gcc47/
mpirun_np = %(mpi_prefix)s/bin/mpirun -np

mpirun_np is the string with the path to the mpirunner, followed by any additional option you may want
to use. The option used to specifing the number of MPI nodes must be added at the end of the string.

.. tip::
For more examples, consult the configuration files in abinit/tests/mpi_cfg.


Unfortunately, the file abinit/tests/mpi_cf does not exist.

Any help is greatly appreciated!

Re: Testing Abinit with MPI - runtests.py: structure of mpi.

Posted: Thu Dec 05, 2013 11:57 am
by jbeuken
hi,

Unfortunately, the file abinit/tests/mpi_cf does not exist.


~abinit/tests/mpi_cfg/ is a folder then :

Code: Select all

ls  ~abinit/tests/mpi_cfgs/
gmac-mpich2.cfg  testf-gcc43.cfg  testf-gcc44.cfg  testf-gcc47.cfg  woopy-gcc451.cfg

there are some examples with MPICH or OpenMPI

but concerning the LoadLeveler, I have not experience… :(

In our test farm, we have an IBM under AIX 6.1 ( Power 6 ) + xlf ,
and we use this mpi.cfg

Code: Select all

[mpi]
poe = /usr/lpp/ppe.poe/bin/poe
poe_args = -hostfile /usr/local/etc/host.list

and the command to start a test with 4 procs is :

Code: Select all

./runtests.py paral[1] -t 0 -n 4 -c mpi.cfg

the command generated is :

Code: Select all

/usr/lpp/ppe.poe/bin/poe  ~abinit/src/98_main/abinit -hostfile /usr/local/etc/host.list  -procs 4  < ~abinit/tests/Test_suite/paral_t01_MPI4/t01_MPI4.stdin > ~abinit/tests/Test_suite/paral_t01_MPI4/t01_MPI4.stdout 2> ~abinit/tests/Test_suite/paral_t01_MPI4/t01_MPI4.stderr


I hope it will help...

jmb