-
Notifications
You must be signed in to change notification settings - Fork 579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Belos: Question about setting custom convergence tolerances #6733
Comments
@trilinos/belos |
@stelin314 Here's an excerpt from the Belos design paper:
Here's the full reference with more information on that topic:
|
@stelin314 Customization of status tests that define the stopping criterion of iterative solvers has been primarily targeting the GMRES solvers. The CG solvers do not have the same set of options or flexibility. The scaling that you propose would be possible if those extensions were made. Are you using a released version of Trilinos, or the develop/master branch of Trilinos? |
Thank you for the responses! I believe I am using the develop/master branch of Trilinos. The status test sounds quite useful, but there may be other things I can do on my end to get around this issue. I just wanted to check if this diagonal scaling of the residual was possible (for CG), and it seems like it may be in the future. |
I currently have a problem with the following form
r = b - Ax
I've set up the problem to use the CG solver within Belos (currently not preconditioned, will change later). Right now, (I believe) it judges convergence by using the l2 norm of the residual 'r' if I don't use any Implicit/Explicit residual scaling.
I was wondering if there is a way make some kind of custom convergence calculation where rather than using the l2 norm of just the residual r, it uses the l2 norm of something that looks like r/d (an element wise division), where d is some vector of diagonal values from a matrix.
Any input would be appreciated, and thanks for your time!
-Stephen
The text was updated successfully, but these errors were encountered: