On Sun, 6 Oct 2019, Marcin Błażejowski wrote:
On 06.10.2019 16:40, Allin Cottrell wrote:
> On Sun, 6 Oct 2019, Marcin Błażejowski wrote:
>> On 06.10.2019 09:55, Marcin Błażejowski wrote:
>>> I face the problem with MPI in Windows: when I start processing on more
>>> than 3 nodes I'm getting the following message (current git 64 bit
>>> compilation + currenty MS MPI 10 library):
>>> MPI nodes: 4, OMP threads: 1
>>> gretlmpi 2019d-git
>>> job aborted:
>>> [ranks] message
>>> [0-1] terminated
>>>  application aborted
>>> aborting MPI_COMM_WORLD (comm=0x44000000), error 1, comm rank 2
>>>  terminated
> Do you have a "hosts" or "machinefile" active, perhaps?
No, just use 4 local phisical cores.
I just tried running a trivial script with mpi block on Windows 10
with the current gretl snapshot. The machine has two physical cores,
4 threads, and I specified --np=4. The script ran without a problem,
so I don't know what's going on in your case. You might try running
your script with the --verbose flag.
>> 1. Calling mpi block genereted overall problem: mpiexec was
>> execute gretlmpi from '/usr/local/bin' instead of
> That's controlled under /Tools/Preferences/General/MPI : you can reset
> the path to mpiexec there.
Allin, mpiexec (mpiexec.mpich in fact) was found end executed, but it
tried to call '/usr/local/bin/gretlmpi' (which was linked against
OpenMPI) instead of "local" '/home/marcin/gretl/2019c/bin/gretlmpi'.
Ah, OK. The path to the gretlmpi binary is obtained from the "Main
gretl directory" setting under /Tools/Preferences/General. If that's
/path/to/share/gretl we strip off the "share/gretl" and add
As for the --quiet flag, that's an option passed along to gretlmpi,
not aimed at mpiexec, so I don't know how there could be any
difference in result by MPI implementation.