Sorry guys, but just to clarify, mpirun often says things like
--
mpirun has exited due to process rank 5 with PID 8389 on
node workstation exiting without calling finalize. This may
have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
--
does that clarify things for anyone?
From: Oosten, D. van (Dries)
Sent: Wednesday, March 12, 2014 8:20 PM
To: meep-discuss@ab-initio.mit.edu
Subject: meep mpi harminv problem
Hi guys,
I have been struggling with the following issue. When I use harminv to find
eigenmodes in meep, it is often unreliable when I use it through mpirun. This
is especially the case when the workstation we run meep on is under heavy load.
It seems to me that the process get killed by mpirun before they can give their
results. Could this be the case and if so, what tests can I run to track this
problem down?
Thanks in advance!
best,
Dries
___
meep-discuss mailing list
meep-discuss@ab-initio.mit.edu
http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
