Turn off all smoothing in segmentation

leomigfer · January 25, 2018, 5:24pm

O.S. Win 10 - 64bit
Version: 4.8.1

Hi there,

We are willing to apply this software to segment the thalamus and need to correct segmentation errors on a pixel-by-pixel basis. For this reason, we need to abolish any possible type of smoothing on the source image. Is that by any means possible?

With very best wishes and many thanks in advance,

Leonardo

cpinter · January 25, 2018, 6:08pm

No smoothing is done on the segmentation (the edited labelmap, which is the master representation) without user intervention. The 3D model is smoothed, but it is only extra visualization. You can turn off model smoothing using the Set surface smoothing option under the arrow next to the Show 3D button in Segment Editor.

pieper · January 25, 2018, 6:50pm

Also for the background image you can turn off interpolation to see the original voxel values (interpolation button shown here https://www.slicer.org/wiki/Documentation/4.8/SlicerApplication/MainApplicationGUI#Slice_Viewers)

lassoan · January 25, 2018, 7:03pm

In general, if it makes significant difference if a single voxel is inside/outside of a segment then it indicates that the data processing workflow is not optimal for segmentation. Most processing and visualization algorithms assume that the image resolution is much finer than size of details in the structures of interest - if you violate this assumption then you’ll get suboptimal results. Increasing image acquisition resolution is often not feasible, but it is not a problem: you can still resample your input volume (preferably to cubic voxel size) before you segment it to avoid problems associated with insufficient image resolution.

You can use Crop volume module to resample with smaller, cubic voxels (Isotropic spacing enabled, Spacing scale set to < 1, Interpolator set to B-spline) and crop to the region of interest (to make sure the output image will not get too big due to the smaller voxel size).

gcsharp · January 25, 2018, 6:12pm

Probably you are referring to the interpolation in slice view that is enabled by default.

In the volumes module, in the display tab, there is a check button “Interpolate” which you can deactivate.

leomigfer · February 1, 2018, 1:15pm

Thank you for advice!

Leon · August 1, 2019, 11:32am

About this 3D surface smoothing; I know that when you export your 3D surface smoothed segment as a STL, the viewport smoothing is also applied on the final exported STL.
But what method is used for this smoothing? Which algorithm and settings do I have to use to perform the same smoothing on for instance a labelmap?
In other words; can exactly the same procedure be done afterwards and how?

Or is that a well kept secret?

I’m asking this because I’m trying to mimic a smoothing method that’s used by the applications ‘Mimics’ and ‘3D-Matic’ (both products of Materialise). It’s proprietary software, so they won’t let you how they do their thing.

cpinter · August 1, 2019, 2:00pm

Smoothing is not actually applied when exporting. Whatever you have as closed surface representation, that is what is exported. If you disable smoothing when editing, then it won’t be smoothed.

Nothing is a secret in Slicer Flying edges is used for smoothing. See usage here

github.com

Slicer/Slicer/blob/master/Libs/vtkSegmentationCore/vtkBinaryLabelmapToClosedSurfaceConversionRule.cxx#L181






  // Run marching cubes


#if VTK_MAJOR_VERSION >= 9 || (VTK_MAJOR_VERSION >= 8 && VTK_MINOR_VERSION >= 2)
  // Normals computation in vtkDiscreteFlyingEdges3D is faster than computing normals in a subsequent
  // vtkPolyDataNormals filter. However, if smoothing step is applied after vtkDiscreteFlyingEdges3D then
  // computing normals after smoothing provides smoother surfaces.
  bool marchingCubesComputesSurfaceNormals = (computeSurfaceNormals > 0) && (smoothingFactor <= 0);


  vtkSmartPointer<vtkDiscreteFlyingEdges3D> marchingCubes = vtkSmartPointer<vtkDiscreteFlyingEdges3D>::New();
#else
  bool marchingCubesComputesSurfaceNormals = false;
  vtkSmartPointer<vtkDiscreteMarchingCubes> marchingCubes = vtkSmartPointer<vtkDiscreteMarchingCubes>::New();
#endif
  marchingCubes->SetInputData(binaryLabelmapWithIdentityGeometry);
  const int labelmapFillValue = binaryLabelmapWithIdentityGeometry->GetScalarRange()[1]; // max value
  marchingCubes->GenerateValues(1, labelmapFillValue, labelmapFillValue);
  marchingCubes->ComputeGradientsOff();
  marchingCubes->SetComputeNormals(marchingCubesComputesSurfaceNormals);
  marchingCubes->ComputeScalarsOff();

and the method here
https://vtk.org/doc/nightly/html/classvtkDiscreteFlyingEdges3D.html (scroll down for the description)

lassoan · August 1, 2019, 2:49pm

Most of the smoothing is provided vtkWindowedSincPolyDataFilter applied on the flying edges output:

github.com

Slicer/Slicer/blob/master/Libs/vtkSegmentationCore/vtkBinaryLabelmapToClosedSurfaceConversionRule.cxx#L217


  decimator->SplittingOff();
  decimator->PreserveTopologyOn();
  decimator->SetMaximumError(1);
  decimator->SetTargetReduction(decimationFactor);
  decimator->Update();
  processingResult = decimator->GetOutput();
  }


if (smoothingFactor > 0)
  {
  vtkSmartPointer<vtkWindowedSincPolyDataFilter> smoother = vtkSmartPointer<vtkWindowedSincPolyDataFilter>::New();
  smoother->SetInputData(processingResult);
  smoother->SetNumberOfIterations(20); // based on VTK documentation ("Ten or twenty iterations is all the is usually necessary")
  // This formula maps:
  // 0.0  -> 1.0   (almost no smoothing)
  // 0.25 -> 0.1   (average smoothing)
  // 0.5  -> 0.01  (more smoothing)
  // 1.0  -> 0.001 (very strong smoothing)
  double passBand = pow(10.0, -4.0*smoothingFactor);
  smoother->SetPassBand(passBand);
  smoother->BoundarySmoothingOff();

Xiaojie_Guo · August 7, 2023, 6:42am

May I change the smoothing method for the closed surface?

lassoan · August 7, 2023, 8:05am

Yes! This is an underutilized feature in the segmentation infrastructure: you can specify any number of alternative conversion rule(s) that can get from a binary labelmap to a closed surface representation. The conversion path with the smallest cost is used by default, but to can choose alternative path when you click on Update in the representation list in Segmentations module.

What algorithm do you have in mind?

Xiaojie_Guo · August 7, 2023, 8:23am

Is it the method you said? It seems some parameters can be changed, but the method can’t be changed to another smoothing one. Actually, I just want to see the segmentation result without any postprocessing like the example from VTK.

cpinter · August 7, 2023, 2:05pm

You can turn off smoothing very easily in Segment Editor, see Show 3D option in the documentation.

For existing segmentations you just change the smoothing factor to 0 (see second parameter in the red box in your screenshot).

ruili · November 22, 2023, 4:11pm

Hello! Do you know if there is a way to change the default setting so that it always sets the smoothing factor to 0?

lassoan · November 22, 2023, 6:10pm

Smoothing step is part of the reconstruction. It is not some optional postprocessing step that you may or may not want to have. If you don’t apply smoothing then you will get a surface corrupted with aliasing artifacts (staircases), which are not there in the continuous signal. Therefore, you should not disable smoothing by default.

Of course, you can do everything in Slicer. So, if you decide that you always want to have artifacts in the reconstructed surface then you can change the default by adding these lines to your .slicerrc.py file:

# Note: running this code is not recommended, as it introduces artifacts in the reconstructed surface
defaultSegmentationNode = slicer.vtkMRMLSegmentationNode()
defaultSegmentationNode.GetSegmentation().SetConversionParameter("Smoothing factor", "-0.5")  # use negative number to make it easy to enable smoothing
slicer.mrmlScene.AddDefaultNode(defaultSegmentationNode)

rbumm · November 23, 2023, 1:09am

lassoan:

In general, if it makes significant difference if a single voxel is inside/outside of a segment then it indicates that the data processing workflow is not optimal for segmentation. Most processing and visualization algorithms assume that the image resolution is much finer than size of details in the structures of interest - if you violate this assumption then you’ll get suboptimal results. Increasing image acquisition resolution is often not feasible, but it is not a problem: you can still resample your input volume (preferably to cubic voxel size) before you segment it to avoid problems associated with insufficient image resolution.

You can use Crop volume module to resample with smaller, cubic voxels (Isotropic spacing enabled, Spacing scale set to < 1, Interpolator set to B-spline) and crop to the region of interest (to make sure the output image will not get too big due to the smaller voxel size).

This is wise and useful information that should be prominently placed somewhere.

chir.set · November 23, 2023, 11:16am

This is still a confusing topic. Please consider the 2 images below.

In the first one, there is no surface smoothing in 3D. In the second image, surface smoothing is at default 0.5.

We see that the contrasted structure is better filled without surface smoothing in the the 3D view. The slice view outlines the contrast as reference.

Should we consider that surface smoothing should be applied in 2D views to remove what is considered as artifacts? But the contrast pleads against this.

ruili · November 23, 2023, 11:41am

lassoan:

defaultSegmentationNode = slicer.vtkMRMLSegmentationNode()
defaultSegmentationNode.GetSegmentation().SetConversionParameter("Smoothing factor", "-0.5")  # use negative number to make it easy to enable smoothing
slicer.mrmlScene.AddDefaultNode(defaultSegmentationNode)

Yes it is indeed due to scenarios like this one that I did not want to have any smoothing. I tried the code suggested:

defaultSegmentationNode = slicer.vtkMRMLSegmentationNode()
defaultSegmentationNode.GetSegmentation().SetConversionParameter("Smoothing factor", "-0.5")  # use negative number to make it easy to enable smoothing
slicer.mrmlScene.AddDefaultNode(defaultSegmentationNode)

However, it did not work as I hoped. I want to make it so that whenever I load a segmentation and click “Show 3D” the visualisation has a smoothing factor of 0. However, after adding this code to .slicerrc.py, the default smoothing factor is still 0.5. I really want to change this default setting as in my workflow I have to load many segmentation files, and each time I have the change the smoothing factor manually.

chir.set · November 23, 2023, 11:46am

Did you restart Slicer after updating .slicerrc.py?

ruili · November 23, 2023, 11:48am

Yes I did. I also tried running those codes in the python console inside slicer to ensure that they were applied, but neither worked.

Topic		Replies	Views
Using the show 3D smoothing algorithm on exported meshes Support segmentation	2	392	May 2, 2022
What smoothing is applied to segmentations before STL export? Support	3	56	February 19, 2025
Option to disable smoothing of the segment surfaces in Segment Editor Feature requests segmentation	16	2662	October 7, 2021
Surface representation of segmentation is too much smoothed Support	1	520	March 9, 2018
Smoothing the 3D model Support	5	1939	April 7, 2020

Turn off all smoothing in segmentation

Related topics