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

Oversplit data #137

Closed
hkneu-95 opened this issue Nov 11, 2019 · 1 comment · Fixed by #595
Closed

Oversplit data #137

hkneu-95 opened this issue Nov 11, 2019 · 1 comment · Fixed by #595

Comments

@hkneu-95
Copy link

Hi,
So I have been using Kilosort2 for 32 channel e-phys data. One observation is this certain oversplitting where what appears to be the same waveform is detected with respect to different reference points and therefore shows largely different amplitudes and is often restricted to small sections of the recording. Also they seem to have spikes in complementary sections of the recording. I have noticed this in several instances and have attached one example below. We have been manually merging them in Phy but would like to know what might be the reason and if such instances could be reduced by parameter changes.
Capture2
Capture

@marius10p
Copy link
Contributor

I think this is because of how the spikes are aligned to either the negative or positive waveform extremes. We don't want to force negative peaks only, because certain kinds of spikes would not be detected well by that.

Until we come up with better alignment, your best option is to write a custom matching step, detecting best timelags between waveforms and merging those that are too similar.

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