-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bipartite R-mat graph generation. #3512
Merged
rapids-bot
merged 18 commits into
rapidsai:branch-23.06
from
seunghwak:fea_bipartite_rmat
May 1, 2023
Merged
Changes from 3 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
6ebc067
bi-partite R-mat graph generation API
seunghwak b7bc790
Merge branch 'branch-23.06' of github.com:rapidsai/cugraph into fea_b…
seunghwak 124702c
[no ci] initial implementation of bipartite R-mat generator
seunghwak 0c4cbad
[no ci] fix copmile error
seunghwak a6a4cc3
remove unused seed from sramble_vertex_ids()
seunghwak f7c2c73
[no ci] delete inaccurate input parameter check
seunghwak 5181f99
update scramble_vertex_ids
seunghwak ebfc7e3
[no ci] update scramble_vertex_ids to take an R-value input and retur…
seunghwak a930f6c
[no ci] test R-mat generator was ignoring scramble_vertex_ids input p…
seunghwak ca3572d
[no ci] cleanup R-mat generator test
seunghwak 0cdccab
create a separate file for bipartite R-mat grpah generator
seunghwak 79d5325
cleanup R-mat test
seunghwak c257d71
add bipartite R-mat generator code
seunghwak 69c037e
Merge branch 'branch-23.06' of github.com:rapidsai/cugraph into fea_b…
seunghwak b364ca8
copyright year
seunghwak 8fea6f0
bi-partite to bipartite
seunghwak a5b9fd1
Merge branch 'branch-23.06' of github.com:rapidsai/cugraph into fea_b…
seunghwak b9b900e
Merge branch 'branch-23.06' of github.com:rapidsai/cugraph into fea_b…
seunghwak File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wondering, is it the algorithm used here?
https://www.cambridge.org/core/journals/network-science/article/linear-work-generation-of-rmat-graphs/68A0DDA58A7B84E9B3ACA2DBB123A16C
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possibly, but this code basically follows the algorithm used in graph 500 reference code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe not... I just skimmed the abstract, and it seems like the paper claims that edge generation time is just function of the number of edges to generate and irrelevant to scale.
Here, it is dependent on scale. Not sure the algorithm in the paper might actually be faster, but here, scale is pretty much limited, and R-mat graph generation is fast enough for our use cases.