You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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)
The text was updated successfully, but these errors were encountered:
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.
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
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.
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)
The text was updated successfully, but these errors were encountered: