[vtkusers] High memory cost of vtkDecimatePro for 3D model generation from DICOM series

[David Gobbi]

On Wed, Mar 16, 2016 at 10:35 PM, Liu_tj <tjlp at netease.com> wrote:

> Hi,David,
>
> If using vtkImageThreshold before vtkMarchingCubes is not a good option,
> what other better way do you have?
>

The output of the reader should go directly into vtkMarchingCubes.


> Beside, for the isovalue, I try 2,3,4 and marched->GetNumberOfPoints()
> return 0, only isovalue is 1 and marched->GetNumberOfPoints() return a
> number greater than 0. I have no idea this is relating to the DICOM series
> or other problem.
>

If you remove vtkImageThreshold, and put the output of the reader directly
into vtkMarchingCubes, then you should be able to use an isovalue somewhere
between 100 and 2000 and get a good result.

Also, after vtkMarchingCubes, you can use vtkConnectivityFilter to clean up
the polydata before you decimate it.

 - David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20160316/4ecfa48e/attachment.html>