Replace VectorEncoder usage

Question

Replace VectorEncoder usage

scottpurdy opened this issue 9 years ago · comments

@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.

Alexander Lavin · Answer 1 · Wed Apr 01 2015 22:02:55 GMT+0800 (China Standard Time)

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

Scott Purdy · Answer 2 · Fri Apr 03 2015 07:45:45 GMT+0800 (China Standard Time)

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.

Alexander Lavin · Answer 3 · Fri Apr 03 2015 12:18:51 GMT+0800 (China Standard Time)

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 · Answer 4 · Fri Apr 03 2015 16:35:27 GMT+0800 (China Standard Time)

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.

Alexander Lavin · Answer 5 · Fri Apr 03 2015 20:31:52 GMT+0800 (China Standard Time)

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

Scott Purdy · Answer 6 · Sat Apr 04 2015 04:12:35 GMT+0800 (China Standard Time)

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