For all those who have been following the issue of HTM.Java receiving its final vetting, it is now fully vetted and will be fully operational following the next upcoming release (0.6.9).
Thanks to @mrcslws (Marcus Lewis) identifying a parameter that gets set internally within the OPF and NuPIC Network API (
potentialRadius), which for global inhibition (the most frequently used mode of operation for the SpatialPooler); is set to the
inputWidth internally instead of its default of “16” - we now have respectable scores within NAB, and Anomaly Detection will no longer be broken. See Marcus’ Blog about the significance of this parameter!
HTM.Java has undergone 2 full re-writes of its TemporalMemory and test, 1 re-write of its SpatialPooler and test, the addition of multiple compatibility and consistency tests - and one full toss out the window! And is now ship-shape!
Thanks also go out to @fergalbyrne (Fergal Byrne), who heroically stepped right up to help smooth over rough spots within the code; @alavin (Alex Lavin), who’s dedication, perseverance and guidance also contributed greatly; @lscheinkman (Luiz Sheinkman) who’s enthusiasm caused him to write the Java Anomaly Detector in the first place; (Matt Taylor) without whom, nothing would get done anywhere :-P; (Subutai Ahmad) who’s early direction contributed greatly; (Gerald Loeffler - Head of Development at cortical.io), who’s advice and never-wavering support kept me going; and (Scott Purdy) who’s advice and general vast knowledge of all things NuPIC, was relied upon very frequently (in the background as his modesty dictates).
Thank you to all the interested parties who have been keeping up with this issue and silently cheering by following closely as indicated by the popularity of this forum post. Your interest was also inspiring for all of us to persevere!
P.S. I only linked 4 users because apparently the Forum is set up to limit user-mentioning to 4 within a post?