Skip to content
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

Problems opening a 384 well-plate #84

Open
tibuch opened this issue Mar 15, 2023 · 2 comments
Open

Problems opening a 384 well-plate #84

tibuch opened this issue Mar 15, 2023 · 2 comments

Comments

@tibuch
Copy link

tibuch commented Mar 15, 2023

Hi,

I have a 384 well-plate ome-zarr file where each well has a single field of shape (4, 5, 4096, 4096) (CZYX). When I try to open this I get the following error message:
ValueError: Shape of in dividual tiles in multiscale (16384, 24576) cannot exceed GL_MAX_TEXTURE_SIZE 16384. Rendering is currently in 2D mode.

@jeskowagner
Copy link

jeskowagner commented Jun 15, 2023

I am encountering the same error with a 384 well-plate, six sites per well, each of shape (5, 2048, 2048) (CYX). The error mentions a slightly different dimension: (8192, 18432) instead of your (16384, 24576).

@jluethi
Copy link

jluethi commented Jun 16, 2023

Hey both!
If you have a full 384 well plate, the question for napari will be: "How big is the stitched image of all the wells at lowest resolution". If you only have relatively few pyramid levels, the lowest resolution of each well stitched together for the whole plate is still an image that is too large to load with the GL_MAX_TEXTURE_SIZE of your GPU.

An easy way to avoid this is to ensure you create more pyramid levels, thus having the lowest resolution below the GL_MAX_TEXTURE_SIZE limit. By just adding 1-2 extra pyramid levels, you probably get there. Many GPUs have a limit around 16k. To be save, maybe add 3-4 pyramid levels => also works on lower quality GPUs still.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants