Add computation of smoothed firing rates for spike trains #189
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The old behavior would issue a warning when a negative firing rate was detected. Because of machine precision errors, this warning was almost always issued. This change removes the warning and instead clips the values, so that negative firing rates are replaced with zero.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a major new feature used when lazy loading is off
lazy=False.Smoothed firing rates may be computed via spike train convolution, stored as annotations of the
SpikeTrainobjects, and plotted in the GUI. Users may specify a convolution kernel from the elephant package, or use the CausalAlphaKernel provided by neurotic.See the documentation for details: https://neurotic.readthedocs.io/en/latest/metadata.html#firing-rates