MeshingSummer2009 - Revision history

Clisle: /* Key Investigators */

2009-06-26T14:35:11Z

Key Investigators

2009-06-26T14:24:01Z

Key Investigators

2009-06-26T13:39:06Z

2009-06-26T13:38:16Z

2009-06-26T13:28:23Z

Key Investigators

2009-06-22T02:16:00Z

2009-06-02T14:22:35Z

2009-06-02T14:20:11Z

2009-06-02T14:18:51Z

2009-06-02T14:18:29Z

@@ Line 42: / Line 42: @@
 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 a separate 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.
+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>

← Older revision		Revision as of 14:24, 26 June 2009
Line 42:		Line 42:
	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.		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 a separate 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 3: / Line 3: @@
 Image:PW2009-v3.png|[[2009_Summer_Project_Week#Projects|Projects List]]
 Image:Femesh-in-trunk-120808.png|First Release of IA-FEMesh module
-Image:MeshingSummerProjectWeek2009.png|Screenshot of IA-FEMesh release 2 alpha
+Image:MeshingSummerProjectWeek2009.png| IA-FEMesh release 2 alpha with MRML transform
 </gallery>

@@ Line 3: / Line 3: @@
 Image:PW2009-v3.png|[[2009_Summer_Project_Week#Projects|Projects List]]
 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|Screenshot of IA-FEMesh release 2 alpha
 </gallery>

← Older revision		Revision as of 13:28, 26 June 2009
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.

@@ Line 1: / Line 1: @@
 __NOTOC__
 <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:Slicer-meshing-display-nodes-053009.png|Screenshot of IA-FEMesh release 2 alpha

@@ Line 47: / Line 47: @@
 ==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).
 </div>