Skip to content
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

[Ifpack] Move parameters and options to xml-file #365

Open
2 of 4 tasks
dharinib98 opened this issue Feb 12, 2025 · 0 comments
Open
2 of 4 tasks

[Ifpack] Move parameters and options to xml-file #365

dharinib98 opened this issue Feb 12, 2025 · 0 comments
Assignees
Labels
status: in progress Issues that are currently being worked on team: solvers type: enhancement A new feature or enhancement to be implemented

Comments

@dharinib98
Copy link
Contributor

This issue was originally created by @maxfirmbach in https://gitlab.lrz.de/baci/baci/-/issues/1361 on 2024-10-16

Description

Similar to the multigrid and block preconditioning methods, I would like to move the parameter selection of incomplete factorization based preconditioners to xml-files. This would make all the preconditioning business similar and more or less finalizes all the efforts we've been putting into the preconditioning framework. This would also make the transition to Ifpack2 easier.

Possible Solution and Definition of Done

  • Provide a way to configure Ifpack with a xml-file,
  • Replace the input parameter based ILU preconditioners with appropriate xml-file versions and adapt all test cases
  • Delete the Ifpack related input parameters
  • Move to backend based on Stratimikos

Interested Parties

@maxfirmbach

@dharinib98 dharinib98 self-assigned this Feb 12, 2025
@maxfirmbach maxfirmbach added team: solvers status: in progress Issues that are currently being worked on type: enhancement A new feature or enhancement to be implemented labels Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: in progress Issues that are currently being worked on team: solvers type: enhancement A new feature or enhancement to be implemented
Projects
None yet
Development

No branches or pull requests

2 participants