toloudis

@Nicholas-Schaub is this still something that would be useful if merged into our repo?

Coincidentally, I have an immediate need to parameterize the `order` parameter which we left at order=1 for the dask skimage rescale function. https://github.com/ome/ome-zarr-py/blob/master/ome_zarr/scale.py#L153 Interestingly, for visualization of raw microscopy intensities,...

Interestingly, I just reproduced the same issue both on Windows and on Linux with dask 2023.6.0 when trying to convert a microscopy time series to zarr (TCZYX =~ (1000, 1,...

I'm also interested in optimal implementations for generating downsampled data for large datasets. There are many alternate implementations to the Scaler -- one intriguing one is here: https://github.com/spatial-image/multiscale-spatial-image , which...

I believe #470 allows this one to be closed/deleted

Thanks to guidance from this issue I have begun to integrate OME-Zarr in my volume viewer as seen here: https://github.com/allen-cell-animated/agave/pull/73 https://github.com/allen-cell-animated/agave/pull/73/files#diff-c2505cb0ef29a0b26d0eedacbc8049b5b3dd87214baa7ff4ae72a5bb23d7168f

> I see you gave `netCDF` a shot as well, @toloudis 😄 Nothing against it, but I did attempt it but just found the integration with cmake and getting it...

I have not specifically measured this so I'll speculate that it is our code that tries to make sure the dimensions are in a consistent order for the rest of...

Ok this is wonderful and thank you for the detailed profile. I forgot about the reader check. You can give aicsimageio a hint about which reader to use like this:...

I'll also add that determine_reader should hopefully be a fixed cost that doesn't scale with the data size. We expect the data loading to be the bottleneck. Arguably we could...