SpikeInterface / SpikeInterface/spikeinterface
Update the way we handle spikeinterface installation in containers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Some container images come with a pre-installed version of spikeinterface.
If this is the case, spikeinterface is NOT installed in the container (see here), but this can cause versioning issues.
We should add a mode that checks that the major version is the same, and if it's not it forces reinstall
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 in src/spikeinterface/sorters/runsorter.py around lines 490-498, where pre-installed spikeinterface is currently handled. Trace the container installation and version checks, then define the behavior for matching versus different major versions. Done means a mode detects a major-version mismatch and forces reinstallation without affecting matching versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100