-
Notifications
You must be signed in to change notification settings - Fork 7
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
Re: error with opening a ome.tiff file. #106
Comments
|
|
I will come back with a sample image in a few days... |
Bump. Are you still running into this issue? |
Oh, Sorry. |
I have also been working on a Zeiss setup recently and can't open the files. If I first open them in FIJI and export them to OME-TIFF then they seem to work. I cannot access this system anymore so I can't get lightweight images to reproduce the error, but I'm willing to share one of the stacks I have (~5 GB) if it helps to identify the issue. EDIT: Whether they open or not after the FIJI export seems to be random, but the error is different. E.g., if I open it, slice it down (in this case taking only 5 frames) and export it, then I get indexing issues:
|
I am having the same issue loading the tiff files. Error encountered while load FileIO.File{FileIO.DataFormat{:OMETIFF}, String}("morphology_mip.ome.tif"). Fatal error: |
Unfortunately, the error messages aren't super helpful here. Does anyone have a small-ish file (<100 MB) that reproduces this error that they can share with me? |
Hi,
My images was acquired by a Zeiss confocal microscope and saved images as ome.tiff. When I tried to load the file in julia, I got this error:
Interestingly, I was able to load the same files in Fiji (but the pixel parameters were were not correct). I also checked the header file with
tiffcomment
command:Also I have the "original" czi file format. If I open it in fiji and store it as ome.tif, Julia could load the resulting ome.tif file. While I can convert all files in Fiji, I wanted to check if these is better ways to solve this issue.
The text was updated successfully, but these errors were encountered: