SpikeInterface / SpikeInterface/spikeinterface
Request: ability to select time windows within SortingAnalyzers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
We are working on linking units across sortings, and as there is always some unit instability over time, we've found that this requires comparing the waveform properties from the end of one recording with those from the beginning of the next recording, particularly for continuous recordings where we're sorting a day at a time.
We'd therefore like to be able to specify template extraction and potentially other metrics limited to specific windows within a sorting as a SortingAnalyzer feature so that users can do the matching across datasets.
I think this could be broadly helpful and will be a more and more important feature as people move toward longer recordings.
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 locating the SortingAnalyzer implementation and its template extraction and metric entry points. Clarify how users should specify windows within a sorting, then define the expected behavior for comparing the end of one recording with the beginning of the next and identify tests covering continuous recordings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100