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

Training doesn't work with synapses #54

Closed
hunse opened this issue Sep 5, 2018 · 2 comments
Closed

Training doesn't work with synapses #54

hunse opened this issue Sep 5, 2018 · 2 comments

Comments

@hunse
Copy link
Collaborator

hunse commented Sep 5, 2018

One issue I've run into a number of times is that I've forgotten to make synapses=None on my connections for training, and the training does not converge.

I realize that in some types of networks (recurrent networks?) synapses might be desirable, but I'm wondering if there could be some kind of warning that reminds users if they have synapses in their network, that training might not work.

@drasmuss
Copy link
Member

drasmuss commented Sep 5, 2018

Yeah I think a warning for the special case where you're training over one timestep would make sense (since in that case we can be pretty sure that synapse!=None is a mistake). For training over any steps >1 I'd think no warning though, since it would be not unreasonable for someone to want synaptic filtering there.

@hunse
Copy link
Collaborator Author

hunse commented Sep 5, 2018

Makes sense to me.

If you wanted to be fancy you could check the number of steps versus the time constant of the filter. But that could get messy for more complex filters. Probably better to just have a note about that in some notebook on training networks over time (maybe there already is one).

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

No branches or pull requests

2 participants