Difference between revisions of "MeshingSummer2009"

From NAMIC Wiki
Jump to: navigation, search
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 
<gallery>
 
<gallery>
Image:PW2009-v3.png|[[2009_Summer_Project_Week|Project Week Main Page]]
+
Image:PW2009-v3.png|[[2009_Summer_Project_Week#Projects|Projects List]]
 
Image:Femesh-in-trunk-120808.png|First Release of IA-FEMesh module
 
Image:Femesh-in-trunk-120808.png|First Release of IA-FEMesh module
Image:Slicer-meshing-display-nodes-053009.png|Screenshot of IA-FEMesh release 2 alpha
+
Image:MeshingSummerProjectWeek2009.png| IA-FEMesh release 2 alpha with MRML transform
 
</gallery>
 
</gallery>
  
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 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.  
+
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 have some minor remaining rendering issues, but Meshing module objects are now stored in MRML successfully.  Over the next few months, we will complete the integration and testing of this approach and  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.
 +
 +
This recent work will remain in the Slicer Meshing-V-2-1 branch for now.  The IA_FEMesh module  V1, which matches the tutorial, is currently in the Slicer trunk and Slicer V3.4.
  
 
</div>
 
</div>
Line 47: Line 50:
  
 
==References==
 
==References==
*Grosland Nicole M; Shivanna Kiran H; Magnotta Vincent A; Kallemeyn Nicole A; DeVries Nicole A; Tadepalli Srinivas C; Lisle Curtis IA-FEMesh: an open-source, interactive, multiblock approach to anatomic finite element model development. Computer methods and programs in biomedicine 2009;94(1):96-107.
+
*Grosland Nicole M; Shivanna Kiran H; Magnotta Vincent A; Kallemeyn Nicole A; DeVries Nicole A; Tadepalli Srinivas C; Lisle Curtis R; IA-FEMesh: an open-source, interactive, multiblock approach to anatomic finite element model development. Computer methods and programs in biomedicine 2009;94(1):96-107.
 
*Shivanna KH, Grosland NM, Russell ME, Pedersen DR, Diarthrodial  Joint Contact Models:  A finite element analysis of the human hip, Engineering with Computers (accepted).
 
*Shivanna KH, Grosland NM, Russell ME, Pedersen DR, Diarthrodial  Joint Contact Models:  A finite element analysis of the human hip, Engineering with Computers (accepted).
  
  
 
</div>
 
</div>

Latest revision as of 14:35, 26 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 have some minor remaining rendering issues, but Meshing module objects are now stored in MRML successfully. Over the next few months, we will complete the integration and testing of this approach and 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.

This recent work will remain in the Slicer Meshing-V-2-1 branch for now. The IA_FEMesh module V1, which matches the tutorial, is currently in the Slicer trunk and Slicer V3.4.

References

  • Grosland Nicole M; Shivanna Kiran H; Magnotta Vincent A; Kallemeyn Nicole A; DeVries Nicole A; Tadepalli Srinivas C; Lisle Curtis R; IA-FEMesh: an open-source, interactive, multiblock approach to anatomic finite element model development. Computer methods and programs in biomedicine 2009;94(1):96-107.
  • Shivanna KH, Grosland NM, Russell ME, Pedersen DR, Diarthrodial Joint Contact Models: A finite element analysis of the human hip, Engineering with Computers (accepted).