Samu, Thanks you are a life saver. Your efforts saved me a ton of time. I went through basically exactly the same process as you describe. To summarize the same issue you have I get the following phenomenon: spawning appears to not happen the same every time. How can you specify how the nodes are being spawned? Did you ever figure this out? I see almost no documentation anywhere on Windows deployments.
Thanks Tom Samu Mäntyniemi wrote: > > Hello! > > I finally got MPICH 1.06 + R 2.6.1 + Rmpi 0.5-5 working with multiple > computers. The key was to realize that the number of processes should be > one when launching Rgui using mpiexec and not the number of > master+slaves, as I had first wrongly understood. > > However, I seem to have a new problem which I have not been able to > figure out: > > After loading Rmpi, the first attempt to mpi.spawn.Rslaves() always > spawns the slaves on the local machine instead of on both machines. If I > close the slaves and spawn again, then one slave gets spawned on remote > machine. Each time I close and then spawn againg, the order of machines > is different, and eventually I get back to the situation where all > slaves are on the local machine. Continuing to do spawning and closing > seems to reveal a pattern. I can see similar behavior if I have more > than two machines, and it takes more spawn-close cycles to get all my > slave machines spawned on. > > Below is an example session with two machines. This pattern shows > everytime I start R and run this script. How to control the spawning so > that I get everything right at the first call of mpi.spawn.Rslaves()? > > Regards, > > Samu > > -- View this message in context: http://www.nabble.com/Multicore-computation-in-Windows-network%3A-How-to-set-up-Rmpi-tp14436938p16465801.html Sent from the R help mailing list archive at Nabble.com. ______________________________________________ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.