SpikeInterface / SpikeInterface/spikeinterface
Roadmap question: deep inter-session unit matching / UnitMatch-style matching
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Is implementing deep inter-session unit matching (UnitMatch-style / chronic alignment) on the SpikeInterface roadmap? If so, what is the expected timeline and preferred integration point (module/API)?
Context: Issue #2626 discusses inter-session alignment workflows and post-hoc unit matching, including compatibility with MouseLand/UnitMatch. Linking here for reference.
I will likely be implementing UnitMatch for my own pipeline regardless, so if this feature is planned I would be happy to contribute an implementation under maintainer guidance (tests + docs included). That way the effort could support both my project and SpikeInterface.
Happy to align on scope and placement before starting development.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #2626 and the linked MouseLand/UnitMatch repository to understand the existing inter-session alignment workflow and compatibility questions. Before implementation, confirm the intended roadmap, module or API placement, scope, and maintainer guidance; done means those integration decisions are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100