[vtk-developers] Fwd: Surface

[Will Schroeder]

SetBoundaryVertexDeletion(0) or BoundaryVertexDeletionOff() are equivalent.

If you have any problems contact Bill Lorensen since he just volunteered ;-)

W

On Mon, Feb 21, 2011 at 12:10 PM, Paulo Henrique Junqueira Amorim <
paulojamorim at gmail.com> wrote:

> Hi Will,
>
> In Python is only set decimate.BoundaryVertexDeletionOff() ?
>
> Regards,
> Paulo
>
>
>
> On 21 February 2011 14:03, Will Schroeder <will.schroeder at kitware.com>wrote:
>
>> Mark-
>>
>> Try disabling vertex deletion:
>>
>>   // Description:
>>   // Turn on/off the deletion of vertices on the boundary of a mesh. This
>>   // may limit the maximum reduction that may be achieved.
>>   vtkSetMacro(BoundaryVertexDeletion,int);
>>   vtkGetMacro(BoundaryVertexDeletion,int);
>>   vtkBooleanMacro(BoundaryVertexDeletion,int);
>>
>> If problems remain let me know please.
>>
>> Will
>>
>> On Mon, Feb 21, 2011 at 11:40 AM, Mark Roden <mmroden at gmail.com> wrote:
>>
>>> Hi VTK developers,
>>>
>>> There appears to be some problems running decimation routines of large
>>> volumes in parallel.  This is a bug report forwarded by one of the
>>> gdcm contributors for their large project involving both gdcm and vtk.
>>>
>>> Thanks,
>>> Mark
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: totonixsame at gmail.com <totonixsame at gmail.com>
>>> Date: 21 February 2011 10:21
>>> Subject: Superficie
>>> To: Paulo Henrique Junqueira Amorim <paulojamorim at gmail.com>
>>>
>>>
>>> Hi,
>>>
>>> In InVesalius we generate a vtkPolydata from a medical vtkImageData
>>> using marching cubes. But the vtkImagedata we are working are very
>>> large, like 512x512x1000, in a 32-bit OS it crashes and is a lot slow.
>>> So we thought in parallelize this part of software, then InVesalius
>>> could generate vtkPolydata faster. To do that firstly we split the
>>> vtkImagedata in smaller pieces, to each pieces we do this pipeline:
>>>
>>> vtkMarchingCubes -> vtkTriangleFilter -> vtkDecimatePro
>>> (PreserveTopologyOn and SetTargetReduction(0.3)
>>>
>>> Each piece can run in parallel.
>>>
>>> After all piece are processed we join them, using this pipeline:
>>>
>>> vtkAppendPolyData -> vtkCleanPolyData -> vtkStripper
>>>
>>> Then it shows to the user. But it has a problems: In junctions there
>>> is some marks like showed in [1] and [2]. When I open the STL
>>> generated from that vtkPolydata in Meshlab, for example, in those
>>> junctions there are some holes [3] and [4].
>>>
>>> Do you have some idea why that problem occurs? I have to use some
>>> other filter(s)?
>>>
>>> Thanks!
>>>
>>> [1] - http://i.imgur.com/MLXPw.png
>>> [2] - http://i.imgur.com/DRFHy.png
>>> [3] - http://i.imgur.com/0RB45.png
>>> [4] - http://i.imgur.com/70fIa.png
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.vtk.org/mailman/listinfo/vtk-developers
>>>
>>>
>>
>>
>> --
>> William J. Schroeder, PhD
>> Kitware, Inc.
>> 28 Corporate Drive
>> Clifton Park, NY 12065
>> will.schroeder at kitware.com
>> http://www.kitware.com
>> (518) 881-4902
>>
>
>


-- 
William J. Schroeder, PhD
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
will.schroeder at kitware.com
http://www.kitware.com
(518) 881-4902
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20110221/65850246/attachment.html>