<div class="gmail_quote">On Wed, Oct 12, 2011 at 06:38, Dominik Szczerba <span dir="ltr"><<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div id=":2s5">Is it legal to call KSPSolve with the solution vector being a<br>
ghost-aware vector created e.g. with VecCreateGhost?<br></div></blockquote><div><br></div><div>Yes</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div id=":2s5">
<br>
Underlying motivation: when setting up my element stiffness matrix I<br>
have a term depending on previous value of x, say in a transient<br>
scheme. But it has to be a ghosted vector, because local size of x is<br>
smaller than the amount of all nodes referenced by the local cells.<br>
For the moment I maintain a ghost-aware copy of 'x' that I update<br>
manually but am thinking if there are more efficient solutions<br>
possible.</div></blockquote></div><br><div>It's unlikely that this will make a performance difference in your application. (I can design a real problem where it's measurable, but it usually isn't.)</div>