Difference between revisions of "2008 Winter Project Week:UnstructuredGrids"

From NAMIC Wiki
Jump to: navigation, search
Line 34: Line 34:
 
<h1>Progress</h1>
 
<h1>Progress</h1>
  
##Added MRML Display and Storage Nodes for Meshing Datatypes.  Picture is generated from MRML instead of using actors, as we previously were doing.  
+
#Added MRML Display and Storage Nodes for Meshing Datatypes.  Picture is generated from MRML instead of using actors, as we previously were doing.  
## vtkMRMLUnstructuredGrid subclasses are working stored in the MRML tree.
+
#vtkMRMLUnstructuredGrid subclasses are working stored in the MRML tree.
##Bob's help was  appreciated with Mesh modification algorithms.  It was good understanding that VTK will have a meshing datatype in future revisions.  
+
#Bob's help was  appreciated with Mesh modification algorithms.  It was good understanding that VTK will have a meshing datatype in future revisions.  
  
 
</div>
 
</div>

Revision as of 15:49, 11 January 2008

Home < 2008 Winter Project Week:UnstructuredGrids
FE Module Prototype in Slicer3


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 future Modules' needs. Our current design 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

  1. Added MRML Display and Storage Nodes for Meshing Datatypes. Picture is generated from MRML instead of using actors, as we previously were doing.
  2. vtkMRMLUnstructuredGrid subclasses are working stored in the MRML tree.
  3. Bob's help was appreciated with Mesh modification algorithms. It was good understanding that VTK will have a meshing datatype in future revisions.