Yes, this is a pretty straightforward case that is supported (as long as the microcontroller supports C++). In this case it might be better to not use an encoder on the panels since encoder output is generally are more inefficient than the original numbers. It might be best to transmit the raw data and instantiate the encoders in the Philippines.
All the Link classes use bounded buffers already (fixed length contiguous buffers). The dimensions are fixed at network construction time and the Regions have access to the pointers. Or, the application can just ignore that and instantiate encoders, algorithms directly. We don't have UBF or networking right now. I'm interested to learn more about UBF. I don't know much about it other than it's used in Erlang. Networking could be added in - not sure yet if that belongs in nupic.core or in supporting libraries. That would be something we'd want to decide together. --Subutai On Sat, Jan 25, 2014 at 10:38 PM, Stewart Mackenzie <[email protected]>wrote: > > > > For example, a mate of mine is electrifying outlying Philippines islands ( > tinypipes.net). Off grid is hard, he's using solar, could he spin up an > encoder only on his microcontroller installed on the panels which then > intermittently phone home (GSM) and upload the data. To a first level > region located in the Philippines somewhere. that region then uploads to > the classifier based somewhere else in the world. > > These are the kinds of usecases we should be engineering for. > The inevitable Internet of Things is here, if we aren't ready for it you > can be sure the greater community wont adopt our tech. > > So being tight and fitting into small places with good predictions is > terribly important. > > So replace the 2DLink/3DLink classes with bounded buffers? > This entails serialization (UBF) and built in networking sockets for each > component. The more types of protocols they support the better.... maybe a > dependency like nanomsg might bring more pleasure than pain? > > >As far as the application creating the graphs, loops, etc. yes that is > >supported. The Network API is optional. The host could directly call > >the > >lower level algorithm/encoder classes and bypass the Network API > >altogether. > > > >Hope this helps, > > > > Kind regards > Stewart > > -- > Please excuse my typos and brevity > > _______________________________________________ > 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
