Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Teach users about initial PES functions #99

Closed
tbekolay opened this issue Sep 28, 2018 · 2 comments
Closed

Teach users about initial PES functions #99

tbekolay opened this issue Sep 28, 2018 · 2 comments
Labels

Comments

@tbekolay
Copy link
Member

As we found out in #89, the choice of the initial function across a PES learned connection can affect its behavior significantly. While we should determine more robust ways to discretize in the long term (see #83), in the short term we should at least attempt to inform users that this choice makes a big difference.

A few ideas on how we might do this:

  • Make an example showing how different things can be given the initial function (similar to what's in the Multidimensional learning #89 comment thread)
  • Raise a warning either at model construction or model build time if the user has made a learned connection and specified a function. This is similar to what we're doing with connection from nodes with synapse=None right now. This assumes that the identity function (communication channel) always puts weights in a decent range, which might not be true.
@drasmuss
Copy link
Member

drasmuss commented Apr 5, 2019

I believe the discretization has been improved so that using an all-zero initialization no longer causes things to fall apart, @hunse can confirm?

@hunse
Copy link
Collaborator

hunse commented Apr 8, 2019

Yep. We now test initializing with zeros, too: https://github.com/nengo/nengo-loihi/blob/master/nengo_loihi/tests/test_learning.py#L37

@hunse hunse closed this as completed Apr 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants