I see. Thank you both for the prompt replies.
On Thu, Jul 26, 2012 at 8:21 PM, Ralph Castain wrote:
> Application processes will *only* be placed on nodes included in the
> allocation. The -nolocal flag is intended to ensure that no application
> processes are started on the
Application processes will *only* be placed on nodes included in the
allocation. The -nolocal flag is intended to ensure that no application
processes are started on the same node as mpirun in the case where that node is
included in the allocation. This happens, for example, with Torque, where
I was under the impression that the -nolocal option keeps processes off the
submit
host (since there may be hundreds or thousands of jobs submitted at any
time,
and we don't want this host to be overloaded).
My understanding of what you said in you last email is that, by listing the
hosts, I
Ah - okay, my misunderstanding. Would you be willing to give the trunk a try?
It might help to know if the problem is solely in 1.6, or continues.
On Jul 26, 2012, at 4:32 PM, Brock Palen wrote:
> I think so, sorry if I gave you the impression that Rmpi changed,
>
> Brock Palen
>
I think so, sorry if I gave you the impression that Rmpi changed,
Brock Palen
www.umich.edu/~brockp
CAEN Advanced Computing
bro...@umich.edu
(734)936-1985
On Jul 26, 2012, at 7:30 PM, Ralph Castain wrote:
> Guess I'm confused - your original note indicated that something had changed
> in
Guess I'm confused - your original note indicated that something had changed in
Rmpi that broke things. Are you now saying it was something in OMPI?
On Jul 26, 2012, at 4:22 PM, Brock Palen wrote:
> Ok will see, Rmpi we had working with 1.4 and has not been updated after
> 2010, this this
Ok will see, Rmpi we had working with 1.4 and has not been updated after 2010,
this this kinda stinks.
I will keep digging into it thanks for the help.
Brock Palen
www.umich.edu/~brockp
CAEN Advanced Computing
bro...@umich.edu
(734)936-1985
On Jul 26, 2012, at 7:16 PM, Ralph Castain wrote:
Crud - afraid you'll have to ask them, then :-(
On Jul 26, 2012, at 3:50 PM, Brock Palen wrote:
> Ralph,
>
> Rmpi wraps everything up, so I tried setting them with
>
> export OMPI_plm_base_verbose=5
> export OMPI_dpm_base_verbose=5
>
> and I get no extra messages even on helloworld example
Ralph,
Rmpi wraps everything up, so I tried setting them with
export OMPI_plm_base_verbose=5
export OMPI_dpm_base_verbose=5
and I get no extra messages even on helloworld example simple MPI-1.0 code.
Brock Palen
www.umich.edu/~brockp
CAEN Advanced Computing
bro...@umich.edu
(734)936-1985
Well, it looks like comm_spawn is working on 1.6. Afraid I don't know enough
about Rmpi/snow to advise on what changed, but you could add some debug params
to get an idea of where the problem is occurring:
-mca plm_base_verbose 5 -mca dpm_base_verbose 5
should tell you from an OMPI
Do you have
OMPI_IMPORTS, OPAL_IMPORTS and ORTE_IMPORTS
defined in your preprocessor flags? You need those.
Damien
On 26/07/2012 3:56 PM, Sayre, Alan N wrote:
I'm trying to replace the usage of platform mpi with open mpi. I am
trying to compile on Windows 7 64 bit using Visual Studio
Am 26.07.2012 um 23:58 schrieb Erik Nelson:
> Reuti,
>
> Thank you. Our queue is backed up, so it will take a little while before I
> can try this.
>
> I assume that by specifying the nodes this way, I don't need (and it would
> confuse
> the system) to add -nolocal. In other words, qsub
Weird - looks like it has done a comm_spawn and having trouble connecting
between the jobs. I can check the basic code and make sure it is working - I
seem to recall someone else recently talking about Rmpi changes causing
problems (different ones than this, IIRC), so you might want to search
Am 26.07.2012 um 23:48 schrieb Reuti:
> Am 26.07.2012 um 23:33 schrieb Erik Nelson:
>
>> I have a purely parallel job that runs ~100 processes. Each process has
>> ~identical
>> overhead so the speed of the program is dominated by the slowest processor.
>>
>> For this reason, I would like to
I'm trying to replace the usage of platform mpi with open mpi. I am
trying to compile on Windows 7 64 bit using Visual Studio 2010. I have
added the paths to the openmpi include and library directories and added
the libmpid.lib and libmpi_cxxd.lib to the linker input. The application
compiles
Am 26.07.2012 um 23:33 schrieb Erik Nelson:
> I have a purely parallel job that runs ~100 processes. Each process has
> ~identical
> overhead so the speed of the program is dominated by the slowest processor.
>
> For this reason, I would like to restrict the job to a specific set of
>
I have ran into a problem using Rmpi with OpenMPI (trying to get snow running).
I built OpenMPI following another post where I built static:
./configure --prefix=$INSTALL/gcc-4.4.6-static
--mandir=$INSTALL/gcc-4.4.6-static/man --with-tm=/usr/local/torque/
--with-openib --with-psm
I have a purely parallel job that runs ~100 processes. Each process has
~identical
overhead so the speed of the program is dominated by the slowest processor.
For this reason, I would like to restrict the job to a specific set of
identical (fast)
processors on our cluster.
I read the FAQ on
hello Hristo
Thank you for taking a look at the program and the output.
The detailed explanation was very helpful. I also found out that the
signature of a derived datatype is the specific sequence of the primitive
datatypes and is independent of the displacements. So the differences in
the
No it's not related to the version of Visual Studio.
On 2012-07-26 4:08 AM, Kumar, Sudhir wrote:
I am wondering if it is related to the version of Visual Studio, I am
using Visual Studio 2005.
*Sudhir Kumar*
*From:*users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org]
*On Behalf
20 matches
Mail list logo