-
Notifications
You must be signed in to change notification settings - Fork 111
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
Usability on Colab #200
Comments
Hi, @cytwill Yes I'm currently using pykg2vec on google colab. The way Im'm doing it is to firstly mount my google drive onto colab using:
Then I clone pykg2vec into my drive:
And finally make the instalation:
(Note: colab may ask you to restart runtime in order to load some packages) From that point on you can use the library inside the colab notebook. Hope this helps! Best regards, |
Hi, Thanks I have made it work on Colab. But when I was trying to modify the parameter of the negative sampling rate from 1 to 20, it was not successful. Hope you can help me fix this, thank you so much! |
Hi again, Yes that error in fact occurs, however it is not completely a bug, at least for TransE (i'm am not sure what model you are using, but I'm considering transE since is the most "basic" pairwise model). On the original paper of TransE the author generates a batch with the same ammount of negative triples and positive triples. So in case you are using TransE the negative rate has to always be 1. In pairwise models that use adversarial negative sampling such as RotatE you can in fact alter the negative rate to be higher. Pseudo code from the original TransE paper However i think that you are right in that, the error should be prevented, the most simple way to do this is to probably not allow the changing of negative rate in pairwise models that do not use such sampling(such as transE). Maybe you should open an issue so someone with more experience in the library can propse a fix. Hope this was helpfull. :) Rodrigo Pereira |
Ok, thanks for your help! |
Hi, there was a command name mismatch between the README and the implementation. It has been fixed and merged. Thanks for reporting this. |
I feel it is a good choice to show off our use cases in colab, it can be more straightforward to users. |
To whom it may concern,
I am wondering if anyone has tried this package on Google Colab? I currently try to test this package on Colab, but when I processed to Validate the Installation, it suggests there is no command named "pykg2vec-train".
Hope someone can help! Thanks!
The text was updated successfully, but these errors were encountered: