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

Strange 'chunks' in TraceView linked possibly to Nblocks and temp_wh.dat #487

Closed
ross-folkard opened this issue Mar 29, 2022 · 0 comments · Fixed by #595
Closed

Strange 'chunks' in TraceView linked possibly to Nblocks and temp_wh.dat #487

ross-folkard opened this issue Mar 29, 2022 · 0 comments · Fixed by #595

Comments

@ross-folkard
Copy link

Hi there,
I'm using 64-channel single shank probes from CN, and sometimes in the phy visualisation of the traces I get these strange 'chunks' after spike-sorting with KS3 or KS2.5:

image

image

They do not obviously change when altering the ops.ntbuff, but do change when altering the Nblocks for registration. They are absent when Nblocks = 0, and the nature of the chunks changes when Nblocks changes:

Nblocks = 0
image
image

Nblocks = 1
image

Nblocks = 2
image

Nblocks = 5
image

I can't quite tell if this phenomenon is more frequent in periods of low spiking activity, or if it's just more noticeable then.

What also seems to matter is whether the dat_path is 'temp_wh.dat' or 'recording.dat'. The chunks only seem present in the 'temp_wh.dat' visualization.

'temp_wh.dat':
image

'recording.dat':
image

I have to say this is not something I've noticed in many recordings. Nevertheless I'm wondering if this may underlie some deeper issue that may affect the validity of the units that I get from recordings where this is not so obvious.

In general, I have 3 questions:

What do you think might be happening here?

How likely is it that this obvious chunking may affect the clustering say before and after these time periods?

Might it affect clusters in recordings where Nblocks is used during spike-sorting but the chunking is not as obvious or seemingly absent?

Any help would be greatly appreciated, and thank you in advance for your time!

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.

1 participant