SpikeInterface / SpikeInterface/spikeinterface
motion_interpolation recording is not preserved after whitening
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Hello,
I'm getting a new recording object from "interpolate_motion" which I can explore with widgets.plot_traces and the motion correction is reflected on the traces. However, when I apply whitening (lazy), the resulting recording object is no longer motion-corrected, is the original recording whitened. The original recording came from a binary folder (created with spikeInterface).
The way I made it work was by saving the interpolate_motion-recording (binary folder), and after loading it, I applied the whitening (lazy) and the motion correction was there.
Just wanted to know if I did something wrong or whether I should always save the motion-corrected recording in case of applying whitening.
I haven't tried to run any sorter yet, but in case I didn't apply any whitening, I assume that it is ok to run any sorter on the recording object that came directly from "interpolate_motion". Am I right?
Thanks in advance for any comments about the best practices to run a sorter after motion correction.
Best
Pepe
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 reported sequence: load a binary-folder recording, apply interpolate_motion, then apply lazy whitening and inspect the result with widgets.plot_traces. Compare that with saving and reloading the motion-corrected recording before whitening. Done means determining whether motion correction is preserved through lazy whitening and documenting or fixing the behavior, including the expected sorter workflow.
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