DICOM stack imported as one image

Provides a system for patient-specific cardiovascular modeling and simulation.
POST REPLY
User avatar
Shion Matsumoto
Posts: 14
Joined: Tue Nov 06, 2018 9:09 am

DICOM stack imported as one image

Post by Shion Matsumoto » Tue Jul 21, 2020 1:51 pm

Hi,

I have been trying to import a DICOM stack but am only able to import what seems like a single slice or none at all.

The error below has also been appearing for almost every stack. Is this an error that can be neglected?

[17.509] Reader 4 (Image Position by Acquisition) suggests 24 3D blocks
#17.638# ERROR: Reader 5 (2013 default sorting for 3D+t) threw exception during file analysis, ignoring this reader. Exception: Invalid tag values when constructing tilt information from origin1 '', origin2 '', and orientation ''
#17.773# ERROR: Reader 6 (IPP 3D+t) threw exception during file analysis, ignoring this reader. Exception: Invalid tag values when constructing tilt information from origin1 '', origin2 '', and orientation ''
#18.534# ERROR: Reader 7 (3D+t by AcquisitionNumber) threw exception during file analysis, ignoring this reader. Exception: Invalid tag values when constructing tilt information from origin1 '', origin2 '', and orientation ''
#18.676# ERROR: Reader 8 (3D+t by TriggerTime) threw exception during file analysis, ignoring this reader. Exception: Invalid tag values when constructing tilt information from origin1 '', origin2 '', and orientation ''
one_slice.png
one_slice.png (120.38 KiB) Viewed 410 times
Thanks,
Shion

User avatar
Weiguang Yang
Posts: 110
Joined: Mon Apr 07, 2008 2:17 pm

Re: DICOM stack imported as one image

Post by Weiguang Yang » Tue Jul 21, 2020 9:38 pm

You can try to use VolView https://www.kitware.com/volview/ to load a DICOM stack and save it as a vti file. Then load the vti file into SimVascular instead.

User avatar
David Parker
Posts: 1651
Joined: Tue Aug 23, 2005 2:43 pm

Re: DICOM stack imported as one image

Post by David Parker » Wed Jul 22, 2020 11:25 am

Hi Shion,

Problems reading in DICOM are often caused by having multiple sequences in the same folder. The DICOM reader tries to stack the images into a 3D volume but this fails when you have images at the same location.

Cheers,
Dave

User avatar
Shion Matsumoto
Posts: 14
Joined: Tue Nov 06, 2018 9:09 am

Re: DICOM stack imported as one image

Post by Shion Matsumoto » Fri Jul 31, 2020 12:56 pm

Hi,

I've been trying to use VolView but it seems the software is outdated on Mac OS. When VolView was suggested, did you mean for it to be used on Windows/Linux?

Best,
Shion

User avatar
David Parker
Posts: 1651
Joined: Tue Aug 23, 2005 2:43 pm

Re: DICOM stack imported as one image

Post by David Parker » Mon Aug 03, 2020 11:54 am

Hi Shion,

VolView is way out of date, crashes on MacOS.

I've written a Python script that converts DICOM to a VTK .vtk image. This file can then be read in by SV. Have a look here https://github.com/ktbolt/cardiovascula ... vti/python. I tested this on a Mac.

Cheers,
Dave

User avatar
Shion Matsumoto
Posts: 14
Joined: Tue Nov 06, 2018 9:09 am

Re: DICOM stack imported as one image

Post by Shion Matsumoto » Wed Aug 05, 2020 11:17 am

Hi Dave,

Thanks! I will give this a try.

Best,
Shion

User avatar
Joanne Sarsam
Posts: 34
Joined: Tue Oct 25, 2022 11:44 am

Re: DICOM stack imported as one image

Post by Joanne Sarsam » Thu Apr 20, 2023 10:22 am

Hello Dave,

How can I go about running the source code you posted? I am new to coding and I'm unsure of how to run source code posted by others on GitHub.

Thanks,
Joanne

User avatar
David Parker
Posts: 1651
Joined: Tue Aug 23, 2005 2:43 pm

Re: DICOM stack imported as one image

Post by David Parker » Thu Apr 20, 2023 11:08 am

Hi Joanne,

You can view the Python script here (https://github.com/ktbolt/cardiovascula ... -to-vtk.py) and then select the Raw button located on the panel the code is displayed in. This will display the script in the web browser which you can then save to a file using the File/Save As menu option.

You can then run the script as described in the README file.

Cheers,
Dave

POST REPLY