Add parallel percolation centrality - #161
Open
paumartin2407 wants to merge 1 commit into
Open
paumartin2407 wants to merge 1 commit into
paumartin2407 wants to merge 1 commit into
Conversation
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
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.
Adds a parallel implementation of percolation_centrality.
I used the existing betweenness_centrality implementation as the main reference, since both algorithms iterate independently over source nodes and use the same shortest-path machinery. The implementation splits source nodes into chunks, computes partial percolation centrality contributions in parallel, and then reduces the partial results before applying the final normalization.
I also added the backend registration, benchmark, generated backend metadata, and timing heatmap.
Tests run:
Contributes to #82
I used AI assistance during development to help understand the existing implementations, reason through the parallelization approach, and review the changes. I manually implemented, inspected, and tested the final code.
I’m happy to receive feedback, discuss the approach, and iterate on the implementation if needed. If the maintainers find this contribution useful, I’d also be interested in working on more of the parallelization opportunities and would be very open to some guidance or mentorship on which algorithms would be most valuable to tackle next.
@dschult @Schefflera-Arboricola