Metal artefact reduction on CT


I am trying to segment bone with a metal prosthesis. Is there a plugin that will do this and remove the metal at the same time as segmenting the bone?

you can use the segment editor to deal with it.

1 Like


Is there a tutorial on how to do this?

I agree that for Segment Editor is a good tool for manual removal of metal artefacts. You can find some more background information and detailed description of segmentation related modules and links to tutorials here:

In Segment Editor, you can get initial segmentation using Threshold effect (that creates a segment that contains what you need and as small artifact as possible), apply a little Smoothing to make 3D reconstruction faster, enable “Show 3D” and use Scissors tool to cut off artefacts, then apply Smoothing to make the cut surfaces smoother.

@timeanddoctor do you have a workflow that you find that usually works well for you?

For automatic removal/reduction of artefacts the most effective tools are implemented in the CT scanner and workstation, as they require special image acquisition protocols and 3D reconstruction techniques. If the image is already reconstructed into a 3D volume then there is no generally applicable artefact removal method, but you can still develop techniques that work for certain kind of images. If you post a few screenshots then we might be able to give more specific advice.


I came around this old post searching for a way to do it in slicer.
Depending on your image, you can try wxdicom:

It has filters specifically targetting metal artefacts. It may be better than a direct segmentation (the metal stays there but the radial artefacts are largely removed).
It looks like these filters are not implemented in slicer tough ??


The wxDicom filters look nice, but it’s not clear if the source code is available and if so what license it is released under. You could experiment with the executables and if it’s promising you may want to contact the author.


I don’t know about the source code either but I guess it is published algorithms.
On the trials we did, it seemed to work pretty well.

However, the post was mainly to provide information to people that would look for the same info (what is out there, in slicer or not) and possibly trigger an updated reaction. I have no urgent need to have it implemented in slicer (it is fine for us to use it as wxdicom).