Difference between revisions of "MeshingSummer2009"

From NAMIC Wiki
Jump to: navigation, search
Line 31: Line 31:
 
Standalone mesh creation tools exist in the standalone application IA-FEMesh found  [http://www.ccad.uiowa.edu/mimx/IA-FEMesh  by clicking here.]
 
Standalone mesh creation tools exist in the standalone application IA-FEMesh found  [http://www.ccad.uiowa.edu/mimx/IA-FEMesh  by clicking here.]
  
The first integration of the IA-FEMesh module was released at the NA-MIC All Hands Meeting in January 2009. The module's first release functions in 3D Slicer for creating meshes interactively, but doesn't allow MRML saves & restores.   During the project week, we will be testing the second iteration of integration with 3D Slicer.  The second implementation uses MRML display nodes to display the meshes and supports interactive exploration and edting with VTK 3D widgets.  
+
The first integration of the IA-FEMesh module was released at the NA-MIC All Hands Meeting in January 2009. The module's first release functions in 3D Slicer for creating meshes interactively, but doesn't allow MRML saves & restores.   The second implementation will use MRML display nodes to display the meshes and will support interactive exploration and editing using VTK 3D widgets.  
  
 
</div>
 
</div>
Line 38: Line 38:
  
 
<h3>Progress</h3>
 
<h3>Progress</h3>
The rendering and data storage methods have been modified to conform to Slicer's MRML architecture for separate model and display nodes.  The three major classes of objects managed by IA-FEMesh (surfaces, building blocks, and meshes) are currently rendering in slicer using custom MRMLDisplayNode subclasses.  We will be completing and testing the interaction with the objects and their MRML representations during the project week.  We also hope to propagate changes back to the standalone code version of IA-FEMesh so future development of the standalone and integrated versions can continue from a single code base.  
+
The rendering and data storage methods have been modified to conform to Slicer's MRML architecture for separate model and display nodes.  The three major classes of objects managed by IA-FEMesh (surfaces, building blocks, and meshes) are currently rendering in slicer using custom MRMLDisplayNode subclasses.  We hope to complete and test the interaction with the objects and their MRML representations during the project week.  We also look to propagate changes back to the standalone code version of IA-FEMesh so future development of the standalone and integrated versions can continue from a single code base.  
  
  

Revision as of 13:12, 2 June 2009

Home < MeshingSummer2009


Key Investigators

  • University of Iowa: Nicole Grosland, Vince Magnotta, Kiran Shivanna
  • Isomics: Steve Pieper, Curtis Lisle

Objective

We are integrating finite element mesh creation tools developed at the University of Iowa into 3D Slicer. The result will be that 3D Slicer models can be further processed into meshes for analysis using external finite element programs, such as ABAQUS.




Approach, Plan

Standalone mesh creation tools exist in the standalone application IA-FEMesh found by clicking here.

The first integration of the IA-FEMesh module was released at the NA-MIC All Hands Meeting in January 2009. The module's first release functions in 3D Slicer for creating meshes interactively, but doesn't allow MRML saves & restores. The second implementation will use MRML display nodes to display the meshes and will support interactive exploration and editing using VTK 3D widgets.

Progress

The rendering and data storage methods have been modified to conform to Slicer's MRML architecture for separate model and display nodes. The three major classes of objects managed by IA-FEMesh (surfaces, building blocks, and meshes) are currently rendering in slicer using custom MRMLDisplayNode subclasses. We hope to complete and test the interaction with the objects and their MRML representations during the project week. We also look to propagate changes back to the standalone code version of IA-FEMesh so future development of the standalone and integrated versions can continue from a single code base.


References