-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Can't interpolate traces" with int16 dtype in motion_correction #3146
Comments
Update: changing dtype to float coming out of preprocessing chain solved the issue and correct_motion runs with both presets now. (Is there any reason why this would alter spike sorting outcomes, and should be changed back to original int16 at some point?) Note: trying to plot the motion vector as per the documentation now gives an error that the API has been updated, but doesn't specify that recording object now needs to be passed.
|
Hi Ava. And yes the solution was to dtype as float32 like you said. For plotting you can do this motion_info = si.load_motion_info(folder)
motion = motion_info['motion'] #<<< this is the Motion object
print(motion)
plot_motion(motion, mode='map')
plot_motion(motion, mode='line') |
I'll close this but if something else comes up let us know! |
Hello,
I'm trying out a few motion correction algorithms on Neuropixel 1.0 data. I'm currently running through the pipeline with a short (<5 minute) recording. After chaining preprocessing steps, I get the following error when the detect and localize step completes. Any ideas what is causing this behavior?
At first I thought the error may have been caused by one bad channel that had been removed, but the error persists regardless of whether any channels are removed or not.
Also, the dtype has not changed through preprocessing - og dtype is and remains int16.
Many thanks,
ava
The text was updated successfully, but these errors were encountered: