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

[FEA][NV] Expose vertex data support in similarity metric (weighted jaccard feature) #31

Closed
afender opened this issue Jan 4, 2019 · 1 comment
Assignees
Labels
doc Documentation feature request New feature or request
Milestone

Comments

@afender
Copy link
Member

afender commented Jan 4, 2019

Account for vertex weights in the modified Jaccard similarity. This allows using PageRank data rather than just vertex degree for instance. More details in this publication.

This should be exposed with its own API as it has its own parameters and the formula is different than the regular Jaccard feature.

@afender afender added feature request New feature or request python doc Documentation labels Jan 4, 2019
@afender afender added this to the 0.6.0 milestone Jan 4, 2019
@afender afender self-assigned this Jan 4, 2019
@afender
Copy link
Member Author

afender commented Jan 28, 2019

Subtasks checklist for python:

  • Python bindings and API
  • Documentation
    • Doxygen (C++)
    • Sphinx (Python)
  • Validate everything in Jenkins

@afender afender changed the title [FEA][NV] Expose vertex data support in similarity metric [FEA][NV] Expose vertex data support in similarity metric (weighted jaccard feature) Jan 28, 2019
@afender afender assigned aschaffer and unassigned afender Jan 30, 2019
BradReesWork pushed a commit that referenced this issue Sep 16, 2020
merge 0.16 release into forked
alexbarghi-nv added a commit to alexbarghi-nv/cugraph that referenced this issue Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Documentation feature request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants