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

Make learning snip more efficient #100

Open
tbekolay opened this issue Sep 28, 2018 · 0 comments
Open

Make learning snip more efficient #100

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

Comments

@tbekolay
Copy link
Member

Currently the communication protocol introduced in #89 is not too efficient. We store metadata in the userData struct, and read it on every timestep to determine what part of the userData struct is used for each learned connection.

It would be more efficient to make nengo_learn.c a jinja template like nengo_io.c so that the metadata and slices of the userData struct associated with each learning connection is known a priori and don't need to be read on every timestep.

If we have time to really bust out the profiler, we should also see if there is any benefit to doing all of the IO in nengo_io.c rather than making separate channels and also doing IO in nengo_learn.c.

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

1 participant