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

Update API for node2vec and biased random walks #4841

Open
wants to merge 42 commits into
base: branch-25.02
Choose a base branch
from

Conversation

jnke2016
Copy link
Contributor

@jnke2016 jnke2016 commented Dec 28, 2024

This PR

  1. Add MG support for node2vec random walks on the C, PLC and Python API
  2. Fix renumbering bug in the CAPI for node2vec and biased random walks
  3. Enable and fix bug in the MG C tests
  4. Deprecate legacy node2vec and uniform random walks
  5. Add SG and MG support for Biased random walks

closes #3277
closes #2558
closes #2559
closes #2560
closes #2561

# padded results. The flags 'legacy_result_type' and 'use_padding" should be
# removed.

if legacy_result_type or use_padding is False:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Note... it seems like the old mechanism (coalesced format) is not particularly helpful other than a modest savings in memory on a small result type anyway.

We don't intend to support that in the C++ code any longer. If we need to continue to support this old mechanism while it is deprecated before we can delete it I would suggest implementing something to convert the format within the python layer.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We still have the old mechanism around and I deprecated the coalesced path in the python API. Since there is no real benefit of using the coalesced path, I suggest to not support in the new API. @rlratzel any thoughts?

@jnke2016 jnke2016 self-assigned this Jan 11, 2025
@jnke2016 jnke2016 added this to the 25.02 milestone Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants