[vtkusers] vtk.vtkExodusIIReader: information in GetOutput()?

[Nico Schlömer]

> Reading the source for its RequestData()
> method illustrates how to iterate over all the edges yourself if you don't
> want to use the filter.

The filter? I'm not familiar with this concept (though it seems to
appear within VTK a lot).
If that something that help in iterating over the edges, I'd be more
than happy to use it of course! Are there examples?

--Nico



On Tue, Dec 7, 2010 at 2:43 AM, David Thompson <dcthomp at sandia.gov> wrote:
>> ... I tried the snippet your provided and got
>>
>> ============ *snip* ============
>> Element Blocks
>>  block_5
>> ...
>> ============ *snap* ============
>>
>> I guess that tells me I got one element block, and that'd be it. I
>> guess Exodus is minimalistic in the sense that it contains exactly
>> what was put into the file once, and even though there are egdes in
>> the mesh naturally, they are not stored in the file.
>
> True.
>
>> Do you happen to know if it's possible to iterate over the edges
>> and/or faces of a vtkUnstructuredGrid?
>
> You can use vtkExtractEdges to get a vtkPolyData that contains all the edges
> of the input vtkUnstructuredGrid. Reading the source for its RequestData()
> method illustrates how to iterate over all the edges yourself if you don't
> want to use the filter.
>
>        David
>
>
>