<div>ops.... it worked for ex2 and ex2f ;-)</div>
<div> </div>
<div>so what could be wrong? is there some commands or subroutine which i must call? btw, i'm programming in fortran.</div>
<div> </div>
<div>thank you.<br><br> </div>
<div><span class="gmail_quote">On 2/9/07, <b class="gmail_sendername">Matthew Knepley</b> <<a href="mailto:knepley@gmail.com">knepley@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Problems do not go away by ignoring them. Something is wrong here, and it may<br>affect the rest of your program. Please try to run an example:
<br><br> cd src/ksp/ksp/examples/tutorials<br> make ex2<br> ./ex2 -log_summary
<div><span class="e" id="q_110a71f014704853_1"><br><br> Matt<br><br>
<div><span class="gmail_quote">On 2/9/07, <b class="gmail_sendername">Ben Tay</b> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:zonexo@gmail.com" target="_blank">zonexo@gmail.com</a>> wrote:
</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<div>Well, I don't know what's wrong. I did the same thing for -info and it worked. Anyway, is there any other way?</div>
<div> </div>
<div>Like I can use -mat_view or call matview( ... ) to view a matrix. Is there a similar subroutine for me to call?</div>
<div> </div>
<div>Thank you.<br><br> </div>
<div><span>
<div><span class="gmail_quote">On 2/9/07, <b class="gmail_sendername">Matthew Knepley</b> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:knepley@gmail.com" target="_blank">knepley@gmail.com</a>
> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">Impossible, please check the spelling, and make sure your<br>command line was not truncated. <br>
<br> Matt
<div><span><br><br>
<div><span class="gmail_quote">On 2/9/07, <b class="gmail_sendername">Ben Tay</b> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:zonexo@gmail.com" target="_blank"> zonexo@gmail.com</a>> wrote:
</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">ya, i did use -log_summary. but no output.....
<div><span><br><br>
<div><span class="gmail_quote">On 2/9/07, <b class="gmail_sendername">Barry Smith</b> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>> wrote:
</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><br>-log_summary<br><br><br>On Fri, 9 Feb 2007, Ben Tay wrote:<br><br>> Hi,<br>><br>> I've tried to use log_summary but nothing came out? Did I miss out
<br>> something? It worked when I used -info...<br>><br>><br>> On 2/9/07, Lisandro Dalcin <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:dalcinl@gmail.com" target="_blank">dalcinl@gmail.com
</a>> wrote:<br>> ><br>> > On 2/8/07, Ben Tay < <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:zonexo@gmail.com" target="_blank">zonexo@gmail.com</a>> wrote:<br>> > > i'm trying to solve my cfd code using PETSc in parallel. Besides the
<br>> > linear<br>> > > eqns for PETSc, other parts of the code has also been parallelized using <br>> > > MPI.<br>> ><br>> > Finite elements or finite differences, or what?<br>> >
<br>> > > however i find that the parallel version of the code running on 4<br>> > processors<br>> > > is even slower than the sequential version.<br>> ><br>> > Can you monitor the convergence and iteration count of momentum and
<br>> > poisson steps?<br>> ><br>> ><br>> > > in order to find out why, i've used the -info option to print out the <br>> > > details. there are 2 linear equations being solved - momentum and
<br>> > poisson.<br>> > > the momentum one is twice the size of the poisson. it is shown below:<br>> ><br>> > Can you use -log_summary command line option and send the output attached? <br>> >
<br>> > > i saw some statements stating "seq". am i running in sequential or<br>> > parallel<br>> > > mode? have i preallocated too much space?<br>> ><br>> > It seems you are running in parallel. The "Seq" are related to local,
<br>> > internal objects. In PETSc, parallel matrices have inner sequential<br>> > matrices.<br>> ><br>> > > lastly, if Ax=b, A_sta and A_end from MatGetOwnershipRange and b_sta<br>> > and
<br>> > > b_end from VecGetOwnershipRange should always be the same value, right?<br>> ><br>> > I should. If not, you are likely going to get an runtime error.<br>> ><br>> > Regards,<br>> >
<br>> > --<br>> > Lisandro Dalcín<br>> > ---------------<br>> > Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)<br>> > Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
<br>> > Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)<br>> > PTLC - Güemes 3450, (3000) Santa Fe, Argentina<br>> > Tel/Fax: +54-(0)342-451.1594<br>> ><br>> ><br>> </blockquote>
</div><br></span></div></blockquote></div><br><br clear="all"><br></span></div>-- <br>One trouble is that despite this system, anyone who reads journals widely<br>and critically is forced to realize that there are scarcely any bars to eventual
<br>publication. There seems to be no study too fragmented, no hypothesis too<br>trivial, no literature citation too biased or too egotistical, no design too<br>warped, no methodology too bungled, no presentation of results too
<br>inaccurate, too obscure, and too contradictory, no analysis too self-serving,<br>no argument too circular, no conclusions too trifling or too unjustified, and<br>no grammar and syntax too offensive for a paper to end up in print. -- Drummond Rennie
</blockquote></div><br></span></div></blockquote></div><br><br clear="all"><br>-- <br>One trouble is that despite this system, anyone who reads journals widely<br>and critically is forced to realize that there are scarcely any bars to eventual
<br>publication. There seems to be no study too fragmented, no hypothesis too<br>trivial, no literature citation too biased or too egotistical, no design too<br>warped, no methodology too bungled, no presentation of results too
<br>inaccurate, too obscure, and too contradictory, no analysis too self-serving,<br>no argument too circular, no conclusions too trifling or too unjustified, and<br>no grammar and syntax too offensive for a paper to end up in print. -- Drummond Rennie
</span></div></blockquote></div><br>