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
Currently, there are two functions for measuring mean firing rate: mean_firing_rate and firing_rate. @harisorgn, I think we should probably try to converge to a single function.
The function firing_rate has some serious performance issues, at least in the following case:
Agreed. I wrote firing_rate sloppily to debug my tutorial. The issue is most likely the multiple calls to detect_spikes. A solution with a single call is definitely possible, so more like what you have. We just need a dispatch where the first argument is a composite blox or a vector of bloxs.
Added more comments to #455 as I was going through your new dispatch. These comments are more relevant here though, apologies 😅 . I am linking so we don't forget.
Currently, there are two functions for measuring mean firing rate:
mean_firing_rate
andfiring_rate
. @harisorgn, I think we should probably try to converge to a single function.The function
firing_rate
has some serious performance issues, at least in the following case:I don't have time now to dig into what is causing that performance issue (I'll probably come back to this on Tuesday), but I guess it's due to:
in the
detect_spikes
function, similar to what used to happen instate_timeseries
here: 87eb04b.BTW, I've just added a dispatch for
mean_firing_rate
to account for EnsembleProblems and fixed the trimming of the initial transient in #455.The text was updated successfully, but these errors were encountered: