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

NumpySortingExtractor doesn't save primary channel information #24

Open
BMT01 opened this issue Mar 19, 2020 · 0 comments
Open

NumpySortingExtractor doesn't save primary channel information #24

BMT01 opened this issue Mar 19, 2020 · 0 comments

Comments

@BMT01
Copy link

BMT01 commented Mar 19, 2020

Hello -

I'm using ml_ms4alg in the context of SpikeTemplate. I have a simple 3 channel dataset which I'm sorting units on. When I save firings.mda or curate the results in phy through spikesorters.run_mountainsort4(), all units are assigned channel 0. The units however are on distinct channels (see attached image).
Figure_1

My three electrodes are 2 mm apart, so they are effectively independent. This occurs with adjacency_radius set to 0 or -1.

I was debugging and found that channel information is preserved within the firings array in ms4alg.MountainSort4(), but mountainsort4.py converts the sorting output to a spikeextractors.NumpySortingExtractor() object, which doesn't save channel information. Is this expected behavior within the SpikeTemplate ecosystem, or is there a way to pass channel information along? It would be helpful to have this information for curation (e.g. combining multiple channel clusters to a single unit in phy).

Would it be possible to potentially save MS4 results as a MdaSortingExtractor object, to preserve channel information? Please let me know if I'm asking too much.

Thank you.

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

No branches or pull requests

1 participant