SpikeInterface / SpikeInterface/spikeinterface
Feature request: `gputouse` keyword argument in `run_<sorter that supports GPU>()` and `run_sorter()`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Feature
gputouse: Optional[int, Sequence[int]]. Integer or Sequence of integers indicating the index of the GPU(s) for spike sorting. For CPU, and not GPU, set to None. Index for each GPU can be found with nvidia-smi command.
This keyword argument should be available on sorters that support GPU; run_<sorter that supports GPU>() and run_sorter().
Remarks
Containerized workflows can also take advantage of this kwarg. Docker supports GPU-passthrough on all major platforms; including Windows (WSL 2 required). Should be possible with Singularity.
Question
Do any of the sorters support multi-gpu?
(last issue of the day 😁)
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 locating the GPU-capable sorter entry points named in the issue, along with run_sorter(), and inspect how their keyword arguments are defined. Check the existing sorter support and the multi-GPU question before deciding the scope; done means the gputouse argument is consistently available where requested and its CPU, single-GPU, and sequence-of-GPUs behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- backend-api-design, data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100