mpirun with win-64

[Adrian Spidle]

Hello;

I am trying to run migrate with parallel processing under windows
2008. My terminal for some reason cannot see the migrate-n-mpi.exe
executable. Here is my error:

/my documents/analysis/migrate_3.6
$ mpirun migrate-n-mpi
--------------------------------------------------------------------------
mpirun.exe was unable to launch the specified application as it could
not find an executable:

Executable: migrate-n-mpi
Node: spinnershark

while attempting to start process rank 0.

I would appreciate any advice on how to get this running.

Thanks,

Adrian

[Peter Beerli]

Adrian,

I have very little experience with windows and mpi (my testrun on my virtual windows barely count).
Your mpirun does not find the path to migrate-n-mpi (is it really in that directory [and not in ./src]?
Can you try to full path?
or is it simply that it expects the .exe ?

Maybe someone else with windows experience can help?
[I know there are some migrate-support readers who have run migrate-n-mpi.exe on windows]

Peter

> --
> You received this message because you are subscribed to the Google Groups "migrate-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to migrate-suppo...@googlegroups.com.
> To post to this group, send email to migrate...@googlegroups.com.
> Visit this group at http://groups.google.com/group/migrate-support.
> For more options, visit https://groups.google.com/groups/opt_out.

[parks.wr]

I've run quite a bit on windows.  First, yes, windows requires the full executable name.  mpirun -np # ../migrate-n-mpi.exe parmfilename -nomenu  is my standard command where # is the number of cpu's available.

The easiest way I've found due to odd folder names in windows at times is to place the unzipped folder "migrate-3.6" in the root.  In that folder you have all the executables and migrate folders.

Then within that folder create another folder for each project eg c:/migrate-3.6/project1

In folder project 1 place the infile and parmfile of the project run. 

Navigate to the folder from a command prompt so that the prompt says C:migrate-3.6/project1

From that command prompt you would type "mpirun -np # ../migrate-n-mpi.exe parmfile -nomenu" all on one line

Note that this only works if your parmfile is called parmfile and the infile name specified in the parmfile is in the same folder.

Using the path ../migrate-n-mpi.exe tells it to look for the file one folder above the current directory.

Good luck,

RP

[Peter Beerli]

Thanks PR for giving a windows mpi start guide, 

I was wondering about your “/“, I guess that you had some UNIX emulation installed on your system and on standard systems one should use

“\” instead, or is this a openmpi feature?

Peter

[parks.wr]

Odd, yes.  I'm unsure.  I switch systems enough that I often get it backwards the first time and I remember in the past it wouldn't work. I just tested both / & \ on a brand new windows system and it appears to treat them the same.  Typing mpirun -np 6 ../migrate-n-mpi.exe and ..\migrate-n-mpi.exe both worked equally well.  

No emulation was ever installed on this system since it just arrived last week.

Color me confused.  Perhaps MS has enough dual system users that got annoyed with the difference they treat them the same now.

Even typing "cd migrate\example" or "cd migrate/example" both work equally well.

RP

[Peter Beerli]

thanks for the clarification, I learned something new

Peter

[Adrian Spidle]

Thanks for that advice, it has gotten me to the next step, now my
error missage is 'dispatch () failed'

aspidle@spinnershark /cygdrive/c/users/aspidle/my documents/analysis/migrate_3.6
$ mpirun -np 8 migrate-n-mpi.exe parmfile.testbayes
[spinnershark:05884] ..\..\..\openmpi-1.5.3\opal\event\event.c:
ompi_evesel->dispatch() failed.

That might point to a problem with my mpi installation.

Adrian

[Peter Beerli]

This is definitely a problem with your MPI installation because migrate is not calling these commands directly
perhaps you will need a recompile of MPI, also you MUST use the same version migrate-n-mpi is using
I will eventually produce a more updated version of the parallel migrate for windows with the newer openmpi library.

Peter