Why not generate an ifort version with a prefix of _intel
And the gfortran version with a prefix of _gcc
?
That's what I do and then use mpi-selector to switch between versions as
required.
Jim
-Original Message-
From: users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org] On
Be
Hi,
I am wondering whether it is possible to support both the Intel
compiler ifort and gfortran within a single compiled version of
openmpi.
E.g.,
1. compile openmpi ifort as the Fortran compiler and install it
in /usr/local/openmpi-1.3.3
2. compile openmpi using gfortran, but do not install it
I'll give it a try.
Steve Dale
Senior Platform Analyst
Health Canada
Phone: (613)-948-4910
E-mail: steven_d...@hc-sc.gc.ca
Ralph Castain
Sent by: users-boun...@open-mpi.org
07/17/2009 10:35 AM
Please respond to
Open MPI Users
To
Open MPI Users
cc
Subject
Re: [OMPI use
Okay, just checking the obvious. :-)
We regularly run with the exact same configuration here (i.e., slurm +
16cpus/node) without problem on jobs that are both short and long, so
it seems doubtful that it would be an OMPI bug. However, it is
possible as the difference could be due to configu
I think it unlikely that its a time limit thing. Firstly, slurm is set up
with no time limit on jobs, and we get the same behaviour whether or not
slurm is in the picture.
In addition, we've run several other much larger jobs with a greater
number of permutations and they complete fine.
This jo
Dear OpenMPi developers,
i'm writing you about a possibile bug in OpenMPi 1.3.2 I'm running
under LSF and Infiniband net. When i launch a job, sometimes i have
the follow error:
Jul 17 10:10:54 2009 10653 4 7.02 handleTSRegisterStart: unwanted task
registration. PAM expected 3 tasks on host. This
:) thanks. and good luck with your project. I myself might try this if I
could find sometime.
On Fri, Jul 17, 2009 at 11:42 AM, Ashika Umanga Umagiliya <
auma...@biggjapan.com> wrote:
> Hi prasad ,
>
> thanks you for your reply.After some googling, I realized that you are a
> key member behind
Hi prasad ,
thanks you for your reply.After some googling, I realized that you are
a key member behind Axis2/C SAML , so saying "a bit of experience" is
being too much humble :)
So nice meet a smart sri lankan in the forum.Really appropriate your
guys great work.
Cheers,
umanga
Prasadcse Pe
Hi, with a bit of experience I have with the Axis2/C, I think your second
model with MPI_Comm_spawn might solve your problem. One of crude
restriction with Axis2/C architecture is the run time service loading using
static libs. This sometimes prevent many user needed handling where your
logic has
I do not know anything about implementing webservices, but you should
take a look at MPI-2 dynamic process management. This way, your
webservice can MPI_Comm_spawn() a brand-new set of parallel processes
doing the heavy work. This way, your webservice will act as a kind of
proxy application between
From what I can see, it looks like your job is being terminated -
something is killing mpirun. Is it possible that the job runs slowly
enough on 14 or less cpus that it simply isn't completing within your
specified time limit?
The lifeline message simply indicates that a process self-aborte
11 matches
Mail list logo
