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

p::f::T: allow repartitioning #13038

Merged
merged 3 commits into from Dec 15, 2021
Merged

Conversation

peterrum
Copy link
Member

@peterrum peterrum commented Dec 6, 2021

This PR allows to reparation p::f::T with the help of RepartitioningPolicyTools.

To allow AMR for p::f::T, one needs to revive #8834. Also a RepartitioningPolicyTools class that wraps Parmetis would be nice! Anyone interested in doing that?

FYI @elauksap @drwells

@peterrum peterrum changed the title [WIP] p::f::T: allow repartitioning p::f::T: allow repartitioning Dec 8, 2021
{
Assert(cell->at_boundary(pair.first),
ExcMessage("Cell face is not on the boundary!"));
if (cell->face(pair.first)->at_boundary())
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this safe? Or do we have a way to check the previous check when we know the data is comprehensive?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is safe. We are re-partitioning p:f:T. Here we still don't have a good mean to distinguish between actual boundary cells and calls at the boundary of the locally-relevant coarse grid. Such internal boundaries, cause the problem here - but can be safely ignored.

@kronbichler kronbichler merged commit 506f07b into dealii:master Dec 15, 2021
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

2 participants