Adding pthread could fix something, but I'm a little dubious. It seems
unlikely.
You should probably contact the Aztec authors at this point.
Sent from my PDA. No type good.
On Sep 3, 2010, at 3:05 AM, Rachel Gordon
wrote:
> Dear Jeff, Ralf and Manuel
>
> There are some good news,
> I a
Dear Jeff, Ralf and Manuel
There are some good news,
I added -pthread to both the compilation and link for running
az_tutorial_with_MPI.f, and I also compiled aztec with -pthread
Now the code runs O.K for np=1,2.
Now bad news: when I try running with 3,4 or more processors I get a
similar err
Hello Rachel, Jeff,
* Rachel Gordon wrote on Thu, Sep 02, 2010 at 01:35:37PM CEST:
> The cluster I am trying to run on has only the openmpi MPI version.
> So, mpif77 is equivalent to mpif77.openmpi and mpicc is equivalent
> to mpicc.openmpi
>
> I changed the Makefile, replacing gfortran by mpif77
On Sep 2, 2010, at 10:15 AM, Rachel Gordon wrote:
> 1).
> I run it on 4 processors and got:
> node 0 :Hello, world
> node 2 :Hello, world
> node 1 :Hello, world
> node 3 :Hello, world
Ok, good.
> 2). The AZTEC code was compiled with openmpi.
>
> 3). Enclo
Hi Jeff,
1).
I run it on 4 processors and got:
node 0 :Hello, world
node 2 :Hello, world
node 1 :Hello, world
node 3 :Hello, world
2). The AZTEC code was compiled with openmpi.
3). Enclosed please fined the fortran routine:
az_tutorial_with_MPI.f
On Sep 2, 2010, at 9:28 AM, Rachel Gordon wrote:
> Concerning 1. : I just ran the simple MPI fortran program hello.f which uses:
> call MPI_INIT(ierror)
> call MPI_COMM_SIZE(MPI_COMM_WORLD, size, ierror)
> call MPI_COMM_RANK(MPI_COMM_WORLD, rank, ierror)
>
> The program ran with no
Dear Jeff,
Concerning 1. : I just ran the simple MPI fortran program hello.f which
uses:
call MPI_INIT(ierror)
call MPI_COMM_SIZE(MPI_COMM_WORLD, size, ierror)
call MPI_COMM_RANK(MPI_COMM_WORLD, rank, ierror)
The program ran with no problem.
Some more information:
The AZTEC
I'm afraid I have no insight into Aztec itself; I don't know anything about it.
Two questions:
1. Can you run simple MPI fortran programs that call MPI_Comm_size with
MPI_COMM_WORLD?
2. Can you get any more information than the stack trace? I.e., can you gdb a
corefile to see exactly where i
BTW, just to reinforce: we do strongly recommend using the wrapper compilers
whenever possible because we reserve the right to change the list of flags that
are passed to the underlying compiler at any given release.
If you can't or don't want to use the wrappers directly, you can safely extract
Dear Jeff,
The cluster has only the openmpi version of MPI and the mpi.h file is
installed in /shared/include/mpi.h
Anyhow, I omitted the COMM size parameter and recompiled/linked the case
using:
mpif77 -O -I../lib -c -o az_tutorial_with_MPI.o az_tutorial_with_MPI.f
mpif77 az_tutorial_wi
If you're segv'ing in comm size, this usually means you are using the wrong
mpi.h. Ensure you are using ompi's mpi.h so that you get the right values for
all the MPI constants.
Sent from my PDA. No type good.
On Sep 2, 2010, at 7:35 AM, Rachel Gordon
wrote:
> Dear Manuel,
>
> Sorry, it d
Dear Manuel,
Sorry, it didn't help.
The cluster I am trying to run on has only the openmpi MPI version. So,
mpif77 is equivalent to mpif77.openmpi and mpicc is equivalent to
mpicc.openmpi
I changed the Makefile, replacing gfortran by mpif77 and gcc by mpicc.
The compilation and linkage stage
Hi Rachel,
I'm not very familiar with Fortran, so I'm most likely of not too much
help here. I added Jeff to CC, maybe he can shed some lights into this.
Am Montag, den 09.08.2010, 12:59 +0300 schrieb Rachel Gordon:
> package: openmpi
>
> dpkg --search openmpi
> gromacs-openmpi: /usr/share/doc/
13 matches
Mail list logo
