Pascal, Matt, I might have this wrong, but HTM Engine refers to the Network API no? HTM.java can process lat/long data in its Network API. If there is no other criteria, perhaps HTM.java could be an alternative?
On Mon, Aug 3, 2015 at 5:42 PM, Matthew Taylor <[email protected]> wrote: > Hi Pascal, > > First of all, thanks for all your interest in NuPIC and HTM. I can > tell you're really excited about this stuff and I love that kind of > energy in our community! > > Taurus was established as a scalar anomaly detection system, not a > geospatial anomaly detection system. Because all of its data displays > are tuned towards scalar charts and graphs, I'm not sure how much help > it will be. > > This leads me to the next point.... HTM Engine was also build for > scalar anomaly detection, not geospatial :(. The pretty much means > that you will not be able to pass HTM Engine "timestamp / lat / long" > events. It currently only works for "timestamp / scalar value" input. > > But, this doesn't mean things are hopeless. IMO there are many great > opportunities to improve the interface of HTM Engine. There are > several things I wish that it did: > > - prediction > - multiple input fields > - geospatial encoding > > Just to name a few. If these are features that others want to see in > HTM engine, please file a ticket so we can prioritize our work: > https://github.com/numenta/numenta-apps/issues/new > > Regards, > > --------- > Matt Taylor > OS Community Flag-Bearer > Numenta > > > On Mon, Aug 3, 2015 at 2:14 PM, Pascal Weinberger > <[email protected]> wrote: > > Hey All! > > > > For the htmengine infrastructure for nostradamIQ, I was trying to > understand > > Taurus and use it as a template to build on, as it already has multiple > > metrics (stock and twitter) for multiple classes (companies). This is > what > > would be appropriate for nostradamIQ as well... e.g. streaming multiple > > metrics like air pressure etc. for multiple geofences. > > > > This is at least the idea... to get anomaly scores for each metric in > each > > geolocation plus one HTM anomaly model on top of it all (to capture > > geophysical correlations) and then build a logistic-regression model > > combining the anomalies to evaluate the likelihood for different natural > > disasters for each region ... > > > > Digging into Taurus, I learn that this is a bit too much for me alone... > > I still think though that this is a really valuable project and feel > like it > > could make a good contribution to our general safety and preparedness. > > > > My question now is two-fold: > > a) Do you think this is a valid approach? Do you have ideas? concerns? > > b) Would any more experienced programmer // engineer like to join and > work > > on this? Anyone from Numenta? Take Grok to the next level? :) > > > > This would really help, as I am not experienced enough to build this > complex > > architecture quickly alone and the earlier it stands and learns, the > quicker > > we can all benefit from it. > > > > > > Thank you for any help! > > > > --Pascal > > -- *With kind regards,* David Ray Java Solutions Architect *Cortical.io <http://cortical.io/>* Sponsor of: HTM.java <https://github.com/numenta/htm.java> [email protected] http://cortical.io
