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

2014-12-12 Thread Alex A. Schmidt
Hello Gilles, Ok, I believe I have a simple toy app running as I think it should: 'n' parent processes running under mpi_comm_world, each one spawning its own 'm' child processes (each child group work together nicely, returning the expected result for an mpi_allreduce call). Now, as I mentioned

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

2014-12-12 Thread Gilles Gouaillardet
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

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

2014-12-12 Thread Alex A. Schmidt
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