Alan Stokes
Alan Stokes
i was thinking about this a little bit over the easter weekend (god forbid i work over the hols) and a thought occurred. If you have a random distribution which...
pass will check in a bit
many many places it can go wrong. but we might as well remove 1 of them if we can
what definition are you using for run there? after p.end() or between p.run()'s. after p.end() im fine with (esp as we're killing reload func) whereas between runs could cause issues...
its also worth noting that app data is cleared at the same level of report folders. when not set to default. that being said, that functionality has issue with crashing...
other idea. have the cores themselves do the spike counts for their neurons. store as another data region / provenance region. have a sdp messgage asking for them. for average...
the devision is at the end when its finished. so not fussed about that cost. And it stops you from having to record the spikes. If we just have it...
could be done via another recording region.
"In our case we can compute n_values as we know how many timesteps and if applicable how many neurons." that's only true on models which don't spikes more than once...
Just to add, the reason why the current code is harder to understand than it could be, may be because of performance. You must note that Dave Lester was pleased...