SpikeInterface / SpikeInterface/spikeinterface
Feeding multi segment recording to sorters
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
@samuelgarcia @alejoe91
https://github.com/SpikeInterface/spikeinterface/pull/489
By the way, I think the users should always give to sorters an AppendRecording and get back a SplitSorting. For the sorters that only operate on ConcatRecording (and not on AppendRecording) they should just convert the AppendRecording to ConcatRecording under the hood. This is because AppendRecording/SplitSorting is obviously the correct way to handle multiple segments. Maybe can print a message to let the user know that this is happening. Thoughts? @alejoe91 @samuelgarcia
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 pull request #489 and the handling of AppendRecording, ConcatRecording, and SplitSorting in the sorter entry points. Determine the intended multi-segment behavior and how completion should be verified, including whether users receive a message when conversion occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100