Skip to content
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

Allow returning edge indices from random walk #139

Conversation

pbielak
Copy link
Contributor

@pbielak pbielak commented Aug 8, 2022

This PR addresses the feature request in #137. The changes can be easily ported to pyg-lib (at least in theory 😅 ), but currently, we still rely on torch_cluster, so I added the change here first.

This commit adds an optional argument in the random_walk function, namely return_edge_indices. The default behaviour is not changed, but if a user wants to directly use the edges visited by the random walker, we can return the indices of those edges by setting return_edge_indices to True. New cases are also added to the test suite.

This commit adds an optional argument in the `random_walk` function,
namely `return_edge_indices`. The default behaviour is not changed, but
if a user wants to directly use the edges visited by the random walker,
we can return the indices of those edges by setting
`return_edge_indices` to `True`. New cases are also added to the test
suite.
Copy link
Owner

@rusty1s rusty1s left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Luckily, this was already supported on the CUDA/C++ side :)

@rusty1s rusty1s merged commit cc4696b into rusty1s:master Aug 8, 2022
@pbielak pbielak deleted the dev/pbielak/return-edge-indices-from-random-walk branch August 8, 2022 14:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants