Closed Heerpa closed 2 years ago
similar to #71, can you try updating nd2 and see if you get an improvement? Some things got better in https://github.com/tlambert03/nd2/pull/51 (which is >=0.2.3). I wouldn't expect that to fully solve everything, but perhaps a little gain
assuming this is fixed like #71
Description
I have long microscopy movies - e.g. 30000 frames, otherwise only dimensions X and Y. All frames are analysed independently.
For reading .nd2 files, I've tested nd2reader, and nd2 (which I'd prefer because of better access to the metadata). using the nd2reader, I can read at a speed of about 800 frames/second (single-process) using nd2, I get 20 frames/second (when converting frames from dask to numpy using .compute()). Only loading the frames as dask arrays, I get 2000 frames/second - but of course I need to do the computations in numpy.
Is there a way to load planes faster? I don't have enough memory to directly load the complete dataset.
What I Did
output