-
Notifications
You must be signed in to change notification settings - Fork 174
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
Probing Connections #973
Labels
Milestone
Comments
Does doing p1 = nengo.Probe(c1, 'input', synapse=0.05)
p2 = nengo.Probe(c2, 'input', synapse=0.05) Give you what you want? By default, probing a connection probes the |
hunse
added a commit
that referenced
this issue
Mar 2, 2016
I thought probing the |
Does #974 do what you want? |
yup! |
tbekolay
pushed a commit
that referenced
this issue
Mar 16, 2016
tbekolay
pushed a commit
that referenced
this issue
Mar 17, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that a probe on a connection returns the output of the post object rather than just the signal from that connection. So if you have multiple inputs going into an object, the connection probes on each return the sum of all the inputs, not the signal going through each connection.
In the following example all the probes show the same value.
The text was updated successfully, but these errors were encountered: