You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we use custom writers that try to be compliant with OME-NGFF and OME-HCS specs. This was out of necessity since there was no existing tool at the time. However, maintenance overhead to keep up with the specs is high and the writers now write to outdated versions of these formats.
The official implementation appears to be still far from feature complete. While the reader may prove useful, the writer's APIs does not meet our needs in fine-grained control of data IO.
They update the spec much more frequently than the python API. I think it will take a very long time for it to be feature complete.
If our writer uses cupy for the pyramid generation it would be great.
I implemented a tiled version for large images in here it should work on 3d with minor tuning.
Currently we use custom writers that try to be compliant with OME-NGFF and OME-HCS specs. This was out of necessity since there was no existing tool at the time. However, maintenance overhead to keep up with the specs is high and the writers now write to outdated versions of these formats.
Now that tools have evolved within the community, we should be able to switch to the official Python implementation of OME-NGFF as our writer to OME-Zarr.
The text was updated successfully, but these errors were encountered: