Problems creating a volume from rotational angiography data

Hello Slicer wizards,

I’ve been trying to generate a volume from DICOM data that I’ve obtained from a rotational angiography scan. To help me explain the problem I’m encountering, I’ve attached 2 images. The first image shows the problem I’m getting, apparently the rotational angiography does not provide me 3D data, but sort of a “2D data over a time”, not sure how I could classify it. This can be easily seen when analysing the top right of the image, where only one view is actually correct. Is it possible to generate volume from this type of data or a CT scan is what I should be looking for?
For the second image, a 3D model was generated in the machine that does the angiography. Is it possible to generate volumes from these already pre-made volumes from the machine’s software? Because if I try to import it, slicer only treats it as being a 2D image, as seen from the Y and G views.

Thanks in advance!

slicer3d_1 slicer3d_2

1 Like

This looks like a sinogram (projection images acquired during the rotation), which needs to be reconstructed to a 3D Cartesian volume. See more information in these topics:

That is just a screenshot. If there is any 3D information in that image, it is stored in private fields.

What devices (manufacturer, model, number) did you use to acquire and visualize/reconstruct the images?

@gcsharp would it make sense to consider an openrtk extension?

Maybe for people who are uncomfortable with command line programs it could be good. Currently, a (potential, proposed) workflow within Slicer does not seem easier (IMO) than to run RTK separately.

If an RTK extension were available would people make add-on programs to do image processing on projection data, thereby proving the value of the extension? Who knows!

[Edited for clarity.]

Oh yes, I would find it much easier if it was distributed as a Slicer extension and could be installed and executed by a couple of clicks!

The problem with RTK starts with a note on download page: “The current release is version 1.3.0 from September 2016”. For me, it means that the project is dead and I should probably not waste any time with it.

OK, I go past this, but then I find that there is no binary download. I give up at this point. Since the project is dead, I will not spend time with trying to build it, running into issues, and then having difficulties with trying to get help. Github repository seems to be linked to a single GitHub user, not an organization - another red flag.

I also glanced at the documentation section. There was no mention of any command-line tools, just API reference. After this, I’m certain that this toolkit will not work for me.

Maybe the actual situation is better, maybe the toolkit is not dead, there are pre-built binaries and documentation available somewhere… but then toolkit’s website is extremely poor and misleading.

1 Like

I hadn’t looked at openrtk in detail and not recently, but I noticed that version 2.0 was released very recently and that gives me hope the project is still very viable. I agree with @lassoan that easy to install and use binaries could be a boost.

Typical use cases for reconstruction software are: (1) algorithm R&D, and (2) equipment development. As such, RTK has a more narrowly focused set of users than Slicer, and I don’t know how an extension would improve their workflow.

If an RTK extension were made, it should include the python API.

Thank you for spotting the error on the web site about the current release. I’ll post a message to let them know.

True, if users with a sinogram could just as easily request a reconstruction from their scanner then there’s no point in making an extension.

Thanks for the help @lassoan
Let me see if I got the right idea after reading the 2 topics you have sent me.
I can reconstruct a volume from the software that acquired the sinogram and from that I would export as .dcm to slicer? Because the screenshot that I showed in the second image was the reconstruction made by the machine’s software, but I probably exported it wrong.
As for the device, I’ll contact the physician responsible for the images, since all I know is that the device/software are from Philips (I don’t think that this is enough info).

Edit: Just got in contact with the physician and the device model is “Allura FD10” with the “3D RA” software. Both the device and software are from Philips.

Thanks for the update. I agree that the best would be to export the reconstructed 3D volume as a CT image from the Philips software.

Try to import that fluoroscopy study in Philips IntelliSpace Portal (you should ask someone at your radiology department) and if you can open it maybe it is possible to make VRT reconstructions. If you are able to do so than you could export that VRT as. stl file simply by clicking right mouse button on VRT and choose save as stl.
Please let me know the results because my department got Philips Azurion :slight_smile:


Thanks for the suggestion @kopachini.
However, I do not think our radiology department has this software at our disposal, unfortunately. I had a check on this software, and it would probably solve our problem, but I need to work with what we have, which is the Allura - 3DRA software. Has your department used or has any idea if this specific software is able to do something similar or at least export volumetric data as .dcm so I can generate a 3D model in blender?

Hi, unfortunately I don’t know what softwer we will have with Azurion.
What I ment is that if you have Philips fluoroscopy, maybe the department have Philips CT machine wich comes with Intellispace Portal so you could import it there.

uto, 30. tra 2019. 14:39 Deyline via 3D Slicer Forum je napisao:

1 Like

It would be extremely limiting if you could only export STL files from your 3DRA acquisitions. The 3D reconstructed volumetric image contains much more information. You can use volume rendering for visualization or segmentation structures to save them as STL files, etc.

Your Philips representative should be able to tell you what options you have to access reconstructed 3D volume in DICOM format.


Hello everybody, a few days ago educator from Philips came at angio suite regarding Azurion machine. Under rotational angiography, you mean CBCT? If that is so than it is possible to export that study into Philips IntelliSpace portal and export stl file from VRT

1 Like

Is there any module in 3D Slicer related to “filtered backprojection”?
I have similar problem, creating volume from a rotational angiography data, and noticed Lasso’s reply in Volume rendering shows solid black cube only, which mentioned the technique to reconstruct 3D volume from sinogram. If necessary, I can share the DICOM (anonymous) link here.

I’m not aware of any Slicer module that can do this. The best would be to implement a GUI for RTK toolkit as a Slicer module. You can submit a request on their bugtracker to implement a Slicer module, implement it yourself (we can help you to get started), or use its existing Python or command-line interface.

1 Like

Hi everybody,
i’m writing a thesis about 3D printing aplications in neurosurgery and i’m having the same trouble that has generated this topic: i haven’t found any way to obtain a 3D model from a rotational angiography:

Since some time is passed, do you know if any solution has been created? because RTK toolkit looks really too much complicated for me…
Otherwise i will follow @lassoan 's suggestion and i will submit a request to implement a Slicer module

Thanks in advance :wink:

You have a 2D projection image sequence, which is not a 3D volume. You can use RTK to reconstruct a 3D volume.

1 Like

Hi Deyline. I have the exact same issue as you (trying to use Slicer to reconstruct cerebral angio). Just wondering - did you ever find a solution to this issue? If so would love to hear from you ASAP