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

Remove "inhibitory" and "excitatory" spiking input port specifiers #944

Open
clinssen opened this issue Aug 9, 2023 · 0 comments
Open

Comments

@clinssen
Copy link
Contributor

clinssen commented Aug 9, 2023

Depends on #938.

"Excitatory" and "inhibitory" input port specifiers are confusing and should be eliminated.

Current sitation: if specifiers are present, spikes get "routed" to the right buffer depending on weight of the incoming event.

exc_spikes <- excitatory spike
inh_spikes <- inhibitory spike

(this example: actually only one in-port (one rport)

Behaviour is such that:

w < 0:
	gets routed to inh_spikes
w > 0:
	gets routed to exc_spikes

Proposal: change to multisynapse model (behavioural/API change), or preserve current situation by putting the check for the sign of the weight inside the onEvent() handler function.

in_spikes <- spikes

onEvent(in_spikes):
	if in_spikes < 0:
		g_syn_inh += 1
	else:
		g_syn_exc += 1
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