This repository has been archived by the owner on Sep 1, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 110
Replace VectorEncoder usage #137
Comments
With the removal of VectorEncoder, is there now an intended replacement encoder in nupic/encoders? |
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. |
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? |
there's a PR on 'removing unused encoders' under Nupic, where I mentioned I
will probably need VectorEnc too. You can find the removing commits and
revert and bring it back either to nupic or nupic.research.
|
Thank you @breznak, here's the PR. I'll take a look today. |
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.
@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.
The text was updated successfully, but these errors were encountered: