Node partitioning rework#1659
Merged
Merged
Conversation
If we didn't set processor ids at node creation time, then some may still be unpartitioned, and if we aren't setting them via MeshCommunication of a distributed mesh, then we need another mechanism to partition them.
The Partitioner:: code assumes it's part of a full repartitioning, which we may have disabled.
We always may have to repartition some nodes in some adaptive coarsening cases, but we can skip nodes whose partitioning is still valid. This makes it possible for refinement-based estimators refine and re-coarsen, from any starting node partitioning, without ending up with a different partitioning afterward.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
These first four commits (cherry-picked from #1621 and tweaked) should only make node partitioning slightly more robust for future changes, but I'm going to test with them first in the hopes of pinning down that Civet Rattlesnake failure.
Assuming they work, I'm also going to tack on the work that delays new node repartitioning.