SpikeInterface / SpikeInterface/probeinterface
provenance of doc/img/probeinterface_naming.png
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 85
- Forks
- 49
- Avg merge
- 13h 47m
- Merged PRs (30d)
- 3
Description
is there .svg?
was committed as part of the e9e531b1ddd97b52b0f8e78b61fd867d7e245a1f
NB FWIW, for code-produced changes, I recommend using datalad run (could be ran on pure git repos) to get commits like https://github.com/SpikeInterface/probeinterface/pull/370/commits/285bb1ea9cee5d159b84426e1e80accf0b9b8367 or even more complete reproducible example: https://cerebra.fz-juelich.de/f.hoffstaedter/ds000007-catqc/commit/2bebd8b789517cbec85d633e9bbc4928c3cd6111
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 inspecting doc/img/probeinterface_naming.png and its history, especially commit e9e531b1ddd97b52b0f8e78b61fd867d7e245a1f. Check whether an SVG counterpart exists and review the linked DataLad documentation and example commits. Done means the image's provenance and available format are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100