-
Notifications
You must be signed in to change notification settings - Fork 14
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
Dimension mismatch with loading a lazily loaded image to memory #177
Comments
Does |
Yes, |
Interesting. Can you give me the output of |
first(ifds(image)) = IFD, with tags: |
Ah, the image is tiled.
This error now makes more sense, since the tile sizes are 256x256. Do you mind providing the full stacktrace (all of the output) for |
Lines 138 to 141 in f4d285b
If you lazyio load the image, what's the output of |
size(img.cache) doesn't work, I get
Full stacktrace:
|
That means that you weren't loading using with |
This was the code I ran:
|
Ah, my bad. I forgot that we wrap with a |
|
@tlnagy perhaps I could also share the image with you if that would be easier? It is quite large though. |
Yeah, do you mind uploading it to dropbox/similar place and I can download it? It'll be easier to diagnose that way then going back and forth here. You can send the link to my email listed on my github profile page. |
Sent |
Do you mind sharing it as a public link? It's requiring me to log in to access it. |
Sorry, just sent a link. Let me know if that works. |
I'm preparing a PR for this |
Does this require a PR? |
Thanks to @chrstphrbrns' quick work this should be fixed in the newest release |
I have loaded in a large image (26 GB) lazily with the lazyio=true flag and am now trying to load a subset of that image to memory by indexing as follows:
This gives the following error: LoadError: DimensionMismatch: parent has 18596 elements, which is incompatible with size (256, 256). The reason I am loading in a loop like this is because I couldn't even @show the size of a 3D chunk of the image without the same error being thrown. I can @show the size of a slice, though (not sure why). I have verified that the size and eltype of the lazily loaded image is correct. Any ideas what is going on?
The text was updated successfully, but these errors were encountered: