-
Notifications
You must be signed in to change notification settings - Fork 45
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
Unable to find an appropriate device to wire to #272
Comments
Hi! Do you have a channel map for your setup? |
Yes, I can send you the paperwork we have. We are currently using acute probes that are hooked into an adaptor which is in turn connected to our headstage.
Adaptor map:
[image0.jpeg]
The map of probe/adaptor together.
[image1.jpeg]
Thanks so much, Eva
Sent from my iPhone
On May 9, 2024, at 11:10 AM, Alessio Buccino ***@***.***> wrote:
WARNING: This email originated from outside of Advocate Health ***@***.***). DO NOT click links or open attachments unless you know and trust the sender. NEVER provide your login information to anyone. USE Squish the Phish to report suspicious email.
Hi! Do you have a channel map for your setup?
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/SpikeInterface/probeinterface/issues/272*issuecomment-2102853445__;Iw!!GA8Xfdg!3sURDQknBMYMGcZD9lluG1k9Qsv8fQxapRG0ZqhJzgrja99CEX8riQ3KjTt22U692zJPR_FDTOyseMD2CexHp2_P$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BIL2EVUMRO6IDPNCBU3JBIDZBOGXVAVCNFSM6AAAAABHO7KZL6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBSHA2TGNBUGU__;!!GA8Xfdg!3sURDQknBMYMGcZD9lluG1k9Qsv8fQxapRG0ZqhJzgrja99CEX8riQ3KjTt22U692zJPR_FDTOyseMD2CZ0PUjlH$>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
…________________________________
This electronic message is intended only for the use of the individual(s) and entity named as recipients in the message. If you are not an intended recipient of this message, please notify the sender immediately and delete the material from any computer. Do not deliver, distribute or copy this message, and do not disclose its contents or take any action in reliance on the information it contains. Thank you.
|
I cannot see the images because I think you replied to the email. Can you reply to the issue instead? |
@ebach23, could you also share the headstage info you're using. We need to see the final connectors on the other side of the omnetics! |
Oops, I missed your question until now. The headstage we are using is an Intan C3334 | RHD 16-channel headstage18-pin Omnetics electrode connector |
This would be very useful for our lab as well ! We are also using an omnetics adapter to connect to the Intan headstage for our 4 tetrodes twisted wires. |
I posted this on the main spike interface issue page and was suggested the following:
"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."
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?
The text was updated successfully, but these errors were encountered: