OK. My vision is made more clear.<br>So, after a line-search update in newton iteration, I should in some way pass the updated values into my objects (elements) so that the FormJacobian and FormFunctions use these objects for the next newton iteration. Then, where is the proper place to do this?<br>
<br><br><br><div class="gmail_quote">On Sat, Nov 12, 2011 at 9:44 PM, Jed Brown <span dir="ltr"><<a href="mailto:jedbrown@mcs.anl.gov">jedbrown@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;">
<div class="im"><div class="gmail_quote">On Sat, Nov 12, 2011 at 12:10, behzad baghapour <span dir="ltr"><<a href="mailto:behzad.baghapour@gmail.com" target="_blank">behzad.baghapour@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Yes.The Roe average is a common method in this area. <br>I couldn't understand well what you said about stashing the quantities. Each residual evaluation is proceeded by a Jacobian one if I choose an Inexact Newton method and freeze Jacobian matrix for some Newton iterations. Please make it for me more clear. </div>
</blockquote></div><br></div><div>As the FAQ discusses, the residual may be called multiple times before a Jacobian is needed, for example, in a line search. Also, some time integration methods (e.g. Rosenbrocks) will evaluate the residual several times before getting a new Jacobian. If it's free for you to stash these intermediate quantities during residual evaluation, then go ahead and do it (but don't forget that even if it's all computed, just putting it in memory costs something too). But make residual evaluation, not the monitor, the place where these intermediate quantities are computed and stored. The monitor is not called in the semantically correct place for this purpose.</div>
</blockquote></div><br>