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

BDDC Example #728

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

BDDC Example #728

wants to merge 1 commit into from

Conversation

jeremylt
Copy link
Member

@jeremylt jeremylt commented Apr 6, 2021

Nothing much to look at here yet. I'm just putting this here to make it easier to see/comment on what I'm doing.

@jeremylt jeremylt self-assigned this Apr 6, 2021
@jeremylt jeremylt force-pushed the jeremy/bddc branch 7 times, most recently from cf2dd0e to 68502ef Compare April 14, 2021 18:32
@jeremylt jeremylt force-pushed the jeremy/bddc branch 5 times, most recently from 3c49d53 to 07eaff5 Compare April 16, 2021 20:23
@jeremylt
Copy link
Member Author

There is some debugging to do after #744 merges, but this should be close. The open task is prolonging into the broken space - We don't really have a way to go from 1 qfunction output into a pair of target vectors

@jeremylt jeremylt force-pushed the jeremy/bddc branch 2 times, most recently from c2b2f48 to 53349b4 Compare April 18, 2021 22:32
@jeremylt
Copy link
Member Author

I have not started debugging yet, but all of the pieces I want are there. Here's to hoping

@jeremylt jeremylt force-pushed the jeremy/bddc branch 6 times, most recently from 10d7e27 to c250336 Compare April 19, 2021 16:00
@jeremylt
Copy link
Member Author

Huzzah - it compiles. Now to see what else is broken about it.

@jeremylt jeremylt force-pushed the jeremy/bddc branch 3 times, most recently from b82348d to bc61d0a Compare April 19, 2021 18:59
@jeremylt
Copy link
Member Author

jeremylt commented Jul 7, 2023

Oh cool, some memcheck backend change shows that we have a problem with how we are treating memory. That gives some direction to future debugging efforts here

@jeremylt
Copy link
Member Author

ToDo: Fix assembly to use libCEED native assembly

@jeremylt
Copy link
Member Author

jeremylt commented Aug 17, 2023

Turns out the memcheck issue was unrelated - see the vector fix PR.

I wonder if the convergence issue can in part can be related to the loss of accuracy from using coloring to assemble the schur problem, which is part of why I want to switch to libCEED assembly (and it'll be faster) Nope, I assembled the way I assembled for good reasons since I'm assembling the action of several operators in sequence with other actions in between.

@jeremylt
Copy link
Member Author

Note to self - I'm suspicious about possible pollution of helper function input vectors. Also, the addition of the preconditioning contributions back from the restricted problem looks funko

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants