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

issue with GUI/channel map #364

Closed
rclein94 opened this issue Mar 25, 2021 · 4 comments · Fixed by #595
Closed

issue with GUI/channel map #364

rclein94 opened this issue Mar 25, 2021 · 4 comments · Fixed by #595

Comments

@rclein94
Copy link

rclein94 commented Mar 25, 2021

Hi, I'm trying to use Kilosort2.5 for the 16 channel Buzsaki probe from Neuronexus. The probe has two shanks with one shank having 7 active sites, and the other having 8 active sites. Whenever I load my channel map into the GUI, I get a page that looks like the attached image. I also have an error that says index exceeds the number of array elements (15). I have tried some debugging, but it looks like because I have loaded in several different channel maps in the past to try to test things, all of those channel maps are being used. I'm not sure how to delete channel maps from the GUI's "memory". Whenever I start by loading in my data, the GUI tells me that it cannot calculate the number of channels, but nothing happens even after I enter the number. I'm not really sure what I'm doing wrong, so any advice is appreciated. I should add that I'm using Matlab 2020b, and I think I have downloaded everything correctly, but am not totally sure as I haven't had any success running the eMouse simulation either. I'm very new to ephys so looking for any advice! Thank you!

gui

@JoseGuzman
Copy link
Contributor

Hi @rclein94 ,

I was having similar issues with multi-shank probes. I would design your probes as linear (one shank after each other in the y-axis, see some examples here). Both KiloSort and Phy are designed for linear probes and the sorting will not be affected since the probes are independent.

@rclein94
Copy link
Author

Thank you so much!! I will definitely give that a try!!

@Tywang-720
Copy link

We have similar issues.

Previously I tested KiloSort3 using some 1024 channel map.

Then, when I tried to run some 128 channel recording, KiloSort3 keeps telling me " index exceeds the number of array elements" at whitening stage.

Perhaps its trying to use the old 1024 channel setting, even though I have already entered a new 128 channel map.

@rclein94
Copy link
Author

rclein94 commented May 6, 2021

I think that is the same problem I'm having @Tywang-720 . Have you had any luck with it?

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.

3 participants