Operating system: Windows
Slicer version: 4.10.2

In my slicer version there isn´t the “PETTumorSegmentationEffect” recommended by the wiki for segmentation in PET images.

Another one, my image of PET display with background black. How I could change that?


You need to install the PETTumorSegmentation extension: Documentation/Nightly/Extensions/PETTumorSegmentation - Slicer Wiki

You can use Volumes module to pick a different lookup table.

It doesn´t appear in my extension manager, it´s possible that this extension don´t be compatible with x64bit?


It looks like the module has build issues on all platforms with the nightly:

Based on the error, looks like it has not been migrated to ITK5:

@chribaue not sure if you are aware of this?

@Mgi at this point, your best bet is probably to try latest stable build. I checked, and at least on Mac, the extension is available in the stable build.

Dear Fedorov,

I want to normalize some PET images by the SUVmáx, that´s possible with the PETDICOM extension in 3Dslicer?

If the answer is negative you could recommend to me another extensions

Thank you!


Do you have some documents where explain how to normalize using the PET DICOM extension?

Thank you! Regards

Hi @fedorov, I did install the 3Dslicer versions 4.8.1 and 4.6.2 on windows, because I though those are stable build. I load a PET serie, the “PETTumorSegmentationEffect” button appear but it didn’t serve when I used didn’t segment. What version should I use?

You should use the latest stable, which is 4.10.2

I have this version 4.10.2 on windows but it doesn´t appear the “PETTumorSgementationEffect” button in Editor Module neither PETIndic module.

@Mgi you are right - the effect button is missing!

@chribaue any suggestions? There are no errors in the log, or in the python console.

For visibility, JC issued a PR back in April to update this extension with ITKv5 and python3 support and tagged you @fedorov (also received a response from @chribaue ). It would be a good time to review this PR.

Paired with this, JC suggested to create a branch for Slicer 4.10 code.

1 Like

Thanks a lot @jamesobutler - I completely missed those issues! Now that I did look into this, I also see this issue,, which explains why the user was looking into 4.6.2. It looks like @chribaue did not find time to get to this. I am not sure if the team has resources to support this extension, let’s wait until Christian responds. It appears to me from those issues and the PR that they are not trivial.

We do have an upcoming project where resources will become available to fix above mentioned issues.

The extension used to work on Slicer 4.10.0. Why it’s not working in Slicer 4.10.2, I do not know. Switching to ITKv5 and python3 will indeed not be trivial as can see from For now, I can only refer interested users to use the extension with Slicer 4.10.0.

1 Like

For the reference, 4.10 packages are available here: (following “older releases” link on