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

ShyLu: use MueLu as coarse solver for ShyLy/FROSch #5851

Open
mayrmt opened this issue Sep 4, 2019 · 12 comments
Open

ShyLu: use MueLu as coarse solver for ShyLy/FROSch #5851

mayrmt opened this issue Sep 4, 2019 · 12 comments
Assignees
Labels
pkg: MueLu pkg: ShyLU type: enhancement Issue is an enhancement, not a bug

Comments

@mayrmt
Copy link
Member

mayrmt commented Sep 4, 2019

Enhancement

@trilinos/shylu

@searhein wants to experiment with MueLu as a coarse solver for his ShyLu/FROSch preconditioner. This issue is just meant to track and discuss some progress.

@mayrmt mayrmt added type: enhancement Issue is an enhancement, not a bug pkg: MueLu pkg: ShyLU labels Sep 4, 2019
@mhoemmen
Copy link
Contributor

mhoemmen commented Sep 4, 2019

Be careful of circular dependencies. ShyLu depending on MueLu directly (even optionally) means that MueLu can't depend on ShyLu directly. (Using ShyLu as a smoother or coarse-grid solver for MueLu would also make sense.)

It's probably healthier to put this kind of code fully downstream, in TrilinosCouplings.

@mayrmt
Copy link
Member Author

mayrmt commented Sep 4, 2019

@mhoemmen Thanks for pointing this out! I didn't think about that so far.
@searhein, let's discuss this soon.

mayrmt added a commit to mayrmt/Trilinos that referenced this issue Feb 17, 2021
In this first draft, a 3D elasticity example is done. Certain problem
dimensions, e.g. spatial dimension and number of nullspace vectors, is
read from the xml file. That's not a great solution in the long run, but
is ok to get our feet on the ground.

Part of trilinos#5851.
@mayrmt
Copy link
Member Author

mayrmt commented Feb 17, 2021

@searhein I've made a first attempt at using MueLu as a subdomain solver for an elasticity problem. I've pushed the implementation to the branch frosch-muelu-for-elasticity to my Trilinos fork.

@srajama1
Copy link
Contributor

@mayrmt This is going to be interesting ! I have never thought this would even be a use case. (MueLu as a subdomain solver). Are your subdomains that large that you can't use the standard approach (direct methods or incomplete methods) ? As @mhoemmen said above, we need to make sure we can enable all packages correctly. This may not be a problem if just ShyLU_DD will depend on MueLu, and not ShyLU itself.

@mayrmt
Copy link
Member Author

mayrmt commented Feb 18, 2021

@srajama1 Right now, only FROSch has a optional dependency on MueLu. @searhein and I will discuss this.

@searhein
Copy link
Contributor

@srajama1 Our primary goal is actually to use MueLu as the coarse solver. However, FROSch uses the same class (SubdomainSolver) to set up both the subdomain and the coarse solver. Therefore, we can then try out both.

@github-actions
Copy link

This issue has had no activity for 365 days and is marked for closure. It will be closed after an additional 30 days of inactivity.
If you would like to keep this issue open please add a comment and/or remove the MARKED_FOR_CLOSURE label.
If this issue should be kept open even with no activity beyond the time limits you can add the label DO_NOT_AUTOCLOSE.
If it is ok for this issue to be closed, feel free to go ahead and close it. Please do not add any comments or change any labels or otherwise touch this issue unless your intention is to reset the inactivity counter for an additional year.

@github-actions github-actions bot added the MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. label Feb 19, 2022
@mayrmt
Copy link
Member Author

mayrmt commented Feb 19, 2022

@searhein and I are still actively pursuing this.

@mayrmt mayrmt removed the MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. label Feb 19, 2022
ndellingwood added a commit that referenced this issue Feb 6, 2023
…6af130

From repository at [email protected]:kokkos/kokkos.git

At commit:
commit 36f65d03f48e504e63ad124f7f5cf74dd46af130
Merge: f4cc47a31 0f820d0d2
Author: Damien L-G <[email protected]>
Date:   Fri Feb 3 12:47:26 2023 -0500

    Merge pull request #5851 from crtrott/no-deprecated-3-in-makefile-400

    [4.0.0] Don't enable deprecated code 3 in Makefile builds anymore
@github-actions
Copy link

This issue has had no activity for 365 days and is marked for closure. It will be closed after an additional 30 days of inactivity.
If you would like to keep this issue open please add a comment and/or remove the MARKED_FOR_CLOSURE label.
If this issue should be kept open even with no activity beyond the time limits you can add the label DO_NOT_AUTOCLOSE.
If it is ok for this issue to be closed, feel free to go ahead and close it. Please do not add any comments or change any labels or otherwise touch this issue unless your intention is to reset the inactivity counter for an additional year.

@github-actions github-actions bot added the MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. label Feb 22, 2023
@mayrmt
Copy link
Member Author

mayrmt commented Feb 22, 2023

@searhein and I are still working on this.

@mayrmt mayrmt removed the MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. label Feb 22, 2023
ndellingwood added a commit to ndellingwood/Trilinos that referenced this issue Mar 17, 2023
…6af130

From repository at [email protected]:kokkos/kokkos.git

At commit:
commit 36f65d03f48e504e63ad124f7f5cf74dd46af130
Merge: f4cc47a31 0f820d0d2
Author: Damien L-G <[email protected]>
Date:   Fri Feb 3 12:47:26 2023 -0500

    Merge pull request trilinos#5851 from crtrott/no-deprecated-3-in-makefile-400

    [4.0.0] Don't enable deprecated code 3 in Makefile builds anymore
Copy link

This issue has had no activity for 365 days and is marked for closure. It will be closed after an additional 30 days of inactivity.
If you would like to keep this issue open please add a comment and/or remove the MARKED_FOR_CLOSURE label.
If this issue should be kept open even with no activity beyond the time limits you can add the label DO_NOT_AUTOCLOSE.
If it is ok for this issue to be closed, feel free to go ahead and close it. Please do not add any comments or change any labels or otherwise touch this issue unless your intention is to reset the inactivity counter for an additional year.

@github-actions github-actions bot added the MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. label Feb 24, 2024
@mayrmt
Copy link
Member Author

mayrmt commented Feb 24, 2024

@searhein and I are still working on this.

@github-actions github-actions bot removed the MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. label Feb 25, 2024
@jhux2 jhux2 added this to MueLu Aug 12, 2024
@jhux2 jhux2 moved this to Backlog in MueLu Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pkg: MueLu pkg: ShyLU type: enhancement Issue is an enhancement, not a bug
Projects
Status: Backlog
Development

No branches or pull requests

4 participants