Fix `n_jobs`'s default and make it work for more APIs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 779
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 27
Description
n_jobs : Optional[int] (default: None)
Number of threads to use in training. All cores are used by default.
n_jobs (integer, optional, default: 1) – The number of jobs to use for the computation. If -1 all CPUs are used. If 1 is given, no parallel computing code is used at all, which is useful for debugging.
scanpy code:
I'm guessing the scanpy docs are wrong when they say "All cores are used by default." ?
Contributor guide
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 comparing the n_jobs handling in scanpy/external/pp/_magic.py with the default defined in scanpy/_settings.py and the linked Scanpy and MAGIC documentation. Trace which APIs currently expose or ignore this option; done means the default and supported APIs have consistent behavior and documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, bioinformatics
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100