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

Troubleshooting Spike Sorting Issues in Kilosort4 with High Noise Data #852

Open
mamang1101 opened this issue Jan 16, 2025 · 1 comment
Open

Comments

@mamang1101
Copy link

Feature you'd like to see:

"Hi, I’m currently a Ph.D. student who has just started experimenting. Since I’m new to spike sorting with Kilosort4, there are still many things I don’t fully understand, so I hope you can bear with me.

I’ve converted the .tev file obtained from TNT into a .bin file and proceeded with spike sorting using Kilosort4. My data has a characteristic where there’s significant noise (caused by the mouse licking), which persists continuously. However, as you can see in the figure below, when I check the overall recording data using NeuroExplorer, clear spikes are consistently present. When I sort this data using OfflineSorter, it seems to sort well, so I currently assume that the issue is not with the data itself.

image
image

However, when I process this data in Kilosort4 and check it in Phy, as you can see, it doesn’t seem to sort properly. Even when I look at the waveforms, they don’t look like spikes at all.

image

If the significant noise in my data is causing these results in Kilosort4, is there any way to address this?
I ran Kilosort4 with the settings below. Are there any parameters I should consider changing?"

Thank you for reading, and I hope everyone gets lots of 'good'

Additional Context

No response

@jacobpennington
Copy link
Collaborator

Please start by uploading kilosort4.log from the results directory.

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