<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 12 January 2016 at 15:06, <span dir="ltr"><<a href="mailto:gideon.simpson@gmail.com" target="_blank">gideon.simpson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div>Do I have to manually code in the divergence criteria too?<br></div></div></blockquote><div><br></div><div>Yes.<br><br>By calling<span style="font-family:arial,helvetica,sans-serif"><font size="2"><span style="font-weight:normal"> SNESSetConvergenceTest()</span></font></span> you are replacing the default SNES convergence test function which will get called at each SNES iteration, therefore you are responsible for defining all reasons for convergence and divergence.<br><br></div><div>To make life easy, you could copy everything in the funciton SNESConvergedDefault(), <br><br><a href="http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/SNES/SNESConvergedDefault.html#SNESConvergedDefault" target="_blank">http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/SNES/SNESConvergedDefault.html#SNESConvergedDefault</a><br><div><br></div><font size="2"><span style="font-family:arial,helvetica,sans-serif">and just replace the rule for <br></span></font></div><div><font size="2"><span style="font-family:arial,helvetica,sans-serif"> SNES_CONVERGED_FNORM_RELATIVE<br></span></font></div><div><font size="2"><span style="font-family:arial,helvetica,sans-serif">with your custom scaled stopping condition.<br><br><br></span></font><pre width="80"><font size="2"><span style="font-family:arial,helvetica,sans-serif"><br><br></span></font></pre></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div></div><div><div><div><br>On Jan 12, 2016, at 8:37 AM, Dave May <<a href="mailto:dave.mayhem23@gmail.com" target="_blank">dave.mayhem23@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 12 January 2016 at 14:33, Gideon Simpson <span dir="ltr"><<a href="mailto:gideon.simpson@gmail.com" target="_blank">gideon.simpson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div>I’m just a bit confused by the documentation for SNESConvergenceTestFunction. the arguments for the xnorm, gnorm, and f are passed in, at the current iterate, correct? </div></div></blockquote><div><br></div><div>Yes, but nothing requires you to use them :D<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div> I interpreted this as though I had to build by convergence test based on those values.</div></div></blockquote><div><br></div><div>This is a misinterpretation. You can ignore all of xnorm, gnorm and fnorm and define any crazy stopping condition you like. <br><br>xnorm, gnorm and fnorm are commonly required for many stopping conditions and are computed by the snes methods. As such, are readily available and for efficiency and convenience they are provided to the user (e.g. to avoid you having to re-compute norms).<br><br></div><div>Cheers,<br></div><div> Dave<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div><span><font color="#888888"><br><div>
<span style="border-collapse:separate;color:rgb(0,0,0);font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">-gideon</span>
</div></font></span><div><div>
<br><div><blockquote type="cite"><div>On Jan 12, 2016, at 8:24 AM, Dave May <<a href="mailto:dave.mayhem23@gmail.com" target="_blank">dave.mayhem23@gmail.com</a>> wrote:</div><br><div><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 12 January 2016 at 14:14, Gideon Simpson <span dir="ltr"><<a href="mailto:gideon.simpson@gmail.com" target="_blank">gideon.simpson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word">That seems to to allow for me to cook up a convergence test in terms of the 2 norm. </div></blockquote><div><br></div><div>While you are only provided the 2 norm of F, you are also given access to the SNES object. Thus inside your user convergence test function, you can call SNESGetFunction() and SNESGetSolution(), then you can compute your
convergence criteria and set the converged reason to what ever you want.<br><div><br></div>See <br><div><br><a href="http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/SNES/SNESGetFunction.html" target="_blank">http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/SNES/SNESGetFunction.html</a><br><br><a href="http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/SNES/SNESGetSolution.html" target="_blank">http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/SNES/SNESGetSolution.html</a><br><br></div><div>Cheers,<br></div><div> Dave<br></div><div><br></div><br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word">What I’m really looking for is the ability to change things to be something like the 2 norm of the vector with elements<div><br></div><div>F_i/|x_i|</div><div><br></div><div>where I am looking for a root of F(x). I can just build that scaling into the form function, but is there a way to do it without rewriting that piece of the code?</div><span><font color="#888888"><div><br></div></font></span><div><div><div><span><font color="#888888"><br><div>
<span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">-gideon</span>
</div></font></span><div><div>
<br><div><blockquote type="cite"><div>On Jan 12, 2016, at 12:14 AM, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>> wrote:</div><br><div><div><br> You can use SNESSetConvergenceTest() to use whatever test you want to decide on convergence.<br><br>Barry<br><br><blockquote type="cite">On Jan 11, 2016, at 3:26 PM, Gideon Simpson <<a href="mailto:gideon.simpson@gmail.com" target="_blank">gideon.simpson@gmail.com</a>> wrote:<br><br>I’m solving nonlinear problem for a complex valued function which is decomposed into real and imaginary parts, Q = u + i v. What I’m finding is that where |Q| is small, the numerical phase errors tend to be larger. I suspect this is because it’s using the 2-norm for convergence in the SNES, so, where the solution is already, the phase errors are seen as small too. Is there a way to use something more like an infinity norm with SNES, to get more point wise control?<br><br>-gideon<br><br></blockquote><br></div></div></blockquote></div><br></div></div></div></div></div></div></blockquote></div><br></div></div>
</div></blockquote></div><br></div></div></div></div></blockquote></div><br></div></div>
</div></blockquote></div></div></div></blockquote></div><br></div></div>