This survey is about the htm-community fork of Numenta’s Nupic code repository. The purpose of this survey is to determine the overall goals and direction for this project. We are trying to make plans for what to do with this code and we want to hear from all of you.
I encourage all prospective users to respond. We will leave this survey open indefinitely. Comments & feedback are welcome.
We have an implementation of all of these things which originated in the Numenta repository. Currently none of these things fully work, some are outright broken. This is a work in progress, and we don’t know how long this will take. Please check as many of the features as you’d like:
- Algorithms in C++ - Fast and production ready.
- C++/Python bindings - Fast, production ready, and easy to use.
- Algorithms in Python (no C++) - Good for experimentation
- NetworkAPI (Regions, Links, Engine)
- OPF framework, Swarming, and other parameter optimization techniques
- Other - Write feature requests in reply to this thread
This project started as a clone of Nupic and so it inherited Nupic’s API, which is documented at: http://nupic.docs.numenta.org/stable/api/index.html . Please check ONE of the following:
- Strict API-Compatibility - Community fork should be a drop in replacement for numenta’s nupic.
- Moderate API-Compatibility - Minor API changes are okay, as long as they’re done for good reason, are well documented, and cause minimal disruption.
- Loose API-Compatibility - Improve Nupic as much as possible. My existing applications can be modified to work with a substantially changed API.
Currently the code base is split into two repositories, and there has been some discussion around merging them into one repository. Please check ONE of the following:
- All one repository - Ease of use, better continuous integration, will maintain strict separation between C++, Python, and Python Bindings for C++.
- Separate C++ & Python repositories - I don’t want anything to change.
- I’m interested in C++ only
Thank you for your response.