Hello,
I have just finished the installation of Nupic on a Virtual Machine using VirtualBox and Vagrant, over Windows 7. Although the instructions given at https://github.com/numenta/nupic/wiki/Running-NuPIC-in-a-Virtual-Machine seemed pretty detailed, a couple of things were not that clear to me and this caused me a lot of lost time and frustration. So, I would like to share some hints with the community and hope that if you find them useful they might get included to the installation instructions. I am not sure that the following apply in general but this is what seemed to work in my case: 1) When getting the nupic codebase from GitHub with the command "git clone https://github.com/numenta/nupic.git"; script files were automatically transformed to dos format. The first symptom of this was to get "command not found" and "unexpected end of file" errors when running env.sh (and .bashrc). Moreover, this created fatal errors to the whole build process. Although individual files can be repaired to unix format by using the utility dos2unix <filename>, it is a huge task to find and convert all such files in the directory tree. The solution is to enter the command "git config --global core.autocrlf false" in the Git Shell before issuing the command "git clone https://github.com/numenta/nupic.git";. 2) Running the "pip" command requires su privileges "sudo pip ..." otherwise it ends with a "permission denied" error message. However, if you run the build.sh with sudo, you are going to build the executables under /root and end up in a big mess. 3) Maybe this is obvious to most people but it had me wondering for sometime from which directory to run each command: the "sudo pip" command should be ran from within $NUPIC and the "build.sh" from within $HOME. Keep up the good work! Spyros
_______________________________________________ nupic mailing list [email protected] http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org
