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

reporting un-matched events #28

Open
nsteinme opened this issue Sep 19, 2016 · 0 comments
Open

reporting un-matched events #28

nsteinme opened this issue Sep 19, 2016 · 0 comments

Comments

@nsteinme
Copy link
Collaborator

Events of high enough magnitude that didn't match any template should be reported. As an easiest thing, it could just tell you how many of these there were (on each channel, maybe), so you know if it's a problem. Second stage, it could report the event times and peak channels of all of these, perhaps even adding them to the clustering with an extra template for each channel or local group of channels, and give it a flat template shape. This way these events could be easily visualized in phy.

It might be tricky though - one might expect lots of residuals (events left after subtracting some spike) to be unmatched, but these would look worrying to the user since they will see the raw data, without the first spike subtracted.

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

No branches or pull requests

1 participant