Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • James Willenbring
  • Trilinos
  • Issues
  • #4645

Closed
Open
Created Mar 18, 2019 by James Willenbring@jmwilleMaintainer

Belos: Add condition number estimation to GMRES

Created by: mhoemmen

@trilinos/belos

@drnoble requests that we add condition number estimation to GMRES.

Motivation and Context

@drnoble wants this feature for scaling studies. CG already has this feature (thanks to @csiefer2 :-) ). AztecOO's GMRES does too.

Possible Solution

It may be possible to do this with a custom StatusTest. The StatusTest would have access to the iteration object, which in turn has access to GMRES' upper Hessenberg matrix (actually matrices, since we're talking about Belos::PseudoBlockGmresIter).

Assignee
Assign to
Time tracking