[petsc-dev] consequences of setting KSP_NORM_TYPE to NONE

Jed Brown jed at jedbrown.org
Sun Jun 12 23:14:23 CDT 2016


Barry Smith <bsmith at mcs.anl.gov> writes:
>   Less code is, of course, always most appealing. Currently KSPConvergedDefault() has
>
>  if (normtype == KSP_NORM_NONE) SETERRQ(PetscObjectComm((PetscObject)ksp),PETSC_ERR_ARG_WRONGSTATE,"Use KSPConvergedSkip() with KSPNormType of KSP_NORM_NONE");
>
> presumably this is so that a user won't mistakenly set the convergence test after setting the norm to none and assume that the test will work? But does this really provide anything of value?

I think it likely causes more confusion than it fixes.  And when do people explicitly set the convergence test to Default?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20160612/bee21ff1/attachment.sig>


More information about the petsc-dev mailing list