Os: Windows 10 Pro
Slicer version: 4.11.20210226
All extensions updated.
I am trying to load CT data slices using ImageStacks. I get the following error when I try any slices, and when I try to generate a preview and full resolution.
Loading failed: Exception thrown in SimpleITK ImageFileReader_Execute: D:\D\S\Slicer-1-build\ITK\Modules\IO\TIFF\src\itkTIFFImageIO.cxx:1408:
itk::ERROR: itk::ERROR: TIFFImageIO(00000209510E01C0): Problem reading the row: 941
Slice error number does change based on which slice axis I try to load (X, Y or Z)
That looks like a read error that would come from corrupted data. Are the files readable with other applications? If you can read them in another app, maybe try re-saving them and trying those in Slicer. If you find a version that works elsewhere but not in Slicer please share an example for debugging.
Hi @muratmaga and @pieper , thank you for the help! I’ve attached a link to a zipped file of the slices. When the person CT scanning our birds includes the slices, they have a X, Y and Z slices files. I’ve historically been able to load the X slices (of other birds) in ImageStacks, but now wonder if I’m missing something. Hopefully you can look at the data and see. Thanks, again! download link
Hi @Rosalee_Elting - I tried downloading the google drive link but the zip file is invalid somehow. Can you confirm the zipfile is valid on your end and maybe try re-uploading? The issue may be due to the size of the zipfile so maybe you can see if you can replicate the issue with just one or two images?
I donwnloaded and unzipped and used the X-slices folder, didn’t encounter any issues either loading the preview or full resolution dataset. There are many datasets in the zip file, is there a particular one you are facing the issue with?
Hi @muratmaga ! Looks great! This scan was taken with a 16.2um slice distance, I’m wondering if my changing the auto-populated values (0.264…mm) is where the error generated from. Coincidental or related, do you think?
You can manually update the voxel spacing at the ImageStacks. I simply used whatever the value tiff files reported (hence another reason not to use 2D formats like that).
Slice spacing shouldn’t cause an issue like that. Perhaps as @pieper indicated one of your files were corrupted, thought I don’t know why you got that with other datasets. All I can say that ImageStacks working correctly with this dataset using the stable version of slicer.
Thank you for looking into it! I will check the files for corruption (they were transferred in a strange way, so that could be it). I appreciate you trying it on your machine and narrowing down the issue and that it isn’t ImageStacks. Can you direct me to a forum for preferred formats (non-tiff)? Thank you!
If the imaging lab gave you this, you will have to import it through the ImageStack, and when you are importing make sure you enter the correct voxel spacing values. After a successful import, you should save the resultant volume as NRRD so that you don’t have to keep importing and fixing the voxel spacing, everytime you want to work with this dataset.
There are a few other volumetric dataset options, but NRRD is the most flexible and supported by other open source biomedical visualization programs, so thats what we suggest.
Great! That is super helpful. I usually save the scene and only load the slices once to prevent mis-loading with the wrong voxels or other slice issues.
