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
They then check the first spike wave moves from the position 0,0 in waves until it reaches 5,5
0,0 spikes at time = 4
0,1, 1,0 and 1,1 all spike at time = 11
0,2 1,2 2,0 2,1 and 2,2 all spike at 17 (or 18 as 2,2 only gets one spike)
0,3 ect at around 23
Then 0,4 at around 29
However if split into 2,2 grids the weights are correct
spike waves are a MESS
I added a log to see when the cores thing they spikes and that matches with the reported spikes.
So it is not a local back to raster ids issue
The issue is that the cores are numbered by Slice.lo_atom to slice.hi_atom and not by raster ids.
The text was updated successfully, but these errors were encountered:
See #1309
It check the weights are as expected.
They then check the first spike wave moves from the position 0,0 in waves until it reaches 5,5
0,0 spikes at time = 4
0,1, 1,0 and 1,1 all spike at time = 11
0,2 1,2 2,0 2,1 and 2,2 all spike at 17 (or 18 as 2,2 only gets one spike)
0,3 ect at around 23
Then 0,4 at around 29
However if split into 2,2 grids the weights are correct
spike waves are a MESS
I added a log to see when the cores thing they spikes and that matches with the reported spikes.
So it is not a local back to raster ids issue
The issue is that the cores are numbered by Slice.lo_atom to slice.hi_atom and not by raster ids.
The text was updated successfully, but these errors were encountered: