Nope, didn't try either, I downloaded Marek's Ubuntu VM (thanks Marek!),
and everything is working fine there. After the hackaton I wont use the
Snow Leopard laptop anymore, so I wont try again...

On Tuesday, October 1, 2013, freeha azmat wrote:

> @Gari... have you build "Cerebo" using vagrant as well?
>
>
>
>
>    *From:* Garikoitz Lerma-Usabiaga <[email protected]<javascript:_e({}, 
> 'cvml', '[email protected]');>
> >
> *To:* NuPIC general mailing list. <[email protected]<javascript:_e({}, 
> 'cvml', '[email protected]');>>
>
> *Sent:* Tuesday, October 1, 2013 1:02 AM
> *Subject:* Re: [nupic-dev] Installation Error Resolved
>
> Hi!
> thanks to everybody, I couldn't make it with OSX, with all possible
> combinations of versions and packages, there must be some strange default
> underneath because I always got the same error.
>
> Now I installed Vagrant and as Pedro said everything is running smoothly,
> excepting one (different) error:
>
> E       Exception: Encoding Error: encoding value 1.000000
>                     expected [1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0]
> E        got None
> tests/unit/py2/nupic/encoders/nonuniformscalar_test.py:54: Exception
>
>
> Should I worry about it?
>
> Thanks for all the help!
> Gari
>
>
>
>
> On Mon, Sep 30, 2013 at 9:56 PM, Pedro Tabacof <[email protected]> wrote:
>
> Hello,
>
> I tried building NuPIC first on a 32bit Linux Mint 15, unsuccessfully.
> Then I changed to the 64bit version, and while I managed build NuPIC, there
> were some failed tests and the hotgym example didn't work through the OPF
> client. I used the latest 2.7 Python version alongside the latest 4.7 GCC,
> without any Python 2.6 on my virtual machine. Unfortunately since I tried
> so many things, I don't have the specific error logs, but most of them were
> known issues regarding 32 bit Linux and the lack of Python 2.6.
>
> Instead of trying to hack my way through the Linux incompatibilities
> issues (since Python 2.6 and Pythonbrew are deprecated, it's not fun to try
> to get them working), I've decided to take another approach and use the
> Vagrant VM (
> https://github.com/numenta/nupic/wiki/Running-Nupic-in-a-Virtual-Machine).
>
> So far it has been a much smoother experience and I have finally managed
> to pass all tests but one. While doing the Python test (run_tests.sh), the
> script accused this problem:
>
> ==================================== ERRORS
> ====================================
>
>  ERROR collecting
> tests/unit/py2/nupic/bindings/algorithms/fast_cla_classifier_test.py
> tests/unit/py2/nupic/bindings/algorithms/fast_cla_classifier_test.py:43:
> in <module>
> >   from py2.nupic.algorithms import cla_classifier_test
> E   ImportError: No module named py2.nupic.algorithms
>
> Should I worry about it? Anyways, if anyone is encountering compilation or
> test problems, I highly recommend to use the Vagrant VM. Thanks for the
> person who set it up and wrote the walkthrough!
>
> Pedro.
>
>
> On Mon, Sep 30, 2013 at 12:38 PM, Matthew Taylor <[email protected]> wrote:
>
> Even better! :) Thanks, Austin.
>
> ---------
> Matt Taylor
> OS Community Flag-Bearer
> Numenta
>
>
> On Mon, Sep 30, 2013 at 8:26 AM, Austin Marshall <[email protected]>wrote:
>
> With the exception of matplotlib and pytz (which are, for the time being,
> bundled with nupic), the list of modules which are explicitly required by
> nupic can be found in
> https://github.com/numenta/nupic/blob/master/external/common/requirements.txt.
>  Some of those, have separate requirements, all of which are currently
> checked in at
> https://github.com/numenta/nupic/tree/master/external/common/pip-cache.
>
> For an isolated environment with the dependencies pre-installed, there is
> https://github.com/numenta/nupic-darwin64 and 
> <https://github.com/numenta/nupic-linux64>
>
>
_______________________________________________
nupic mailing list
[email protected]
http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org

Reply via email to