We have to check if the property is applied or the reason for no difference is that the rate is to small.

I looked into this and can verify that there is no visible effect when changing the decimation rate. The property "Decimation rate" is correctly used inside ShowSegmentationAsSurface::ConvertBinaryImageToSurface as reductionRate. It is then used as an argument for ImageToSurfaceFilter::SetTargetReduction. The brief description of this parameter is:

Set desired TargetReduction of triangles in the range from 0.0 to 1.0.
The destroyed triangles are in relation with the size of data. For example 0.9
will reduce the data set to 10%.

That tells me that we cannot see any change using the surface representation but need to change the representation of the polygon-nodes to "Wireframe". Here the reduction is clearly visible.

I will adapt the checklist accordingly to clearly state what to do and how to observe the result.

We discussed this and we decided to remove the options from the preferences completely. That means, that

• the user cannot change the smoothing hint / value
• the user cannot change the decimation rate
• the checklists don't need to ask for changing these values
• the smoothing will use the default values (set inside QmitkCreatePolygonModelAction::Run)
  • "smoothing hint" = true (will always use image spacing as hint)
  • "smoothing value" = 1.0
  • "decimation rate" = 0.5
  • "closing ratio" was not used at all
  • note that different default values are given in ShowSegmentationAsSurface::Initialize (and other functions of this class), but are overwritten / reset by the polygon action.

I removed the „Smoothed surface creation“ Preference section from the Segmentation - Options checklist.