You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think I know why this is happening. The connections object does not know how many presynaptic inputs it has. It infers that number from the synapse data it gets. So if the spatial pooler forms zero connections from an input, then that input will not be counted.
. So if the spatial pooler forms zero connections from an input, then that input will not be counted.
that sounds reasonable. Should just mention in a comment "The number of inputs is infered from input-synapses formed, so it does not have to be exactly the same."
connections object does not know how many presynaptic inputs it has. It infers that number from the synapse data it gets
And let me follow up with a question, are these potential synapses? Ie, if it's not formed initially, it never would later. Or a new segment can be created on uncovered input-space if needed?
If the latter, it's ok, if the former, we should use this to check for some sensible settings. As I can form a SP 100k inputs -> 200 cols. And obviously
Reproduce: create a SP in python with a large number of inputs, print it. The output does not match.
probably some casting/integer overflow bug, either only in the print statement (low bug), or in the SP/Conn parameter.
Output
Inputs above incorrect.
The text was updated successfully, but these errors were encountered: