MantisBT - VTK
View Issue Details
0004946VTK(No Category)public2007-04-26 20:322016-08-12 09:54
David Thompson (old) 
David Thompson (old) 
normalfeaturealways
closedmoved 
 
 
0004946: vtkExodusIIReader doesn't provide model metadata
The new vtkExodusIIReader doesn't yet create model a metadata object containing QA records, etc. from the Exodus file.

This is a feature request to replace the original bug (0004923) that caused crashes.
No tags attached.
related to 0005741closed Kitware Robot VTK Exodus metadata should be available from Python (and other wrapped languages) 
related to 0005742closed Utkarsh Ayachit ParaView Server/manager objects for accessing model metadata 
Issue History
2007-09-18 15:36David Thompson (old)Note Added: 0009099
2007-09-18 15:48David Thompson (old)Relationship addedrelated to 0005741
2007-09-18 15:48David Thompson (old)Relationship addedrelated to 0005742
2011-06-16 13:11Zack GalbreathCategory => (No Category)
2016-08-12 09:54Kitware RobotNote Added: 0036910
2016-08-12 09:54Kitware RobotStatusexpired => closed
2016-08-12 09:54Kitware RobotResolutionopen => moved

Notes
(0009099)
David Thompson (old)   
2007-09-18 15:36   
The vtkModelMetadata classes should most probably be deprecated; the relevant information can be stored using vtkInformation objects. This is cleaner than metadata being stored in a dataset's field data because global variables are now stored there as well and the potential for name collisions/confusion would be high if both global variables and metadata were stored in the field data.

Because the metadata may be extensive, loading it into a mesh should be an option. The option should most probably take the form of both an ivar and a vtkInformation key which could be added to pipeline requests by downstream consumers (such as the Exodus writer). If either the key is present or the ivar is true, the data should be read.
(0036910)
Kitware Robot   
2016-08-12 09:54   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current VTK Issues page linked in the banner at the top of this page.