Re: [OMPI users] running externalprogram on same processor (Fortran)

2010-03-22 Thread Richard Treumann
abc def The MPI_Barrier call in the parent must be on the intercomm returned by the spawn. The call in the children must be on MPI_COMM_PARENT. The semantic of an MPI_Barrier call on an intercomm is: No MPI_Barrier caller in the local group returns until all members of the remote group have m

Re: [OMPI users] running externalprogram on same processor (Fortran)

2010-03-19 Thread abc def
not wait for each other with the following commands: CALL MPI_BARRIER(MPI_COMM_WORLD,ierr) ! in parent CALL MPI_BARRIER(MPI_COMM_WORLD,ierr) ! in child To: us...@open-mpi.org From: treum...@us.ibm.com List-Post: users@lists.open-mpi.org Date: Wed, 17 Mar 2010 13:25:03 -0400 Subject: Re: [OMPI users] r

Re: [OMPI users] running externalprogram on same processor (Fortran)

2010-03-17 Thread Richard Treumann
MPI Users" Date: 03/17/2010 12:21 PM Subject:Re: [OMPI users] running externalprogram onsame process

Re: [OMPI users] running externalprogram on same processor (Fortran)

2010-03-17 Thread Jeff Squyres
On Mar 16, 2010, at 5:12 AM, abc def wrote: > 1. Since Spawn is non-blocking, but I need the parent to wait until the child > completes, I am thinking there must be a way to pass a variable from the > child to the parent just prior to the FINALIZE command in the child, to > signal that the pare

Re: [OMPI users] running externalprogram on same processor (Fortran)

2010-03-16 Thread abc def
15:02:57 -0500 > To: us...@open-mpi.org > Subject: Re: [OMPI users] running externalprogram on same > processor (Fortran) > > On Mar 5, 2010, at 2:38 PM, Ralph Castain wrote: > > >> CALL SYSTEM("cd " // TRIM(dir) // " ; mpirun -machin

Re: [OMPI users] running externalprogram on same processor (Fortran)

2010-03-11 Thread Jeff Squyres
On Mar 10, 2010, at 9:25 PM, abc def wrote: > -- > Fatal error in MPI_Comm_spawn: Other MPI error, error stack: > MPI_Comm_spawn(130).: MPI_Comm_spawn(cmd="./mpitest-2.ex", > argv=0x75e920, maxprocs=1, info=0x9c00, root=0, MPI_COMM_SELF, > intercomm=0x7fff

Re: [OMPI users] running externalprogram on same processor (Fortran)

2010-03-11 Thread abc def
y, mvapich1, but not mvapich2). As ever, I'm very grateful for all the help so far, and am hoping this can eventually be solved, step-by-step. From: r...@open-mpi.org List-Post: users@lists.open-mpi.org Date: Sun, 7 Mar 2010 01:00:40 -0700 To: us...@open-mpi.org Subject: Re: [OMPI users] ru

Re: [OMPI users] running externalprogram on same processor (Fortran)

2010-03-07 Thread Ralph Castain
it compiles, but crashes once I reach the spawn command.Can you help?Thank you very much.> From: jsquy...@cisco.com> Date: Fri, 5 Mar 2010 15:02:57 -0500> To: us...@open-mpi.org> Subject: Re: [OMPI users] running externalprogram on same processor (Fortran)> > On Mar 5, 2010, at

Re: [OMPI users] running externalprogram on same processor (Fortran)

2010-03-06 Thread abc def
but crashes once I reach the spawn command. Can you help? Thank you very much. > From: jsquy...@cisco.com > Date: Fri, 5 Mar 2010 15:02:57 -0500 > To: us...@open-mpi.org > Subject: Re: [OMPI users] running externalprogram on same > processor (Fortran) > >

Re: [OMPI users] running externalprogram on same processor (Fortran)

2010-03-05 Thread Jeff Squyres
On Mar 5, 2010, at 2:38 PM, Ralph Castain wrote: >> CALL SYSTEM("cd " // TRIM(dir) // " ; mpirun -machinefile ./machinefile -np >> 1 /home01/group/Execute/DLPOLY.X > job.out 2> job.err ; cd - > /dev/null") > > That is guaranteed not to work. The problem is that mpirun sets environmental > varia