-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raw pixel data from OMERO #4
Comments
Hi Will, This is great, thanks for sharing! Unfortunately, I've got very little experience with Docker and |
Hi, I'm afraid I can't think of anything obvious (I'm also not super familiar with Docker). I'm also on holidays just now, along with most of the OME team, so this was probably a bit premature and we'll need to pick it up again in 2 or 3 weeks. |
Hi Will, thanks for you help again! Hope you enjoy(ed) your holiday. |
@melvingelbard: likely the easiest is to make use of one of the existing Zarr libraries -- https://github.com/zarr-developers/zarr_implementations#zarr-implementations, with part of the decision coming down to classpath & jar size considerations. |
Reset CSRF token to null when logging out from a server
Currently the OMERO web api doesn't provide raw pixel data.
Pixel data in the form of OME-Zarr v0.1 can be provided by omero-ms-zarr but the limitation is lack of authentication.
I have tried another approach with https://github.com/will-moore/omero-web-zarr (not yet tested/supported by the OME team) which also uses OME-Zarr v0.1.
It's not yet included in the
omero-web-standalone
docker but you can add it by:Make the modification to
/standalone/Dockerfile
and/standalone/01-default-webapps.omero
as described in:ome/omero-web-docker#60 (comment)
Then:
Then, for Image ID: 79248, the top-level URL is http://localhost:4080/zarr/image/79248.zarr leading to:
http://localhost:4080/zarr/image/79248.zarr/.zattrs
http://localhost:4080/zarr/image/79248.zarr/0/.zarray
http://localhost:4080/zarr/image/79248.zarr/0/.zarray/0.0.0.0.0
etc.
In time,
omero-web-zarr
will hopefully be included in the docker, and on the demo server etc. but I wanted to let you know that it's possible to start trying it now.cc @jburel @joshmoore
The text was updated successfully, but these errors were encountered: