Hi, Been (carefully) thinking about this more, it's occupying a disproportionately large amount of time.
I'm going to go one step further: The proof of concept works, NuPIC has cracked it to a large degree. But its based on an old codebase that went through a few fundamental architectural changes. It doesn't support serialization nor can operate in a hierarchy. Most of the issues are about compilation, incompatibilities, the code base is dependency heavy yet... despite all this the algorthims have got it right. I propose we retain the core algorithms and start from scratch. Its the algorithms that are important. What I have brewing will make a distributed HTM dramanically easier to achieve, serialization becomes trivial and it is portable. If nupic is about to do some major move. Then lets at least think about how to make it easier to distribute and serialize. Insane as it sounds. Stewart Matthew Taylor <[email protected]> wrote: >Thanks, Stewart. > >I think we should put the discussion about releases to the side for >awhile, >because it's evident that we cannot release until we've nailed down the >API >for NuPIC. This should take priority. I'll start that discussion soon. > >This has been quite enlightening, and I really appreciate everyone's >input. > _______________________________________________ nupic mailing list [email protected] http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org
