AllowDistributedWells with (default) partitioning method 3 #827
Conversation
This file contains 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
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.
Switch off the merging of the well cells when
--allowDistributedWells==true.This goes against the nature of the partitioner that was designed to allow cell merging. However, with this flag set to true the partitioning results are still different1 to
partitioning-method=1(normal Zoltan). For this reason I think it is better to switch off the main feature of this partitioner instead of delegating the work to the partitioning method 1 when the--allowDistributedWells==true.1 From my limited experimenting, the partitioning of method 3 has fewer overlap cells than method 1. It is also slower on a small grid but gets faster on a big grid (limited testing! one grid with >1.5 million cells) and needs a negligible amount of extra memory (less than 1% extra, and there are procedures before and after partitioning that demand more memory - it is far from peak requirements).