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

Tune node2vec parameters for link prediction demo #42

Closed
2 tasks
PantelisElinas opened this issue May 10, 2018 · 4 comments
Closed
2 tasks

Tune node2vec parameters for link prediction demo #42

PantelisElinas opened this issue May 10, 2018 · 4 comments
Assignees

Comments

@PantelisElinas
Copy link
Contributor

Description

Currently, the link prediction demo uses fixed parameter values, e.g., p=q=1 and several other parameters, for node2vec. We need to allow for these parameters to be tuned for improved link prediction performance.

User Story

As a: Research Engineer
I want: to tune the hyper-parameters of the node2vec algorithm
so that: I can achieve the highest performance in link prediction

Done Checklist (Development)

  • Code to tune node2vec hyper-parameters
  • Pull request
@PantelisElinas PantelisElinas self-assigned this May 10, 2018
@arc0 arc0 added this to the Sprint 6 milestone Jun 18, 2018
@arc0 arc0 removed this from the Sprint 6 milestone Jul 18, 2018
@youph
Copy link
Contributor

youph commented Oct 10, 2018

@PantelisElinas is this still relevant?

@PantelisElinas
Copy link
Contributor Author

Hi @youph

it is only relevant as a demo notebook or just extending the node2vec example to include tuning the p,q parameters. Since tuning the parameters is something that can be done outside our library, there is nothing to implement.

Regards,

P.

@youph
Copy link
Contributor

youph commented Oct 22, 2018

I agree, so perhaps this should be closed?

@PantelisElinas
Copy link
Contributor Author

PantelisElinas commented Oct 22, 2018

Hi @youph

I think yes, unless we have a need for a demo for parameter tuning, that honestly in this case, I don't think we need.

Regards,

P.

@youph youph closed this as completed Dec 3, 2018
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

No branches or pull requests

3 participants