Add shank thickness to the Probe model

Abierto
#452 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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?

Lenguaje dominante
Python
Estrellas
85
Forks
49
Merge medio
13 h 47 min
PR fusionados (30 d)
3

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de SpikeInterface/probeinterface

Todos los issues de SpikeInterface/probeinterface

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.