Node.output is assumed to not change about nengo-dl HOT 7 CLOSED

Including unit tests in the bug report 😍

from nengo-dl.

Should be fixed if you want to check out the change_nodes branch. Let me know if that works for you and I'll merge it into master

from nengo-dl.

Woops didn't mean to close this

from nengo-dl.

I haven't tested it yet as my computer seems to be annoyed at me trying to uninstall nengo_dl... I'll take another stab at it this weekend.... :)

from nengo-dl.

(woops, accidentally deleted comment, reposting)

@tcstewar I was just relooking at this, and noticed that your example shows that the output of the network does not change after node.output changes (i.e. it continues to output 0.0, even though post_val is 1). Is that the intended behaviour? I had understood the first time that you wanted the output to change as node.output changes.

from nengo-dl.

@tcstewar I was just relooking at this, and noticed that your example shows that the output of the network does not change after node.output changes (i.e. it continues to output 0.0, even though post_val is 1). Is that the intended behaviour? I had understood the first time that you wanted the output to change as node.output changes

The intended behaviour is that after the Simulator is built, if someone changes the model, there should be no change in the simulated behaviour. The same thing would be true if someone adds Connections or Ensembles, or changing the properties of any of those things, so this is meant to be consistent with that. So yes, it should continue to output 0, even though post_val is 1. :)

from nengo-dl.

OK good, that's how I thought it should work, was confused why the GUI required that weird behaviour 😄

from nengo-dl.