VTK/Composite data changes: Difference between revisions
From KitwarePublic
< VTK
Jump to navigationJump to search
Yuanxin.liu (talk | contribs) No edit summary |
Yuanxin.liu (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
Primarily motivated by better support of AMR data structures, | Primarily motivated by better support of AMR data structures, various | ||
APIs related to vtkCompositeDataSet have been changed. | |||
=== Refactoring === | |||
vtkCompositeDataSet has been primarily used a container of data sets, | |||
even though it really represents a tree of data sets. So we first | |||
renamed the class vtkDataObjectTree, then exctracted the methods that | |||
support simple container functionalities and put them into a fully | |||
abstract class vtkCompositeDataSet. The refactored hierarchy is shown | |||
below. It should be noted here that vtkUniformGridAMR now provides a | |||
new implementation. The details can be found in a later section. | |||
[[Image:new_composite.png]] | |||
=== New Keys For Demand Driven Execution ==== | |||
=== Better AMR Data Structures === | |||
Revision as of 15:59, 21 September 2012
Primarily motivated by better support of AMR data structures, various APIs related to vtkCompositeDataSet have been changed.
Refactoring
vtkCompositeDataSet has been primarily used a container of data sets, even though it really represents a tree of data sets. So we first renamed the class vtkDataObjectTree, then exctracted the methods that support simple container functionalities and put them into a fully abstract class vtkCompositeDataSet. The refactored hierarchy is shown below. It should be noted here that vtkUniformGridAMR now provides a new implementation. The details can be found in a later section.
