So, this problem shows up when I'm building my final project for my univ.
A SpatialPooler is designed to be easily construct-able. And the default format of the constructor is: SpatialPooler(input_shape, output_shape).
So, when you call the constructor like so, SpatialPooler({128}, {32}) you'll expect a SP that takes in 128 bits and generates a 32bit output. But no, in fact this calls to the alternative constructor for topology. i.e. SpatialPooler(input_shape, kernel_size).
So, this problem shows up when I'm building my final project for my univ.
A SpatialPooler is designed to be easily construct-able. And the default format of the constructor is:
SpatialPooler(input_shape, output_shape). So, when you call the constructor like so,SpatialPooler({128}, {32})you'll expect a SP that takes in 128 bits and generates a 32bit output. But no, in fact this calls to the alternative constructor for topology. i.e.SpatialPooler(input_shape, kernel_size).This is super confusing, We'll have to fix this.