SpikeInterface / SpikeInterface/spikeinterface
[Question]: Usage of Graph Algorithms and Any Slowdowns?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Hi there,
I'm interested in understanding if spikeinterface depends on any graph algorithms from its usage of NetworkX? If so,
- What algorithms are used for what purpose?
- What graph sizes are they being used with?
- Have users experienced any slowdowns or issues with algorithms provided by NetworkX? (Speed, algorithm availability, etc)
Furthermore, would users be interested in accelerated nx algorithms via a GPU backend? This would involve zero code change.
Any insight into this topic would be greatly appreciated! Thank you.
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
No files, tests, or entry points are named. First locate the project’s NetworkX usage, then inventory the algorithms, graph sizes, and reported slowdowns; done means documenting those findings and recording whether accelerated GPU-backed algorithms would interest users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100