SpikeInterface / SpikeInterface/spikeinterface
Stuck process in Motion_correction
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Hi! I've been trying the drift correction module recently, and I found it to be a really nice combination of tools for addressing this issue. However, I'm having trouble getting the final output from motion_correction: it completes the peak detection and localization (shown in the progress bar) and then gets stuck there for several hours without completing the process. I would like to save this output to run kilosort on the corrected data. I tried so far to run this from a jupyter notebook, using spike interface 0.100.8 and 0.101 in Windows 11.
Any suggestions regarding this are very much appreciated, many thanks!
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 with the motion correction module and reproduce the report in a Jupyter notebook on Windows 11 using SpikeInterface 0.100.8 or 0.101, observing the transition after peak detection and localization. Done means identifying why processing remains stuck and confirming that motion_correction completes and produces output suitable for Kilosort.
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
- 30/100