Go to next spike with ISI < refractory period
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 430
- Forks
- 187
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 2
Description
It would be nice if I could jump in the trace view to the next spike with interval to the spike afterwards shorter than the refractory period that is set in the correlogram view.
I have clusters with RPV due to, in most cases, detecting artifacts or spikes from other cells, which should be excluded from the cluster. To check the trace where RPV is happening, currently I have to navigate through the trace with "Go to next spike". Do you think it makes sense to have such a function and would it be feasible to make it?
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 the existing trace-view “Go to next spike” navigation and how the correlogram view stores or exposes its refractory-period setting. Implement the navigation so it selects the next spike whose interval to the following spike is shorter than that setting. Done means the trace jumps to matching RPV events and preserves the existing navigation behavior otherwise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100