Skip to content

feat: HyperANF implementation#841

Open
SemyonSinchenko wants to merge 4 commits into
graphframes:mainfrom
SemyonSinchenko:840-hyperANF
Open

feat: HyperANF implementation#841
SemyonSinchenko wants to merge 4 commits into
graphframes:mainfrom
SemyonSinchenko:840-hyperANF

Conversation

@SemyonSinchenko
Copy link
Copy Markdown
Collaborator

What changes were proposed in this pull request?

  • HyperANF
  • bump versions in CI matrix

Why are the changes needed?

Close #840

@SemyonSinchenko SemyonSinchenko changed the title [WIP] feat: HyperANF implementation feat: HyperANF implementation Jun 2, 2026
@SemyonSinchenko
Copy link
Copy Markdown
Collaborator Author

@james-willis I will add python bindings (connect/classic) and docs after pre-approve of the API design.

I was thinking a lot... It looks like this one is still neccessary.
@SemyonSinchenko
Copy link
Copy Markdown
Collaborator Author

The final goals are HyperBALL, approximate closeness centrality, etc. All of these are just simple transformations on top of the HyoerANF. Should I add these in the same PRs or in follow-up PRs?

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.

feat: hyperANF

1 participant