SpikeInterface / SpikeInterface/probeinterface
Check consistency with BEP032 version 0.2.0
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 85
- Forks
- 49
- Avg merge
- 13h 47m
- Merged PRs (30d)
- 3
Description
BEP032 had some updates recently. We should check for consistency between the current probeinterface version and BEP032 version 0.2.0.
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 reading BEP032 version 0.2.0 and comparing its probe requirements with the current probeinterface behavior. Identify any inconsistencies before choosing the affected implementation or tests; done means the package is consistent with the specified BEP032 version and the comparison is covered by appropriate verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100