SpikeInterface / spikeinterface

A Python-based module for creating flexible and robust spike sorting pipelines.
https://spikeinterface.readthedocs.io
MIT License
476 stars 183 forks source link

Unable to find an appropriate device to wire to #2821

Open ebach23 opened 2 months ago

ebach23 commented 2 months ago

We recently switched from a Cambridge Neurotech 64 channel probe to a Cambridge Neurotech 16 channel probe that uses an omnetics adapter to connect to our Intan 16 channel headstage. We are trying to analyze a group of our data obtained with this set-up but are not able to wire to any of the devices that are listed as an option for these probes. Our probes are: ASSY-1-P-2 - cambridgeneurotech - 16ch - 1shanks The device options made available are: ['H32>RHD2132', 'ASSY-156>RHD2164', 'ASSY-116>RHD2132', 'ASSY-77>Adpt.A64-Om32_2x-sm-NN>RHD2164', 'ASSY-77>Adpt.A64-Om32_2x-sm-NN>two_RHD2132', 'cambridgeneurotech_mini-amp-64']

All of these appear to be 32 to channel or 64 channel which then read the error: "AssertionError: chan_indices 32 != contact count 16" Can you help us identify how we can fix this problem?

zm711 commented 2 months ago

Hi @ebach23,

Looks like we don't have wiring to RHD2216 yet. I would open this issue on the probeinterface repo so that it can be put on the todo list over there. We have tools to allow you to do it manually if you want help with that and if you get that working then you can actually share the mapping with us and we can include it in probeinterface in the future.

ebach23 commented 2 months ago

Thanks for your prompt response. I have posted this on the probeinterface repo, but may reach out to you about doing this manually. Is it best to reach you through this platform?

zm711 commented 2 months ago

I'm fine with here. Technically it is better to have the issue on the repo directly so have the issue on probeinterface, but that repo gets checked a little bit less. So we can work on this one here and then in the future open probe issues there and spikesorting stuff here :)

ebach23 commented 2 months ago

I got a response about this issue on the probe interface repo section, and gave them my reply. I havn't heard anything back. They had asked for the probe/adaptor map. Can you help me?

zm711 commented 2 months ago

Yep we can try to work on it. We are actually prepping for a conference/hackathon in a couple days so we are a little slower with replying (apologies!)

ebach23 commented 1 month ago

Just checking back in. I left the information on the [probeinterface repo] page in reply to your request (?). I havn't heard anything back. Anything I can help with on my end. Thanks!

zm711 commented 1 month ago

Hey @ebach23 thanks for pinging us. We are so sorry for being slow. We are at a developer hackathon for the project so we are all working on projects together. Could you ping us on Monday when the conference is over and someone will help you then? Thanks for understanding!

ebach23 commented 1 month ago

Hi zm711...per request...pinging you

zm711 commented 1 month ago

So is your question that you're not sure how to make your own mapping? Because you have all the information in order to make a mapping. My advice would be make the mapping and then submitting your mapping (on probeinterface) or here and then we can proofread and doublecheck for you.

If you don't know how to make a mapping we have a tutorial here

zm711 commented 1 month ago

It's a little tricky to explain over an issue text but the tutorial gives you a better idea of what goes into the mapping and it generates pictures as you run it. So I hope that is a better way to explain it! :)