-
Notifications
You must be signed in to change notification settings - Fork 143
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
Accessing the ensembled vectors #43
Comments
In this build process, the labels will appear in There is also a new build process that's part of the conceptnet5 repository, which will give you more up-to-date vectors in |
Thank you - my problem is that I can't find any build-data folder in the repository and so I am not sure where to find these files... would you be able to guid me in this? |
That's where the files created by What happened when you ran |
so I've been running the 16.04 branch....it basically runs through build_conceptnet_retrofitting() which is called in ninja.py. But there's only a source_data folder, I can't find a build_data folder... |
Oh. You haven't run the build yet. Running |
Yes I did run ninja as well... like i ran ninja.py and then I ran ninja but I don't get any new outputs... |
I actually get the error: |
Can you copy and paste the actual output, please? |
What's particularly peculiar about saying you got "Importerror: cannot import ninja from ninja" is that it looks almost like a Python error, and this makes me doubt you're actually running Ninja, which is written in C++. |
I actually don't have that error anymore...when I run ninja it gives the following output: How long would it take for it to complete? It's been running for > 1 hour now. |
It should take a day or so. Keep in mind that this process runs all the conditions of the experiment. |
okay thank you! |
Is it GPU enabled? |
Man, how difficult to set up do you want it to be? This task is memory-constrained, so I think it would actually run much worse on a GPU. |
after running "ninja", where can I find the ensemble vectors?
The text was updated successfully, but these errors were encountered: