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

KS4 over-merging units #667

Closed
florgf88 opened this issue Apr 18, 2024 · 7 comments
Closed

KS4 over-merging units #667

florgf88 opened this issue Apr 18, 2024 · 7 comments

Comments

@florgf88
Copy link

Describe the issue:

Hi, I have recently tried KS4, which yielded nice clusters across some regions in a NP 1 recording. However, in one of the areas I'm interested in, which has high activity during my experiments, not several clusters were detected (highlighted in white in the spike position across the probe plot).
Screenshot 2024-04-12 180243

When I looked at the units from this area in Phy, I noticed that most of them are MUAs with high violations in the RP. In this example, the distribution of the amplitude looks bimodal:
Capture

I have compared the results in pyKilosort for this area, and it seems that KS4 is over-merging clusters. Is there any way to control this? I tried adjusting Th(universal) and Th(learned), but it didn't help.

I appreciate any help or suggestion, many thanks!

@marius10p
Copy link
Contributor

marius10p commented Apr 18, 2024 via email

@florgf88
Copy link
Author

Hi Marius, many thanks for the response.

I tried to split it, here's the result:
Screenshot 2024-04-18 141554

In pyKilosort the clusters look like this:
image

@marius10p
Copy link
Contributor

Thanks, can you please show the good cluster view for this entire area like you did for Kilosort4? It's possible that individual cluster exmaples are segmented better by one algorithm or another, but it would be good to see a picture showing KS2.5 consistently being better in this area.

@florgf88
Copy link
Author

Yes, of course. I hope this picture helps. It's the area between 2800-2500 um.
Screenshot 2024-04-18 160825

@marius10p
Copy link
Contributor

Looks similar doesn't it? The area in 1800-2200 looks like there are plenty of units for both algorithms and the 2200-2800 is similarly sparse for both. That area 2200-2800 just seems like higher noise / lower amplitude units, right?

@florgf88
Copy link
Author

Yes, exactly. Units in this area have lower amplitude generally. It's true that there are not that many, but we still have some. I tried to decrease the learned Th first, but it got worse in general.

@marius10p
Copy link
Contributor

I am not sure if this message means you agree with us, but basically to me it looks like both algorithms perform similarly in terms of how many good units they find in that particular region. Perhaps the different visualizations make this harder to compare but if I just try to count them, I don't see a big difference.

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

2 participants