Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CambridgeNeurotech ASSY-325D H10 & E-1 probes inconsistent with documentation

Open
#67 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Domain
data

Research direction

Compare the repository images at cambridgeneurotech/ASSY-325D-H10/ASSY-325D-H10.png and cambridgeneurotech/ASSY-325D-E-1/ASSY-325D-E-1.png with the linked Cambridge Neurotech mapping PDFs. Verify the channel ordering, vertical orientation, and conical shank geometry, then update the probe descriptions so both versions match the documentation.

Written by the indexing model from the issue text.

Description

The channel IDs and the geometry of the version here seems inconsistent with documentation.
ASSY-325D H10: Firstly the channels should be vertically flipped and mapped in this order.
ASSY-325D E-1: Seems quite inconsistent with documentation. The geometry should be along inclination of shank in a conical fashion
I'm not sure maybe this version refers to some old version or is just incorrect
documentation:
ASSY-325D H10:: https://www.cambridgeneurotech.com/assets/files/ASSY-325D-H10_H10-2-map.pdf
ASSY-325 E1-D: https://www.cambridgeneurotech.com/assets/files/ASSY-325D-E-1_E-2-map.pdf

your versions:
https://github.com/SpikeInterface/probeinterface_library/blob/main/cambridgeneurotech/ASSY-325D-H10/ASSY-325D-H10.png
https://github.com/SpikeInterface/probeinterface_library/blob/main/cambridgeneurotech/ASSY-325D-E-1/ASSY-325D-E-1.png

Dominant language
TypeScript
Stars
21
Forks
11
Avg merge
22h 23m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SpikeInterface/probeinterface_library

All issues in SpikeInterface/probeinterface_library

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.