-
Notifications
You must be signed in to change notification settings - Fork 61
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
🐍 Rename spike detector -> threshold detector #1976
🐍 Rename spike detector -> threshold detector #1976
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We just break API? I'm fine with that.
Yes, of course. But: less confusion across C++/Python and a clearer name. It's also still pre-1.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes!!!!!!
I appreciate the excitement for homogenising APIs, but any particular reason? |
This name has been confusing me for some time now. |
Rename
spike_detector
tothreshold_detector
and makespike_detector
throw a deprecation error.This brings the Python API more in line with C++ and is closer to the object's actual function.
Closes #1642