Support for edge multiplicities in non_distributed_betweenness_centrality #2
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
Pull request boostorg#6 in boostorg/graph changes some internal structs used by graph-parallel, and so some fixes have been made so it still compiles. Note that support for multiplicities has not been added yet.
…ality Added the possibility to include edge multiplicities in non_distributed_betweenness_centrality.
|
Of course, the next (and I guess final) step for this feature is to get it implemented in the fully distributed version of |
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.
Added the possibility to include edge multiplicities in
non_distributed_betweenness_centrality. Also, this fixes the compilation issues caused by PR #6 in boostorg/graph.Note: The named parameters retrieval has been changed a little bit, not only to get
edge_multiplicitybut also to make it similar to the sequentialbrandes_betweenness_centrality(thetypedefdeclarations). This has been done so bothweight_mapandmultiplicity_mapcan be used optionally, which was not the case before (i.e. there would be a compilation error if you didn't provideweight_map, as explained in this message in the Boost mailing list). Please point it out if there was any reason for it and should not be changed. On the contrary, if this change is right it should also be done in the parallel version ofbrandes_betweenness_centrality.