Skip to content
This repository has been archived by the owner on Sep 1, 2023. It is now read-only.

Replace VectorEncoder usage #137

Open
scottpurdy opened this issue Mar 3, 2015 · 6 comments
Open

Replace VectorEncoder usage #137

scottpurdy opened this issue Mar 3, 2015 · 6 comments
Assignees

Comments

@scottpurdy
Copy link
Contributor

@BoltzmannBrain discovered some of the research code is broken due to obsolete VectorEncoder usage. You can replicate the bug with python experiments/sm_test_with_pooling.py from the sensorimotor directory.

It should be fairly simple to swap out the VectorEncoder for another encoder for the motor command.

@BoltzmannBrain BoltzmannBrain self-assigned this Apr 1, 2015
@BoltzmannBrain
Copy link
Contributor

With the removal of VectorEncoder, is there now an intended replacement encoder in nupic/encoders?

@scottpurdy
Copy link
Contributor Author

Can you use a category encoder for the motor commands? There is also a pass through encoder if none of the existing encoders provide what you want.

@BoltzmannBrain
Copy link
Contributor

A category encoder may not be a good solution b/c there's no category list associated with the motor commands; there's a pool of all the sensory elements, but none for the motor commands. Where can I find the removed VectorEncoder code?

@breznak
Copy link
Member

breznak commented Apr 3, 2015 via email

@BoltzmannBrain
Copy link
Contributor

Thank you @breznak, here's the PR. I'll take a look today.

@scottpurdy
Copy link
Contributor Author

I think it should be very easy to add multiple identical encoders without the need for a VectorEncoder.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants