[vtkusers] vtkExtractGeometry problems on large cell sets

Laurence Griffiths lgriffiths.aero at gmail.com
Wed May 15 07:26:23 EDT 2013


Thanks for the inputs, I have yet to run the code through valgrind, but I
will try this.

Using vtkExtractUnstructuredGrid works without errors. Perhaps I was miss
using vtkExtractGeometry, as the input dataset is an unstructured grid.


On Fri, May 10, 2013 at 1:26 PM, Laurence Griffiths <
lgriffiths.aero at gmail.com> wrote:

> Hi All,
> I'm using vtkExtractGeometry on a large ensight dataset
> (vtkUnstructuredGrid - 60 million cells, approximately).
>
> ExtractData=vtk.vtkExtractGeometry()
> ExtractData.SetInput(MultiBlock.GetOutput().GetBlock(0))
> ExtractData.SetImplicitFunction(ClipBox)
> ExtractData.ExtractInsideOn()
> ExtractData.ExtractBoundaryCellsOn()
> ExtractData.Update()
>
> ClipBox is an instance of vtk.vtkBox()
>
> On small datasets it works fine, however on large datasets I seem to get
> Bands of cells missing internally in the dataset. (seen by by saving the
> volume, opening in paraview, and taking a slice).
>
> If i take a slice of the raw dataset (i.e. the vtkUnstructuredGrid) before
> passing to vtkExtractGeometry - I have no internal cells missing
>
> If i take a slice in vtk, I get a repeatable Bad Alloc error.
>
> Anyone else had simillar problems to this? Or Know a work around?
>
> Cheers,
> Laurence.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20130515/c29a83d5/attachment.htm>


More information about the vtkusers mailing list