SpikeInterface / SpikeInterface/spikeinterface
Motion correction error: win_step_um=400.0/win_margin_um=-200.0 are too large for the probe size
Open
Nobody has claimed this yet.
motion correction
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Hello!
I'm following the spike interface tutorial on testing different motion correctors on my NP2 4 shank recording.
The kilosort-like correction works..... but when I run dredge , I get a probe size issue.
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
Reproduce the SpikeInterface tutorial with the NP2 four-shank recording and compare the working kilosort-like correction with dredge. Start from the reported win_step_um=400.0 and win_margin_um=-200.0 probe-size error; done means determining the compatible dredge settings or documenting the required correction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100