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

[Liu_tj]

Hi, David,

If I don't use vtkImageThreshol, how to generate 3D model from the points whose grayscale is in some specific range? This range can be changed by the user.

Thanks
Liu Peng


在2016-03-17，"David Gobbi" <david.gobbi at gmail.com> 写道： -----原始邮件-----
发件人:"David Gobbi" <david.gobbi at gmail.com>
发送时间:2016年03月17日 星期四
收件人:"Liu_tj" <tjlp at netease.com>
抄送:"vtkusers" <vtkusers at vtk.org>
主题:Re: Re: [vtkusers] High memory cost of vtkDecimatePro for 3D model generation from DICOM series


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/20160317/efc1f0de/attachment.html>