I just wanted to point out to all of you that that is exactly the way I think new features should be proposed, following the guidelines I've recently written up on the Development Process wiki[1]. Thanks, Marek, for the good example.
[1] https://github.com/numenta/nupic/wiki/Development-Process --------- Matt Taylor OS Community Flag-Bearer Numenta On Sun, Nov 17, 2013 at 6:04 AM, Marek Otahal <[email protected]> wrote: > Scalar encoder is used almost everywhere (SDRCategory, Date enc,..). I've > found some (commented out) checks in SDRCategory encoder that ensure number > of ON bits is above certain level ( w>= 3). I thought this is reasonable and > should be used in ScalarEncoder as well. > > It's job of the spatial pooler to ensure that the final SDR has stable (~2%) > # of ON bits at all times. Yet it looks as a possible weakness to have an > encoder that has only 1 bit on at a time. Robustness to noice, comes to > mind. Do you think this is an issue? Limit of min 3 bits ON sounds > reasonable to me, it doesn't make things with small needs too big and yet is > somewhat robust. Also, in the brain, would some feature rarely depend on > just one neuron. > > I've prepared https://github.com/breznak/nupic/tree/scalar_w3 for you to > have a look. There's still one issue with a failing example, but seems ready > to me. > > Thanks, Mark > > -- > Marek Otahal :o) > > _______________________________________________ > 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
