SpikeInterface / SpikeInterface/spikeinterface
Memory error on concatenating and slicing recording with OpenEphys
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
What is the best way to cut a multi-segment recording, slice it to get only certain time points across the recording and concatenate those slices for sorting?
I have used frame_slice and then concatenate but then when I use this it does not complete the spikesorting.
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 from the reported frame_slice and concatenate workflow for a multi-segment OpenEphys recording, then reproduce the memory failure through spike sorting. The issue does not name files, tests, or an expected fix; done would require identifying the supported slicing and concatenation behavior and documenting or correcting the failing path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100