Gregory Lee

> Also the reconstruction is not always exact, it depends on the shape of the image (ideally should be power of two). Is it really power of two or is...

Probably should not have hit the "approve changes" button above just yet as there were still a couple of minor comments pending (see the last two above). I thought perhaps...

> any updates on this? Thanks! At this point the PR needs to await a second reviewer before it can be merged. It will have to be rebased again at...

I don't know what is going on with the one Travis failure. From the message it seems related to the intial `pip` call for installing dependencies (not sure why astropy...

I may be somewhat less available until the 28th. I never did a close comparison to the original publication, but the unit tests here at least verify that round trip...

Thanks @JoOkuma, this has also come up a few times in the past and the scikit-image dispatch backend work would be a good reason to revisit this. I am personally...

Agree that this definitely needs improvement. The scikit-image examples gallery is currently the best way to reference the API usage for the image processing functions under `cucim.skimage`: https://scikit-image.org/docs/stable/auto_examples/index.html We can...

For Image I/O functionality, there are small number of [notebooks](https://github.com/rapidsai/cucim/tree/branch-25.10/notebooks) in the repository, but we don't currently render these in the docs.

## Current issues running cuCIM with NumPy 2.0 and CuPy 13.2 I ran the cuCIM test suite locally with NumPy 2.0 and CuPy 13.2. The remaining compatibility issues encountered are...

Looks like the first issue above (`cupy.full`) is resolved by cupy/cupy#8408 and the second (`cp.random.seed`) seems to be in progress in cupy/cupy#8407 The last two can be resolved within cuCIM...