+1 Excellent initiative!
On 23 January 2014 14:29, Matthew Taylor <[email protected]> wrote: > You guys want a C++ core extracted from NuPIC, so we're going to plan it. > Starting next sprint[1], we're going to work on pulling all the C++ out of > NuPIC into a repo called 'nupic-core'. > > We had a meeting Monday[2] where we discussed many of the details of this > plan, and I created some diagrams to describe the plan[3]. Please take a > moment to review these and provide feedback for this plan. The end goal is > this: > > https://github.com/numenta/nupic/wiki/images/nupic-core-extraction-goal.jpg > > We still have some open questions that we'll work out as we go along, for > example: > > 1. Should there be different repos for language bindings AND clients? Or > should they be combined in one repository? > 2. How will our build automation need to change to accommodate these > changes? > 3. Do we include general encoders in nupic-core? (they are all currently > within python) > > I'd like to hear opinions on this whole plan. We want nupic-core to be > generic enough to provide what everyone wants, so if this plan seems to > restrict your particular use-case, let's discuss it. > > [1] https://github.com/numenta/nupic/issues?milestone=9 > [2] > https://github.com/numenta/nupic/wiki/2014-January-Core-API-Meeting-Notes > [3] https://github.com/numenta/nupic/wiki/NuPIC-Core-Extraction-Plan > > --------- > Matt Taylor > OS Community Flag-Bearer > Numenta > > > > _______________________________________________ > nupic mailing list > [email protected] > http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org > >
_______________________________________________ nupic mailing list [email protected] http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org
