Why are memmap
files saved twice during motion correction?
#1425
Unanswered
programerkotik
asked this question in
Q&A
Replies: 1 comment
-
Probably saving the memmap in C-order to run CNMF? There's no saving of memmaps twice for motion correction, mescore doesn't do it, the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When running the parts of codes from the CNMF-E demo notebook for motion correction part, I observed that
memmap
files are saved twice:motion_correct(save_movie=True)
.cm.save_memmap
.Here:
This redundancy becomes problematic with large datasets and it seems unnecessary to save the data twice, yet my attempts to bypass one of the saves lead to issues.
Question
Why are
memmap
files saved twice during motion correction?The design seems intentional, but I wonder why. I noticed that one of them is saved in "F" order, and another one in "C". What is the meaning of that?
Beta Was this translation helpful? Give feedback.
All reactions