This looks broken:<div><br></div><div><div>virsaug.c: In function 'SNESSolveVI_SS': virsaug.c:784: error: 'struct _SNESOps' has no member named 'computefunction' virsaug.c:785: error: 'struct _SNESOps' has no member named 'computefunction' virsaug.c:807: error: 'struct _SNESOps' has no member named 'computefunction' virsaug.c:828: error: 'struct _SNESOps' has no member named 'computefunction' virsaug.c:883: error: 'struct _SNESOps' has no member named 'computefunction' virsaug.c:916: error: 'struct _SNESOps' has no member named 'computefunction' ('ERROR: Missing object file', 'virsaug.o')</div>
<div><br></div><div>Am I missing something?</div><div><br></div><div> Matt</div><br><div class="gmail_quote">On Tue, Mar 13, 2012 at 8:47 AM, Stefano Zampini <span dir="ltr"><<a href="mailto:stefano.zampini@gmail.com">stefano.zampini@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The same test should be used to run also other MATIS based preconditioners as PCNN. I think PCNN is broken into petsc-dev (it doesn't preallocate for coarse matrix if I remember well)<br>
<br>Regarding roughness/portability of PCBDDC: please let me know which parts of code should I improve so I can put them in my todo list.<div class="HOEnZb"><div class="h5"><br>
<br><div class="gmail_quote">2012/3/13 Jed Brown <span dir="ltr"><<a href="mailto:jedbrown@mcs.anl.gov" target="_blank">jedbrown@mcs.anl.gov</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>The code is still pretty rough/not entirely portable, so I don't think we will turn it on by default. Having a runable example is important. If you want to get it ready, I would try to do it in the next week or so.</p>
<div><div>
<div class="gmail_quote">On Mar 13, 2012 8:15 AM, "Stefano Zampini" <<a href="mailto:stefano.zampini@gmail.com" target="_blank">stefano.zampini@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Are you planning to include pcbddc in the next release?<br><br>It works, but some parts of PCBDDC code are not fully developed as we decided with Jed (primarly, the MatPartitioning procedure for multilevel).<br><br>In case you want to include it into the next release, how many days I have to work on the code until the release ?<br>
<br><div class="gmail_quote">2012/3/12 Jed Brown <span dir="ltr"><<a href="mailto:jedbrown@mcs.anl.gov" target="_blank">jedbrown@mcs.anl.gov</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class="gmail_quote">On Mon, Mar 12, 2012 at 14:40, Barry Smith <span dir="ltr"><<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I still like including the private in the name since it makes clear they are private include files.</blockquote></div><br></div><div>Cool, glad that's out of the way.</div><div><br></div><div>Now about namespacing all the variables in the makefiles. This is an opportunity to clarify/normalize variable names. I don't know what SL_LINKER is, for example.</div>
<div><br></div><div>Also, should there be an "exported" version that makes some of the PETSC symbols public? (I think so, even just for internal use, because I don't want to type ${PETSC_MPIEXEC}, ${PETSC_DIFF}, ${PETSC_PYTHON}, etc in all the makefiles.)</div>
</blockquote></div><br><br clear="all"><br>-- <br>Stefano<br>
</blockquote></div>
</div></div></blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br>Stefano<br>
</font></span></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>
</div>