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

Max number of filters per channel? #42

Closed
chris-angeloni opened this issue Mar 26, 2019 · 2 comments · Fixed by #595
Closed

Max number of filters per channel? #42

chris-angeloni opened this issue Mar 26, 2019 · 2 comments · Fixed by #595

Comments

@chris-angeloni
Copy link

chris-angeloni commented Mar 26, 2019

I'm trying to figure out what the ops.nfilt_factor parameter does. It seems like it tries to limit the number of clusters assigned to each channel. By default, it's set at 4, but I'm not sure what that means. Does that mean that each channel can at max have 4 clusters assigned to it?

(seems unlikely, I often get many clusters for a given channel):
image

Otherwise, does this just limit the maximum number of clusters that KS will find to 4x the number of good channels? ie. if I had 32 channels, it can find, at most, 32x4 clusters?

@marius10p
Copy link
Contributor

Your second interpretation is correct, and it only refers to clusters obtained in the main optimization, which is overmerged. before the final splits and merges. It is unlikely you will ever hit 4x so it should be a safe upper bound.

@chris-angeloni
Copy link
Author

Ok, the reason I was curious is that I sometimes see a large number of low spike count, low amplitude clusters on the same channel. My guess is that they are just noise, given how close they are to the noise floor, and some strangeness with the ACGs and CCGs. I'm trying to get a good sense of an amplitude cutoff for noise, but it seems to depend on the noise floor of each recording (or channel). Maybe a measure of SNR in addition/instead of the amplitude would be useful in phy.

image

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