Hi David, I agree it's best to move forward. I believe the Network API and the OPF already supports the new TemporalMemory. You have to specify "tm_py" for the "temporalImp" parameter.
--Subutai On Thu, Oct 16, 2014 at 5:19 AM, David Ragazzi <[email protected]> wrote: > Hi guys, > > Fortunatelly many people are using NuPIC Studio to getting started with > NuPIC. This is nice! However a problem arose: once their projects are well > tunned, how finally code their projects to consume NuPIC. Thinking on that, > my idea is create a NUPIC Studio tool that would automatically generate > source code for those that wish use NuPIC Network API on their > applications. Actually this tool would be available as a "tab page" besides > NodeSelector tool. This way when a user create a region on the NodeSelector > tool, he might click on SourceCode tool and immediately see the source code > needed for build his HTM using the NuPIC Network API. This would improve > the life of many people (including mine)! > > The only problem that I've seen is that NuPIC Studio is using the new > TemporalMemory while Network API use the old TemporalPooler (as far I > know). So the temporal parameters set by user wouldn't be enough to pass to > Network API. So either Network API should be updated to use the new TM or > NuPIC Studio should use the old TP. > > What do you think? > > -- > David Ragazzi > MSc in Sofware Engineer (University of Liverpool) > OS Community Commiter at Numenta.org > -- > "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." >
