Re: [OMPI users] OMPI users] MPI inside MPI (still)

Hi, Am 13.12.2014 um 02:43 schrieb Alex A. Schmidt: > MPI_comm_disconnect seem to work but not quite. > The call to it returns almost immediatly while > the spawn processes keep piling up in the background > until they are all done... > > I think system('env -i qsub...') to launch the third

Re: [OMPI users] OMPI users] MPI inside MPI (still)

You have to call MPI_Comm_disconnect on both sides of the intercommunicator. On the spawner processes you should call it on the intercom, while on the spawnees you should call it on the MPI_Comm_get_parent. George. > On Dec 12, 2014, at 20:43 , Alex A. Schmidt wrote: > >

Re: [OMPI users] OMPI users] MPI inside MPI (still)

Gilles, MPI_comm_disconnect seem to work but not quite. The call to it returns almost immediatly while the spawn processes keep piling up in the background until they are all done... I think system('env -i qsub...') to launch the third party apps would take the execution of every call back to

Re: [OMPI users] OMPI users] MPI inside MPI (still)

Alex, You need MPI_Comm_disconnect at least. I am not sure if this is 100% correct nor working. If you are using third party apps, why dont you do something like system("env -i qsub ...") with the right options to make qsub blocking or you manually wait for the end of the job ? That looks like