On Tue, Dec 13, 2011 at 8:59 AM, Aron Ahmadia <span dir="ltr"><<a href="mailto:aron.ahmadia@kaust.edu.sa">aron.ahmadia@kaust.edu.sa</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi Thomas,<div><br></div><div>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</div><div><br></div><div>MPI_Init() is called, in which case we can blame this on your MPI implementation and not PETSc :)</div>
</div></blockquote><div><br></div><div>Alternatively, configure PETSc using --with-mpi=0 and check.</div><div><br></div><div>PETSc really has no way of intercepting output or changing buffering, but MPI does.</div><div><br>
</div><div> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><span class="HOEnZb"><font color="#888888">-A</font></span><div>
<div class="h5"><br><br><div class="gmail_quote">On Tue, Dec 13, 2011 at 5:55 PM, Thomas Leissing <span dir="ltr"><<a href="mailto:thomas.leissing@cstb.fr" target="_blank">thomas.leissing@cstb.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>
<div>
<br>
<tt>> </tt><tt><font color="#4d4d4d">This sounds like MPI rather than PETSc, since it plays with output. Are you</font></tt><br>
<tt>> </tt><tt><font color="#4d4d4d">running with mpiexec?</font></tt><br>
<tt>></tt><tt><font color="#4d4d4d"> Matt</font></tt><br>
<br>
Yes I do. I have the same results with and without mpiexec.<br>
<br>
<br>
</div>
</blockquote></div><br></div></div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>
-- Norbert Wiener<br>