Replies: 2 comments 3 replies
-
Thanks for pointing this out. I thought I had looked into this and done some profiling! 😱 Will check it out again and try to reproduce what you are showing -- it absolutely makes sense you would get this, and I was surprised when I didn't find something similar. If you show code snippets that might help me reproduce (just to be clear: it's about calculating the correlation/pnr image on F versus C-mapped arrays, right? This is what I thought I had profiled but I may well be wrong, or have made a mistake). |
Beta Was this translation helpful? Give feedback.
-
Yes, I think what made the biggest difference was File incrementing instead of frame incrementing (for increment 1 there's "only" 100s difference).
At first I loaded the files separately and then I concadinate them, but I found load movie chain to work just as well
Hope this helps :) |
Beta Was this translation helpful? Give feedback.
-
caiman uses the giant C_framed file to calculate the summary image (for pnr and corr), I replaced it with the smaller F_framed ones and it gave me much better runtime (especially if you're fetching the file from the network) and it allows for file level increment with reduces runtime even more (went down on my setup from230s on frame_increment= 5 to 73s on the same frame increment)
F_ordered seems to work so much faster especially if you do file increment instead of frame increment.
and it's as easy as loading the F_ordered files with the "cm.load_movie_chain()" function, you can also do file increment instead of frame increment
Beta Was this translation helpful? Give feedback.
All reactions