-
Notifications
You must be signed in to change notification settings - Fork 219
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
User defined delay
variable in Synapses
object creates ambigiuity
#927
Comments
Uh, indeed -- I'm actually surprised that this was not already the case... 😒
This is not that trivial, unfortunately. We add a reference to the pre pathway's delay to the That said, I think we should fix both things, i.e.: no longer allow to declare variables called "delay", and change the mechanism so that the |
Also, make exception types for illegal identifiers consistently `SyntaxError` (previously, they could be `KeyError`, `ValueError`, or `SyntaxError`). Together with previous commit, fixes #927
The
delay
variable (as shortcut for the pre pathways delay) is accessible in theSynapses
objects equations (model
,on_event
etc). Butdelay
can also be defined as a synaptic variable, which create ambiguity about which variable is used when.Quick example I was just running. When using
delay
in a differential equation like thisdelay=2*ms
is used for the state update ofA
. But when defining anotherdelay
variable, e.g. like thisdelay = 4*ms
is used in the state update ofA
.I guess banning
delay
as synaptic variables as done forlastupdate
would solve this. Or removing the accessibility to the synaptic delay in synapse code since other pathways delay variables (e.g.post.delay
) are not accessible in synapse code either.The text was updated successfully, but these errors were encountered: