ESyS-Particle

Mpirun non-zero status

Asked by huisky

Hello,

I'm running the compiled esys-particle compiled by myself under ubuntu LTS 16.04. Everything seems fine, most of the examples run smoothly. However, there are several examples, like the "shearcell.py" always end up with following error message:

wrong number of process! aborting
--------------------------------------------------------------------
primary job terminated normally, but 1 process returned a
non-zero exit code.. Per user direction, the job has been aborted
-----------------------------------------------------------
--------------------------------------------------------
mpirun detected that one or more process exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:

process name: [[25863,1],0]
exit code: 255

Does anyone know why?

Question information

Language:
English Edit question
Status:
Answered
For:
ESyS-Particle Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Dion Weatherley (d-weatherley) said : 		#1

Hi huisky,

This error message usually occurs because the number of MPI processes you have requested (via the -np argument to mpirun) is not consistent with the number of worker processes required by the ESyS-Particle simulation script.

For the case of the shear cell example, the LsmMpi(..) call requests 2 worker processes. Consequently, this script should be executed with the following command:

mpirun -np 3 esysparticle shearcell.py

The number of MPI processes for any ESyS-Particle simulation must be equal to the number (Nw) of worker processes requested in the LsmMpi(..) call plus 1 more MPI process for the ESyS-P master process (i.e. Nw+1). In the shearcell example, Nw=2 so 3 MPI processes are required.

Cheers,

Dion

Can you help with this problem?

Provide an answer of your own, or ask huisky for more information if necessary.

To post a message you must log in.