You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This could be a general issue of how we compute the circular eventspaces and might also apply to a normal thresholder running on a different clock (should be tested!).
EDIT:
This does also apply to NeuronGroup on a different clock. I renamed the test above to test_circular_evenstpace_different_clock_spikegenerator and added another test with NeuronGroup names test_circular_evenstpace_different_clock_neurongroup.
The text was updated successfully, but these errors were encountered:
Update and fix spikegenerator.
Fixes#48.
New issue for spikegenerator on differnt clock in #222
Additional optimization suggestions in #193
denisalevi
changed the title
Circular eventspaces fail when SpikeGeneratorGroup runs on a different clock
Circular eventspaces fail when source group runs on a different clock than synapses
Jun 23, 2022
SpikeGeneratorClock(..., dt=2*defaultclock.dt)
produces wrong results in the following test:brian2cuda/brian2cuda/tests/test_synaptic_propagations.py
Lines 231 to 266 in 2b28ac6
This could be a general issue of how we compute the circular eventspaces and might also apply to a normal thresholder running on a different clock (should be tested!).
EDIT:
This does also apply to
NeuronGroup
on a different clock. I renamed the test above totest_circular_evenstpace_different_clock_spikegenerator
and added another test withNeuronGroup
namestest_circular_evenstpace_different_clock_neurongroup
.The text was updated successfully, but these errors were encountered: