[petsc-users] petsc-users Digest, Vol 36, Issue 46

[Matthew Knepley]

On Tue, Dec 13, 2011 at 8:59 AM, Aron Ahmadia <aron.ahmadia at kaust.edu.sa>wrote:

> Hi Thomas,
>
> That wasn't quite Matt's question, since MPI_Init gets called regardless
> of whether you use mpiexec.  He wants to know if your code breaks if
>
> MPI_Init() is called, in which case we can blame this on your MPI
> implementation and not PETSc :)
>

Alternatively, configure PETSc using --with-mpi=0 and check.

PETSc really has no way of intercepting output or changing buffering, but
MPI does.

   Matt


> -A
>
>
> On Tue, Dec 13, 2011 at 5:55 PM, Thomas Leissing <thomas.leissing at cstb.fr>wrote:
>
>> **
>>
>> > This sounds like MPI rather than PETSc, since it plays with output.
>> Are you
>> > running with mpiexec?
>> >   Matt
>>
>> Yes I do. I have the same results with and without mpiexec.
>>
>>
>>
>


-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20111213/aaca3116/attachment.htm>