MantisBT - VTK
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0008835VTK(No Category)public2009-04-02 13:452016-08-12 09:55
ReporterCorey McBride 
Assigned ToKitware Robot 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Project
Type
Summary0008835: Exodus Writer doesn't respect the block ids from vtkModelMetadata explicitly supplied by user.
DescriptionThe Exodus writer internally increments block ids to avoid a block id of 0. This change was introduced in revision 1.38. By internally incrementing the block ids the block ids no longer match those given in the vtkModelMetadata explicitly supplied by a user.

It is very important that the information in the vtkModelMetadata supplied by the user be respected. Changing block ids to avoid a block id of 0 should probably be done outside of the writer.
Steps To Reproduce
Additional InformationAn example of the change made in revision 1.38 can be found in the method
     int vtkExodusIIWriter::ConstructBlockInfoMap ()
search for the line
     "// shift by 1 in case there's a 0"

 
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-04-02 13:45Corey McBrideNew Issue
2009-04-02 14:54Corey McBrideNote Added: 0015895
2011-06-16 13:11Zack GalbreathCategory => (No Category)
2016-08-12 09:55Kitware RobotNote Added: 0037069
2016-08-12 09:55Kitware RobotStatusexpired => closed
2016-08-12 09:55Kitware RobotResolutionopen => moved
2016-08-12 09:55Kitware RobotAssigned To => Kitware Robot

Notes
(0015895)
Corey McBride   
2009-04-02 14:54   
It appears that the problem goes beyond block ids. Side sets supplied in the vtkModelMetadata aren't respected either. This problem may have been introduced with when the writer was changed to support multi-block data sets.
(0037069)
Kitware Robot   
2016-08-12 09:55   
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.