You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This transpose call (m_reg.transpose(1, 2, 0)) is hardcoded for a 3D array corresponding to a 2D movie (with shape (n_frames, height, width)). It works correctly for 2D movies but fails to generalize when the movie data is 3D (e.g., having a shape like (n_frames, height, width, depth)).
It seems like switching to moveaxis resolves this for both 2D and 3D, like this:
In the function apply_shifts_movie (see line 477 of the current version), the block that saves the memory-mapped file uses the following code:
CaImAn/caiman/motion_correction.py
Line 477 in 0b5a9e1
This transpose call (m_reg.transpose(1, 2, 0)) is hardcoded for a 3D array corresponding to a 2D movie (with shape (n_frames, height, width)). It works correctly for 2D movies but fails to generalize when the movie data is 3D (e.g., having a shape like (n_frames, height, width, depth)).
It seems like switching to
moveaxis
resolves this for both 2D and 3D, like this:Could this be a change work making to the function? Thanks very much.
The text was updated successfully, but these errors were encountered: