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

Connection seed not being set in __init__ #725

Closed
cjmpseth opened this issue May 29, 2015 · 3 comments · Fixed by #726
Closed

Connection seed not being set in __init__ #725

cjmpseth opened this issue May 29, 2015 · 3 comments · Fixed by #726

Comments

@cjmpseth
Copy link

If I set a seed when initializing a connection (ie conn = nengo.Connection(a,b,seed=5)) the seed is still left as default None. I think the line "self.seed = seed" is missing in connection.py

hunse added a commit that referenced this issue May 29, 2015
@tcstewar
Copy link
Contributor

Hmm, I'm not actually sure what a seed should even do on a Connection. I would have thought that should be a syntax error. (The randomness is in the Ensemble, not in the connection itself). Although I suppose that seed could be used when computing the decoder for that connection.....

@hunse
Copy link
Collaborator

hunse commented May 29, 2015

@tcstewar: good point. We had the property in there for some reason...

@hunse
Copy link
Collaborator

hunse commented May 29, 2015

Yeah, it looks like we pass it to the solver in case it wants an rng, and when generating the eval points if they haven't been generated by the ensemble.

hunse added a commit that referenced this issue Jun 14, 2015
hunse added a commit that referenced this issue Jun 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants