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

are template features affected by spike overlap? #185

Closed
tonylien opened this issue Feb 3, 2020 · 1 comment · Fixed by #595
Closed

are template features affected by spike overlap? #185

tonylien opened this issue Feb 3, 2020 · 1 comment · Fixed by #595

Comments

@tonylien
Copy link

tonylien commented Feb 3, 2020

I have a question about the template features (rez.cProj). From the documentation and #82, they are the projection of each spike onto various templates. Are the influence of all other spikes "subtracted" out first? In other words, if there are spikes from multiple templates co-occuring in time (overlapping spikes), does this cause the projection of a spike onto its template to be worse? I'm trying to get some intuition about how the template features could be used to quantify cluster separation and whether spike overlap would distort a spike's projection in template feature space.

I tried to look at where cProj is computed in the code but it's a little beyond my understanding. Any help is greatly appreciated.

@marius10p
Copy link
Contributor

Yes, the influence of other spikes is subtracted out first for these features (but not for the PCA features).

The main reason we compute template features is to show them in Phy so you can tell if two clusters are well separated or not. See figure 4 in the original Kilosort paper for more detail on the maths of these features. Note there is some centering and rescaling going on to make the features more comparable between clusters (see the footnote in the paper).

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

Successfully merging a pull request may close this issue.

2 participants