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

RateCodeSpikeGen does not behave correctly when incoming pattern amplitude is higher than 12000 #15

Open
gkarray opened this issue Dec 9, 2021 · 0 comments · May be fixed by #16
Open
Assignees
Labels
1-bug Something isn't working

Comments

@gkarray
Copy link
Contributor

gkarray commented Dec 9, 2021

When RateCodeSpikeGen receives a pattern containing one amplitude that is higher than 12000, the expected behavior would be that the neuron corresponding to that amplitude would spike every time step (saturate).

However, currently, it is not the case. Current behavior is that said neuron will not fire at all.

This is due to the fact that, when computing distances, upon new pattern arrival, we do the following :

distances[idx_non_negligible] = \
            np.rint(TIME_STEPS_PER_MINUTE / pattern[idx_non_negligible])\
            .astype(int)

This would result to distances having a 0 at indices where the pattern is higher than 12000 (since TIME_STEP_PER_MINUTE is set to 6000 right now). 0 representing an infinite distance with the current way RateCodeSpikeGen is implemented, this is not correct.
It should saturate to 1, in that case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1-bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants