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

BUG: Odd merging behavior #801

Open
Lathomas42 opened this issue Oct 19, 2024 · 1 comment
Open

BUG: Odd merging behavior #801

Lathomas42 opened this issue Oct 19, 2024 · 1 comment

Comments

@Lathomas42
Copy link

Describe the issue:

I am not sure this is a bug, or something wonky with parameters, but I am seeing a reoccurring pattern, and would like to know what parameters to tweak to fix this.
After sorting, I will have units that look like this in phy, which, I would consider noise based on the ISI plot alone
KSBUG_01
And, as you can see by the feature view, there appears to be one main cluster, and a lot around that. If i just crudely go and isolate the main cluster, the ISI plot changes dramatically.
KSBUG_02
I am wondering if there is a parameter i can tune to prevent this kind of merging from happening?

Changed Parameters from default:
settings['nearest_chans'] = 16
settings['batch_size'] = 30000*4 # 4s of data
settings['dminx'] = 18.5

Reproduce the bug:

No response

Error message:

No response

Version information:

KSVersion: up to comit ddb16d1
OS: Ubuntu 20.04
GPU: 1080Ti
Probe: Cambridge Neuro 2 shank 64 channels (shanks sorted individually)

@jacobpennington
Copy link
Collaborator

This looks like a recording artifact that will need to be removed prior to sorting. If you know what is causing it, you should try to remove that from the data yourself. You could also try using the artifact_threshold parameter in KS4, but that will simply zero out the whole batch where those big fluctuations occur, which may not be ideal.

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