Of course I'm connected to the internet. Please help..
From: Nadia Derbey
To: Open MPI Users
Sent: Wed, February 24, 2010 10:44:04 PM
Subject: Re: [OMPI users] MPi Abort verbosity
On Wed, 2010-02-24 at 07:36 -0700, Ralph Castain wrote:
> I'm afra
On Wed, 2010-02-24 at 07:36 -0700, Ralph Castain wrote:
> I'm afraid not. We are working on alternative error response
> mechanisms, but nothing is released at this time.
Don't know if this would work, but why not doing what follows:
1. set a signal handler in your application. This where you woul
I'm afraid not. We are working on alternative error response mechanisms, but
nothing is released at this time.
On Feb 24, 2010, at 7:17 AM, Gabriele Fatigati wrote:
> Mm,
> i'm trying to explain better.
>
> My target is, when a MPI process dead for some reason, after launched
> MPI_Abort i wou
Mm,
i'm trying to explain better.
My target is, when a MPI process dead for some reason, after launched
MPI_Abort i would like to control this behaviour. Example:
rank 0 died and launc MPI_Abort
i would like to do something before other process died. So i want to control
shutdown of my MPI appli
I don't believe the error handler will help suppress the messages you are
trying to avoid as they don't originate in the MPI layer. They are actually
generated in the RTE layer as mpirun is exiting.
You could try adding the --quiet option to your mpirun cmd line. This will help
eliminate some (
On Wed, 24 Feb 2010 14:21:02 +0100, Gabriele Fatigati
wrote:
> Yes, of course,
>
> but i would like to know if there is any way to do that with openmpi
See the error handler docs, e.g. MPI_Comm_set_errhandler.
Jed
Yes, of course,
but i would like to know if there is any way to do that with openmpi
2010/2/24 jody
> Hi Gabriele
> you could always pipe your output through grep
>
> my_app | grep "MPI_ABORT was invoked"
>
> jody
>
> On Wed, Feb 24, 2010 at 11:28 AM, Gabriele Fatigati
> wrote:
> > Hi Nadia,
Hi Gabriele
you could always pipe your output through grep
my_app | grep "MPI_ABORT was invoked"
jody
On Wed, Feb 24, 2010 at 11:28 AM, Gabriele Fatigati
wrote:
> Hi Nadia,
>
> thanks for quick reply.
>
> But i suppose that parameter is 0 by default. Suppose i have the follw
> output:
>
> - --
Hi Nadia,
thanks for quick reply.
But i suppose that parameter is 0 by default. Suppose i have the follw
output:
- --
- --> MPI_ABORT was invoked on rank 1 in communicator MPI_COMM_WORLD
with errorcode 4. <--
NOTE: invokin
On Wed, 2010-02-24 at 09:55 +0100, Gabriele Fatigati wrote:
>
> Dear Openmpi users and developers,
>
> i have a question about MPI_Abort error message. I have a program
> written in C++. Is there a way to decrease a verbosity of this error?
> When this function is called, openmpi prints many info
Dear Openmpi users and developers,
i have a question about MPI_Abort error message. I have a program written in
C++. Is there a way to decrease a verbosity of this error? When this
function is called, openmpi prints many information like stack trace, rank
of processor who called MPI_Abort ecc.. Bu
11 matches
Mail list logo
