Repository navigation
The RandomDistributedScalarEncoder needs ability to set numBuckets #443
Description
numBuckets needs an official Parameter in Parameters.java and it needs to be set by the Network API upon initialization.
Care must be taken to guarantee that the resolution is properly calculated and that the param is tested when absent as well.
Activity
rhyolight commentedon Jul 25, 2016
So will
Parametershave access to the input data to calculate the min / max values required to calculate theresolution?cogmission commentedon Jul 25, 2016
I don't believe this is necessary. Alex mentioned that they are "auto-configured" from the
numBucketsparameter... as seen here and here (numBuckets == maxBuckets, deeper in the code)I'm not averse to having encoder params at all. We do it for the DateEncoder (due to it's need for varied configuration), so we can do it for others as well?
cogmission commentedon Jul 25, 2016
For instance, the NAB assumes that the
numBucketsparameter is sufficient and doesn't specifyresolutionspecifically, however HTM.Java doesn't have this so it thinks theresolutionparameter is missing and throwsjava.lang.AnnoyingAsHellException:-PMy fix for this was to add
resolutionto the NAB JSON config file, but if we were going to do it the NuPIC way, we would allow thenumBucketsparameter to be picked up and usher in the configuration.