tools: scale and shift vertex and edge weights for METIS and SCOTCH #224
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
Codecov ReportBase: 52.11% // Head: 51.85% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #224 +/- ##
==========================================
- Coverage 52.11% 51.85% -0.26%
==========================================
Files 37 37
Lines 6699 6734 +35
==========================================
+ Hits 3491 3492 +1
- Misses 3208 3242 +34
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Seems OK to me. |
It's useful for naming T::one() and T::zero().
These tools cannot handle null weights for vertices nor edges, so the input weights are "zoomed in" so that the sum of the weights plus one is INT_MAX, and then shifted by one. zoom_in() returns a Vec<O> directly, since it's what SCOTCH and METIS want. I tried to make it a `impl Iterator<Item = impl Iterator<Item=O>>` though it made rustc crash.
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.
These tools cannot handle null weights for vertices nor edges, so the input weights are "zoomed in" so that the sum of the weights plus one is INT_MAX.
Closes #220
TODO
return an iterator instead of a Vecrustc panic :s