[vtk-developers] vtkHyperTreeGridGeometry and vtkDataSetSurfaceFilter

Philippe Pebay philippe.pebay at kitware.com
Thu May 10 10:13:50 EDT 2012


Hello all:

I have a question regarding vtkDataSetSurfaceFilter, the accelerated
version of the Geometry filter.

My question is the following: I would like to make
vtkDataSetSurfaceFilter able to automatically fork off to the
vtkHyperTreeGridGeometry filter when the data object is found to have
type VTK_HYPER_TREE_GRID.
This seems like a simple addition to make, by simply instantiating the
hyper tree grid geometry filter when the case is met in the switch
statement of vtkDataSetSurfaceFilter::RequestData().

However, this would introduce a dependency of Filters/Geometry on
Filters/HyperTree because this is where the hyper tree grid geometry
filter currently is, which is certainly a bad thing.

So, we can think of 2 possible ways to mitigate that:
1. Move vtkHyperTreeGridGeometry to Filters/Geometry. Whch would
defeat the purpose of the Filters/HyperTree module, which is there
precisely to hold hyper tree grid algorithms, so one has the option to
not build support for tree-based AMR things.
2. Another route is to create a new module Filters/SurfaceExtractiion
whose purpose would be to contain only surface extraction filters
(including the HyperTreeGrid one).
I am not sure that either of these options is really great, for the
sake of modularity, it would be nice to be able to turn off all hyper
tree support.

Any advice?

Thank you
Philippe
-- 
Philippe Pébay, PhD
Director of Visualization and High Performance Computing /
Directeur de la Visualisation et du Calcul Haute Performance
Kitware SAS
26 rue Louis Guérin, 69100 Villeurbanne, France
+33 (0) 6.83.61.55.70 / 4.37.45.04.15
http://www.kitware.fr



More information about the vtk-developers mailing list