Add shank thickness to the Probe model

Aperta
#452 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend

Direzione di ricerca

Start by locating the Probe model and its existing contact-position and contour geometry fields. Review related issue #14 and the linked double-sided-probe discussion to clarify the API, units, and whether there is a reason thickness was omitted. Done should leave datasheet-sourced shank thickness available for complete probe descriptions and three-dimensional front/back reconstruction.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Thinking about double-sided probes on probeinterface_library surfaced a gap: front and back contacts sit at identical (x, y), so the only physical separation between a front site and its back twin is the shank thickness along the plane normal, and the Probe model has no field for it. The value is published for our main manufacturers (Cambridge NeuroTech 15 microns, https://www.cambridgeneurotech.com/neural-probes; Neuropixels 24 microns, https://www.neuropixels.org/probe1-0), yet it lives only on datasheets. Even SpikeGLX's geometry metadata stores the in-plane electrode coordinates (x, z) and omits thickness (https://billkarsh.github.io/SpikeGLX/help/imroTables/).

Useful beyond double-sided probes:

  • Forward-modeling of extracellular signals: the shank is an insulating body that shapes the recorded field, and ground-truth simulators model the probe body, where thickness is a direct input.
  • Completeness: it is the same datasheet-sourced geometry as the contact positions and contour we already store, so the probe description stays self-contained.
  • Enables reconstructing double-sided probes in three dimensions (front and back at plus or minus thickness/2 along the normal). [This is how I started thinknig about it]

Related: #14.

Altought maybe this is omited for a good reason?

Lingua principale
Python
Stelle
85
Fork
49
Merge medio
13h 47m
PR unite (30g)
3

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di SpikeInterface/probeinterface

Tutte le issue di SpikeInterface/probeinterface

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.