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

Improve flexibility of emit_spike() #959

Closed
clinssen opened this issue Sep 18, 2023 · 1 comment
Closed

Improve flexibility of emit_spike() #959

clinssen opened this issue Sep 18, 2023 · 1 comment

Comments

@clinssen
Copy link
Contributor

clinssen commented Sep 18, 2023

emit_spike() sends out an event, that can be optionally tagged with data fields like weight and delay, for instance: emit_spike(my_weight, 1 ms).

We should create a more flexible syntax and semantics to allow arbitrary data fields, with given types, to be attached to emitted events, for instance: emit_spike(w=my_weight, d=1 ms).

This could be "read out" on the receiving side as follows (for instance):

onReceive(spikes_in):
  V_m += spikes_in.w
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant