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

optimizing main sorting parameters #500

Closed
DanEgert opened this issue May 13, 2022 · 1 comment · Fixed by #595
Closed

optimizing main sorting parameters #500

DanEgert opened this issue May 13, 2022 · 1 comment · Fixed by #595

Comments

@DanEgert
Copy link

Is there a good way to find better fitting main parameters (ops.Th, ops.AUCsplit and ops.lam)?
I have had unexpected strong variation in number of clusters in similar recordings and many merged clusters.
It would be cool to have a cluster metrics assessment that allows comparing the sort quality.

@marius10p
Copy link
Contributor

A single set of parameters should work well for all data from the same probe and prep. The default set of parameters should work well in most cases.

If this is not the case, the underlying cause might be something about the data. Use the GUI to look at different sessions, especially the whitened image view, which is the preprocessing that Kilosort uses.

It is also possible that KS3 is more sensitive, and you can try using KS2.5.

Have you tried the "good" flag in the output to get a sense of how many good clusters you get?

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