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

EIG did not converge (for Utah array data) #575

Closed
liz-ok opened this issue Nov 6, 2023 · 1 comment · Fixed by #595
Closed

EIG did not converge (for Utah array data) #575

liz-ok opened this issue Nov 6, 2023 · 1 comment · Fixed by #595

Comments

@liz-ok
Copy link

liz-ok commented Nov 6, 2023

We are working with a 96ch Utah array data. It runs without errors when using a linear widely spaced channel map. However, when rearranging the channel map to represent a 2D utah array (attached), we run into this issue after main optimization:

Error running kilosort! EIG did not converge at index = 71926

followed by:

Error saving data for phy! Unrecognized filed name "Wphy".

Windows 11
Matlab R2022a
Cuda 12.1
UEA_kilosort_chanmap.zip

Any ideas?

Thank you!!

@kermit000000
Copy link

I've run into a similar issue before, and I still can't figure out what aspect of the channel map triggers an error in the final step of KiloSort. But from my experience, it seems that arranging the xcoords and ycoords in incremental order (or linear order) in the channel map resolves the problem. On the flip side, when the chanMap numbers are in sequence and the corresponding xcoords and ycoords are all jumbled up, it throws an error.

While I can't guarantee the absolute truth of this observation, I recommend giving it a shot—organize your xcoords and ycoords in order while mixing up the corresponding chanMap and chanMap0ind numbers. For instance, your current map starts chanMap 1 at coordinates (800,3600), then 2 at (400,3600). However, try the sequence with chanMap number 79 at (0,400), followed by 77 at (0,800), 75 at (0,1200), and so on. It worked for me; hopefully, it does the trick for you too.

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