Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ordered spikes in a Spiketrain #27

Open
mdenker opened this issue May 2, 2017 · 0 comments
Open

Ordered spikes in a Spiketrain #27

mdenker opened this issue May 2, 2017 · 0 comments

Comments

@mdenker
Copy link
Member

mdenker commented May 2, 2017

Currently, spikes in a spiketrain are not sorted in time. This could be confusing for users. On the other hand, sorting should not just automatically happen, as this may also cause bugs. This issue aims to find a clear, transparent solution (in code and/or documentation) to define if and when Spiketrains are sorted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant