SpikeInterface / SpikeInterface/spikeinterface
correct motion run time and output
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Hi,
I've noticed 2 things when running the motion corrections. First thing is that the recording object post correction has fewer channels. Is that deliberate?
Secondly, the estimate motion step is taking much longer that the detect and localise step, 200 s vs 1500s. Also wondering if that's common
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 by reproducing the motion-correction workflow and compare the recording channel count before and after correction. Measure the detect and localise steps against estimate motion, then determine whether the channel change and runtime difference are expected; done means the behavior is explained or corrected with coverage for both observations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100