[vtk-developers] vtkExodusIIReader.GetExodusModel() always returns NULL

[Nico Schlömer]

I was actually concerned about reading an Exodus file and throwing
away information. As the documentation says:

"There is a great deal of model information lost when an Exodus II
file is read in to a vtkMultiBlockDataSet."

It is then advised to store the data in an ExodusModel.

What would be very helpful for me is a pointer to example code that
reads and Exodus file, and writes it out to VTK without loss of
information (and/or the other way around).

Cheers,
Nico



On Mon, Dec 6, 2010 at 8:49 PM, David Thompson <dcthomp at sandia.gov> wrote:
>> I suspect that the ExodusModel is no longer supported. ...
>
> Indeed, VTK now has better ways of representing the information it used to
> contain:
> + The QA & info records are now stored in the field data of the output
> dataset.
> + Global node and element IDs are marked using vtkDataSetAttributes' new
> GLOBALIDS attribute.
>
>        David
>
>> On Fri, Dec 3, 2010 at 12:01 PM, Nico Schlömer <nico.schloemer at gmail.com>
>> wrote:
>> Hi all,
>>
>> I've compiled a minimal example file that highlights how
>> vtkExodusIIReader's GetExodusModel() always returns the null pointer;
>> see attachements.
>>
>> I'm not quite sure where the error sits: Is there an option that needs
>> to be specified, is the file not properly formatted, is it a bug in
>> VTK?
>>
>> All hints are very much appreciated!
>>
>> Cheers,
>> Nico
>>
>> _______________________________________________
>> 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
>>
>>
>>
>> <ATT00001..txt>
>
>
>