BEP032 support

Open
#309 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
data

Research direction

Start by reading the linked BIDS BEP32 pull request and the three proposed integration approaches. The issue mentions bidirectional conversion between ProbeInterface JSON files and BIDS electrodes.tsv and probes.tsv structures, but does not identify files, tests, or a settled implementation location. Done would require an agreed integration path and defined conversion utilities or documentation reference.

Written by the indexing model from the issue text.

Description

We're working on BIDS Enhancement Proposal 32 (BEP32) https://github.com/bids-standard/bids-specification/pull/1705 which requires probe layout specification capabilities. After evaluating ProbeInterface for this purpose, we've considered three approaches:

  1. Referencing ProbeInterface atlases directly
  2. Including ProbeInterface JSON files within datasets
  3. Adding ProbeInterface-inspired columns to existing electrodes.tsv and probes.tsv tables

We've decided to proceed with option 3 as it best aligns with BIDS' existing layout, form, and infrastructure. Moving forward, we'd like to develop bidirectional conversion utilities between ProbeInterface JSON files and the BIDS columnar structure.

While we're actively developing this on the BIDS side, we're still determining the best location for the conversion code. It might be sufficient to simply reference the BIDS implementation in the ProbeInterface documentation.
I'm creating this issue primarily to keep the ProbeInterface development team informed of these developments and potential future integration needs.

Dominant language
Python
Stars
85
Forks
49
Avg merge
13h 47m
Merged PRs (30d)
3

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

All issues in SpikeInterface/probeinterface

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.