DynamicsAndNeuralSystems / DynamicsAndNeuralSystems/pyspi
Record compute time for each SPI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 256
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Will be useful for knowing which methods are fast/slow to compute and allows users to select faster options.
This might be finicky since many of the methods inherit preprocessed information from other methods (e.g., all spectral methods inherit spectral decompositions).
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. Start by tracing how SPI methods execute and how shared preprocessed information is inherited, then determine how timing should be attributed to each method. Done means compute times are recorded per SPI and can support comparison of faster options without misleading double-counting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100