Congratulations on getting this working. I think visualisation is very important to understand what the HTM does so this will really help newcomers especially. The current experience of using NuPIC at the command line is that it is too black box IMO and the user does not get any feel for the neural net behaviour. I have not had a chance to try but will do so shortly.
One thing I would have liked to see is a native Windows version as it appears to only be compatible with Linux at the moment? While NuPIC is a library of Python functions and classes it seems to me NuStudio is more like an self-contained, GUI-based application program and as such it should have a 1-click installation procedure and then run from the Start Menu (or Mac equivalent). I think this would improve take up hugely if you could do it. Then NuStudio becomes a software "product" rather than library (which is what NuPIC itself is) (I realize you are constrained by the underlying NuPIC libs which seem to be highly Unix specific. Never quite understood why however, as C++ and Python are both -- obviously! -- available in Windows) And yes, to echo other people, you absolutely DO need a tutorial! I would suggest make a video tutorial as this takes less time. John. On Wed, Sep 10, 2014 at 12:39 AM, David Ragazzi <[email protected]> wrote: > Hello NuPICers! > > Just for inform that in all these days I was out, I was creating an a tool > that > I believe will be a breakthrough for the community. This tool calls > "NuPIC Studio", or just NuStudio. NuStudio is an all-in-one tool that > allows users create a HTM neural network from scratch, train it, collect > statistics, and share it among the members of the community. It is not just > a visualization tool but an HTM builder, debugger and laboratory for > experiments. It is ideal for newbies with little intimacy with NuPIC code > as well as experts that wish a better productivity. Among its features and > advantages I list: > - Users can open, save, or change their "HTM projects" or of other > developers. A typical project contains data to be trained, neural network > configuration, statistics, etc, which can be shared to be analysed or > integrated with other projects. > - The HTM engine is the own original NuPIC libray (Python distribution). > This means no port, no bindings, no re-implementation, etc. So any changes > in the original nupic source can be immediatedly viewed. This helps users > that wish test improvements like new encoders or even hierarchy, attention, > and motor integration. > - The project is pip-installable and for desktop use. > > Project details: > - All code is implemented in Python. When I say "all code", I really mean > that code like GUI, 3d simulation, etc, are writen in Python and use > open-source and cross platform components. > - All GUI stuff (forms, controls, etc) is implemented in PyQT. PyQT is the > version of the famous QT adapted for python apps, which is open-source, > cross-platform, complete, and very easy to code and change. > - All utilities like XML serialization, canvas 2d, etc, also are > implemented in PyQT. > - A front-end object-oriented layer also written in Python is provided in > order to ease the understanding of the NuPIC code and keep backwards > compatibility. This means that someone with less experience in NuPIC could > re-use this front-end in her projects. > > The project's site is: > https://github.com/DavidRagazzi/nupic.studio > > and you can see some screen-shots attached to this message. > > Surely it still is not 100%, and it's expected that some installation > issues arise, but I hope optimize the process as soon as possible. By the > way, it works reasonably well and any people is welcome to try it or even > improve it. > > I look forward for your feedback, it is very important! > > Cheers, > David > > -- > David Ragazzi > MSc in Sofware Engineer (University of Liverpool) > Try NuPIC Studio! https://github.com/DavidRagazzi/nupic.studio > -- > "I think James Connolly, the Irish revolutionary, is right when he says that > the only prophets are those who make their future. So we're not > anticipating, we're working for it." >
