SpikeInterface / SpikeInterface/spikeinterface
drift correction (Dredge) parameter optimization for long NHP recording
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Hi all, I’m using Dredge (with default SpikeInterface parameters, except for a longer chunk_duration of 6s) to correct motion in my 3-4 hour acute recording in head-fixed macaque. However, I’m seeing spikes in the motion vector trace, even though the animal wasn’t moving much at those times. Could these spikes be real, or might they reflectartifacts? If they’re artifactual, how should I adjust my parameters to improve the motion correction? Thanks in advance for your help!
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 reviewing the Dredge motion-correction parameters used through SpikeInterface, including the 6-second chunk_duration, and compare them with the motion vector trace from the long macaque recording. Determine whether the reported spikes are artifacts or real motion, then document parameter changes that improve the correction and explain how the result was validated.
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