While changing to Temporal Predictor is an easy out for our predicament, I feel that keeping the TP acronym for two different parts of the code will continue to create confusion in the code and on the mailing list. I would vote for officially changing the name to Sequence Memory and just change all of the current TP references to SM to create a clean space for the new TP implementation. I believe that a completely different name is the best solution for the long term, and that should be our focus before we lock it into the API.
That's my 2 cents. Subutai and Scott, what is your opinion? Matt On May 12, 2014, at 2:07 PM, Matthew Taylor <[email protected]> wrote: > Not a bad idea. What do others think? I have no opinion, but looking > at Subutai and Scott for their input... > --------- > Matt Taylor > OS Community Flag-Bearer > Numenta > > > On Mon, May 12, 2014 at 1:03 PM, Fergal Byrne > <[email protected]> wrote: >> >> In light of Jeff's new ideas about Temporal Pooling, every time we mention >> the current Temporal Pooler (TP) in NuPIC, we now have to use a qualifier >> like "the old Temporal Pooler" or "the thing we mistakenly called Temporal >> Pooler, but what we'll be now be calling Sequence Memory". >> >> Since the current TP in fact only does a single timestep prediction, and >> since everyone calls it the TP (in code, in docs, on the lists etc), >> changing from "TP" to some other acronym will be slow, painful and >> error-prone, my suggestion is to keep the initials but switch the name to >> "Temporal Prediction" or (if you want a more active name) "Temporal >> Predictor". >> >> This name sheds anything about temporal pooling, and more correctly >> describes the single thing it does - predict the SP(s) one step ahead using >> recent temporal context. >> >> If we can reach a consensus about this (or please provide a better >> alternative!), we should implement it now in NuPIC before nupic.core goes to >> API release, and before Jeff's new Temporal Pooler begins to appear in >> software. >> >> -- >> >> Fergal Byrne, Brenter IT >> >> Author, Real Machine Intelligence with Clortex and NuPIC >> https://leanpub.com/realsmartmachines >> >> Speaking on Clortex and HTM/CLA at euroClojure Krakow, June 2014: >> http://euroclojure.com/2014/ >> and at LambdaJam Chicago, July 2014: http://www.lambdajam.com >> >> http://inbits.com - Better Living through Thoughtful Technology >> http://ie.linkedin.com/in/fergbyrne/ - https://github.com/fergalbyrne >> >> e:[email protected] t:+353 83 4214179 >> Join the quest for Machine Intelligence at http://numenta.org >> Formerly of Adnet [email protected] http://www.adnet.ie >> >> _______________________________________________ >> 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 _______________________________________________ nupic mailing list [email protected] http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org
