Skip to content

[WIP] Move iterative solver interface and internals to Thyra#1594

Draft
maxfirmbach wants to merge 4 commits into4C-multiphysics:mainfrom
maxfirmbach:Move-iterative-solver-interface-to-thyra
Draft

[WIP] Move iterative solver interface and internals to Thyra#1594
maxfirmbach wants to merge 4 commits into4C-multiphysics:mainfrom
maxfirmbach:Move-iterative-solver-interface-to-thyra

Conversation

@maxfirmbach
Copy link
Contributor

Description and Context

This PR aims to move the iterative solver internals to Thyra with the goal of:

  • Removing the inheritance of LinalgPrecondOperator from Epetra_Operator
  • Removing the necessity to call epetra_operator() during solve with overwritten methods like Apply() for our block sparse matrix implementation, which should cut down the need of inheritance of BlockSparseMatrix from Epetra_Operator
  • Remove the need to store the preconditioner object as Epetra_Operator
  • Moves the LinalgPrecondOperator directly to the projection based preconditioner solver internals
  • Enables the use of individual linear solver status tests on specific multi-physics blocks with GMRES
  • Simplifies some code paths

I put this in draft PR mode as I already know that this does not work with AMGnxn and with the monolithic multigrid from MueLu. Currently this PR serves to see how many tests can pass with the changes made.

Related Issues and Pull Requests

Related to #1400

@maxfirmbach maxfirmbach self-assigned this Dec 11, 2025
@maxfirmbach maxfirmbach added the taskforce: tpetra Issues related to the migration from Epetra to Tpetra label Dec 11, 2025
@maxfirmbach maxfirmbach added this to the Migration to Tpetra milestone Dec 11, 2025
@maxfirmbach maxfirmbach changed the title [solve] Move iterative solver interface and internals to Thyra [WIP] Move iterative solver interface and internals to Thyra Dec 20, 2025
@maxfirmbach maxfirmbach force-pushed the Move-iterative-solver-interface-to-thyra branch from dc77336 to dbc0bd1 Compare December 31, 2025 12:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

taskforce: tpetra Issues related to the migration from Epetra to Tpetra

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant