Boundary correction rate for firing rate estimator with Gaussian KDE

[pbouss]

No description provided.

[pep8speaks]

Hello @pbouss! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻

Comment last updated at 2022-03-25 13:50:24 UTC

[coveralls]

Coverage increased (+0.03%) to 88.648% when pulling e4c2cef on INM-6:feature/boundary_correction_rate into d0d3920 on NeuralEnsemble:master.

[mdenker]

Is this fix related to #374?

[mdenker]

Thanks again for committing this useful addition. I think it would be great to have a bit more documentation on what the border correction is actually doing. With the given information, its very difficult to retrace your thoughts, and in particular, as a researcher one would not really know whether to use the correction or not.

[pbouss]

I still have set old versions of neo and scipy in the requirements.txt. Is this issue solve that did not allow including the newest versions for Travis?

[Moritz-Alexander-Kern]

Nice feature, thanks for contributing.

I have created the following test plot with it:

To me the best way to understand this feature is to look at this figure.

[pbouss]

Nice feature, thanks for contributing.

I have created the following test plot with it: To me the best way to understand this feature is to look at this figure.

Thanks, I have various of those figures, also for non-stationary firing rates. And we used this extension already in Stella, Bouss et al. (2021) (bioRxiv and submitted to eneuro).