Difference between revisions of "2008 Winter Project Week:UnstructuredGrids"
Line 25: | Line 25: | ||
[http://www.na-mic.org/Wiki/index.php/Projects/Slicer3/2007_Project_Week_Support_for_Unstructured_Grids 2007 Project Week - Support for Unstructured Grids]<br> | [http://www.na-mic.org/Wiki/index.php/Projects/Slicer3/2007_Project_Week_Support_for_Unstructured_Grids 2007 Project Week - Support for Unstructured Grids]<br> | ||
+ | |||
+ | The main discussion points in this project are how the rendering of unstructured grids should be handled. Unstructured grids could be added for different purposes and rendered in different ways according to a future Module's needs. Our current approach specifies each module should create its own subclasses of vtkMRMLUnstructuredGrid nodes and their corresponding display nodes, so rendering attributes could be accessed through the corresponding MRML display node. | ||
</div> | </div> |
Revision as of 23:10, 21 December 2007
Home < 2008 Winter Project Week:UnstructuredGrids![]() Return to 2008_Winter_Project_Week |
Key Investigators
- Curt, Alex, Steve, Will, Vince, Bob O'Bara
Objective
The Slicer3 infrastructure is being extended to support Unstructured Grid datatypes for meshing processes, and the functions from the Univ. of Iowa workflow are being incorporated incrementally during the course of this project.
Approach, Plan
Unstructured grid node types are now supported in MRML. The external collaboration for Finite Element meshing is creating subclasses of these MRML nodes to store bounding box and FE mesh data. This work is a continuation of this project:
2007 Project Week - Support for Unstructured Grids
The main discussion points in this project are how the rendering of unstructured grids should be handled. Unstructured grids could be added for different purposes and rendered in different ways according to a future Module's needs. Our current approach specifies each module should create its own subclasses of vtkMRMLUnstructuredGrid nodes and their corresponding display nodes, so rendering attributes could be accessed through the corresponding MRML display node.
Progress