<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.na-mic.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Lantiga</id>
	<title>NAMIC Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.na-mic.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Lantiga"/>
	<link rel="alternate" type="text/html" href="https://www.na-mic.org/wiki/Special:Contributions/Lantiga"/>
	<updated>2026-04-19T14:45:06Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.33.0</generator>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2011_Winter_Project_Week:StenosisDetector&amp;diff=62686</id>
		<title>2011 Winter Project Week:StenosisDetector</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2011_Winter_Project_Week:StenosisDetector&amp;diff=62686"/>
		<updated>2010-12-27T11:36:51Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Key Investigators */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
Image:PW-SLC2011.png|[[2011_Winter_Project_Week#Projects|Projects List]]&lt;br /&gt;
Image:step1.png|StensosisDetector Step1&lt;br /&gt;
Image:step2.png|StensosisDetector Step2&lt;br /&gt;
Image:step3.png|StensosisDetector Step3&lt;br /&gt;
Image:step4.png|StensosisDetector Step4&lt;br /&gt;
Image:step5.png|StensosisDetector Step5&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Key Investigators==&lt;br /&gt;
* University of Heidelberg, Germany: Suares Tamekue&lt;br /&gt;
* UPenn: Daniel Haehn&lt;br /&gt;
* [http://www.orobix.com Orobix], Italy: Luca Antiga&lt;br /&gt;
* SPL: Ron Kikinis&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h3&amp;gt;Objective&amp;lt;/h3&amp;gt;&lt;br /&gt;
We are developing a stenosis detector based on VMTK in Slicer 4. The goal is to be able to visualize stenosis after a vessel segmentation using a wizard-based interface.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h3&amp;gt;Approach, Plan&amp;lt;/h3&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Our approach for developing the stenosis detector is: first vessel enhancement, level-set segmentation, network extraction and then quantification and visualization of stenosis.&lt;br /&gt;
&lt;br /&gt;
The tool will be evaluated on datasets.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h3&amp;gt;Progress&amp;lt;/h3&amp;gt;&lt;br /&gt;
A prototyp of the graphical user interface has been designed and implemented.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 97%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Delivery Mechanism==&lt;br /&gt;
&lt;br /&gt;
This work will be delivered to the NA-MIC Kit as a (please select the appropriate options by noting YES against them below)&lt;br /&gt;
&lt;br /&gt;
#ITK Module&lt;br /&gt;
#Slicer Module&lt;br /&gt;
##Built-in&lt;br /&gt;
##Extension -- commandline&lt;br /&gt;
##Extension -- loadable [X]&lt;br /&gt;
#Other (Please specify)&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
* Antiga L, Piccinelli M, Botti L, Ene-Iordache B, Remuzzi A and Steinman DA. An image-based modeling framework for patient-specific computational hemodynamics. Medical and Biological Engineering and Computing, 46: 1097-1112, Nov 2008.&lt;br /&gt;
* D. Hähn. Integration of the vascular modeling toolkit in 3d slicer. SPL, 04 2009. Available online at http://www.spl.harvard.edu/publications/item/view/1728.&lt;br /&gt;
* D. Hähn. Centerline Extraction of Coronary Arteries in 3D Slicer using VMTK based Tools. Master's Thesis. Department of Medical Informatics, University of Heidelberg, Germany. Feb 2010.&lt;br /&gt;
* Piccinelli M, Veneziani A, Steinman DA, Remuzzi A, Antiga L (2009) A framework for geometric analysis of vascular structures: applications to cerebral aneurysms. IEEE Trans Med Imaging. In press.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2011_Winter_Project_Week:The_Vascular_Modeling_Toolkit_in_3D_Slicer&amp;diff=62685</id>
		<title>2011 Winter Project Week:The Vascular Modeling Toolkit in 3D Slicer</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2011_Winter_Project_Week:The_Vascular_Modeling_Toolkit_in_3D_Slicer&amp;diff=62685"/>
		<updated>2010-12-27T11:36:16Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Key Investigators */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
Image:PW-SLC2011.png|[[2011_Winter_Project_Week#Projects|Projects List]]&lt;br /&gt;
Image:Slicervmtk logo.png|VMTK in 3D Slicer&lt;br /&gt;
Image:Vesselenhancement.png|Enhancing vasculature structures&lt;br /&gt;
Image:Easylevelsetsegmentation.png|Level-Set segmentation&lt;br /&gt;
Image:Centerlines.png|Computation of Centerlines&lt;br /&gt;
Image:Networkextraction.png|Network extraction of vessel trees&lt;br /&gt;
Image:Branchsplitting.png|Branchsplitting&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Key Investigators==&lt;br /&gt;
* UPenn: Daniel Haehn, Kilian Pohl&lt;br /&gt;
* Rutgers: M. Gokhan Uzunbas&lt;br /&gt;
* [http://www.orobix.com Orobix], Italy: Luca Antiga&lt;br /&gt;
* SPL: Steve Pieper, Ron Kikinis&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h3&amp;gt;Objective&amp;lt;/h3&amp;gt;&lt;br /&gt;
The Vascular Modeling Toolkit ([http://www.vmtk.org VMTK]) is a collection of libraries and tools for 3D reconstruction, geometric analysis, mesh generation and surface data analysis for image-based modeling of blood vessels. &lt;br /&gt;
&lt;br /&gt;
Several 3D Slicer extensions already exist and provide VMTK functionality in Slicer3. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h3&amp;gt;Approach, Plan&amp;lt;/h3&amp;gt;&lt;br /&gt;
We want to investigate how to include the VMTK in 3D Slicer functionality in the upcoming Slicer4 application. This should include several enhancements to the existing user interfaces.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h3&amp;gt;Progress&amp;lt;/h3&amp;gt;&lt;br /&gt;
..&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 97%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Delivery Mechanism==&lt;br /&gt;
&lt;br /&gt;
This work will be delivered to the NA-MIC Kit as a (please select the appropriate options by noting YES against them below)&lt;br /&gt;
&lt;br /&gt;
#ITK Module&lt;br /&gt;
#Slicer Module&lt;br /&gt;
##Built-in&lt;br /&gt;
##Extension -- commandline&lt;br /&gt;
##Extension -- loadable [X]&lt;br /&gt;
#Other (Please specify)&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
* Antiga L, Piccinelli M, Botti L, Ene-Iordache B, Remuzzi A and Steinman DA. An image-based modeling framework for patient-specific computational hemodynamics. Medical and Biological Engineering and Computing, 46: 1097-1112, Nov 2008.&lt;br /&gt;
* D. Hähn. Integration of the vascular modeling toolkit in 3d slicer. SPL, 04 2009. Available online at http://www.spl.harvard.edu/publications/item/view/1728.&lt;br /&gt;
* D. Hähn. Centerline Extraction of Coronary Arteries in 3D Slicer using VMTK based Tools. Master's Thesis. Department of Medical Informatics, University of Heidelberg, Germany. Feb 2010.&lt;br /&gt;
* Piccinelli M, Veneziani A, Steinman DA, Remuzzi A, Antiga L (2009) A framework for geometric analysis of vascular structures: applications to cerebral aneurysms. IEEE Trans Med Imaging. In press.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=34772</id>
		<title>2009 Winter Project Week Python</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=34772"/>
		<updated>2009-01-09T15:59:36Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Key Investigators */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:Python-logo.png |thumb|320px|[http://www.python.org]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Luca Antiga (Mario Negri Institute)&lt;br /&gt;
* Steve Piper (Isomics)&lt;br /&gt;
* Demian Wasserman (INRIA)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
To finalize the implementation of the Slicer Python interface and solve packaging problems linked to Scipy.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Slicer Python interface now works well for both non-interactive and interactive modules. &lt;br /&gt;
&lt;br /&gt;
Interface has to be stabilized, and it is still lacking setting custom observers to vtkObject.&lt;br /&gt;
&lt;br /&gt;
Documentation has to be improved.&lt;br /&gt;
&lt;br /&gt;
Packaging Scipy is currently a problem.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Python interface is being adopted by several groups, both for command-line and interactive modules. The Numpy interface works well.&lt;br /&gt;
&lt;br /&gt;
A AddObserver method has been added to the wrapped vtkObject that accepts callbacks written in Python.&lt;br /&gt;
&lt;br /&gt;
The Python breakout session has illustrated the ways Python can be used in Slicer and the ways users can implement their own modules. Slides will be on the wiki in a few days.&lt;br /&gt;
&lt;br /&gt;
A --evalpython option has been added to the Slicer3 executable in order to run Python code in Slicer without starting the GUI (for batch processing)&lt;br /&gt;
&lt;br /&gt;
Packaging problems have been&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=AHM_2009&amp;diff=34626</id>
		<title>AHM 2009</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=AHM_2009&amp;diff=34626"/>
		<updated>2009-01-08T16:34:37Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Agenda */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
== Introduction ==&lt;br /&gt;
{| border=&amp;quot;00&amp;quot; cellpadding=&amp;quot;8&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;2&amp;quot;| '''This is the home page for the 2009 NA-MIC all hands meeting (AHM).''' NA-MIC participants meet for a AHM once a year. The purpose of the AHM is to coordinate, discuss plans and report to NIH officers and the external advisory board (EAB). The external advisory board meets with the NA-MIC leadership immediately after the AHM. In parallel, NA-MIC is organizing a project week. These events, with the exception of the EAB meeting, are open to collaborators and potential collaborators.&lt;br /&gt;
&lt;br /&gt;
For more information about the project weeks in general, click [[Engineering:Programming_Events|'''here''']]. &lt;br /&gt;
&lt;br /&gt;
For information about the January 2009 project week, see below or click [[2009_Winter_Project_Week|'''here''']].&lt;br /&gt;
&lt;br /&gt;
For information about Utah as a travel destination click [http://www.utah.com '''here'''].&lt;br /&gt;
| style=&amp;quot;background: #ebeced&amp;quot;  align=&amp;quot;center&amp;quot;| [[Image:SLC.jpg|center|350px|View of the City]]&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;background: #ebeced&amp;quot;|The 2009 AHM, EAB and Project Week will be held &amp;lt;br&amp;gt;'''January 5-9 2009''', in '''Salt Lake City''', Utah.  &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Agenda==&lt;br /&gt;
&lt;br /&gt;
'''wireless connection: capital-ballroom, namic-ballroomB, namic-amethyst'''&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot;&lt;br /&gt;
|- style=&amp;quot;background:#ebeced; color:black&amp;quot; align=&amp;quot;left&amp;quot; &lt;br /&gt;
| style=&amp;quot;width:4%&amp;quot; | '''Time'''&lt;br /&gt;
| style=&amp;quot;width:12%&amp;quot; | '''Monday, January 5''' &lt;br /&gt;
| style=&amp;quot;width:12%&amp;quot; | '''Tuesday, January 6'''&lt;br /&gt;
| style=&amp;quot;width:12%&amp;quot; | '''Wednesday, January 7''' &lt;br /&gt;
| style=&amp;quot;width:32%&amp;quot; | '''Thursday, January 8 '''&lt;br /&gt;
| style=&amp;quot;width:12%&amp;quot; | '''Friday, January 9''' &lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;background:#ffffdd; color:black&amp;quot;|&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:#522200&amp;quot;| '''[[2009_Winter_Project_Week|Project Activities]] ''' in [http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/ Capitol B-C]&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:#522200&amp;quot;| '''[[2009_Winter_Project_Week|Project Activities]] ''' in [http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/ Capitol B-C]&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:#522200&amp;quot;| '''[[2009_Winter_Project_Week|Project Activities]] ''' in [http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/ Capitol B-C]&lt;br /&gt;
| style=&amp;quot;background:#fff6a6; color:#522200&amp;quot;| '''AHM''' in [http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/Capitol A-B], [[2009_EAB|'''EAB''']] in [http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/ Olympus B]&lt;br /&gt;
'''[[2009_Winter_Project_Week|Project Activities]] ''' in [http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/ Olympus A]&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:#522200&amp;quot;|'''[[2009_Winter_Project_Week|Project Activities]] ''' in [http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/ Capitol B-C]&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;background:#ffffdd; color:black&amp;quot;|'''7:30-8:00''' &lt;br /&gt;
| style=&amp;quot;background:#ebeced; color:black&amp;quot;|  &lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;| Breakfast&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;| Breakfast&lt;br /&gt;
| style=&amp;quot;background:#fff6a6; color:black&amp;quot;| Breakfast&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;| Breakfast&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;background:#ffffdd; color:black&amp;quot;|'''8:00-10:00''' &lt;br /&gt;
| style=&amp;quot;background:#ebeced; color:black&amp;quot;|'''9:30''' Core 1 and 2 PI closed session in [http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/ Capitol A]&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;|Project Work &amp;lt;br&amp;gt; '''8:00-9:00''' [[AHM2009:NITRC and Slicer|How to use NITRC and slicer]] (Steve, Terry)&amp;lt;br&amp;gt; &lt;br /&gt;
'''9:00-10:00''' [[AHM2009:Batchmake and XNAT|Using Batchmake and XNAT to process large studies]] (Stephen Aylward and Dan Marcus) in [http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/     Amethyst 1]&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;|Project Work &amp;lt;br&amp;gt;'''8:00-9:00''' [[AHM2009:Tutorial Review and Judging|Tutorial Review and Judging]] [http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/ Amethyst 1]&lt;br /&gt;
'''9:00-10:00''' Particle Correspondence Breakout (Capital Ballroom A) &lt;br /&gt;
| style=&amp;quot;background:#fff6a6; color:black&amp;quot;|'''8:00''' [[AHM 2009 Introduction|Introduction]], [http://www.spl.harvard.edu/~kikinis Ron Kikinis] &amp;lt;br&amp;gt;&lt;br /&gt;
'''8:05''' [[AHM 2009 NA-MIC Highlights|NA-MIC Highlights]] ([http://www.cs.utah.edu/~whitaker/ Ross Whitaker])&amp;lt;br&amp;gt;&lt;br /&gt;
'''Roadmap Projects'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''8:35''': [[AHM2009:JHU|JHU/Queens]] ([http://research.cs.queensu.ca/~gabor/ Gabor Fichtinger])&amp;lt;br&amp;gt;&lt;br /&gt;
'''8:55''': [[AHM2009:UNC|UNC]] ([http://www.med.unc.edu/psych/directories/faculty/hazlett/ Heather Cody])&amp;lt;br&amp;gt;&lt;br /&gt;
'''9:15''': [[AHM2009:PNL|PNL]] ([http://pnl.bwh.harvard.edu/people/profiles/kubicki.html Marek Kubicki])&amp;lt;br&amp;gt;&lt;br /&gt;
'''9.35''': [[AHM2009:Mind|Mind Institute]] ([http://www.mrn.org/principle-investigators/h.-jeremy-bockholt.html Jeremy Bockolt])&amp;lt;br&amp;gt;&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;|Project Work &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;background:#ffffdd; color:black&amp;quot;|'''10:00-10:30''' &lt;br /&gt;
| style=&amp;quot;background:#ebeced; color:black&amp;quot;| Core 1 and 2 PI closed session&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;| '''10:30-11:30'''[[AHM2009:GUI Testing|Automated GUI Testing for Slicer]] (Sebastien) [http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/ Amethyst 1]&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;| Coffee&lt;br /&gt;
| style=&amp;quot;background:#fff6a6; color:black&amp;quot;| Coffee&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;| Coffee&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;background:#ffffdd; color:black&amp;quot;|'''10:30-12:00''' &lt;br /&gt;
| style=&amp;quot;background:#ebeced; color:black&amp;quot;| Core 1 and 2 PI closed session&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;|Project Work &lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;|Project Work &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;background:#fff6a6; color:black&amp;quot;|&lt;br /&gt;
'''Collaborations'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''10:30''': [[media:NA-MIC_Mesh_Collaboration_2009.ppt|Iowa collaboration]] ([http://www.engineering.uiowa.edu/faculty-staff/profile-directory/bme/grosland_n.php Nicole Grosland])&amp;lt;br&amp;gt;&lt;br /&gt;
'''10:45''': [[AHM2009:ExternalWFU|Wake Forest collaboration]] ([http://www.ece.vt.edu/faculty/wyatt.html Chris Wyatt])&amp;lt;br&amp;gt;&lt;br /&gt;
'''11:00''': [[media:NA-MIC_Cleary_RF_Ablation_Georgetown_Jan_2009.ppt|Georgetown U. collaboration]] ([http://www.isis.georgetown.edu/PORTALVBVS/DesktopDefault.aspx?tabindex=2&amp;amp;tabid=8 Kevin Cleary])&amp;lt;br&amp;gt;&lt;br /&gt;
'''11:15''': [[media:HAMMER.ppt | UNC collaboration]] ([http://www.med.unc.edu/~dgshen Dinggang Shen])&amp;lt;br&amp;gt;&lt;br /&gt;
'''11:30''': [[media:AHM2009_MarioNegriCollaboration.pdf | Mario Negri Collaboration]] ([http://villacamozzi.marionegri.it/~luca/ Luca Antiga])&amp;lt;br&amp;gt;&lt;br /&gt;
'''11:45''': Discussion&amp;lt;br&amp;gt;&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;|Project Work&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;background:#ffffdd; color:black&amp;quot;|'''12:00-1:00'''  &lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;| Lunch&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;| Lunch &amp;lt;br&amp;gt; &lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;| Lunch&amp;lt;br&amp;gt; &lt;br /&gt;
| style=&amp;quot;background:#fff6a6; color:black&amp;quot;| Lunch&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;| Adjourn &lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;background:#ffffdd; color:black&amp;quot;|'''1:00-3:00''' &lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;|[[2009_Winter_Project_Week|Begin Project Activities]]: Introduce Projects and Participants &lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;|[[AHM 2009:DTI Breakout|DTI Discussion]] (Sonia, Randy, Others) [http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/Amethyst 1]&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;|Project Work (Capital Ballroom A) &amp;lt;br&amp;gt; '''1:00-2:00''' [[AHM2009:Python Modules|Python Modules]] (Luca Antiga) &amp;lt;br&amp;gt; '''2:00-3:00''' [[AHM2009:VTKWidgets | VTK Widgets]] (Will Schroeder) &lt;br /&gt;
| style=&amp;quot;background:#fff6a6; color:black&amp;quot;|&lt;br /&gt;
'''Tools and Tutorials''' (coordinator) &amp;lt;br&amp;gt;&lt;br /&gt;
'''1:00-1:20''' [[AHM2009:Slicer|Slicer]] ([http://www.spl.harvard.edu/~pieper Steve Pieper])&amp;lt;br&amp;gt;&lt;br /&gt;
'''1:20-1:40''' [[AHM2009:Plug-ins|Plug-ins for Slicer]] ([http://wiki.na-mic.org/Wiki/index.php/User:Millerjv Jim Miller])&amp;lt;br&amp;gt;&lt;br /&gt;
'''1:40-2:00''' [[AHM2009:Non-interactive-tools|Non-interactive tools]] ([http://www.kitware.com/company/team/aylward.html Stephen Aylward])&amp;lt;br&amp;gt;&lt;br /&gt;
'''2:00-3:00''' [[AHM2009:Tutorial-Contest-Winners|Tutorial Contest]]: Presentations by the winners ([http://www.nmr.mgh.harvard.edu/martinos/people/showPerson.php?people_id=64 Randy Gollub])&amp;lt;br&amp;gt;&lt;br /&gt;
| style=&amp;quot;background:#ebeced; color:black&amp;quot;|&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;background:#ffffdd; color:black&amp;quot;|'''3:00-3:30''' &lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;| Coffee&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;| Coffee&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;| Coffee&lt;br /&gt;
| style=&amp;quot;background:#fff6a6; color:black&amp;quot;| Coffee&lt;br /&gt;
| style=&amp;quot;background:#ebeced; color:black&amp;quot;|&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;background:#ffffdd; color:black&amp;quot;|'''3:00-5:00''' &lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;| &lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;|'''3:30-4:30''' [[AHM2009:Cell Segmentation|Cell Segmentation]] (Alex G) &amp;lt;br&amp;gt; Project Work &amp;lt;br&amp;gt;[http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/ Amethyst 1]&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;|Project Work &amp;lt;br&amp;gt;'''3:00-5:00''' Meshing Tutorial (Nicole Grosland, Vincent Magnotta)&amp;lt;br&amp;gt;[[Iowa_Meshing_Tutorial]]&amp;lt;br&amp;gt;[http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/ Amethyst 1]&lt;br /&gt;
| style=&amp;quot;background:#fff6a6; color:black&amp;quot;|[[2008 EAB|EAB]]&amp;lt;br&amp;gt;[http://www.marriott.com/hotels/event-planning/floor-plans/slccc-salt-lake-city-marriott-city-center/ Olympus B]&amp;lt;br&amp;gt;'''3:00-4:00''' Discussion with NA-MIC Leadership&amp;lt;br&amp;gt; '''4:00-5:00''' Closed Session&lt;br /&gt;
| style=&amp;quot;background:#ebeced; color:black&amp;quot;|&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;background:#ffffdd; color:black&amp;quot;|'''05:00-07:00''' &lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;|&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;|&lt;br /&gt;
| style=&amp;quot;background:#b4d597; color:black&amp;quot;|'''05:00-06:00''' [[AHM2009:Meshing Breakout | Meshing Breakout]] (Capital Ballroom A)&lt;br /&gt;
| style=&amp;quot;background:#fff6a6; color:black&amp;quot;|'''6:00''' Optional: [http://www.skisaltlake.com/murphys.htm Beer at Murphy's] (like last year)&lt;br /&gt;
| style=&amp;quot;background:#ebeced; color:black&amp;quot;| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Please note that there will be a Core 1&amp;amp;2 Site PI Retreat on the morning of Monday, January 5th. This is a closed session for Core 1&amp;amp;2 Site PIs, with no delegates. The topic is the competitive renewal.&lt;br /&gt;
&lt;br /&gt;
== Dates. Venue. Registration ==&lt;br /&gt;
'''Dates:''' &lt;br /&gt;
* The All Hands Meeting and External Advisory Board Meeting will be held on '''Thursday, January 8th'''.  &lt;br /&gt;
* Project Activities will be held rest of the week between '''Monday, January 5th and Friday, January 9th'''.&lt;br /&gt;
&lt;br /&gt;
'''Venue:''' The venue for the meeting is [http://www.marriott.com/hotels/travel/slccc-salt-lake-city-marriott-city-center/ Marriot City Center, Salt Lake City, Utah] Mariott City Center, Salt Lake City, Utah. [http://marriott.com/property/meetingsandevents/floorplans/slccc (Floorplan)]. Please either call the hotel at 1-801-961-8700 or 1-866-961-8700 (toll free) or book online '''by December 4, 2008''' using the code SCISCIA to get rooms at $139/night. Please note that we do need attendees to use this hotel in order to not incur additional charges for the use of conference rooms.&lt;br /&gt;
&lt;br /&gt;
'''Registration:''' We are charging a registration fee to all participants ($200 for AHM only, and $450 for AHM+). The fee covers the costs of the facilities and food provided. In order to keep the fee low, we need to get a sufficient number of hotel nights by our participants. See above for more on this. Please click http://www.sci.utah.edu/namic2009/registration.html for online registration. This registration must be completed by December 12, 2008.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Connectivity'''&lt;br /&gt;
We have three wireless access points at the AHM. Two of them are located in the capital ballroom.  One is named capital-ballroom, the other is named capital-ballroom2.  If one access point doesn't let you connect it is probably overloaded.  In that case, please try connecting to the other one.&lt;br /&gt;
&lt;br /&gt;
== Attendees ==&lt;br /&gt;
&lt;br /&gt;
Please follow http://www.sci.utah.edu/namic2009/registration.html to complete your online registration.  The organizers will periodically publish the list of registered attendees in the space below.  Attendees should '''NOT''' add their names in this section.  This list is a snapshop as of 01:46, 23 December 2008 (UTC)&lt;br /&gt;
&lt;br /&gt;
#	Michael	Ackerman	NA-MIC All Hands Meeting	National Library of Medicine at NIH&lt;br /&gt;
#	Luca	Antiga	NA-MIC All Hands Meeting and Project Week 2009	Mario Negri Institute&lt;br /&gt;
#	Kevin	Archie	NA-MIC All Hands Meeting and Project Week 2009	Washington University&lt;br /&gt;
#	Nicole	Aucoin	NA-MIC All Hands Meeting and Project Week 2009	BWH&lt;br /&gt;
#	Stephen	Aylward	NA-MIC All Hands Meeting and Project Week 2009	Kitware&lt;br /&gt;
#	Sebastien	Barre	NA-MIC All Hands Meeting and Project Week 2009	Kitware, Inc.&lt;br /&gt;
#	Morry	Blumenfeld	NA-MIC All Hands Meeting	EAB&lt;br /&gt;
#	H Jeremy	Bockholt	NA-MIC All Hands Meeting and Project Week 2009	The Mind Research Network&lt;br /&gt;
#	Sylvain	Bouix	NA-MIC All Hands Meeting and Project Week 2009	PNL&lt;br /&gt;
#	Josh	Cates	NA-MIC All Hands Meeting and Project Week 2009	SCI Institute&lt;br /&gt;
#	German	Cavelier	NA-MIC All Hands Meeting	NIH-NIMH&lt;br /&gt;
#	Kiyoyuki	Chinzei	NA-MIC All Hands Meeting and Project Week 2009	AIST&lt;br /&gt;
#	Kevin	Cleary	NA-MIC All Hands Meeting	Georgetown University&lt;br /&gt;
#	Manasi	Datar	NA-MIC All Hands Meeting and Project Week 2009	SCI Institute&lt;br /&gt;
#	Michal	Depa	NA-MIC All Hands Meeting and Project Week 2009	MIT CSAIL&lt;br /&gt;
#	Harish	Doddi	NA-MIC All Hands Meeting and Project Week 2009	Stanford University&lt;br /&gt;
#	Andriy	Fedorov	NA-MIC All Hands Meeting and Project Week 2009	SPL-BWH&lt;br /&gt;
#	Gabor	Fichtinger	NA-MIC All Hands Meeting	Queens Univ&lt;br /&gt;
#	Yi	Gao	NA-MIC All Hands Meeting and Project Week 2009	&lt;br /&gt;
#	Arnaud	Gelas	NA-MIC All Hands Meeting and Project Week 2009	Harvard Medical School&lt;br /&gt;
#	Guido	Gerig	NA-MIC All Hands Meeting and Project Week 2009	SCI Institute&lt;br /&gt;
#	Polina	Golland	NA-MIC All Hands Meeting and Project Week 2009	MIT CSAIL&lt;br /&gt;
#	Randy L. 	Gollub	NA-MIC All Hands Meeting and Project Week 2009	MGH&lt;br /&gt;
#	Casey	Goodlett	NA-MIC All Hands Meeting and Project Week 2009	SCI Institute&lt;br /&gt;
#	Alexandre	Gouaillard	NA-MIC All Hands Meeting and Project Week 2009	Harvard Medical School&lt;br /&gt;
#	Sylvain	Gouttard	NA-MIC All Hands Meeting and Project Week 2009	SCI Institute&lt;br /&gt;
#	Jeffrey	Grethe	NA-MIC All Hands Meeting and Project Week 2009	UC San Diego&lt;br /&gt;
#	Nicole	Grosland	NA-MIC All Hands Meeting and Project Week 2009	The University of Iowa&lt;br /&gt;
#	Daniel	Haehn	NA-MIC All Hands Meeting and Project Week 2009	SPL-BWH&lt;br /&gt;
#	Nathan	Hageman	NA-MIC All Hands Meeting and Project Week 2009	UCLA&lt;br /&gt;
#	Nobuhiko	Hata	NA-MIC All Hands Meeting and Project Week 2009	Brigham and Womens Hospital&lt;br /&gt;
#	Kathryn	Hayes	NA-MIC All Hands Meeting and Project Week 2009	Brigham and Womens Hospital&lt;br /&gt;
#	Heather Cody	Hazlett	NA-MIC All Hands Meeting	University of North Carolina&lt;br /&gt;
#	Jaesung	Hong	NA-MIC All Hands Meeting and Project Week 2009	Kyushu University&lt;br /&gt;
#	Luis 	Ibanez	NA-MIC All Hands Meeting and Project Week 2009	Kitware, Inc.&lt;br /&gt;
#	Chris 	Johnson	NA-MIC All Hands Meeting and Project Week 2009	EAB&lt;br /&gt;
#	Ron	Kikinis	NA-MIC All Hands Meeting and Project Week 2009	SPL - BWH&lt;br /&gt;
#	Ivan	Kolesov	NA-MIC All Hands Meeting and Project Week 2009	Georgia Tech&lt;br /&gt;
#	Karthik 	Krishnan	NA-MIC All Hands Meeting and Project Week 2009	Kitware, Inc.&lt;br /&gt;
#	Marek	Kubicki	NA-MIC All Hands Meeting and Project Week 2009	PNL_BWH&lt;br /&gt;
#	Curtis	Lisle	NA-MIC All Hands Meeting and Project Week 2009	KnowledgeVis, LLC&lt;br /&gt;
#	Yanling	Liu	NA-MIC All Hands Meeting and Project Week 2009	SAIC-Frederick, Inc.&lt;br /&gt;
#	Zhexing	Liu	NA-MIC All Hands Meeting and Project Week 2009	NIRAL, UNC&lt;br /&gt;
#	Terry	Lorber	NA-MIC All Hands Meeting and Project Week 2009	Isomics, Inc&lt;br /&gt;
#	Bill	Lorensen	NA-MIC All Hands Meeting and Project Week 2009	EAB&lt;br /&gt;
#	Vincent	Magnotta	NA-MIC All Hands Meeting and Project Week 2009	The University of Iowa&lt;br /&gt;
#	Daniel	Marcus	NA-MIC All Hands Meeting and Project Week 2009	Washington University&lt;br /&gt;
#	Katie	Mastrogiacomo	NA-MIC All Hands Meeting and Project Week 2009	SPL - BWH&lt;br /&gt;
#	Cedric	Mathieu	NA-MIC All Hands Meeting and Project Week 2009	UNC&lt;br /&gt;
#	Bjoern	Menze	NA-MIC All Hands Meeting and Project Week 2009	MIT CSAIL&lt;br /&gt;
#	Mikhail	Milchenko	NA-MIC All Hands Meeting	Washington University in St Louis&lt;br /&gt;
#	James	Miller	NA-MIC All Hands Meeting and Project Week 2009	&lt;br /&gt;
#	Vandana	Mohan	NA-MIC All Hands Meeting and Project Week 2009	Georgia Inst of Technology&lt;br /&gt;
#	kishore	mosaliganti	NA-MIC All Hands Meeting and Project Week 2009	Harvard Medical School&lt;br /&gt;
#	Sandy 	Napel	NA-MIC All Hands Meeting	EAB&lt;br /&gt;
#	Marc	Niethammer	NA-MIC All Hands Meeting and Project Week 2009	UNC Chapel Hill&lt;br /&gt;
#	Guy	Nir	NA-MIC All Hands Meeting and Project Week 2009	Technion&lt;br /&gt;
#	Ipek	Oguz	NA-MIC All Hands Meeting and Project Week 2009	UNC&lt;br /&gt;
#	Saikat 	Pal	NA-MIC All Hands Meeting and Project Week 2009	Stanford University&lt;br /&gt;
#	Steve	Pieper	NA-MIC All Hands Meeting and Project Week 2009	Isomics, Inc.&lt;br /&gt;
#	Marcel	Prastawa	NA-MIC All Hands Meeting and Project Week 2009	SCI Institute&lt;br /&gt;
#	Fred	Prior	NA-MIC All Hands Meeting	EAB&lt;br /&gt;
#	Sonia	Pujol	NA-MIC All Hands Meeting and Project Week 2009	Surgical Planning Lab, Brigham  Womens Hosp&lt;br /&gt;
#	Vidya	Rajagopalan	NA-MIC All Hands Meeting and Project Week 2009	Virginia Tech&lt;br /&gt;
#	Austin	Ramme	NA-MIC All Hands Meeting and Project Week 2009	The University of Iowa&lt;br /&gt;
#	Petter	Risholm	NA-MIC All Hands Meeting and Project Week 2009	Brigham Womens Hospital&lt;br /&gt;
#	James	Ross	NA-MIC All Hands Meeting and Project Week 2009	SPL-BWH&lt;br /&gt;
#	Marco	Ruiz	NA-MIC All Hands Meeting and Project Week 2009	UCSD&lt;br /&gt;
#	Raul	San Jose	NA-MIC All Hands Meeting and Project Week 2009	LMI-BWH&lt;br /&gt;
#	Peter	Savadjiev	NA-MIC All Hands Meeting and Project Week 2009	Brigham  Womens Hospital&lt;br /&gt;
#	William	Schroeder	NA-MIC All Hands Meeting and Project Week 2009	Kitware, Inc.&lt;br /&gt;
#	Mark	Scully	NA-MIC All Hands Meeting and Project Week 2009	The Mind Research Network&lt;br /&gt;
#	Madeleine	Seeland	NA-MIC All Hands Meeting and Project Week 2009	LMI&lt;br /&gt;
#	Gregory	Sharp	NA-MIC All Hands Meeting and Project Week 2009	MGH&lt;br /&gt;
#	Dinggang	Shen	NA-MIC All Hands Meeting	UNC-Chapel Hill&lt;br /&gt;
#	Kiran	Shivanna	NA-MIC All Hands Meeting and Project Week 2009	The University of Iowa&lt;br /&gt;
#	Shantanu	Singh	NA-MIC All Hands Meeting and Project Week 2009	The Ohio State University&lt;br /&gt;
#	Martin	Styner	NA-MIC All Hands Meeting and Project Week 2009	University of North Carolina&lt;br /&gt;
#	Allen	Tannenbaum	NA-MIC All Hands Meeting and Project Week 2009	Georgia Tech&lt;br /&gt;
#	Xiaodong	Tao	NA-MIC All Hands Meeting and Project Week 2009	GE Global Research&lt;br /&gt;
#	Doug	Terry	NA-MIC All Hands Meeting and Project Week 2009	Psychiatry Neuroimaging Lab&lt;br /&gt;
#	Clement	Vachet	NA-MIC All Hands Meeting and Project Week 2009	UNC&lt;br /&gt;
#	Koen	Van Leemput	NA-MIC All Hands Meeting and Project Week 2009	MIT CSAIL&lt;br /&gt;
#	Archana	Venkataraman	NA-MIC All Hands Meeting and Project Week 2009	MIT CSAIL&lt;br /&gt;
#	Siddharth	Vikal	NA-MIC All Hands Meeting and Project Week 2009	Queens University&lt;br /&gt;
#	William	Wells	NA-MIC All Hands Meeting and Project Week 2009	SPL-BWH&lt;br /&gt;
#	Carl-Fredrik	Westin	NA-MIC All Hands Meeting and Project Week 2009	Brigham and Womens Hospital&lt;br /&gt;
#	Ross	Whitaker	NA-MIC All Hands Meeting and Project Week 2009	SCI Institute&lt;br /&gt;
#	Nathan	Wilson	NA-MIC All Hands Meeting	Cardiovascular Simulation, Inc.&lt;br /&gt;
#	Chris	Wyatt	NA-MIC All Hands Meeting	&lt;br /&gt;
#	Alexander	Yarmarkovich	NA-MIC All Hands Meeting and Project Week 2009	ISOMIC&lt;br /&gt;
#	Dr. Terry S	Yoo	NA-MIC All Hands Meeting	DHHSNIHNLM&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=File:AHM2009_MarioNegriCollaboration.pdf&amp;diff=34625</id>
		<title>File:AHM2009 MarioNegriCollaboration.pdf</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=File:AHM2009_MarioNegriCollaboration.pdf&amp;diff=34625"/>
		<updated>2009-01-08T16:33:42Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=File:AHM2008_MarioNegriCollaboration.pdf&amp;diff=34580</id>
		<title>File:AHM2008 MarioNegriCollaboration.pdf</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=File:AHM2008_MarioNegriCollaboration.pdf&amp;diff=34580"/>
		<updated>2009-01-08T07:40:23Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=AHM2009:Python_Modules&amp;diff=34024</id>
		<title>AHM2009:Python Modules</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=AHM2009:Python_Modules&amp;diff=34024"/>
		<updated>2008-12-26T17:18:07Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt; Back to [[AHM_2009]]&lt;br /&gt;
&lt;br /&gt;
Breakout session Moderator: Luca Antiga&lt;br /&gt;
&lt;br /&gt;
Agenda:&lt;br /&gt;
&lt;br /&gt;
* Python in Slicer: the user's standpoint&lt;br /&gt;
** Overview&lt;br /&gt;
** Command-line modules (XML-based)&lt;br /&gt;
** Slicer to Numpy and back&lt;br /&gt;
** Interactive modules&lt;br /&gt;
&lt;br /&gt;
* Python in Slicer: the inner workings&lt;br /&gt;
** Overview&lt;br /&gt;
** Lower layer: Python through Tcl&lt;br /&gt;
** Higher layer: Python classes with metaprogramming&lt;br /&gt;
&lt;br /&gt;
* Discussion: where to go from here&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=AHM2009:Meshing_Breakout&amp;diff=34023</id>
		<title>AHM2009:Meshing Breakout</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=AHM2009:Meshing_Breakout&amp;diff=34023"/>
		<updated>2008-12-26T17:09:31Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt; Back to [[AHM_2009]]&lt;br /&gt;
&lt;br /&gt;
Breakout session Moderator: Steve Pieper&lt;br /&gt;
&lt;br /&gt;
Topics:&lt;br /&gt;
* Mesh Generation &lt;br /&gt;
** Hexahedral&lt;br /&gt;
** Tetrahedral&lt;br /&gt;
** Open Source Tools&lt;br /&gt;
* Applications&lt;br /&gt;
** Cardiology&lt;br /&gt;
** Orthopedics&lt;br /&gt;
** Neurosurgery&lt;br /&gt;
** Vascular disease and vascular surgery&lt;br /&gt;
&lt;br /&gt;
Attendees (anyone interested, please sign up):&lt;br /&gt;
* Andriy Fedorov&lt;br /&gt;
* Allen Tannenbaum&lt;br /&gt;
* Curt Lisle&lt;br /&gt;
* Vince Magnotta&lt;br /&gt;
* Nicole Grosland&lt;br /&gt;
* Steve Pieper&lt;br /&gt;
* Ron Kikinis&lt;br /&gt;
* Saikat Pal&lt;br /&gt;
* Harish&lt;br /&gt;
* Jeroen Stinstra&lt;br /&gt;
* Luca Antiga&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week&amp;diff=33415</id>
		<title>2009 Winter Project Week</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week&amp;diff=33415"/>
		<updated>2008-12-12T12:27:37Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Other NA-MIC Projects */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[Project Events]], [[AHM_2009]], [[Events]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction to NA-MIC Project Week==&lt;br /&gt;
&lt;br /&gt;
Please read an introduction about these events [[Project_Events#Introduction|here]].&lt;br /&gt;
&lt;br /&gt;
== Dates.Venue.Registration ==&lt;br /&gt;
&lt;br /&gt;
Please [[AHM_2009#Dates._Venue._Registration| click here for Dates, Venue, and Registration]] for this event.&lt;br /&gt;
&lt;br /&gt;
== Agenda==&lt;br /&gt;
&lt;br /&gt;
Please [[AHM_2009#Agenda|click here for the agenda for AHM 2009 and Project Week]].&lt;br /&gt;
&lt;br /&gt;
==Projects==&lt;br /&gt;
Please note:&lt;br /&gt;
*Please use the [[2009_Winter_Project_Week_Template|'''2009 Project Week Template''']] to create a page for your project(s)&lt;br /&gt;
*[[2008_Summer_Project_Week#Projects|Last Event's Projects as a reference]]&lt;br /&gt;
*For hosting projects, we are planning to make use of the NITRC resources.  See [[NA-MIC_and_NITRC | Information about NITRC Collaboration]]&lt;br /&gt;
*Next Project Week is at MIT -- June 22-26, 2009&lt;br /&gt;
The following is a list of all projects that will be pursued at this meeting.&lt;br /&gt;
&lt;br /&gt;
===NA-MIC DBP Roadmap Projects===&lt;br /&gt;
Please note that these projects correspond to four clinical Roadmap application projects that will be pursued in focused parallel tracks at the meeting, each corresponding to a DBP problem.  &lt;br /&gt;
&lt;br /&gt;
#[[DBP2:Harvard:Brain_Segmentation_Roadmap|Harvard Roadmap Project: Stochastic Tractography for VCFS]]&lt;br /&gt;
##[[2009_Winter_Project_Week:GT_TubularSurfaceSeg|Tubular Surface Segmentation for fiber bundle extraction]] (Vandana Mohan GATech, Allen Tannenbaum GATech, Marek Kubicki BWH, Stephen Aylward Kitware)&lt;br /&gt;
##[[2009_Winter_Project_Week_StochasticTractography |Stochastic Tractograhy Tool for Slicer]] (Marek Kubicki BWH, Julien de Siebenthal BWH, Steve Pieper Isomics) &lt;br /&gt;
##[[2009_Winter_Project_Week_Slicer3Functioning |Evaluation of basic Slicer 3.0 Functionality from a User Perspective]] (Doug Terry BWH, Marek Kubicki BWH, Sylvain Bouix BWH, Steve Pieper, Wendy Plesniak, Nicole Aucoin) &lt;br /&gt;
#[[DBP2:UNC:Cortical_Thickness_Roadmap|UNC Roadmap Project: Cortical Thickness Measurement for Autism]]&lt;br /&gt;
#[[DBP2:MIND:Roadmap|MIND Roadmap Project: Brain Lesion Analysis in Lupus]]&lt;br /&gt;
##[[2009_Winter_Project_Week:HighLevelWizard|Slicer High Level Wizard Project]](Steve Piper, Mark Scully, Jeremy Bockholt)&lt;br /&gt;
##[[2009_Winter_Project_Week:LesionAlgorithms|Review of Lesion Algorithms]](Ross Whitaker, Vincent Magnotta, Marcel Prastawa, Mark Scully, Jeremy Bockholt)&lt;br /&gt;
##[[2009_Winter_Project_Week:LongitudinalLesions|Determine Requirements of Longitudinal Lesion Analyses]](Marcel Prastawa, Mark Scully, Jeremy Bockholt, Andrey Fedorov)&lt;br /&gt;
#[[DBP2:JHU:Roadmap|JHU Roadmap Project: Segmentation and Registration for Robotic Prostate Intervention]]&lt;br /&gt;
##[[2009_Winter_Project_Week:SterotacticFrameModel|Generating a Model of a Stereotactic Frame for Neurosurgery]] (Rares Crisan, Queens, Gabor Fichtinger, Queens, Katie Hayes, BWH)&lt;br /&gt;
&lt;br /&gt;
===Other NA-MIC Projects===&lt;br /&gt;
#[[2009_Winter_Project_Week_Hageman_FMTractography | Fluid mechanics tractography and visualization]] (Nathan Hageman UCLA)&lt;br /&gt;
#UCLA BrainLab/Slicer Neurosurgery Preoperative Tumor Planning - using Slicer and its link to BrainLab to investigate whether different tractography methods aid in preoperative planning of tumor resection.(Nathan Hageman UCLA)&lt;br /&gt;
#Development of FEM / FVM solver library in ITK/VTK (and/or Python?) (Nathan Hageman UCLA, Vince, Luca, Steve)&lt;br /&gt;
#[[2009_Winter_Project_Week_Transform_Management | Transform Management]](Jim Miller)&lt;br /&gt;
#Interactive 3D Widgets - Introduce new interactors into Slicer; extensions to current widgets to support Slicer (Karthik, Will Schroeder, Nicole Aucoin)&lt;br /&gt;
#[[2009_Winter_Project_Week_vtkITK_Pipeline | Using ITK in VTK Pipelines]] (Jim, Steve)&lt;br /&gt;
#[[2009_Winter_Project_Week_SlicerLayouts | User Interface Flexible Layouts]] (Wendy, Jim, Steve, Sebastien, Ron)&lt;br /&gt;
#[[2009_Winter_Project_Week_Python | Python interface completion and packaging - Fortran and openssl problems]] (Luca, Steve, Demian)&lt;br /&gt;
#Two-tensor tractography in Slicer using Python and Teem (Madeleine Seeland, C-F Westin, Xiaodong Tao)&lt;br /&gt;
#[[2009_Winter_Project_Week_Rotation_Tangents | Diffusion Tensor Invariant gradients and rotation tangents in Python and Teem]] (Peter Savadjiev, C-F Westin, Luis Ibanez)&lt;br /&gt;
#Automated GUI testing (Sebastien, Interested User: Vince)&lt;br /&gt;
#[[2009_Winter_Project_Week_ColorModule | Slicer Colors Module update ]](Nicole)&lt;br /&gt;
#[[Volume Rendering]] (Alex, Curt, Nicholas)&lt;br /&gt;
#[[2009_Winter_Project_Week_XND | XNAT Desktop BatchMake integration &amp;amp; Slicer interface]] (Dan Marcus, Stephen Aylward, Wendy Plesniak, Curt Lisle)&lt;br /&gt;
#Cortical correspondence using DTI (Ipek, Martin, Xiaodong)&lt;br /&gt;
#[[2009_Winter_Project_Week_Command_Line_Program_Testing |Command Line Program Testing]] (Lorensen, Ron)&lt;br /&gt;
#[[2009_Winter_Project_Week_Slicer_VMTK |Vessel Segmentation in Slicer using VMTK]] ([[User:haehn|Daniel Haehn]], [[User:lantiga| Luca Antiga]])&lt;br /&gt;
#[[2009_Winter_Project_Week_fMRI_Clustering |Exploring Functional Connectivity in fMRI via Clustering]] (Archana Venkataraman, Marek Kubicki, Polina Golland)&lt;br /&gt;
#[[2009_Winter_Project_Week_Compiler_Warnings:Slicer3_Graffiti |Compiler Warnings:Slicer3's Graffiti]] (Lorensen, NA-MIC)&lt;br /&gt;
#[[2009_Winter_Project_Week_ChangeTracker |Measuring dynamics of tumor growth in Slicer3 with ChangeTracker]] (Andriy Fedorov)&lt;br /&gt;
#[[2009_Winter_Project_Week_GWE_Catalogs |GWE integration with catalog files]] (Marco)&lt;br /&gt;
&lt;br /&gt;
===External Collaborations===&lt;br /&gt;
* [[Iowa Meshing Tutorial]] &lt;br /&gt;
*Wake Forest - Virginia Tech&lt;br /&gt;
** [[2009_Winter_Project_Week_WFU1 | Move to All Slicer3 Workflow]]&lt;br /&gt;
** [[2009_Winter_Project_Week_WFU2 | Development of deformation based morphometry module]]&lt;br /&gt;
*Georgetown U: Prototype RF Lesion Ablation Workflow prototyped in Slicer&lt;br /&gt;
*UNC: &lt;br /&gt;
**[[2009_UNC_HAMMER | MR-image registration algorithm to be extended and added to namic kit]]&lt;br /&gt;
**[[2009_UNC_White_Matter_Lesion | white matter lesion segmentation]]&lt;br /&gt;
*Mario Negri&lt;br /&gt;
*Stanford SIMBIOS: segmentation of knee joint&lt;br /&gt;
* [[2009_Winter_Project_Week_MRSI | MRSI Module for Slicer (Bjoern Menze)]]&lt;br /&gt;
*[[NCI Evaluating NA-MIC Tools for Image Analysis]]&lt;br /&gt;
&lt;br /&gt;
=== Preparation ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
# Please make sure that you are on the [http://public.kitware.com/cgi-bin/mailman/listinfo/na-mic-project-week na-mic-project-week mailing list]&lt;br /&gt;
# Starting Thursday, October 16th, part of the weekly Thursday 3pm NA-MIC Engineering TCON will be used to prepare for this meeting.  The schedule for these preparatory calls is as follows:&lt;br /&gt;
#*October 16: Engineering Infrastructure Projects&lt;br /&gt;
#*October 23: Funded External Collaboration Projects&lt;br /&gt;
#*November 6: DPB Projects &lt;br /&gt;
#*November 20: New Collaborations&lt;br /&gt;
#*December 4: Other Projects&lt;br /&gt;
#*December 18: Loose Ends&lt;br /&gt;
#By December 17, 2008: [[2009_Winter_Project_Week_Template|Complete a templated wiki page for your project]]. Please do not edit the template page itself, but create a new page for your project and cut-and-paste the text from this template page.  If you have questions, please send an email to tkapur at bwh.harvard.edu.&lt;br /&gt;
# By December 17, 2008: Create a directory for each project on the [[Engineering:SandBox|NAMIC Sandbox]] (Zack)&lt;br /&gt;
##[https://www.kitware.com/Admin/SendPassword.cgi Ask Zack for a Sandbox account]&lt;br /&gt;
## Commit on each sandbox directory the code examples/snippets that represent our first guesses of appropriate methods. (Luis and Steve will help with this, as needed)&lt;br /&gt;
## Gather test images in any of the Data sharing resources we have (e.g. the BIRN). These ones don't have to be many. At least three different cases, so we can get an idea of the modality-specific characteristics of these images. Put the IDs of these data sets on the wiki page. (the participants must do this.)&lt;br /&gt;
## Setup nightly tests on a separate Dashboard, where we will run the methods that we are experimenting with. The test should post result images and computation time. (Zack)&lt;br /&gt;
# FINAL TCON: December 18th 3pm ET to tie loose ends&lt;br /&gt;
# Please note that by the time we get to the project event, we should be trying to close off a project milestone rather than starting to work on one...&lt;br /&gt;
&lt;br /&gt;
== Previous Project Events ==&lt;br /&gt;
&lt;br /&gt;
A history of all the programming/project events in NA-MIC is available by following [[Project Events|this link]].&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33414</id>
		<title>2009 Winter Project Week Python</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33414"/>
		<updated>2008-12-12T12:27:08Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Key Investigators */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:Python-logo.png |thumb|320px|[http://www.python.org]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Luca Antiga (Mario Negri Institute)&lt;br /&gt;
* Steve Piper (Isomics)&lt;br /&gt;
* Demian Wasserman (INRIA)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
To finalize the implementation of the Slicer Python interface and solve packaging problems linked to Scipy.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Slicer Python interface now works well for both non-interactive and interactive modules. A few improvements are still needed, namely &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- calling VTK static methods - e.g. slicer.vtkMath.Norm(v)&lt;br /&gt;
&lt;br /&gt;
- handling modified arguments - e.g. slicer.vtkMath::Normalize(v)&lt;br /&gt;
&lt;br /&gt;
- defining methods with the exact number of arguments (now it's not constrained, so if it's wrong Tcl complains) - this will require a patch on the VTK Tcl wrappers&lt;br /&gt;
&lt;br /&gt;
- fix a memory leak associated with Python scripted modules&lt;br /&gt;
&lt;br /&gt;
- review the Slicer Python to Numpy code and eventually extend it to handle more general image or data types&lt;br /&gt;
&lt;br /&gt;
- implement callback functions in Slicer Python, for widgets and programmable filters&lt;br /&gt;
&lt;br /&gt;
As for packaging problems, testing will have to be performed on several architectures.&lt;br /&gt;
&lt;br /&gt;
Finally, documentation will be improved.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TODO&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33413</id>
		<title>2009 Winter Project Week Python</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33413"/>
		<updated>2008-12-12T12:26:52Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:Python-logo.png |thumb|320px|[http://www.python.org]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Luca Antiga (Medical Imaging Unit, Biomedical Engineering Department, Mario Negri Institute)&lt;br /&gt;
* Steve Piper (Isomics)&lt;br /&gt;
* Demian Wasserman (INRIA)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
To finalize the implementation of the Slicer Python interface and solve packaging problems linked to Scipy.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Slicer Python interface now works well for both non-interactive and interactive modules. A few improvements are still needed, namely &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- calling VTK static methods - e.g. slicer.vtkMath.Norm(v)&lt;br /&gt;
&lt;br /&gt;
- handling modified arguments - e.g. slicer.vtkMath::Normalize(v)&lt;br /&gt;
&lt;br /&gt;
- defining methods with the exact number of arguments (now it's not constrained, so if it's wrong Tcl complains) - this will require a patch on the VTK Tcl wrappers&lt;br /&gt;
&lt;br /&gt;
- fix a memory leak associated with Python scripted modules&lt;br /&gt;
&lt;br /&gt;
- review the Slicer Python to Numpy code and eventually extend it to handle more general image or data types&lt;br /&gt;
&lt;br /&gt;
- implement callback functions in Slicer Python, for widgets and programmable filters&lt;br /&gt;
&lt;br /&gt;
As for packaging problems, testing will have to be performed on several architectures.&lt;br /&gt;
&lt;br /&gt;
Finally, documentation will be improved.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TODO&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=AHM2009:Meshing_Breakout&amp;diff=33412</id>
		<title>AHM2009:Meshing Breakout</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=AHM2009:Meshing_Breakout&amp;diff=33412"/>
		<updated>2008-12-12T09:40:37Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Meshing Breakout Discussion&lt;br /&gt;
&lt;br /&gt;
Topics:&lt;br /&gt;
* Mesh Generation &lt;br /&gt;
** Hexahedral&lt;br /&gt;
** Tetrahedral&lt;br /&gt;
** Open Source Tools&lt;br /&gt;
* Applications&lt;br /&gt;
** Cardiology&lt;br /&gt;
** Orthopedics&lt;br /&gt;
** Neurosurgery&lt;br /&gt;
** Vascular disease (atherosclerosis, aneurysmal disease) and vascular surgery&lt;br /&gt;
&lt;br /&gt;
Attendees (anyone interested, please sign up):&lt;br /&gt;
* Andriy Fedorov&lt;br /&gt;
* Allen Tannenbaum&lt;br /&gt;
* Curt Lisle&lt;br /&gt;
* Vince Magnotta&lt;br /&gt;
* Nicole Grosland&lt;br /&gt;
* Steve Pieper&lt;br /&gt;
* Ron Kikinis&lt;br /&gt;
* Saikat Pal&lt;br /&gt;
* Harish&lt;br /&gt;
* Jeroen Stinstra&lt;br /&gt;
* Luca Antiga&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=User:Lantiga&amp;diff=33203</id>
		<title>User:Lantiga</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=User:Lantiga&amp;diff=33203"/>
		<updated>2008-12-10T19:46:47Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* 2009 Winter project week */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 2009 Winter project week ==&lt;br /&gt;
&lt;br /&gt;
* Projects&lt;br /&gt;
** [[2009_Winter_Project_Week_Slicer_VMTK | Slicer VMTK]]&lt;br /&gt;
** [[2009_Winter_Project_Week_Python | Python]]&lt;br /&gt;
&lt;br /&gt;
* Breakouts&lt;br /&gt;
** Wed, Jan 7, 1.00pm - 3.00pm: Python Modules (with Demian Wasserman)&lt;br /&gt;
&lt;br /&gt;
* Presentations&lt;br /&gt;
** Thu, Jan 8, 11.30am - 11.45am: Collaborations: Mario Negri Institute&lt;br /&gt;
&lt;br /&gt;
* Misc&lt;br /&gt;
** Propose addition of vtkMRMLLevelSetNode&lt;br /&gt;
** Discuss on level set architecture&lt;br /&gt;
** Commit first implementation of modular-solver pluggable-term level sets&lt;br /&gt;
** Commit backwards-compatible improvement to itkCollidingFrontsImageFilter&lt;br /&gt;
** Commit 3D test for CURVES.&lt;br /&gt;
&lt;br /&gt;
== Progress in 2008 ==&lt;br /&gt;
&lt;br /&gt;
The NAMIC - Mario Negri Institute external collaboration has brought the following contributions to Slicer and the NAMIC kit:&lt;br /&gt;
&lt;br /&gt;
* Python in Slicer&lt;br /&gt;
** background: in 2007, Dan Blezek produced the first implementation of Python interface in Slicer, providing a method to access Slicer instances from Python through Tcl.&lt;br /&gt;
** during the 2008 January project week in SLC, several sample Python command-line (i.e. non-interactive) modules have been implemented, and the vtkScriptedModule module has been extended to handle Python in addition to Tcl as a scripting language. This allowed the implementation of interactive modules in Python. &lt;br /&gt;
** during the 2008 June project week in Boston, the Python interface has been largely improved (keeping Dan's original code as the core), in order to provide Slicer Python objects as real Python class instances, rather than thin wrappers around Tcl objects. This way, coding Python modules has become very close to coding Python-wrapped VTK.&lt;br /&gt;
** during August 2008, the Python/Numpy interface has been improved, allowing seamless integration of Numpy objects within the Slicer Python interface.&lt;br /&gt;
&lt;br /&gt;
* VMTK Slicer&lt;br /&gt;
** background: during 2007, functionality for turning vmtk command lines into Slicer command-line modules had been implemented. However, need for interactive modules based on vmtk was still needed.&lt;br /&gt;
** during 2008, a first implementation of some of the interactive components of VMTK segmentation has been created, although no code has been committed to the sandbox yet. Rather, this work will be integrated with the work of Daniel Haehn during the January 2009 project week in SLC. In this context, the addition of a vtkMRMLLevelSet node will be proposed (derived from vtkMRMLScalarVolumeNode with a poly data display node).&lt;br /&gt;
** in the meantime, VMTK has been largely improved and now provides vessel enhancement and surface and volume mesh generation capabilities. Therefore, the integration of VMTK in Slicer will readily bring these functionalities to Slicer. In addition, the Mario Negri Institute has implemented and validated a computational fluid dynamics solver that could be interfaced with Slicer and the NAMIC kit.&lt;br /&gt;
&lt;br /&gt;
* ITK&lt;br /&gt;
** during the first half of 2008, the extension of the level set framework to (moderately) anisotropic voxel spacings has been committed to ITK. Work is underway to extend the sparse field level set framework to severely anisotropic spacings.&lt;br /&gt;
** during August 2008, a first draft implementation of a modular level set framework with pluggable terms has been coded, and will tentatively be commited to the NAMIC sandbox during the January 2009 project week.&lt;br /&gt;
&lt;br /&gt;
* Project weeks&lt;br /&gt;
** during the 2008 January AHM in SLC, a presentation was given at the [[2008_Winter_Project_Week_Geometry_and_Topology_processing_of_Meshes | Geometry and Topology Processing of Meshes]] breakout session.&lt;br /&gt;
&lt;br /&gt;
* NAMIC Kit&lt;br /&gt;
** the adoption of the NAMIC Kit within the [http://www.robocast.eu ROBOCAST] project, funded by the European Commission, has been pushed forward, and it is now official.&lt;br /&gt;
** the development of a Slicer-based pre-operative planning workflow is underway at the University of Verona, under the guide of Dr. Roberto Foroni.&lt;br /&gt;
&lt;br /&gt;
== Extending ITK finite difference and level set filters to anisotropic spacing ==&lt;br /&gt;
&lt;br /&gt;
This is the (tentative) list of classes that assume that spacing is isotropic (i.e. they give incorrect results for anisotropic spacings).&lt;br /&gt;
The plan is to go in and extend them to properly account for anisotropic spacings. This addresses BUG [http://public.kitware.com/Bug/view.php?id=6156 ITK 6156].&lt;br /&gt;
&lt;br /&gt;
* Insight/Code/Common:&lt;br /&gt;
** itkLevelSetFunction - FIXED&lt;br /&gt;
** itkSegmentationLevelSetFunction - FIXED&lt;br /&gt;
&lt;br /&gt;
* Insight/Code/BasicFilters:&lt;br /&gt;
** itkLevelSetFunctionWithRefitTerm&lt;br /&gt;
** itkNormalVectorDiffusionFunction&lt;br /&gt;
** itkParallelSparseFieldLevelSetImageFilter&lt;br /&gt;
** itkSparseFieldFourthOrderLevelSetImageFilter&lt;br /&gt;
** itkSparseFieldLevelSetImageFilter - FIXED&lt;br /&gt;
&lt;br /&gt;
Insight/Code/Algorithms:&lt;br /&gt;
** itkBinaryMinMaxCurvatureFlowFunction&lt;br /&gt;
** tkCurvatureFlowFunction - FIXED&lt;br /&gt;
** itkLevelSetNeighborhoodExtractor&lt;br /&gt;
** itkLevelSetVelocityNeighborhoodExtractor&lt;br /&gt;
** itkReinitializeLevelSetImageFilter&lt;br /&gt;
** itkShapePriorSegmentationLevelSetFunction&lt;br /&gt;
&lt;br /&gt;
== 2008 Winter Project Week ==&lt;br /&gt;
&lt;br /&gt;
* Python modules: Python support, existing modules and new modules&lt;br /&gt;
* Transform hardening in MRML (should be finished on a local copy before the project week)&lt;br /&gt;
* Localized command line modules using MRML transform hardening&lt;br /&gt;
* Breakout: Geometry and Topology processing of Meshes&lt;br /&gt;
* vmtk module&lt;br /&gt;
&lt;br /&gt;
== Python modules ==&lt;br /&gt;
&lt;br /&gt;
Below is a list of Python modules that will be implemented using the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation:Python Python script plugin] functionality.&lt;br /&gt;
&lt;br /&gt;
===Done===&lt;br /&gt;
* SurfaceConnectivity.py (color by connected regions or extract the connected surface closest to a fiducial) (issue: crash with more than one fiducial on the Mac?)&lt;br /&gt;
* SurfaceToolbox.py (decimation + smoothing + normals + cleaner, with individual &amp;quot;Enable&amp;quot; switches)&lt;br /&gt;
* PythonScript.py (takes a surface and/or an image, runs Python code on it loading it from a file, and output the result. Fast way of using Slicer through Python and prototyping modules) (why does it fail with multiple inputs/outputs on the Mac?)&lt;br /&gt;
* GradientAnisotropicDiffusion.py (by Dan)&lt;br /&gt;
* SurfaceICPRegistration.py&lt;br /&gt;
&lt;br /&gt;
===In the works===&lt;br /&gt;
* SurfaceTransformHardening.py&lt;br /&gt;
&lt;br /&gt;
===Ideas===&lt;br /&gt;
* MarchingCubes.py&lt;br /&gt;
* ArrayCalculator.py&lt;br /&gt;
* Glyphs.py&lt;br /&gt;
* ShortestPath.py (use new Djikstra path)&lt;br /&gt;
* Reference system handling&lt;br /&gt;
&lt;br /&gt;
== Ideas for Slicer3 ==&lt;br /&gt;
&lt;br /&gt;
=== vmtk ===&lt;br /&gt;
&lt;br /&gt;
* figure out an official way to use vmtk within slicer and provide concrete examples and several modules:&lt;br /&gt;
** vessel enhancement&lt;br /&gt;
** vessel segmentation&lt;br /&gt;
** geometric analysis&lt;br /&gt;
** meshing for CFD&lt;br /&gt;
** visualization of CFD data&lt;br /&gt;
* check if any of the vmtk C++ classes can be used for stand-alone C++ modules  (e.g. centerline computation, finite elements)&lt;br /&gt;
* running modules in a localized space is vital: one solution has been implemented in Boston, but a more general approach would have a broader impact (see below)&lt;br /&gt;
* output fiducials would be useful (see below) but not vital for vmtk integration, can be circumvented using world points&lt;br /&gt;
* multistage modules would be useful (see below) but not essential&lt;br /&gt;
* packaging is tricky, but can be postponed for now&lt;br /&gt;
* future developments: vmtk through Tcl, or vmtk through Python through Tcl&lt;br /&gt;
&lt;br /&gt;
=== Modules in localized space ===&lt;br /&gt;
* the rationale is to give command line modules a chance to run in a space where images are oriented as X Y Z (i.e. fully specified by a vtkImageData) but still have correct information available as to image origin, spacing and up/down, left/right, front/back consistency. &lt;br /&gt;
* the solution implemented in Boston consists in computing the transform from the localized space (the XYZ one) to Slicer's RAS for the first image in the CLI. All other CLI arguments (images, surfaces, fiducials and ROIs) are transformed using that transform before being written to command line. Upon completion, Slicer reads the results (which have been generated in localized space) and puts them in the scene as children of the RAStoLocal transform. &lt;br /&gt;
* nicer (more general) solution: there should be a localization mechanism by which Slicer3 creates a miniscene relative to a transformable node (image, model, transform, etc) and runs the module using that miniscene. This involves that all inputs, fiducials, ROIs, etc are first transformed to that miniscene root transform node. The outputs would also be reimported as children of the miniscene. &lt;br /&gt;
** if the CLI module is MRML-aware, Slicer3 will let the module deal with the mini scene&lt;br /&gt;
** if the CLI module is not MRML-aware, Slicer3 will take care of hardening the transforms up to the miniscene's root on the images, surfaces, fiducials, etc, exporting the hardened nodes (which are now direct descendants of the miniscene root), reimporting the results and transferring the mini scene contents to the main scene. &lt;br /&gt;
&lt;br /&gt;
=== Hardening transforms ===&lt;br /&gt;
&lt;br /&gt;
* a user should be able to harden transforms on nodes. In the MRML tree, if a user moves a node and changes its parent (say, from a parent trasform to root), this can have two different meanings:&lt;br /&gt;
** the basis changes, the data doesn't (the way it works now): the effect is that the node changes its position and orientation in the 3D window. &lt;br /&gt;
** the basis doesn't change, the data does: the effect is now that the position and orientation of the node are unchanged, but the node is now child of a different transform (this is what I'd call hardening). This is essential for non-MRML aware command line modules: e.g. if an input image is a child of some transform, it should be hardened (i.e. the IJKToRAS should be composed with the parent transform) before it's written to command line.&lt;br /&gt;
&lt;br /&gt;
=== Output fiducials ===&lt;br /&gt;
&lt;br /&gt;
* currently outputs can be data (images, models) and transforms. However, I also see a need for output fiducials (and ROIs). For example, a module could run in two stages: 1) identification of feature points; 2) operation performed on the feature points. Between 1) and 2) the user should be able to manipulate the fiducials (here I'm thinking at centerline computation: 1) could identify possible endpoints, 2) could trace centerlines between user-selected pairs of enpoints). Therefore, 1) should spit fiducials (with text) as output. &lt;br /&gt;
* output fiducials with text to be placed in scene: probably either through a vtkMRMLFiducialStorageNode that outputs a vtp file or through an XML data structure sent to output as a file or on stdout; the solution of XML description in a XML file is probably the best.&lt;br /&gt;
&lt;br /&gt;
=== Python ===&lt;br /&gt;
* write some sample modules;&lt;br /&gt;
* extend scripted modules to Python?&lt;br /&gt;
&lt;br /&gt;
=== DBPs ===&lt;br /&gt;
&lt;br /&gt;
* vascular (vmtk): segmentation, analysis, meshing, CFD for atherosclerosis, cerebral aneurysms, AAAs.&lt;br /&gt;
* segmentation and registration in PKD (polycystic kidney disease);&lt;br /&gt;
* functional renal imaging;&lt;br /&gt;
* functional brain imaging;&lt;br /&gt;
&lt;br /&gt;
=== Multistage modules ===&lt;br /&gt;
&lt;br /&gt;
Below is a thread on the mailing list on multistage modules. The discussion took place in Boston.&lt;br /&gt;
&lt;br /&gt;
It's sorted according to positive time.&lt;br /&gt;
&lt;br /&gt;
==== Luca ====&lt;br /&gt;
&lt;br /&gt;
Hi everyone,&lt;br /&gt;
I've got a couple of thoughts regarding command line modules.&lt;br /&gt;
Currently Slicer processes command line modules by looking in the  modules directory, choosing files that could either be executables or  shared libraries, peeking into them to see if they are well behaved  and later querying them for their XML description.&lt;br /&gt;
Another possible design (somewhat closer to what Paraview uses) could  have been to have executables (or shared libraries) accompanied by  XML files containing the description of both the executable (or the  shared library) and the GUI parameters.&lt;br /&gt;
The disadvantage would have been to have two files per plugin instead  of one. The advantages would be avoiding peeking into executables or  shared libraries (the XML file could contain that information  already), possibly also speeding up module discovery times. Another  advantage would be making it easier to add other kinds of command  line modules (I'm thinking about Python classes) without messing too  much with the module discovery phase.&lt;br /&gt;
This solution would be come with an additional advantage: multi- staged command line modules.&lt;br /&gt;
Very often a module has the need of doing some processing, asking the  user for info, then processing, then asking for info, and so on.&lt;br /&gt;
This is now possible in Slicer by breaking up a program in several  command line modules, but it would be neat to have a tabbed or wizard  GUI that guides you through the process.&lt;br /&gt;
What I'm thinking is that a single command line module plugin could  be made up of several executables called at each step of a wizard  built using the XML file.&lt;br /&gt;
Separating XML descriptions and executables (or shared libraries)  would make this easier, since one XML file could contain a reference  to several executables, while the current design of asking the  executable for its XML description would make this more complicated.&lt;br /&gt;
Just to clarify: it's not my intention to spread confusion and mess  with a solid and already well established design, but I figured I  would share this thoughts.&lt;br /&gt;
Thanks and see you soon&lt;br /&gt;
Luca&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Steve ====&lt;br /&gt;
&lt;br /&gt;
Hi Luca -&lt;br /&gt;
&lt;br /&gt;
That's a very interesting idea.... it seems to me that could coexist what the current paradigm nicely.&lt;br /&gt;
&lt;br /&gt;
There's another way of creating modules currently supported in slicer3, which we haven't pushed much because it's somewhat experimental.  I'm referring to the ScriptedModule approach used by the Editor module - it's analogous to the CommandLineModule in that modules are discovered at startup, but instead of defining the GUI indirectly with XML, the ScriptedModule can use the tcl API to create it's own GUI and interact with MRML directly.  But I like what you are proposing too because it can retain more of the flexibility to run as either command line tools or as module.&lt;br /&gt;
&lt;br /&gt;
It'll be fun to discuss these options when we get together.&lt;br /&gt;
&lt;br /&gt;
-Steve&lt;br /&gt;
&lt;br /&gt;
==== Bill ====&lt;br /&gt;
&lt;br /&gt;
Interesting ideas, Luca!&lt;br /&gt;
&lt;br /&gt;
I have found myself wanting a bit more interactivity in the command-line&lt;br /&gt;
modules, too. My ambitions are not as lofty as Luca's, however. It would&lt;br /&gt;
be nice to have an input parameter be a 2-way parameter, and to have&lt;br /&gt;
another special execution mode run from the command line so that the&lt;br /&gt;
module could accept the input parameter values, compute some value that&lt;br /&gt;
derived from these inputs, set the value of one or more of the 2-way&lt;br /&gt;
parameters, and then return to Slicer and have Slicer display the&lt;br /&gt;
computed values. This could be mediated by one or more new XML&lt;br /&gt;
command-line options like &amp;lt;cmd&amp;gt;update-params&amp;lt;/cmd&amp;gt; or some such.&lt;br /&gt;
&lt;br /&gt;
Another thing that I have wanted is some more flexibility in how the GUI&lt;br /&gt;
is built for command-line modules. I am working on an application that&lt;br /&gt;
would really benefit from having sliders in the GUI, but if I read the&lt;br /&gt;
Execution Model docs correctly, that only works for built-in modules,&lt;br /&gt;
not for command line modules.&lt;br /&gt;
&lt;br /&gt;
Finally, and this is a biggy -- I wonder if it would be possible to&lt;br /&gt;
implement the interface between Slicer3 and the command line modules so&lt;br /&gt;
that parameters and data could be passed in memory instead of in&lt;br /&gt;
temporary files on disk? This might be possible if pipes are substituted&lt;br /&gt;
for disk files; the API for reading and writing to pipes is pretty&lt;br /&gt;
similar to file I/O, and most systems implement pipes as shared memory&lt;br /&gt;
transfer. Just a thought.&lt;br /&gt;
&lt;br /&gt;
-Bill Leue&lt;br /&gt;
&lt;br /&gt;
==== Raul ====&lt;br /&gt;
&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;br /&gt;
I want to join to the great ideas of Luca and Bill to extend the &lt;br /&gt;
interactivity of the command-line-module.&lt;br /&gt;
In the same direction, it would be nice to be able to have more control &lt;br /&gt;
(for projects that required some advanced customization) before and &lt;br /&gt;
after the module execution in the Slicer execution environment. For &lt;br /&gt;
example, for tensors, it would be great to have the chance to set up &lt;br /&gt;
MRML nodes according to the outputs to assigned a mask and a DWI to the &lt;br /&gt;
tensor MRML node.&lt;br /&gt;
This would equate to be able to prescribe two virtual methods, &lt;br /&gt;
BeforeUpdate and AfterUpdate, from the XML description that would &lt;br /&gt;
generate the appropriate code in the Command Line Interface part. I'm &lt;br /&gt;
thinking something like:&lt;br /&gt;
&amp;lt;code, method=AfterUpdate&amp;gt;&lt;br /&gt;
&amp;lt;method&amp;gt;&lt;br /&gt;
//output1Node is a vtkMRMLDiffusionTensorNode&lt;br /&gt;
output1Node-&amp;gt;SetAndObserveDiffusionWeightedVolume(inputNode-&amp;gt;GetID());&lt;br /&gt;
&amp;lt;/method&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
/Raul&lt;br /&gt;
&lt;br /&gt;
= Misc comments =&lt;br /&gt;
&lt;br /&gt;
* Transforms and CLI: &lt;br /&gt;
** the rationale is to give command line modules a chance not to worry about transforms but still have correct information available as to spacing and up/down, left/right, front/back consistency&lt;br /&gt;
** the image passed to a command line module should be in normalized orientation space, i.e.: real origin, real spacing, &lt;br /&gt;
** reference node specified in XML (either tag of the reference node or tag of child nodes to the reference - the latter allows many references in the same command line). Images in normalized orientation space.&lt;br /&gt;
** the reference transform should be just a rigid transformation bringing the axes to XYZ (by looking at projections, but not necessarily). Therefore, from the node transform, a RASToLocalMatrix should be extracted, containing only the cosines that bring the axes to XYZ.&lt;br /&gt;
** for each XML node, specify what's its reference node. The default is patient space (identity matrix), but in general it could be another node. So the current node matrix should be multiplied by the inverse of the reference node matrix before being written out. Correspondingly, when the command line module has executed, all results have to be multiplied by the corresponding reference node matrix. A reference node could be the node itself, meaning that the node transform wil be multiplied by the inverse of its reference transform.&lt;br /&gt;
** find ways to harden transforms for specific MRML nodes&lt;br /&gt;
** in the end: the writer of a command line module or Python scripted module etc. has to be put in the condition of not knowing anything about transforms, and still deal with legal vtkImageData objects (with their own spacing and right-handedness)&lt;br /&gt;
&lt;br /&gt;
* Multi-stage CLI:&lt;br /&gt;
** wizard or tabbed interface with content generated one page per command line module, and user control is returned from one page to the next.&lt;br /&gt;
** one XML that puts command line modules together. This way command line modules can be either used alone or in a wizard.&lt;br /&gt;
** change the way CLI are specified: XML files are discovered first, each XML describes how's the module is going to be (executable, shared library, Python class, etc). This saves time for module discovery (at least on OSX), and (as suggested by Raoul) it makes it easy for a developer to know how that CLI is going to behave and to develop against it.&lt;br /&gt;
&lt;br /&gt;
* Fix vtkITK CMakeLists.txt (generate vtkITKTCL.so separately from vtkITK.so).&lt;br /&gt;
&lt;br /&gt;
* XML module GUI:&lt;br /&gt;
** give possibility to build a GUI from XML in ScriptedModules (either from Tcl or Python) or even everywhere in Slicer3, even from C++.&lt;br /&gt;
&lt;br /&gt;
* Python: &lt;br /&gt;
** try wrapping VTK. What happens when Python through Tcl is used and ShallowCopy to a true VTK module is called?&lt;br /&gt;
&lt;br /&gt;
* Annotation widget&lt;br /&gt;
** do it for command line modules (like: put this string at this point in the scene)&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=User:Lantiga&amp;diff=33202</id>
		<title>User:Lantiga</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=User:Lantiga&amp;diff=33202"/>
		<updated>2008-12-10T19:43:22Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 2009 Winter project week ==&lt;br /&gt;
&lt;br /&gt;
* Projects&lt;br /&gt;
** [[2009_Winter_Project_Week_Slicer_VMTK | Slicer VMTK]]&lt;br /&gt;
** [[2009_Winter_Project_Week_Python | Python]]&lt;br /&gt;
&lt;br /&gt;
* Breakouts&lt;br /&gt;
** Wed, Jan 7, 1.00pm - 3.00pm: Python Modules (with Demian Wasserman)&lt;br /&gt;
&lt;br /&gt;
* Presentations&lt;br /&gt;
** Thu, Jan 8, 11.30am - 11.45am: Collaborations: Mario Negri Institute&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Progress in 2008 ==&lt;br /&gt;
&lt;br /&gt;
The NAMIC - Mario Negri Institute external collaboration has brought the following contributions to Slicer and the NAMIC kit:&lt;br /&gt;
&lt;br /&gt;
* Python in Slicer&lt;br /&gt;
** background: in 2007, Dan Blezek produced the first implementation of Python interface in Slicer, providing a method to access Slicer instances from Python through Tcl.&lt;br /&gt;
** during the 2008 January project week in SLC, several sample Python command-line (i.e. non-interactive) modules have been implemented, and the vtkScriptedModule module has been extended to handle Python in addition to Tcl as a scripting language. This allowed the implementation of interactive modules in Python. &lt;br /&gt;
** during the 2008 June project week in Boston, the Python interface has been largely improved (keeping Dan's original code as the core), in order to provide Slicer Python objects as real Python class instances, rather than thin wrappers around Tcl objects. This way, coding Python modules has become very close to coding Python-wrapped VTK.&lt;br /&gt;
** during August 2008, the Python/Numpy interface has been improved, allowing seamless integration of Numpy objects within the Slicer Python interface.&lt;br /&gt;
&lt;br /&gt;
* VMTK Slicer&lt;br /&gt;
** background: during 2007, functionality for turning vmtk command lines into Slicer command-line modules had been implemented. However, need for interactive modules based on vmtk was still needed.&lt;br /&gt;
** during 2008, a first implementation of some of the interactive components of VMTK segmentation has been created, although no code has been committed to the sandbox yet. Rather, this work will be integrated with the work of Daniel Haehn during the January 2009 project week in SLC. In this context, the addition of a vtkMRMLLevelSet node will be proposed (derived from vtkMRMLScalarVolumeNode with a poly data display node).&lt;br /&gt;
** in the meantime, VMTK has been largely improved and now provides vessel enhancement and surface and volume mesh generation capabilities. Therefore, the integration of VMTK in Slicer will readily bring these functionalities to Slicer. In addition, the Mario Negri Institute has implemented and validated a computational fluid dynamics solver that could be interfaced with Slicer and the NAMIC kit.&lt;br /&gt;
&lt;br /&gt;
* ITK&lt;br /&gt;
** during the first half of 2008, the extension of the level set framework to (moderately) anisotropic voxel spacings has been committed to ITK. Work is underway to extend the sparse field level set framework to severely anisotropic spacings.&lt;br /&gt;
** during August 2008, a first draft implementation of a modular level set framework with pluggable terms has been coded, and will tentatively be commited to the NAMIC sandbox during the January 2009 project week.&lt;br /&gt;
&lt;br /&gt;
* Project weeks&lt;br /&gt;
** during the 2008 January AHM in SLC, a presentation was given at the [[2008_Winter_Project_Week_Geometry_and_Topology_processing_of_Meshes | Geometry and Topology Processing of Meshes]] breakout session.&lt;br /&gt;
&lt;br /&gt;
* NAMIC Kit&lt;br /&gt;
** the adoption of the NAMIC Kit within the [http://www.robocast.eu ROBOCAST] project, funded by the European Commission, has been pushed forward, and it is now official.&lt;br /&gt;
** the development of a Slicer-based pre-operative planning workflow is underway at the University of Verona, under the guide of Dr. Roberto Foroni.&lt;br /&gt;
&lt;br /&gt;
== Extending ITK finite difference and level set filters to anisotropic spacing ==&lt;br /&gt;
&lt;br /&gt;
This is the (tentative) list of classes that assume that spacing is isotropic (i.e. they give incorrect results for anisotropic spacings).&lt;br /&gt;
The plan is to go in and extend them to properly account for anisotropic spacings. This addresses BUG [http://public.kitware.com/Bug/view.php?id=6156 ITK 6156].&lt;br /&gt;
&lt;br /&gt;
* Insight/Code/Common:&lt;br /&gt;
** itkLevelSetFunction - FIXED&lt;br /&gt;
** itkSegmentationLevelSetFunction - FIXED&lt;br /&gt;
&lt;br /&gt;
* Insight/Code/BasicFilters:&lt;br /&gt;
** itkLevelSetFunctionWithRefitTerm&lt;br /&gt;
** itkNormalVectorDiffusionFunction&lt;br /&gt;
** itkParallelSparseFieldLevelSetImageFilter&lt;br /&gt;
** itkSparseFieldFourthOrderLevelSetImageFilter&lt;br /&gt;
** itkSparseFieldLevelSetImageFilter - FIXED&lt;br /&gt;
&lt;br /&gt;
Insight/Code/Algorithms:&lt;br /&gt;
** itkBinaryMinMaxCurvatureFlowFunction&lt;br /&gt;
** tkCurvatureFlowFunction - FIXED&lt;br /&gt;
** itkLevelSetNeighborhoodExtractor&lt;br /&gt;
** itkLevelSetVelocityNeighborhoodExtractor&lt;br /&gt;
** itkReinitializeLevelSetImageFilter&lt;br /&gt;
** itkShapePriorSegmentationLevelSetFunction&lt;br /&gt;
&lt;br /&gt;
== 2008 Winter Project Week ==&lt;br /&gt;
&lt;br /&gt;
* Python modules: Python support, existing modules and new modules&lt;br /&gt;
* Transform hardening in MRML (should be finished on a local copy before the project week)&lt;br /&gt;
* Localized command line modules using MRML transform hardening&lt;br /&gt;
* Breakout: Geometry and Topology processing of Meshes&lt;br /&gt;
* vmtk module&lt;br /&gt;
&lt;br /&gt;
== Python modules ==&lt;br /&gt;
&lt;br /&gt;
Below is a list of Python modules that will be implemented using the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation:Python Python script plugin] functionality.&lt;br /&gt;
&lt;br /&gt;
===Done===&lt;br /&gt;
* SurfaceConnectivity.py (color by connected regions or extract the connected surface closest to a fiducial) (issue: crash with more than one fiducial on the Mac?)&lt;br /&gt;
* SurfaceToolbox.py (decimation + smoothing + normals + cleaner, with individual &amp;quot;Enable&amp;quot; switches)&lt;br /&gt;
* PythonScript.py (takes a surface and/or an image, runs Python code on it loading it from a file, and output the result. Fast way of using Slicer through Python and prototyping modules) (why does it fail with multiple inputs/outputs on the Mac?)&lt;br /&gt;
* GradientAnisotropicDiffusion.py (by Dan)&lt;br /&gt;
* SurfaceICPRegistration.py&lt;br /&gt;
&lt;br /&gt;
===In the works===&lt;br /&gt;
* SurfaceTransformHardening.py&lt;br /&gt;
&lt;br /&gt;
===Ideas===&lt;br /&gt;
* MarchingCubes.py&lt;br /&gt;
* ArrayCalculator.py&lt;br /&gt;
* Glyphs.py&lt;br /&gt;
* ShortestPath.py (use new Djikstra path)&lt;br /&gt;
* Reference system handling&lt;br /&gt;
&lt;br /&gt;
== Ideas for Slicer3 ==&lt;br /&gt;
&lt;br /&gt;
=== vmtk ===&lt;br /&gt;
&lt;br /&gt;
* figure out an official way to use vmtk within slicer and provide concrete examples and several modules:&lt;br /&gt;
** vessel enhancement&lt;br /&gt;
** vessel segmentation&lt;br /&gt;
** geometric analysis&lt;br /&gt;
** meshing for CFD&lt;br /&gt;
** visualization of CFD data&lt;br /&gt;
* check if any of the vmtk C++ classes can be used for stand-alone C++ modules  (e.g. centerline computation, finite elements)&lt;br /&gt;
* running modules in a localized space is vital: one solution has been implemented in Boston, but a more general approach would have a broader impact (see below)&lt;br /&gt;
* output fiducials would be useful (see below) but not vital for vmtk integration, can be circumvented using world points&lt;br /&gt;
* multistage modules would be useful (see below) but not essential&lt;br /&gt;
* packaging is tricky, but can be postponed for now&lt;br /&gt;
* future developments: vmtk through Tcl, or vmtk through Python through Tcl&lt;br /&gt;
&lt;br /&gt;
=== Modules in localized space ===&lt;br /&gt;
* the rationale is to give command line modules a chance to run in a space where images are oriented as X Y Z (i.e. fully specified by a vtkImageData) but still have correct information available as to image origin, spacing and up/down, left/right, front/back consistency. &lt;br /&gt;
* the solution implemented in Boston consists in computing the transform from the localized space (the XYZ one) to Slicer's RAS for the first image in the CLI. All other CLI arguments (images, surfaces, fiducials and ROIs) are transformed using that transform before being written to command line. Upon completion, Slicer reads the results (which have been generated in localized space) and puts them in the scene as children of the RAStoLocal transform. &lt;br /&gt;
* nicer (more general) solution: there should be a localization mechanism by which Slicer3 creates a miniscene relative to a transformable node (image, model, transform, etc) and runs the module using that miniscene. This involves that all inputs, fiducials, ROIs, etc are first transformed to that miniscene root transform node. The outputs would also be reimported as children of the miniscene. &lt;br /&gt;
** if the CLI module is MRML-aware, Slicer3 will let the module deal with the mini scene&lt;br /&gt;
** if the CLI module is not MRML-aware, Slicer3 will take care of hardening the transforms up to the miniscene's root on the images, surfaces, fiducials, etc, exporting the hardened nodes (which are now direct descendants of the miniscene root), reimporting the results and transferring the mini scene contents to the main scene. &lt;br /&gt;
&lt;br /&gt;
=== Hardening transforms ===&lt;br /&gt;
&lt;br /&gt;
* a user should be able to harden transforms on nodes. In the MRML tree, if a user moves a node and changes its parent (say, from a parent trasform to root), this can have two different meanings:&lt;br /&gt;
** the basis changes, the data doesn't (the way it works now): the effect is that the node changes its position and orientation in the 3D window. &lt;br /&gt;
** the basis doesn't change, the data does: the effect is now that the position and orientation of the node are unchanged, but the node is now child of a different transform (this is what I'd call hardening). This is essential for non-MRML aware command line modules: e.g. if an input image is a child of some transform, it should be hardened (i.e. the IJKToRAS should be composed with the parent transform) before it's written to command line.&lt;br /&gt;
&lt;br /&gt;
=== Output fiducials ===&lt;br /&gt;
&lt;br /&gt;
* currently outputs can be data (images, models) and transforms. However, I also see a need for output fiducials (and ROIs). For example, a module could run in two stages: 1) identification of feature points; 2) operation performed on the feature points. Between 1) and 2) the user should be able to manipulate the fiducials (here I'm thinking at centerline computation: 1) could identify possible endpoints, 2) could trace centerlines between user-selected pairs of enpoints). Therefore, 1) should spit fiducials (with text) as output. &lt;br /&gt;
* output fiducials with text to be placed in scene: probably either through a vtkMRMLFiducialStorageNode that outputs a vtp file or through an XML data structure sent to output as a file or on stdout; the solution of XML description in a XML file is probably the best.&lt;br /&gt;
&lt;br /&gt;
=== Python ===&lt;br /&gt;
* write some sample modules;&lt;br /&gt;
* extend scripted modules to Python?&lt;br /&gt;
&lt;br /&gt;
=== DBPs ===&lt;br /&gt;
&lt;br /&gt;
* vascular (vmtk): segmentation, analysis, meshing, CFD for atherosclerosis, cerebral aneurysms, AAAs.&lt;br /&gt;
* segmentation and registration in PKD (polycystic kidney disease);&lt;br /&gt;
* functional renal imaging;&lt;br /&gt;
* functional brain imaging;&lt;br /&gt;
&lt;br /&gt;
=== Multistage modules ===&lt;br /&gt;
&lt;br /&gt;
Below is a thread on the mailing list on multistage modules. The discussion took place in Boston.&lt;br /&gt;
&lt;br /&gt;
It's sorted according to positive time.&lt;br /&gt;
&lt;br /&gt;
==== Luca ====&lt;br /&gt;
&lt;br /&gt;
Hi everyone,&lt;br /&gt;
I've got a couple of thoughts regarding command line modules.&lt;br /&gt;
Currently Slicer processes command line modules by looking in the  modules directory, choosing files that could either be executables or  shared libraries, peeking into them to see if they are well behaved  and later querying them for their XML description.&lt;br /&gt;
Another possible design (somewhat closer to what Paraview uses) could  have been to have executables (or shared libraries) accompanied by  XML files containing the description of both the executable (or the  shared library) and the GUI parameters.&lt;br /&gt;
The disadvantage would have been to have two files per plugin instead  of one. The advantages would be avoiding peeking into executables or  shared libraries (the XML file could contain that information  already), possibly also speeding up module discovery times. Another  advantage would be making it easier to add other kinds of command  line modules (I'm thinking about Python classes) without messing too  much with the module discovery phase.&lt;br /&gt;
This solution would be come with an additional advantage: multi- staged command line modules.&lt;br /&gt;
Very often a module has the need of doing some processing, asking the  user for info, then processing, then asking for info, and so on.&lt;br /&gt;
This is now possible in Slicer by breaking up a program in several  command line modules, but it would be neat to have a tabbed or wizard  GUI that guides you through the process.&lt;br /&gt;
What I'm thinking is that a single command line module plugin could  be made up of several executables called at each step of a wizard  built using the XML file.&lt;br /&gt;
Separating XML descriptions and executables (or shared libraries)  would make this easier, since one XML file could contain a reference  to several executables, while the current design of asking the  executable for its XML description would make this more complicated.&lt;br /&gt;
Just to clarify: it's not my intention to spread confusion and mess  with a solid and already well established design, but I figured I  would share this thoughts.&lt;br /&gt;
Thanks and see you soon&lt;br /&gt;
Luca&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Steve ====&lt;br /&gt;
&lt;br /&gt;
Hi Luca -&lt;br /&gt;
&lt;br /&gt;
That's a very interesting idea.... it seems to me that could coexist what the current paradigm nicely.&lt;br /&gt;
&lt;br /&gt;
There's another way of creating modules currently supported in slicer3, which we haven't pushed much because it's somewhat experimental.  I'm referring to the ScriptedModule approach used by the Editor module - it's analogous to the CommandLineModule in that modules are discovered at startup, but instead of defining the GUI indirectly with XML, the ScriptedModule can use the tcl API to create it's own GUI and interact with MRML directly.  But I like what you are proposing too because it can retain more of the flexibility to run as either command line tools or as module.&lt;br /&gt;
&lt;br /&gt;
It'll be fun to discuss these options when we get together.&lt;br /&gt;
&lt;br /&gt;
-Steve&lt;br /&gt;
&lt;br /&gt;
==== Bill ====&lt;br /&gt;
&lt;br /&gt;
Interesting ideas, Luca!&lt;br /&gt;
&lt;br /&gt;
I have found myself wanting a bit more interactivity in the command-line&lt;br /&gt;
modules, too. My ambitions are not as lofty as Luca's, however. It would&lt;br /&gt;
be nice to have an input parameter be a 2-way parameter, and to have&lt;br /&gt;
another special execution mode run from the command line so that the&lt;br /&gt;
module could accept the input parameter values, compute some value that&lt;br /&gt;
derived from these inputs, set the value of one or more of the 2-way&lt;br /&gt;
parameters, and then return to Slicer and have Slicer display the&lt;br /&gt;
computed values. This could be mediated by one or more new XML&lt;br /&gt;
command-line options like &amp;lt;cmd&amp;gt;update-params&amp;lt;/cmd&amp;gt; or some such.&lt;br /&gt;
&lt;br /&gt;
Another thing that I have wanted is some more flexibility in how the GUI&lt;br /&gt;
is built for command-line modules. I am working on an application that&lt;br /&gt;
would really benefit from having sliders in the GUI, but if I read the&lt;br /&gt;
Execution Model docs correctly, that only works for built-in modules,&lt;br /&gt;
not for command line modules.&lt;br /&gt;
&lt;br /&gt;
Finally, and this is a biggy -- I wonder if it would be possible to&lt;br /&gt;
implement the interface between Slicer3 and the command line modules so&lt;br /&gt;
that parameters and data could be passed in memory instead of in&lt;br /&gt;
temporary files on disk? This might be possible if pipes are substituted&lt;br /&gt;
for disk files; the API for reading and writing to pipes is pretty&lt;br /&gt;
similar to file I/O, and most systems implement pipes as shared memory&lt;br /&gt;
transfer. Just a thought.&lt;br /&gt;
&lt;br /&gt;
-Bill Leue&lt;br /&gt;
&lt;br /&gt;
==== Raul ====&lt;br /&gt;
&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;br /&gt;
I want to join to the great ideas of Luca and Bill to extend the &lt;br /&gt;
interactivity of the command-line-module.&lt;br /&gt;
In the same direction, it would be nice to be able to have more control &lt;br /&gt;
(for projects that required some advanced customization) before and &lt;br /&gt;
after the module execution in the Slicer execution environment. For &lt;br /&gt;
example, for tensors, it would be great to have the chance to set up &lt;br /&gt;
MRML nodes according to the outputs to assigned a mask and a DWI to the &lt;br /&gt;
tensor MRML node.&lt;br /&gt;
This would equate to be able to prescribe two virtual methods, &lt;br /&gt;
BeforeUpdate and AfterUpdate, from the XML description that would &lt;br /&gt;
generate the appropriate code in the Command Line Interface part. I'm &lt;br /&gt;
thinking something like:&lt;br /&gt;
&amp;lt;code, method=AfterUpdate&amp;gt;&lt;br /&gt;
&amp;lt;method&amp;gt;&lt;br /&gt;
//output1Node is a vtkMRMLDiffusionTensorNode&lt;br /&gt;
output1Node-&amp;gt;SetAndObserveDiffusionWeightedVolume(inputNode-&amp;gt;GetID());&lt;br /&gt;
&amp;lt;/method&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
/Raul&lt;br /&gt;
&lt;br /&gt;
= Misc comments =&lt;br /&gt;
&lt;br /&gt;
* Transforms and CLI: &lt;br /&gt;
** the rationale is to give command line modules a chance not to worry about transforms but still have correct information available as to spacing and up/down, left/right, front/back consistency&lt;br /&gt;
** the image passed to a command line module should be in normalized orientation space, i.e.: real origin, real spacing, &lt;br /&gt;
** reference node specified in XML (either tag of the reference node or tag of child nodes to the reference - the latter allows many references in the same command line). Images in normalized orientation space.&lt;br /&gt;
** the reference transform should be just a rigid transformation bringing the axes to XYZ (by looking at projections, but not necessarily). Therefore, from the node transform, a RASToLocalMatrix should be extracted, containing only the cosines that bring the axes to XYZ.&lt;br /&gt;
** for each XML node, specify what's its reference node. The default is patient space (identity matrix), but in general it could be another node. So the current node matrix should be multiplied by the inverse of the reference node matrix before being written out. Correspondingly, when the command line module has executed, all results have to be multiplied by the corresponding reference node matrix. A reference node could be the node itself, meaning that the node transform wil be multiplied by the inverse of its reference transform.&lt;br /&gt;
** find ways to harden transforms for specific MRML nodes&lt;br /&gt;
** in the end: the writer of a command line module or Python scripted module etc. has to be put in the condition of not knowing anything about transforms, and still deal with legal vtkImageData objects (with their own spacing and right-handedness)&lt;br /&gt;
&lt;br /&gt;
* Multi-stage CLI:&lt;br /&gt;
** wizard or tabbed interface with content generated one page per command line module, and user control is returned from one page to the next.&lt;br /&gt;
** one XML that puts command line modules together. This way command line modules can be either used alone or in a wizard.&lt;br /&gt;
** change the way CLI are specified: XML files are discovered first, each XML describes how's the module is going to be (executable, shared library, Python class, etc). This saves time for module discovery (at least on OSX), and (as suggested by Raoul) it makes it easy for a developer to know how that CLI is going to behave and to develop against it.&lt;br /&gt;
&lt;br /&gt;
* Fix vtkITK CMakeLists.txt (generate vtkITKTCL.so separately from vtkITK.so).&lt;br /&gt;
&lt;br /&gt;
* XML module GUI:&lt;br /&gt;
** give possibility to build a GUI from XML in ScriptedModules (either from Tcl or Python) or even everywhere in Slicer3, even from C++.&lt;br /&gt;
&lt;br /&gt;
* Python: &lt;br /&gt;
** try wrapping VTK. What happens when Python through Tcl is used and ShallowCopy to a true VTK module is called?&lt;br /&gt;
&lt;br /&gt;
* Annotation widget&lt;br /&gt;
** do it for command line modules (like: put this string at this point in the scene)&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=User:Lantiga&amp;diff=33198</id>
		<title>User:Lantiga</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=User:Lantiga&amp;diff=33198"/>
		<updated>2008-12-10T19:36:25Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Progress in 2008 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Progress in 2008 ==&lt;br /&gt;
&lt;br /&gt;
The NAMIC - Mario Negri Institute external collaboration has brought the following contributions to Slicer and the NAMIC kit:&lt;br /&gt;
&lt;br /&gt;
* Python in Slicer&lt;br /&gt;
** background: in 2007, Dan Blezek produced the first implementation of Python interface in Slicer, providing a method to access Slicer instances from Python through Tcl.&lt;br /&gt;
** during the 2008 January project week in SLC, several sample Python command-line (i.e. non-interactive) modules have been implemented, and the vtkScriptedModule module has been extended to handle Python in addition to Tcl as a scripting language. This allowed the implementation of interactive modules in Python. &lt;br /&gt;
** during the 2008 June project week in Boston, the Python interface has been largely improved (keeping Dan's original code as the core), in order to provide Slicer Python objects as real Python class instances, rather than thin wrappers around Tcl objects. This way, coding Python modules has become very close to coding Python-wrapped VTK.&lt;br /&gt;
** during August 2008, the Python/Numpy interface has been improved, allowing seamless integration of Numpy objects within the Slicer Python interface.&lt;br /&gt;
&lt;br /&gt;
* VMTK Slicer&lt;br /&gt;
** background: during 2007, functionality for turning vmtk command lines into Slicer command-line modules had been implemented. However, need for interactive modules based on vmtk was still needed.&lt;br /&gt;
** during 2008, a first implementation of some of the interactive components of VMTK segmentation has been created, although no code has been committed to the sandbox yet. Rather, this work will be integrated with the work of Daniel Haehn during the January 2009 project week in SLC. In this context, the addition of a vtkMRMLLevelSet node will be proposed (derived from vtkMRMLScalarVolumeNode with a poly data display node).&lt;br /&gt;
** in the meantime, VMTK has been largely improved and now provides vessel enhancement and surface and volume mesh generation capabilities. Therefore, the integration of VMTK in Slicer will readily bring these functionalities to Slicer. In addition, the Mario Negri Institute has implemented and validated a computational fluid dynamics solver that could be interfaced with Slicer and the NAMIC kit.&lt;br /&gt;
&lt;br /&gt;
* ITK&lt;br /&gt;
** during the first half of 2008, the extension of the level set framework to (moderately) anisotropic voxel spacings has been committed to ITK. Work is underway to extend the sparse field level set framework to severely anisotropic spacings.&lt;br /&gt;
** during August 2008, a first draft implementation of a modular level set framework with pluggable terms has been coded, and will tentatively be commited to the NAMIC sandbox during the January 2009 project week.&lt;br /&gt;
&lt;br /&gt;
* Project weeks&lt;br /&gt;
** during the 2008 January AHM in SLC, a presentation was given at the [[2008_Winter_Project_Week_Geometry_and_Topology_processing_of_Meshes | Geometry and Topology Processing of Meshes]] breakout session.&lt;br /&gt;
&lt;br /&gt;
* NAMIC Kit&lt;br /&gt;
** the adoption of the NAMIC Kit within the [http://www.robocast.eu ROBOCAST] project, funded by the European Commission, has been pushed forward, and it is now official.&lt;br /&gt;
** the development of a Slicer-based pre-operative planning workflow is underway at the University of Verona, under the guide of Dr. Roberto Foroni.&lt;br /&gt;
&lt;br /&gt;
== Extending ITK finite difference and level set filters to anisotropic spacing ==&lt;br /&gt;
&lt;br /&gt;
This is the (tentative) list of classes that assume that spacing is isotropic (i.e. they give incorrect results for anisotropic spacings).&lt;br /&gt;
The plan is to go in and extend them to properly account for anisotropic spacings. This addresses BUG [http://public.kitware.com/Bug/view.php?id=6156 ITK 6156].&lt;br /&gt;
&lt;br /&gt;
* Insight/Code/Common:&lt;br /&gt;
** itkLevelSetFunction - FIXED&lt;br /&gt;
** itkSegmentationLevelSetFunction - FIXED&lt;br /&gt;
&lt;br /&gt;
* Insight/Code/BasicFilters:&lt;br /&gt;
** itkLevelSetFunctionWithRefitTerm&lt;br /&gt;
** itkNormalVectorDiffusionFunction&lt;br /&gt;
** itkParallelSparseFieldLevelSetImageFilter&lt;br /&gt;
** itkSparseFieldFourthOrderLevelSetImageFilter&lt;br /&gt;
** itkSparseFieldLevelSetImageFilter - FIXED&lt;br /&gt;
&lt;br /&gt;
Insight/Code/Algorithms:&lt;br /&gt;
** itkBinaryMinMaxCurvatureFlowFunction&lt;br /&gt;
** tkCurvatureFlowFunction - FIXED&lt;br /&gt;
** itkLevelSetNeighborhoodExtractor&lt;br /&gt;
** itkLevelSetVelocityNeighborhoodExtractor&lt;br /&gt;
** itkReinitializeLevelSetImageFilter&lt;br /&gt;
** itkShapePriorSegmentationLevelSetFunction&lt;br /&gt;
&lt;br /&gt;
== 2008 Winter Project Week ==&lt;br /&gt;
&lt;br /&gt;
* Python modules: Python support, existing modules and new modules&lt;br /&gt;
* Transform hardening in MRML (should be finished on a local copy before the project week)&lt;br /&gt;
* Localized command line modules using MRML transform hardening&lt;br /&gt;
* Breakout: Geometry and Topology processing of Meshes&lt;br /&gt;
* vmtk module&lt;br /&gt;
&lt;br /&gt;
== Python modules ==&lt;br /&gt;
&lt;br /&gt;
Below is a list of Python modules that will be implemented using the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation:Python Python script plugin] functionality.&lt;br /&gt;
&lt;br /&gt;
===Done===&lt;br /&gt;
* SurfaceConnectivity.py (color by connected regions or extract the connected surface closest to a fiducial) (issue: crash with more than one fiducial on the Mac?)&lt;br /&gt;
* SurfaceToolbox.py (decimation + smoothing + normals + cleaner, with individual &amp;quot;Enable&amp;quot; switches)&lt;br /&gt;
* PythonScript.py (takes a surface and/or an image, runs Python code on it loading it from a file, and output the result. Fast way of using Slicer through Python and prototyping modules) (why does it fail with multiple inputs/outputs on the Mac?)&lt;br /&gt;
* GradientAnisotropicDiffusion.py (by Dan)&lt;br /&gt;
* SurfaceICPRegistration.py&lt;br /&gt;
&lt;br /&gt;
===In the works===&lt;br /&gt;
* SurfaceTransformHardening.py&lt;br /&gt;
&lt;br /&gt;
===Ideas===&lt;br /&gt;
* MarchingCubes.py&lt;br /&gt;
* ArrayCalculator.py&lt;br /&gt;
* Glyphs.py&lt;br /&gt;
* ShortestPath.py (use new Djikstra path)&lt;br /&gt;
* Reference system handling&lt;br /&gt;
&lt;br /&gt;
== Ideas for Slicer3 ==&lt;br /&gt;
&lt;br /&gt;
=== vmtk ===&lt;br /&gt;
&lt;br /&gt;
* figure out an official way to use vmtk within slicer and provide concrete examples and several modules:&lt;br /&gt;
** vessel enhancement&lt;br /&gt;
** vessel segmentation&lt;br /&gt;
** geometric analysis&lt;br /&gt;
** meshing for CFD&lt;br /&gt;
** visualization of CFD data&lt;br /&gt;
* check if any of the vmtk C++ classes can be used for stand-alone C++ modules  (e.g. centerline computation, finite elements)&lt;br /&gt;
* running modules in a localized space is vital: one solution has been implemented in Boston, but a more general approach would have a broader impact (see below)&lt;br /&gt;
* output fiducials would be useful (see below) but not vital for vmtk integration, can be circumvented using world points&lt;br /&gt;
* multistage modules would be useful (see below) but not essential&lt;br /&gt;
* packaging is tricky, but can be postponed for now&lt;br /&gt;
* future developments: vmtk through Tcl, or vmtk through Python through Tcl&lt;br /&gt;
&lt;br /&gt;
=== Modules in localized space ===&lt;br /&gt;
* the rationale is to give command line modules a chance to run in a space where images are oriented as X Y Z (i.e. fully specified by a vtkImageData) but still have correct information available as to image origin, spacing and up/down, left/right, front/back consistency. &lt;br /&gt;
* the solution implemented in Boston consists in computing the transform from the localized space (the XYZ one) to Slicer's RAS for the first image in the CLI. All other CLI arguments (images, surfaces, fiducials and ROIs) are transformed using that transform before being written to command line. Upon completion, Slicer reads the results (which have been generated in localized space) and puts them in the scene as children of the RAStoLocal transform. &lt;br /&gt;
* nicer (more general) solution: there should be a localization mechanism by which Slicer3 creates a miniscene relative to a transformable node (image, model, transform, etc) and runs the module using that miniscene. This involves that all inputs, fiducials, ROIs, etc are first transformed to that miniscene root transform node. The outputs would also be reimported as children of the miniscene. &lt;br /&gt;
** if the CLI module is MRML-aware, Slicer3 will let the module deal with the mini scene&lt;br /&gt;
** if the CLI module is not MRML-aware, Slicer3 will take care of hardening the transforms up to the miniscene's root on the images, surfaces, fiducials, etc, exporting the hardened nodes (which are now direct descendants of the miniscene root), reimporting the results and transferring the mini scene contents to the main scene. &lt;br /&gt;
&lt;br /&gt;
=== Hardening transforms ===&lt;br /&gt;
&lt;br /&gt;
* a user should be able to harden transforms on nodes. In the MRML tree, if a user moves a node and changes its parent (say, from a parent trasform to root), this can have two different meanings:&lt;br /&gt;
** the basis changes, the data doesn't (the way it works now): the effect is that the node changes its position and orientation in the 3D window. &lt;br /&gt;
** the basis doesn't change, the data does: the effect is now that the position and orientation of the node are unchanged, but the node is now child of a different transform (this is what I'd call hardening). This is essential for non-MRML aware command line modules: e.g. if an input image is a child of some transform, it should be hardened (i.e. the IJKToRAS should be composed with the parent transform) before it's written to command line.&lt;br /&gt;
&lt;br /&gt;
=== Output fiducials ===&lt;br /&gt;
&lt;br /&gt;
* currently outputs can be data (images, models) and transforms. However, I also see a need for output fiducials (and ROIs). For example, a module could run in two stages: 1) identification of feature points; 2) operation performed on the feature points. Between 1) and 2) the user should be able to manipulate the fiducials (here I'm thinking at centerline computation: 1) could identify possible endpoints, 2) could trace centerlines between user-selected pairs of enpoints). Therefore, 1) should spit fiducials (with text) as output. &lt;br /&gt;
* output fiducials with text to be placed in scene: probably either through a vtkMRMLFiducialStorageNode that outputs a vtp file or through an XML data structure sent to output as a file or on stdout; the solution of XML description in a XML file is probably the best.&lt;br /&gt;
&lt;br /&gt;
=== Python ===&lt;br /&gt;
* write some sample modules;&lt;br /&gt;
* extend scripted modules to Python?&lt;br /&gt;
&lt;br /&gt;
=== DBPs ===&lt;br /&gt;
&lt;br /&gt;
* vascular (vmtk): segmentation, analysis, meshing, CFD for atherosclerosis, cerebral aneurysms, AAAs.&lt;br /&gt;
* segmentation and registration in PKD (polycystic kidney disease);&lt;br /&gt;
* functional renal imaging;&lt;br /&gt;
* functional brain imaging;&lt;br /&gt;
&lt;br /&gt;
=== Multistage modules ===&lt;br /&gt;
&lt;br /&gt;
Below is a thread on the mailing list on multistage modules. The discussion took place in Boston.&lt;br /&gt;
&lt;br /&gt;
It's sorted according to positive time.&lt;br /&gt;
&lt;br /&gt;
==== Luca ====&lt;br /&gt;
&lt;br /&gt;
Hi everyone,&lt;br /&gt;
I've got a couple of thoughts regarding command line modules.&lt;br /&gt;
Currently Slicer processes command line modules by looking in the  modules directory, choosing files that could either be executables or  shared libraries, peeking into them to see if they are well behaved  and later querying them for their XML description.&lt;br /&gt;
Another possible design (somewhat closer to what Paraview uses) could  have been to have executables (or shared libraries) accompanied by  XML files containing the description of both the executable (or the  shared library) and the GUI parameters.&lt;br /&gt;
The disadvantage would have been to have two files per plugin instead  of one. The advantages would be avoiding peeking into executables or  shared libraries (the XML file could contain that information  already), possibly also speeding up module discovery times. Another  advantage would be making it easier to add other kinds of command  line modules (I'm thinking about Python classes) without messing too  much with the module discovery phase.&lt;br /&gt;
This solution would be come with an additional advantage: multi- staged command line modules.&lt;br /&gt;
Very often a module has the need of doing some processing, asking the  user for info, then processing, then asking for info, and so on.&lt;br /&gt;
This is now possible in Slicer by breaking up a program in several  command line modules, but it would be neat to have a tabbed or wizard  GUI that guides you through the process.&lt;br /&gt;
What I'm thinking is that a single command line module plugin could  be made up of several executables called at each step of a wizard  built using the XML file.&lt;br /&gt;
Separating XML descriptions and executables (or shared libraries)  would make this easier, since one XML file could contain a reference  to several executables, while the current design of asking the  executable for its XML description would make this more complicated.&lt;br /&gt;
Just to clarify: it's not my intention to spread confusion and mess  with a solid and already well established design, but I figured I  would share this thoughts.&lt;br /&gt;
Thanks and see you soon&lt;br /&gt;
Luca&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Steve ====&lt;br /&gt;
&lt;br /&gt;
Hi Luca -&lt;br /&gt;
&lt;br /&gt;
That's a very interesting idea.... it seems to me that could coexist what the current paradigm nicely.&lt;br /&gt;
&lt;br /&gt;
There's another way of creating modules currently supported in slicer3, which we haven't pushed much because it's somewhat experimental.  I'm referring to the ScriptedModule approach used by the Editor module - it's analogous to the CommandLineModule in that modules are discovered at startup, but instead of defining the GUI indirectly with XML, the ScriptedModule can use the tcl API to create it's own GUI and interact with MRML directly.  But I like what you are proposing too because it can retain more of the flexibility to run as either command line tools or as module.&lt;br /&gt;
&lt;br /&gt;
It'll be fun to discuss these options when we get together.&lt;br /&gt;
&lt;br /&gt;
-Steve&lt;br /&gt;
&lt;br /&gt;
==== Bill ====&lt;br /&gt;
&lt;br /&gt;
Interesting ideas, Luca!&lt;br /&gt;
&lt;br /&gt;
I have found myself wanting a bit more interactivity in the command-line&lt;br /&gt;
modules, too. My ambitions are not as lofty as Luca's, however. It would&lt;br /&gt;
be nice to have an input parameter be a 2-way parameter, and to have&lt;br /&gt;
another special execution mode run from the command line so that the&lt;br /&gt;
module could accept the input parameter values, compute some value that&lt;br /&gt;
derived from these inputs, set the value of one or more of the 2-way&lt;br /&gt;
parameters, and then return to Slicer and have Slicer display the&lt;br /&gt;
computed values. This could be mediated by one or more new XML&lt;br /&gt;
command-line options like &amp;lt;cmd&amp;gt;update-params&amp;lt;/cmd&amp;gt; or some such.&lt;br /&gt;
&lt;br /&gt;
Another thing that I have wanted is some more flexibility in how the GUI&lt;br /&gt;
is built for command-line modules. I am working on an application that&lt;br /&gt;
would really benefit from having sliders in the GUI, but if I read the&lt;br /&gt;
Execution Model docs correctly, that only works for built-in modules,&lt;br /&gt;
not for command line modules.&lt;br /&gt;
&lt;br /&gt;
Finally, and this is a biggy -- I wonder if it would be possible to&lt;br /&gt;
implement the interface between Slicer3 and the command line modules so&lt;br /&gt;
that parameters and data could be passed in memory instead of in&lt;br /&gt;
temporary files on disk? This might be possible if pipes are substituted&lt;br /&gt;
for disk files; the API for reading and writing to pipes is pretty&lt;br /&gt;
similar to file I/O, and most systems implement pipes as shared memory&lt;br /&gt;
transfer. Just a thought.&lt;br /&gt;
&lt;br /&gt;
-Bill Leue&lt;br /&gt;
&lt;br /&gt;
==== Raul ====&lt;br /&gt;
&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;br /&gt;
I want to join to the great ideas of Luca and Bill to extend the &lt;br /&gt;
interactivity of the command-line-module.&lt;br /&gt;
In the same direction, it would be nice to be able to have more control &lt;br /&gt;
(for projects that required some advanced customization) before and &lt;br /&gt;
after the module execution in the Slicer execution environment. For &lt;br /&gt;
example, for tensors, it would be great to have the chance to set up &lt;br /&gt;
MRML nodes according to the outputs to assigned a mask and a DWI to the &lt;br /&gt;
tensor MRML node.&lt;br /&gt;
This would equate to be able to prescribe two virtual methods, &lt;br /&gt;
BeforeUpdate and AfterUpdate, from the XML description that would &lt;br /&gt;
generate the appropriate code in the Command Line Interface part. I'm &lt;br /&gt;
thinking something like:&lt;br /&gt;
&amp;lt;code, method=AfterUpdate&amp;gt;&lt;br /&gt;
&amp;lt;method&amp;gt;&lt;br /&gt;
//output1Node is a vtkMRMLDiffusionTensorNode&lt;br /&gt;
output1Node-&amp;gt;SetAndObserveDiffusionWeightedVolume(inputNode-&amp;gt;GetID());&lt;br /&gt;
&amp;lt;/method&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
/Raul&lt;br /&gt;
&lt;br /&gt;
= Misc comments =&lt;br /&gt;
&lt;br /&gt;
* Transforms and CLI: &lt;br /&gt;
** the rationale is to give command line modules a chance not to worry about transforms but still have correct information available as to spacing and up/down, left/right, front/back consistency&lt;br /&gt;
** the image passed to a command line module should be in normalized orientation space, i.e.: real origin, real spacing, &lt;br /&gt;
** reference node specified in XML (either tag of the reference node or tag of child nodes to the reference - the latter allows many references in the same command line). Images in normalized orientation space.&lt;br /&gt;
** the reference transform should be just a rigid transformation bringing the axes to XYZ (by looking at projections, but not necessarily). Therefore, from the node transform, a RASToLocalMatrix should be extracted, containing only the cosines that bring the axes to XYZ.&lt;br /&gt;
** for each XML node, specify what's its reference node. The default is patient space (identity matrix), but in general it could be another node. So the current node matrix should be multiplied by the inverse of the reference node matrix before being written out. Correspondingly, when the command line module has executed, all results have to be multiplied by the corresponding reference node matrix. A reference node could be the node itself, meaning that the node transform wil be multiplied by the inverse of its reference transform.&lt;br /&gt;
** find ways to harden transforms for specific MRML nodes&lt;br /&gt;
** in the end: the writer of a command line module or Python scripted module etc. has to be put in the condition of not knowing anything about transforms, and still deal with legal vtkImageData objects (with their own spacing and right-handedness)&lt;br /&gt;
&lt;br /&gt;
* Multi-stage CLI:&lt;br /&gt;
** wizard or tabbed interface with content generated one page per command line module, and user control is returned from one page to the next.&lt;br /&gt;
** one XML that puts command line modules together. This way command line modules can be either used alone or in a wizard.&lt;br /&gt;
** change the way CLI are specified: XML files are discovered first, each XML describes how's the module is going to be (executable, shared library, Python class, etc). This saves time for module discovery (at least on OSX), and (as suggested by Raoul) it makes it easy for a developer to know how that CLI is going to behave and to develop against it.&lt;br /&gt;
&lt;br /&gt;
* Fix vtkITK CMakeLists.txt (generate vtkITKTCL.so separately from vtkITK.so).&lt;br /&gt;
&lt;br /&gt;
* XML module GUI:&lt;br /&gt;
** give possibility to build a GUI from XML in ScriptedModules (either from Tcl or Python) or even everywhere in Slicer3, even from C++.&lt;br /&gt;
&lt;br /&gt;
* Python: &lt;br /&gt;
** try wrapping VTK. What happens when Python through Tcl is used and ShallowCopy to a true VTK module is called?&lt;br /&gt;
&lt;br /&gt;
* Annotation widget&lt;br /&gt;
** do it for command line modules (like: put this string at this point in the scene)&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=User:Lantiga&amp;diff=33197</id>
		<title>User:Lantiga</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=User:Lantiga&amp;diff=33197"/>
		<updated>2008-12-10T19:35:35Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Progress in 2008 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Progress in 2008 ==&lt;br /&gt;
&lt;br /&gt;
The NAMIC - Mario Negri Institute external collaboration has brought the following contributions to Slicer and the NAMIC kit:&lt;br /&gt;
&lt;br /&gt;
* Python in Slicer&lt;br /&gt;
** background: in 2007, Dan Blezek produced the first implementation of Python interface in Slicer, providing a method to access Slicer instances from Python through Tcl.&lt;br /&gt;
** during the 2008 January project week in SLC, several sample Python command-line (i.e. non-interactive) modules have been implemented, and the vtkScriptedModule module has been extended to handle Python in addition to Tcl as a scripting language. This allowed the implementation of interactive modules in Python. &lt;br /&gt;
** during the 2008 June project week in Boston, the Python interface has been largely improved (keeping Dan's original code as the core), in order to provide Slicer Python objects as real Python class instances, rather than thin wrappers around Tcl objects. This way, coding Python modules has become very close to coding Python-wrapped VTK.&lt;br /&gt;
** during August 2008, the Python/Numpy interface has been improved, allowing seamless integration of Numpy objects within the Slicer Python interface.&lt;br /&gt;
&lt;br /&gt;
* VMTK Slicer&lt;br /&gt;
** background: during 2007, functionality for turning vmtk command lines into Slicer command-line modules had been implemented. However, need for interactive modules based on vmtk was still needed.&lt;br /&gt;
** during 2008, a first implementation of some of the interactive components of VMTK segmentation has been created, although no code has been committed to the sandbox yet. Rather, this work will be integrated with the work of Daniel Haehn during the January 2009 project week in SLC. In this context, the addition of a vtkMRMLLevelSet node will be proposed (derived from vtkMRMLScalarVolumeNode with a poly data display node).&lt;br /&gt;
** in the meantime, VMTK has been largely improved and now provides vessel enhancement and surface and volume mesh generation capabilities. Therefore, the integration of VMTK in Slicer will readily bring these functionalities to Slicer. In addition, the Mario Negri Institute has implemented and validated a computational fluid dynamics solver that could be interfaced with Slicer and the NAMIC kit.&lt;br /&gt;
&lt;br /&gt;
* ITK&lt;br /&gt;
** during the first half of 2008, the extension of the level set framework to (moderately) anisotropic voxel spacings has been committed to ITK. Work is underway to extend the sparse field level set framework to severely anisotropic spacings.&lt;br /&gt;
** during August 2008, a first draft implementation of a modular level set framework with pluggable terms has been coded, and will tentatively be commited to the NAMIC sandbox during the January 2009 project week.&lt;br /&gt;
&lt;br /&gt;
* Project weeks&lt;br /&gt;
** during the 2008 January AHM in SLC, a presentation was given at the [[2008_Winter_Project_Week_Geometry_and_Topology_processing_of_Meshes | Geometry and Topology Processing of Meshes]] breakout session.&lt;br /&gt;
&lt;br /&gt;
* NAMIC Kit&lt;br /&gt;
** the adoption of the NAMIC Kit within the [[www.robocast.eu | ROBOCAST]] project, funded by the European Commission, has been pushed forward, and it is now official.&lt;br /&gt;
** the development of a Slicer-based pre-operative planning workflow is underway at the University of Verona, under the guide of Dr. Roberto Foroni.&lt;br /&gt;
&lt;br /&gt;
== Extending ITK finite difference and level set filters to anisotropic spacing ==&lt;br /&gt;
&lt;br /&gt;
This is the (tentative) list of classes that assume that spacing is isotropic (i.e. they give incorrect results for anisotropic spacings).&lt;br /&gt;
The plan is to go in and extend them to properly account for anisotropic spacings. This addresses BUG [http://public.kitware.com/Bug/view.php?id=6156 ITK 6156].&lt;br /&gt;
&lt;br /&gt;
* Insight/Code/Common:&lt;br /&gt;
** itkLevelSetFunction - FIXED&lt;br /&gt;
** itkSegmentationLevelSetFunction - FIXED&lt;br /&gt;
&lt;br /&gt;
* Insight/Code/BasicFilters:&lt;br /&gt;
** itkLevelSetFunctionWithRefitTerm&lt;br /&gt;
** itkNormalVectorDiffusionFunction&lt;br /&gt;
** itkParallelSparseFieldLevelSetImageFilter&lt;br /&gt;
** itkSparseFieldFourthOrderLevelSetImageFilter&lt;br /&gt;
** itkSparseFieldLevelSetImageFilter - FIXED&lt;br /&gt;
&lt;br /&gt;
Insight/Code/Algorithms:&lt;br /&gt;
** itkBinaryMinMaxCurvatureFlowFunction&lt;br /&gt;
** tkCurvatureFlowFunction - FIXED&lt;br /&gt;
** itkLevelSetNeighborhoodExtractor&lt;br /&gt;
** itkLevelSetVelocityNeighborhoodExtractor&lt;br /&gt;
** itkReinitializeLevelSetImageFilter&lt;br /&gt;
** itkShapePriorSegmentationLevelSetFunction&lt;br /&gt;
&lt;br /&gt;
== 2008 Winter Project Week ==&lt;br /&gt;
&lt;br /&gt;
* Python modules: Python support, existing modules and new modules&lt;br /&gt;
* Transform hardening in MRML (should be finished on a local copy before the project week)&lt;br /&gt;
* Localized command line modules using MRML transform hardening&lt;br /&gt;
* Breakout: Geometry and Topology processing of Meshes&lt;br /&gt;
* vmtk module&lt;br /&gt;
&lt;br /&gt;
== Python modules ==&lt;br /&gt;
&lt;br /&gt;
Below is a list of Python modules that will be implemented using the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation:Python Python script plugin] functionality.&lt;br /&gt;
&lt;br /&gt;
===Done===&lt;br /&gt;
* SurfaceConnectivity.py (color by connected regions or extract the connected surface closest to a fiducial) (issue: crash with more than one fiducial on the Mac?)&lt;br /&gt;
* SurfaceToolbox.py (decimation + smoothing + normals + cleaner, with individual &amp;quot;Enable&amp;quot; switches)&lt;br /&gt;
* PythonScript.py (takes a surface and/or an image, runs Python code on it loading it from a file, and output the result. Fast way of using Slicer through Python and prototyping modules) (why does it fail with multiple inputs/outputs on the Mac?)&lt;br /&gt;
* GradientAnisotropicDiffusion.py (by Dan)&lt;br /&gt;
* SurfaceICPRegistration.py&lt;br /&gt;
&lt;br /&gt;
===In the works===&lt;br /&gt;
* SurfaceTransformHardening.py&lt;br /&gt;
&lt;br /&gt;
===Ideas===&lt;br /&gt;
* MarchingCubes.py&lt;br /&gt;
* ArrayCalculator.py&lt;br /&gt;
* Glyphs.py&lt;br /&gt;
* ShortestPath.py (use new Djikstra path)&lt;br /&gt;
* Reference system handling&lt;br /&gt;
&lt;br /&gt;
== Ideas for Slicer3 ==&lt;br /&gt;
&lt;br /&gt;
=== vmtk ===&lt;br /&gt;
&lt;br /&gt;
* figure out an official way to use vmtk within slicer and provide concrete examples and several modules:&lt;br /&gt;
** vessel enhancement&lt;br /&gt;
** vessel segmentation&lt;br /&gt;
** geometric analysis&lt;br /&gt;
** meshing for CFD&lt;br /&gt;
** visualization of CFD data&lt;br /&gt;
* check if any of the vmtk C++ classes can be used for stand-alone C++ modules  (e.g. centerline computation, finite elements)&lt;br /&gt;
* running modules in a localized space is vital: one solution has been implemented in Boston, but a more general approach would have a broader impact (see below)&lt;br /&gt;
* output fiducials would be useful (see below) but not vital for vmtk integration, can be circumvented using world points&lt;br /&gt;
* multistage modules would be useful (see below) but not essential&lt;br /&gt;
* packaging is tricky, but can be postponed for now&lt;br /&gt;
* future developments: vmtk through Tcl, or vmtk through Python through Tcl&lt;br /&gt;
&lt;br /&gt;
=== Modules in localized space ===&lt;br /&gt;
* the rationale is to give command line modules a chance to run in a space where images are oriented as X Y Z (i.e. fully specified by a vtkImageData) but still have correct information available as to image origin, spacing and up/down, left/right, front/back consistency. &lt;br /&gt;
* the solution implemented in Boston consists in computing the transform from the localized space (the XYZ one) to Slicer's RAS for the first image in the CLI. All other CLI arguments (images, surfaces, fiducials and ROIs) are transformed using that transform before being written to command line. Upon completion, Slicer reads the results (which have been generated in localized space) and puts them in the scene as children of the RAStoLocal transform. &lt;br /&gt;
* nicer (more general) solution: there should be a localization mechanism by which Slicer3 creates a miniscene relative to a transformable node (image, model, transform, etc) and runs the module using that miniscene. This involves that all inputs, fiducials, ROIs, etc are first transformed to that miniscene root transform node. The outputs would also be reimported as children of the miniscene. &lt;br /&gt;
** if the CLI module is MRML-aware, Slicer3 will let the module deal with the mini scene&lt;br /&gt;
** if the CLI module is not MRML-aware, Slicer3 will take care of hardening the transforms up to the miniscene's root on the images, surfaces, fiducials, etc, exporting the hardened nodes (which are now direct descendants of the miniscene root), reimporting the results and transferring the mini scene contents to the main scene. &lt;br /&gt;
&lt;br /&gt;
=== Hardening transforms ===&lt;br /&gt;
&lt;br /&gt;
* a user should be able to harden transforms on nodes. In the MRML tree, if a user moves a node and changes its parent (say, from a parent trasform to root), this can have two different meanings:&lt;br /&gt;
** the basis changes, the data doesn't (the way it works now): the effect is that the node changes its position and orientation in the 3D window. &lt;br /&gt;
** the basis doesn't change, the data does: the effect is now that the position and orientation of the node are unchanged, but the node is now child of a different transform (this is what I'd call hardening). This is essential for non-MRML aware command line modules: e.g. if an input image is a child of some transform, it should be hardened (i.e. the IJKToRAS should be composed with the parent transform) before it's written to command line.&lt;br /&gt;
&lt;br /&gt;
=== Output fiducials ===&lt;br /&gt;
&lt;br /&gt;
* currently outputs can be data (images, models) and transforms. However, I also see a need for output fiducials (and ROIs). For example, a module could run in two stages: 1) identification of feature points; 2) operation performed on the feature points. Between 1) and 2) the user should be able to manipulate the fiducials (here I'm thinking at centerline computation: 1) could identify possible endpoints, 2) could trace centerlines between user-selected pairs of enpoints). Therefore, 1) should spit fiducials (with text) as output. &lt;br /&gt;
* output fiducials with text to be placed in scene: probably either through a vtkMRMLFiducialStorageNode that outputs a vtp file or through an XML data structure sent to output as a file or on stdout; the solution of XML description in a XML file is probably the best.&lt;br /&gt;
&lt;br /&gt;
=== Python ===&lt;br /&gt;
* write some sample modules;&lt;br /&gt;
* extend scripted modules to Python?&lt;br /&gt;
&lt;br /&gt;
=== DBPs ===&lt;br /&gt;
&lt;br /&gt;
* vascular (vmtk): segmentation, analysis, meshing, CFD for atherosclerosis, cerebral aneurysms, AAAs.&lt;br /&gt;
* segmentation and registration in PKD (polycystic kidney disease);&lt;br /&gt;
* functional renal imaging;&lt;br /&gt;
* functional brain imaging;&lt;br /&gt;
&lt;br /&gt;
=== Multistage modules ===&lt;br /&gt;
&lt;br /&gt;
Below is a thread on the mailing list on multistage modules. The discussion took place in Boston.&lt;br /&gt;
&lt;br /&gt;
It's sorted according to positive time.&lt;br /&gt;
&lt;br /&gt;
==== Luca ====&lt;br /&gt;
&lt;br /&gt;
Hi everyone,&lt;br /&gt;
I've got a couple of thoughts regarding command line modules.&lt;br /&gt;
Currently Slicer processes command line modules by looking in the  modules directory, choosing files that could either be executables or  shared libraries, peeking into them to see if they are well behaved  and later querying them for their XML description.&lt;br /&gt;
Another possible design (somewhat closer to what Paraview uses) could  have been to have executables (or shared libraries) accompanied by  XML files containing the description of both the executable (or the  shared library) and the GUI parameters.&lt;br /&gt;
The disadvantage would have been to have two files per plugin instead  of one. The advantages would be avoiding peeking into executables or  shared libraries (the XML file could contain that information  already), possibly also speeding up module discovery times. Another  advantage would be making it easier to add other kinds of command  line modules (I'm thinking about Python classes) without messing too  much with the module discovery phase.&lt;br /&gt;
This solution would be come with an additional advantage: multi- staged command line modules.&lt;br /&gt;
Very often a module has the need of doing some processing, asking the  user for info, then processing, then asking for info, and so on.&lt;br /&gt;
This is now possible in Slicer by breaking up a program in several  command line modules, but it would be neat to have a tabbed or wizard  GUI that guides you through the process.&lt;br /&gt;
What I'm thinking is that a single command line module plugin could  be made up of several executables called at each step of a wizard  built using the XML file.&lt;br /&gt;
Separating XML descriptions and executables (or shared libraries)  would make this easier, since one XML file could contain a reference  to several executables, while the current design of asking the  executable for its XML description would make this more complicated.&lt;br /&gt;
Just to clarify: it's not my intention to spread confusion and mess  with a solid and already well established design, but I figured I  would share this thoughts.&lt;br /&gt;
Thanks and see you soon&lt;br /&gt;
Luca&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Steve ====&lt;br /&gt;
&lt;br /&gt;
Hi Luca -&lt;br /&gt;
&lt;br /&gt;
That's a very interesting idea.... it seems to me that could coexist what the current paradigm nicely.&lt;br /&gt;
&lt;br /&gt;
There's another way of creating modules currently supported in slicer3, which we haven't pushed much because it's somewhat experimental.  I'm referring to the ScriptedModule approach used by the Editor module - it's analogous to the CommandLineModule in that modules are discovered at startup, but instead of defining the GUI indirectly with XML, the ScriptedModule can use the tcl API to create it's own GUI and interact with MRML directly.  But I like what you are proposing too because it can retain more of the flexibility to run as either command line tools or as module.&lt;br /&gt;
&lt;br /&gt;
It'll be fun to discuss these options when we get together.&lt;br /&gt;
&lt;br /&gt;
-Steve&lt;br /&gt;
&lt;br /&gt;
==== Bill ====&lt;br /&gt;
&lt;br /&gt;
Interesting ideas, Luca!&lt;br /&gt;
&lt;br /&gt;
I have found myself wanting a bit more interactivity in the command-line&lt;br /&gt;
modules, too. My ambitions are not as lofty as Luca's, however. It would&lt;br /&gt;
be nice to have an input parameter be a 2-way parameter, and to have&lt;br /&gt;
another special execution mode run from the command line so that the&lt;br /&gt;
module could accept the input parameter values, compute some value that&lt;br /&gt;
derived from these inputs, set the value of one or more of the 2-way&lt;br /&gt;
parameters, and then return to Slicer and have Slicer display the&lt;br /&gt;
computed values. This could be mediated by one or more new XML&lt;br /&gt;
command-line options like &amp;lt;cmd&amp;gt;update-params&amp;lt;/cmd&amp;gt; or some such.&lt;br /&gt;
&lt;br /&gt;
Another thing that I have wanted is some more flexibility in how the GUI&lt;br /&gt;
is built for command-line modules. I am working on an application that&lt;br /&gt;
would really benefit from having sliders in the GUI, but if I read the&lt;br /&gt;
Execution Model docs correctly, that only works for built-in modules,&lt;br /&gt;
not for command line modules.&lt;br /&gt;
&lt;br /&gt;
Finally, and this is a biggy -- I wonder if it would be possible to&lt;br /&gt;
implement the interface between Slicer3 and the command line modules so&lt;br /&gt;
that parameters and data could be passed in memory instead of in&lt;br /&gt;
temporary files on disk? This might be possible if pipes are substituted&lt;br /&gt;
for disk files; the API for reading and writing to pipes is pretty&lt;br /&gt;
similar to file I/O, and most systems implement pipes as shared memory&lt;br /&gt;
transfer. Just a thought.&lt;br /&gt;
&lt;br /&gt;
-Bill Leue&lt;br /&gt;
&lt;br /&gt;
==== Raul ====&lt;br /&gt;
&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;br /&gt;
I want to join to the great ideas of Luca and Bill to extend the &lt;br /&gt;
interactivity of the command-line-module.&lt;br /&gt;
In the same direction, it would be nice to be able to have more control &lt;br /&gt;
(for projects that required some advanced customization) before and &lt;br /&gt;
after the module execution in the Slicer execution environment. For &lt;br /&gt;
example, for tensors, it would be great to have the chance to set up &lt;br /&gt;
MRML nodes according to the outputs to assigned a mask and a DWI to the &lt;br /&gt;
tensor MRML node.&lt;br /&gt;
This would equate to be able to prescribe two virtual methods, &lt;br /&gt;
BeforeUpdate and AfterUpdate, from the XML description that would &lt;br /&gt;
generate the appropriate code in the Command Line Interface part. I'm &lt;br /&gt;
thinking something like:&lt;br /&gt;
&amp;lt;code, method=AfterUpdate&amp;gt;&lt;br /&gt;
&amp;lt;method&amp;gt;&lt;br /&gt;
//output1Node is a vtkMRMLDiffusionTensorNode&lt;br /&gt;
output1Node-&amp;gt;SetAndObserveDiffusionWeightedVolume(inputNode-&amp;gt;GetID());&lt;br /&gt;
&amp;lt;/method&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
/Raul&lt;br /&gt;
&lt;br /&gt;
= Misc comments =&lt;br /&gt;
&lt;br /&gt;
* Transforms and CLI: &lt;br /&gt;
** the rationale is to give command line modules a chance not to worry about transforms but still have correct information available as to spacing and up/down, left/right, front/back consistency&lt;br /&gt;
** the image passed to a command line module should be in normalized orientation space, i.e.: real origin, real spacing, &lt;br /&gt;
** reference node specified in XML (either tag of the reference node or tag of child nodes to the reference - the latter allows many references in the same command line). Images in normalized orientation space.&lt;br /&gt;
** the reference transform should be just a rigid transformation bringing the axes to XYZ (by looking at projections, but not necessarily). Therefore, from the node transform, a RASToLocalMatrix should be extracted, containing only the cosines that bring the axes to XYZ.&lt;br /&gt;
** for each XML node, specify what's its reference node. The default is patient space (identity matrix), but in general it could be another node. So the current node matrix should be multiplied by the inverse of the reference node matrix before being written out. Correspondingly, when the command line module has executed, all results have to be multiplied by the corresponding reference node matrix. A reference node could be the node itself, meaning that the node transform wil be multiplied by the inverse of its reference transform.&lt;br /&gt;
** find ways to harden transforms for specific MRML nodes&lt;br /&gt;
** in the end: the writer of a command line module or Python scripted module etc. has to be put in the condition of not knowing anything about transforms, and still deal with legal vtkImageData objects (with their own spacing and right-handedness)&lt;br /&gt;
&lt;br /&gt;
* Multi-stage CLI:&lt;br /&gt;
** wizard or tabbed interface with content generated one page per command line module, and user control is returned from one page to the next.&lt;br /&gt;
** one XML that puts command line modules together. This way command line modules can be either used alone or in a wizard.&lt;br /&gt;
** change the way CLI are specified: XML files are discovered first, each XML describes how's the module is going to be (executable, shared library, Python class, etc). This saves time for module discovery (at least on OSX), and (as suggested by Raoul) it makes it easy for a developer to know how that CLI is going to behave and to develop against it.&lt;br /&gt;
&lt;br /&gt;
* Fix vtkITK CMakeLists.txt (generate vtkITKTCL.so separately from vtkITK.so).&lt;br /&gt;
&lt;br /&gt;
* XML module GUI:&lt;br /&gt;
** give possibility to build a GUI from XML in ScriptedModules (either from Tcl or Python) or even everywhere in Slicer3, even from C++.&lt;br /&gt;
&lt;br /&gt;
* Python: &lt;br /&gt;
** try wrapping VTK. What happens when Python through Tcl is used and ShallowCopy to a true VTK module is called?&lt;br /&gt;
&lt;br /&gt;
* Annotation widget&lt;br /&gt;
** do it for command line modules (like: put this string at this point in the scene)&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Slicer_VMTK&amp;diff=33195</id>
		<title>2009 Winter Project Week Slicer VMTK</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Slicer_VMTK&amp;diff=33195"/>
		<updated>2008-12-10T19:31:32Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Key Investigators */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:NAMIC-SLC.jpg|thumb|320px|Return to [[2009_Winter_Project_Week|Project Week Main Page]] ]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* [[User:haehn |Daniel Haehn]] (Student of Medical Informatics, University of Heidelberg)&lt;br /&gt;
* [[User:lantiga |Luca Antiga]] (Medical Imaging Unit, Biomedical Engineering Department, Mario Negri Institute)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
The Vascular Modeling Toolkit ([http://vmtk.org VMTK]) is a collection of libraries and tools for 3D reconstruction, geometric analysis, mesh generation and surface data analysis for image-based modeling of blood vessels. It should be very interesting to offer such techniques in Slicer3. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
VMTK provides Python pipeable scripts (PypeS) to connect various commands and/or scripts. An automated mechanism to generate non-interactive Slicer modules has already been implemented. &lt;br /&gt;
&lt;br /&gt;
The plan is to write a python scripted module for Slicer3 that connects to VMTK pipes and provides the same user interaction style found in VMTK.&lt;br /&gt;
This is necessary for interactive segmentation.&lt;br /&gt;
&lt;br /&gt;
In addition, a collection of non-interactive modules relevant to segmentation and characterization of vascular networks will be generated.&lt;br /&gt;
 &lt;br /&gt;
Finally, Slicer-vmtk packaging issues will be tackled.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
For preparation:&amp;lt;br&amp;gt;&lt;br /&gt;
- ground work for making an interactive python scripted module&amp;lt;br&amp;gt;&lt;br /&gt;
- playing with VMTK pypes to generate some CLI VMTK scripts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Slicer_VMTK&amp;diff=33194</id>
		<title>2009 Winter Project Week Slicer VMTK</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Slicer_VMTK&amp;diff=33194"/>
		<updated>2008-12-10T19:31:09Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:NAMIC-SLC.jpg|thumb|320px|Return to [[2009_Winter_Project_Week|Project Week Main Page]] ]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* [[User:haehn |Daniel Haehn]] (Student of Medical Informatics, University of Heidelberg)&lt;br /&gt;
* Luca Antiga, PhD (Medical Imaging Unit, Biomedical Engineering Department, Mario Negri Institute)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
The Vascular Modeling Toolkit ([http://vmtk.org VMTK]) is a collection of libraries and tools for 3D reconstruction, geometric analysis, mesh generation and surface data analysis for image-based modeling of blood vessels. It should be very interesting to offer such techniques in Slicer3. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
VMTK provides Python pipeable scripts (PypeS) to connect various commands and/or scripts. An automated mechanism to generate non-interactive Slicer modules has already been implemented. &lt;br /&gt;
&lt;br /&gt;
The plan is to write a python scripted module for Slicer3 that connects to VMTK pipes and provides the same user interaction style found in VMTK.&lt;br /&gt;
This is necessary for interactive segmentation.&lt;br /&gt;
&lt;br /&gt;
In addition, a collection of non-interactive modules relevant to segmentation and characterization of vascular networks will be generated.&lt;br /&gt;
 &lt;br /&gt;
Finally, Slicer-vmtk packaging issues will be tackled.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
For preparation:&amp;lt;br&amp;gt;&lt;br /&gt;
- ground work for making an interactive python scripted module&amp;lt;br&amp;gt;&lt;br /&gt;
- playing with VMTK pypes to generate some CLI VMTK scripts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33190</id>
		<title>2009 Winter Project Week Python</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33190"/>
		<updated>2008-12-10T19:25:14Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Key Investigators */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:Python-logo.png |thumb|320px|[http://www.python.org]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Luca Antiga (Medical Imaging Unit, Biomedical Engineering Department, Mario Negri Institute)&lt;br /&gt;
* Steve Piper (Isomics)&lt;br /&gt;
* Demian Wasserman (INRIA)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
To finalize the implementation of the Slicer Python interface and solve packaging problems linked to Scipy.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Slicer Python interface now works well for both non-interactive and interactive modules. A few improvements are still needed, namely &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- calling VTK static methods - e.g. slicer.vtkMath.Norm(v)&lt;br /&gt;
&lt;br /&gt;
- handling modified arguments - e.g. slicer.vtkMath::Normalize(v)&lt;br /&gt;
&lt;br /&gt;
- defining methods with the exact number of arguments (now it's not constrained, so if it's wrong Tcl complains) - this will require a patch on the VTK Tcl wrappers&lt;br /&gt;
&lt;br /&gt;
- fix a memory leak associated with Python scripted modules&lt;br /&gt;
&lt;br /&gt;
- review the Slicer Python to Numpy code and eventually extend it to handle more general image or data types&lt;br /&gt;
&lt;br /&gt;
As for packaging problems, testing will have to be performed on several architectures.&lt;br /&gt;
&lt;br /&gt;
Finally, documentation will be improved.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TODO&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33189</id>
		<title>2009 Winter Project Week Python</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33189"/>
		<updated>2008-12-10T19:24:10Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Key Investigators */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:Python-logo.png |thumb|320px|[http://www.python.org]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Luca Antiga (Medical Imaging Unit, Biomedical Engineering Department, Mario Negri Institute)&lt;br /&gt;
* Steve Piper (Isomics)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
To finalize the implementation of the Slicer Python interface and solve packaging problems linked to Scipy.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Slicer Python interface now works well for both non-interactive and interactive modules. A few improvements are still needed, namely &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- calling VTK static methods - e.g. slicer.vtkMath.Norm(v)&lt;br /&gt;
&lt;br /&gt;
- handling modified arguments - e.g. slicer.vtkMath::Normalize(v)&lt;br /&gt;
&lt;br /&gt;
- defining methods with the exact number of arguments (now it's not constrained, so if it's wrong Tcl complains) - this will require a patch on the VTK Tcl wrappers&lt;br /&gt;
&lt;br /&gt;
- fix a memory leak associated with Python scripted modules&lt;br /&gt;
&lt;br /&gt;
- review the Slicer Python to Numpy code and eventually extend it to handle more general image or data types&lt;br /&gt;
&lt;br /&gt;
As for packaging problems, testing will have to be performed on several architectures.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TODO&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33188</id>
		<title>2009 Winter Project Week Python</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33188"/>
		<updated>2008-12-10T19:23:23Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Key Investigators */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:Python-logo.png |thumb|320px|[http://www.python.org]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Luca Antiga (Medical Imaging Unit, Biomedical Engineering Department, Mario Negri Institute)&lt;br /&gt;
* Steve Piper (Isomics)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
To finalize the implementation of the Slicer Python interface and solve packaging problems linked to Scipy.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Slicer Python interface now works well for both non-interactive and interactive modules. A few improvements are still needed, namely &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- calling VTK static methods - e.g. slicer.vtkMath.Norm(v)&lt;br /&gt;
&lt;br /&gt;
- handling modified arguments - e.g. slicer.vtkMath::Normalize(v)&lt;br /&gt;
&lt;br /&gt;
- defining methods with the exact number of arguments (now it's not constrained, so if it's wrong Tcl complains) - this will require a patch on the VTK Tcl wrappers.&lt;br /&gt;
&lt;br /&gt;
- fix a memory leak associated with Python scripted modules.&lt;br /&gt;
&lt;br /&gt;
As for packaging problems, testing will have to be performed on several architectures.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TODO&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33187</id>
		<title>2009 Winter Project Week Python</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33187"/>
		<updated>2008-12-10T19:22:44Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Key Investigators */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:Python-logo.png |thumb|320px|[http://www.python.org]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Luca Antiga (Medical Imaging Unit, Biomedical Engineering Department, Mario Negri Institute)&lt;br /&gt;
* Steve Piper (Isomics)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
To finalize the implementation of the Slicer Python interface and solve packaging problems linked to Scipy.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Slicer Python interface now works well for both non-interactive and interactive modules. A few improvements are still needed, namely &amp;lt;br&amp;gt;&lt;br /&gt;
- calling VTK static methods - e.g. slicer.vtkMath.Norm(v)&lt;br /&gt;
- handling modified arguments - e.g. slicer.vtkMath::Normalize(v)&lt;br /&gt;
- defining methods with the exact number of arguments (now it's not constrained, so if it's wrong Tcl complains) - this will require a patch on the VTK Tcl wrappers.&lt;br /&gt;
- fix a memory leak associated with Python scripted modules.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TODO&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33186</id>
		<title>2009 Winter Project Week Python</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33186"/>
		<updated>2008-12-10T19:16:14Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:Python-logo.png |thumb|320px|[http://www.python.org]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Luca Antiga (Medical Imaging Unit, Biomedical Engineering Department, Mario Negri Institute)&lt;br /&gt;
* Steve Piper (Isomics)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
TODO&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TODO.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
TO:&amp;lt;br&amp;gt;&lt;br /&gt;
- DO&amp;lt;br&amp;gt;&lt;br /&gt;
- ...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week&amp;diff=33185</id>
		<title>2009 Winter Project Week</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week&amp;diff=33185"/>
		<updated>2008-12-10T19:13:03Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Other NA-MIC Projects */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[Project Events]], [[AHM_2009]], [[Events]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction to NA-MIC Project Week==&lt;br /&gt;
&lt;br /&gt;
Please read an introduction about these events [[Project_Events#Introduction|here]].&lt;br /&gt;
&lt;br /&gt;
== Dates.Venue.Registration ==&lt;br /&gt;
&lt;br /&gt;
Please [[AHM_2009#Dates._Venue._Registration| click here for Dates, Venue, and Registration]] for this event.&lt;br /&gt;
&lt;br /&gt;
== Agenda==&lt;br /&gt;
&lt;br /&gt;
Please [[AHM_2009#Agenda|click here for the agenda for AHM 2009 and Project Week]].&lt;br /&gt;
&lt;br /&gt;
==Projects==&lt;br /&gt;
Please note:&lt;br /&gt;
*Please use the [[2009_Winter_Project_Week_Template|'''2009 Project Week Template''']] to create a page for your project(s)&lt;br /&gt;
*[[2008_Summer_Project_Week#Projects|Last Event's Projects as a reference]]&lt;br /&gt;
*For hosting projects, we are planning to make use of the NITRC resources.  See [[NA-MIC_and_NITRC | Information about NITRC Collaboration]]&lt;br /&gt;
*Next Project Week is at MIT -- June 22-26, 2009&lt;br /&gt;
The following is a list of all projects that will be pursued at this meeting.&lt;br /&gt;
&lt;br /&gt;
===NA-MIC DBP Roadmap Projects===&lt;br /&gt;
Please note that these projects correspond to four clinical Roadmap application projects that will be pursued in focused parallel tracks at the meeting, each corresponding to a DBP problem.  &lt;br /&gt;
&lt;br /&gt;
#[[DBP2:Harvard:Brain_Segmentation_Roadmap|Harvard Roadmap Project: Stochastic Tractography for VCFS]]&lt;br /&gt;
##[[2009_Winter_Project_Week:GT_TubularSurfaceSeg|Tubular Surface Segmentation for fiber bundle extraction]] (Vandana Mohan GATech, Allen Tannenbaum GATech, Marek Kubicki BWH)&lt;br /&gt;
##[[2009_Winter_Project_Week_StochasticTractography |Stochastic Tractograhy Tool for Slicer]] (Marek Kubicki BWH, Julien de Siebenthal BWH) &lt;br /&gt;
##[[2009_Winter_Project_Week_Slicer3Functioning |Evaluation of basic Slicer 3.0 Functionality from a User Perspective]] (Doug Terry BWH, Marek Kubicki BWH) &lt;br /&gt;
#[[DBP2:UNC:Cortical_Thickness_Roadmap|UNC Roadmap Project: Cortical Thickness Measurement for Autism]]&lt;br /&gt;
#[[DBP2:MIND:Roadmap|MIND Roadmap Project: Brain Lesion Analysis in Lupus]]&lt;br /&gt;
#[[DBP2:JHU:Roadmap|JHU Roadmap Project: Segmentation and Registration for Robotic Prostate Intervention]]&lt;br /&gt;
&lt;br /&gt;
===Other NA-MIC Projects===&lt;br /&gt;
#Fluid mechanics tractography and visualization (Nathan Hageman UCLA)&lt;br /&gt;
#UCLA BrainLab/Slicer Neurosurgery Preoperative Tumor Planning - using Slicer and its link to BrainLab to investigate whether different tractography methods aid in preoperative planning of tumor resection.(Nathan Hageman UCLA)&lt;br /&gt;
#Development of FEM / FVM solver library in ITK/VTK (and/or Python?) (Nathan Hageman UCLA, Vince, Luca, Steve)&lt;br /&gt;
#[[2009_Winter_Project_Week_Transform_Management | Transform Management]](Jim Miller)&lt;br /&gt;
#Interactive 3D Widgets - Introduce new interactors into Slicer (Karthik)&lt;br /&gt;
#[[2009_Winter_Project_Week_vtkITK_Pipeline | Using ITK in VTK Pipelines]] (Jim, Steve)&lt;br /&gt;
#User Interface Flexible Layouts (Wendy, Jim, Steve)&lt;br /&gt;
#[[2009_Winter_Project_Week_Python | Python interface completion and packaging - Fortran and openssl problems]] (Luca, Steve)&lt;br /&gt;
#Two-tensor tractography in Slicer using Python and Teem (Madeleine Seeland, C-F Westin)&lt;br /&gt;
#[[2009_Winter_Project_Week_Rotation_Tangents | Diffusion Tensor Invariant gradients and rotation tangents in Python and Teem]] (Peter Savadjiev, C-F Westin and Gordon Kindlmann)&lt;br /&gt;
#xnat and batchmake integration (Julien, Dan Marcus)&lt;br /&gt;
#Automated GUI testing (Sebastien, Interested User: Vince)&lt;br /&gt;
#Slicer Colors Module update (Nicole)&lt;br /&gt;
#Volume Rendering (Alex, Curt, Nicholas)&lt;br /&gt;
#XNAT Dekstop &amp;amp; File Repository prototypes (Dan Marcus, Wendy Plesniak)&lt;br /&gt;
#Cortical correspondence using DTI (Ipek, Martin)&lt;br /&gt;
#[[2009_Winter_Project_Week_Command_Line_Program_Testing |Command Line Program Testing]] (Lorensen, NA-MIC)&lt;br /&gt;
#[[2009_Winter_Project_Week_Slicer_VMTK |Vessel Segmentation in Slicer using VMTK]] ([[User:haehn|Daniel Haehn]], [[User:lantiga| Luca Antiga]])&lt;br /&gt;
#[[2009_Winter_Project_Week_fMRI_Clustering |Exploring Functional Connectivity in fMRI via Clustering]] (Archana Venkataraman, Marek Kubicki, Polina Golland)&lt;br /&gt;
#[[2009_Winter_Project_Week_Compiler_Warnings:Slicer3_Graffiti |Compiler Warnings:Slicer3's Graffiti]] (Lorensen, NA-MIC)&lt;br /&gt;
&lt;br /&gt;
===External Collaborations===&lt;br /&gt;
* [[Iowa Meshing Tutorial]] &lt;br /&gt;
** (the work is likely to be completed by the AHM)&lt;br /&gt;
*Wake Forest - Virginia Tech&lt;br /&gt;
** [[2009_Winter_Project_Week_WFU1 | Move to All Slicer3 Workflow]]&lt;br /&gt;
** [[2009_Winter_Project_Week_WFU2 | Development of deformation based morphometry module]]&lt;br /&gt;
*Georgetown U: Prototype RF Lesion Ablation Workflow prototyped in Slicer&lt;br /&gt;
*UNC: &lt;br /&gt;
**[[2009_UNC_HAMMER | MR-image registration algorithm to be extended and added to namic kit]]&lt;br /&gt;
**[[2009_UNC_White_Matter_Lesion | white matter lesion segmentation]]&lt;br /&gt;
*Mario Negri&lt;br /&gt;
*Stanford SIMBIOS: segmentation of knee joint&lt;br /&gt;
* [[2009_Winter_Project_Week_MRSI | MRSI Module for Slicer (Bjoern Menze)]]&lt;br /&gt;
&lt;br /&gt;
=== Preparation ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
# Please make sure that you are on the [http://public.kitware.com/cgi-bin/mailman/listinfo/na-mic-project-week na-mic-project-week mailing list]&lt;br /&gt;
# Starting Thursday, October 16th, part of the weekly Thursday 3pm NA-MIC Engineering TCON will be used to prepare for this meeting.  The schedule for these preparatory calls is as follows:&lt;br /&gt;
#*October 16: Engineering Infrastructure Projects&lt;br /&gt;
#*October 23: Funded External Collaboration Projects&lt;br /&gt;
#*November 6: DPB Projects &lt;br /&gt;
#*November 20: New Collaborations&lt;br /&gt;
#*December 4: Other Projects&lt;br /&gt;
#*December 18: Loose Ends&lt;br /&gt;
#By December 17, 2008: [[2009_Winter_Project_Week_Template|Complete a templated wiki page for your project]]. Please do not edit the template page itself, but create a new page for your project and cut-and-paste the text from this template page.  If you have questions, please send an email to tkapur at bwh.harvard.edu.&lt;br /&gt;
# By December 17, 2008: Create a directory for each project on the [[Engineering:SandBox|NAMIC Sandbox]] (Zack)&lt;br /&gt;
##[https://www.kitware.com/Admin/SendPassword.cgi Ask Zack for a Sandbox account]&lt;br /&gt;
## Commit on each sandbox directory the code examples/snippets that represent our first guesses of appropriate methods. (Luis and Steve will help with this, as needed)&lt;br /&gt;
## Gather test images in any of the Data sharing resources we have (e.g. the BIRN). These ones don't have to be many. At least three different cases, so we can get an idea of the modality-specific characteristics of these images. Put the IDs of these data sets on the wiki page. (the participants must do this.)&lt;br /&gt;
## Setup nightly tests on a separate Dashboard, where we will run the methods that we are experimenting with. The test should post result images and computation time. (Zack)&lt;br /&gt;
# FINAL TCON: December 18th 3pm ET to tie loose ends&lt;br /&gt;
# Please note that by the time we get to the project event, we should be trying to close off a project milestone rather than starting to work on one...&lt;br /&gt;
&lt;br /&gt;
== Previous Project Events ==&lt;br /&gt;
&lt;br /&gt;
A history of all the programming/project events in NA-MIC is available by following [[Project Events|this link]].&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=NA-MIC_VMTK_Collaboration&amp;diff=33182</id>
		<title>NA-MIC VMTK Collaboration</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=NA-MIC_VMTK_Collaboration&amp;diff=33182"/>
		<updated>2008-12-10T19:09:06Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Citations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Collaboration with [http://villacamozzi.marionegri.it/~luca/ Luca Antiga] of the [http://www.marionegri.it Mario Negri Institute].&lt;br /&gt;
&lt;br /&gt;
Back to [[NA-MIC_External_Collaborations]]&lt;br /&gt;
&lt;br /&gt;
[[Image:VmtkSlicerModule.jpg]]&lt;br /&gt;
[[Image:VoronoiVortices lowres.png]]&lt;br /&gt;
&lt;br /&gt;
===Goals of the Project===&lt;br /&gt;
To create a Slicer-based platform for segmentation of vascular segments from angiographic images (CTA, MRA, ...), analysis of vascular geometry, mesh generation and hemodynamic simulation (CFD) and visualization.&lt;br /&gt;
&lt;br /&gt;
Since many of these functionalities are already provided by the Vascular Modeling Toolkit ([http://www.vmtk.org www.vmtk.org]) as command-line tools, the plan is to integrate vmtk scripts within Slicer as command-line modules for the non-interactive tasks, and to create ad-hoc GUI modules for the more interactive tasks (i.e. segmentation).&lt;br /&gt;
&lt;br /&gt;
===Current progress===&lt;br /&gt;
* vmtk script for automated conversion of vmtk command line pipes to Slicer command-line modules (DONE)&lt;br /&gt;
* Implementation of vmtk-based interactive modules (IN PROGRESS)&lt;br /&gt;
&lt;br /&gt;
=== References ===&lt;br /&gt;
&lt;br /&gt;
[http://www.vmtk.org www.vmtk.org]&lt;br /&gt;
&lt;br /&gt;
[[Collaboration/VMTK | 2007 Summer Project Week]]&lt;br /&gt;
&lt;br /&gt;
[[NA-MIC/Projects/External_Collaboration/Slicer3-vmtk_Integration | 2008 Summer Project Week]]&lt;br /&gt;
&lt;br /&gt;
[[2009_Winter_Project_Week_Slicer_VMTK | 2009 Winter Project Week]]&lt;br /&gt;
&lt;br /&gt;
=== Citations ===&lt;br /&gt;
&lt;br /&gt;
* Antiga L, Piccinelli M, Botti L, Ene-Iordache B, Remuzzi A and Steinman DA. An image-based modeling framework for patient-specific computational hemodynamics. Medical and Biological Engineering and Computing, 46: 1097-1112, Nov 2008.&lt;br /&gt;
* Lee SW, Antiga L, Spence JD and Steinman DA. Geometry of the carotid bifurcation predicts its exposure to disturbed flow. Stroke, 39(8): 2341-2347, Aug 2008. Featured on the front cover.&lt;br /&gt;
* Thomas JB, Antiga L, Che S, Milner JS, Hangan Steinman DA, Spence JD, Rutt BK and Steinman DA. Variation in the carotid bifurcation geometry of young vs. older adults: Implications for &amp;quot;geometric risk&amp;quot; of atherosclerosis. Stroke, 36(11): 2450-2456, Nov 2005.&lt;br /&gt;
* Antiga L, Steinman DA. Robust and objective decomposition and mapping of bifurcating vessels. IEEE Transactions on Medical Imaging, 23(6): 704-713, June 2004.&lt;br /&gt;
* Antiga L, Ene-Iordache B and Remuzzi A. Computational geometry for patient-specific reconstruction and meshing of blood vessels from MR and CT angiography. IEEE Transactions on Medical Imaging, 22(5): 674-684, May 2003.&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=NA-MIC_VMTK_Collaboration&amp;diff=33181</id>
		<title>NA-MIC VMTK Collaboration</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=NA-MIC_VMTK_Collaboration&amp;diff=33181"/>
		<updated>2008-12-10T19:08:34Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* References */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Collaboration with [http://villacamozzi.marionegri.it/~luca/ Luca Antiga] of the [http://www.marionegri.it Mario Negri Institute].&lt;br /&gt;
&lt;br /&gt;
Back to [[NA-MIC_External_Collaborations]]&lt;br /&gt;
&lt;br /&gt;
[[Image:VmtkSlicerModule.jpg]]&lt;br /&gt;
[[Image:VoronoiVortices lowres.png]]&lt;br /&gt;
&lt;br /&gt;
===Goals of the Project===&lt;br /&gt;
To create a Slicer-based platform for segmentation of vascular segments from angiographic images (CTA, MRA, ...), analysis of vascular geometry, mesh generation and hemodynamic simulation (CFD) and visualization.&lt;br /&gt;
&lt;br /&gt;
Since many of these functionalities are already provided by the Vascular Modeling Toolkit ([http://www.vmtk.org www.vmtk.org]) as command-line tools, the plan is to integrate vmtk scripts within Slicer as command-line modules for the non-interactive tasks, and to create ad-hoc GUI modules for the more interactive tasks (i.e. segmentation).&lt;br /&gt;
&lt;br /&gt;
===Current progress===&lt;br /&gt;
* vmtk script for automated conversion of vmtk command line pipes to Slicer command-line modules (DONE)&lt;br /&gt;
* Implementation of vmtk-based interactive modules (IN PROGRESS)&lt;br /&gt;
&lt;br /&gt;
=== References ===&lt;br /&gt;
&lt;br /&gt;
[http://www.vmtk.org www.vmtk.org]&lt;br /&gt;
&lt;br /&gt;
[[Collaboration/VMTK | 2007 Summer Project Week]]&lt;br /&gt;
&lt;br /&gt;
[[NA-MIC/Projects/External_Collaboration/Slicer3-vmtk_Integration | 2008 Summer Project Week]]&lt;br /&gt;
&lt;br /&gt;
[[2009_Winter_Project_Week_Slicer_VMTK | 2009 Winter Project Week]]&lt;br /&gt;
&lt;br /&gt;
=== Citations ===&lt;br /&gt;
* Lee SW, Antiga L, Spence JD and Steinman DA. Geometry of the carotid bifurcation predicts its exposure to disturbed flow. Stroke. Accepted.&lt;br /&gt;
* Thomas JB, Antiga L, Che S, Milner JS, Hangan Steinman DA, Spence JD, Rutt BK and Steinman DA. Variation in the carotid bifurcation geometry of young vs. older adults: Implications for &amp;quot;geometric risk&amp;quot; of atherosclerosis. Stroke, 36(11): 2450-2456, Nov 2005.&lt;br /&gt;
* Antiga L, Steinman DA. Robust and objective decomposition and mapping of bifurcating vessels. IEEE Transactions on Medical Imaging, 23(6): 704-713, June 2004.&lt;br /&gt;
* Antiga L, Ene-Iordache B and Remuzzi A. Computational geometry for patient-specific reconstruction and meshing of blood vessels from MR and CT angiography. IEEE Transactions on Medical Imaging, 22(5): 674-684, May 2003.&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=NA-MIC_VMTK_Collaboration&amp;diff=33180</id>
		<title>NA-MIC VMTK Collaboration</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=NA-MIC_VMTK_Collaboration&amp;diff=33180"/>
		<updated>2008-12-10T19:08:23Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* References */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Collaboration with [http://villacamozzi.marionegri.it/~luca/ Luca Antiga] of the [http://www.marionegri.it Mario Negri Institute].&lt;br /&gt;
&lt;br /&gt;
Back to [[NA-MIC_External_Collaborations]]&lt;br /&gt;
&lt;br /&gt;
[[Image:VmtkSlicerModule.jpg]]&lt;br /&gt;
[[Image:VoronoiVortices lowres.png]]&lt;br /&gt;
&lt;br /&gt;
===Goals of the Project===&lt;br /&gt;
To create a Slicer-based platform for segmentation of vascular segments from angiographic images (CTA, MRA, ...), analysis of vascular geometry, mesh generation and hemodynamic simulation (CFD) and visualization.&lt;br /&gt;
&lt;br /&gt;
Since many of these functionalities are already provided by the Vascular Modeling Toolkit ([http://www.vmtk.org www.vmtk.org]) as command-line tools, the plan is to integrate vmtk scripts within Slicer as command-line modules for the non-interactive tasks, and to create ad-hoc GUI modules for the more interactive tasks (i.e. segmentation).&lt;br /&gt;
&lt;br /&gt;
===Current progress===&lt;br /&gt;
* vmtk script for automated conversion of vmtk command line pipes to Slicer command-line modules (DONE)&lt;br /&gt;
* Implementation of vmtk-based interactive modules (IN PROGRESS)&lt;br /&gt;
&lt;br /&gt;
=== References ===&lt;br /&gt;
&lt;br /&gt;
[http://www.vmtk.org www.vmtk.org]&lt;br /&gt;
&lt;br /&gt;
[[Collaboration/VMTK | 2007 Summer Project Week]]&lt;br /&gt;
[[NA-MIC/Projects/External_Collaboration/Slicer3-vmtk_Integration | 2008 Summer Project Week]]&lt;br /&gt;
[[2009_Winter_Project_Week_Slicer_VMTK | 2009 Winter Project Week]]&lt;br /&gt;
&lt;br /&gt;
=== Citations ===&lt;br /&gt;
* Lee SW, Antiga L, Spence JD and Steinman DA. Geometry of the carotid bifurcation predicts its exposure to disturbed flow. Stroke. Accepted.&lt;br /&gt;
* Thomas JB, Antiga L, Che S, Milner JS, Hangan Steinman DA, Spence JD, Rutt BK and Steinman DA. Variation in the carotid bifurcation geometry of young vs. older adults: Implications for &amp;quot;geometric risk&amp;quot; of atherosclerosis. Stroke, 36(11): 2450-2456, Nov 2005.&lt;br /&gt;
* Antiga L, Steinman DA. Robust and objective decomposition and mapping of bifurcating vessels. IEEE Transactions on Medical Imaging, 23(6): 704-713, June 2004.&lt;br /&gt;
* Antiga L, Ene-Iordache B and Remuzzi A. Computational geometry for patient-specific reconstruction and meshing of blood vessels from MR and CT angiography. IEEE Transactions on Medical Imaging, 22(5): 674-684, May 2003.&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=NA-MIC_VMTK_Collaboration&amp;diff=33178</id>
		<title>NA-MIC VMTK Collaboration</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=NA-MIC_VMTK_Collaboration&amp;diff=33178"/>
		<updated>2008-12-10T19:05:32Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* References */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Collaboration with [http://villacamozzi.marionegri.it/~luca/ Luca Antiga] of the [http://www.marionegri.it Mario Negri Institute].&lt;br /&gt;
&lt;br /&gt;
Back to [[NA-MIC_External_Collaborations]]&lt;br /&gt;
&lt;br /&gt;
[[Image:VmtkSlicerModule.jpg]]&lt;br /&gt;
[[Image:VoronoiVortices lowres.png]]&lt;br /&gt;
&lt;br /&gt;
===Goals of the Project===&lt;br /&gt;
To create a Slicer-based platform for segmentation of vascular segments from angiographic images (CTA, MRA, ...), analysis of vascular geometry, mesh generation and hemodynamic simulation (CFD) and visualization.&lt;br /&gt;
&lt;br /&gt;
Since many of these functionalities are already provided by the Vascular Modeling Toolkit ([http://www.vmtk.org www.vmtk.org]) as command-line tools, the plan is to integrate vmtk scripts within Slicer as command-line modules for the non-interactive tasks, and to create ad-hoc GUI modules for the more interactive tasks (i.e. segmentation).&lt;br /&gt;
&lt;br /&gt;
===Current progress===&lt;br /&gt;
* vmtk script for automated conversion of vmtk command line pipes to Slicer command-line modules (DONE)&lt;br /&gt;
* Implementation of vmtk-based interactive modules (IN PROGRESS)&lt;br /&gt;
&lt;br /&gt;
=== References ===&lt;br /&gt;
&lt;br /&gt;
[http://www.vmtk.org www.vmtk.org]&lt;br /&gt;
&lt;br /&gt;
[[Collaboration/VMTK | 2007 Project Week at MIT]]&lt;br /&gt;
&lt;br /&gt;
=== Citations ===&lt;br /&gt;
* Lee SW, Antiga L, Spence JD and Steinman DA. Geometry of the carotid bifurcation predicts its exposure to disturbed flow. Stroke. Accepted.&lt;br /&gt;
* Thomas JB, Antiga L, Che S, Milner JS, Hangan Steinman DA, Spence JD, Rutt BK and Steinman DA. Variation in the carotid bifurcation geometry of young vs. older adults: Implications for &amp;quot;geometric risk&amp;quot; of atherosclerosis. Stroke, 36(11): 2450-2456, Nov 2005.&lt;br /&gt;
* Antiga L, Steinman DA. Robust and objective decomposition and mapping of bifurcating vessels. IEEE Transactions on Medical Imaging, 23(6): 704-713, June 2004.&lt;br /&gt;
* Antiga L, Ene-Iordache B and Remuzzi A. Computational geometry for patient-specific reconstruction and meshing of blood vessels from MR and CT angiography. IEEE Transactions on Medical Imaging, 22(5): 674-684, May 2003.&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=NA-MIC_VMTK_Collaboration&amp;diff=33177</id>
		<title>NA-MIC VMTK Collaboration</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=NA-MIC_VMTK_Collaboration&amp;diff=33177"/>
		<updated>2008-12-10T19:05:08Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Current progress */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Collaboration with [http://villacamozzi.marionegri.it/~luca/ Luca Antiga] of the [http://www.marionegri.it Mario Negri Institute].&lt;br /&gt;
&lt;br /&gt;
Back to [[NA-MIC_External_Collaborations]]&lt;br /&gt;
&lt;br /&gt;
[[Image:VmtkSlicerModule.jpg]]&lt;br /&gt;
[[Image:VoronoiVortices lowres.png]]&lt;br /&gt;
&lt;br /&gt;
===Goals of the Project===&lt;br /&gt;
To create a Slicer-based platform for segmentation of vascular segments from angiographic images (CTA, MRA, ...), analysis of vascular geometry, mesh generation and hemodynamic simulation (CFD) and visualization.&lt;br /&gt;
&lt;br /&gt;
Since many of these functionalities are already provided by the Vascular Modeling Toolkit ([http://www.vmtk.org www.vmtk.org]) as command-line tools, the plan is to integrate vmtk scripts within Slicer as command-line modules for the non-interactive tasks, and to create ad-hoc GUI modules for the more interactive tasks (i.e. segmentation).&lt;br /&gt;
&lt;br /&gt;
===Current progress===&lt;br /&gt;
* vmtk script for automated conversion of vmtk command line pipes to Slicer command-line modules (DONE)&lt;br /&gt;
* Implementation of vmtk-based interactive modules (IN PROGRESS)&lt;br /&gt;
&lt;br /&gt;
=== References ===&lt;br /&gt;
&lt;br /&gt;
[http://vmtk.sourceforge.net vmtk.sourceforge.net]&lt;br /&gt;
&lt;br /&gt;
[[Collaboration/VMTK | 2007 Project Week at MIT]]&lt;br /&gt;
&lt;br /&gt;
=== Citations ===&lt;br /&gt;
* Lee SW, Antiga L, Spence JD and Steinman DA. Geometry of the carotid bifurcation predicts its exposure to disturbed flow. Stroke. Accepted.&lt;br /&gt;
* Thomas JB, Antiga L, Che S, Milner JS, Hangan Steinman DA, Spence JD, Rutt BK and Steinman DA. Variation in the carotid bifurcation geometry of young vs. older adults: Implications for &amp;quot;geometric risk&amp;quot; of atherosclerosis. Stroke, 36(11): 2450-2456, Nov 2005.&lt;br /&gt;
* Antiga L, Steinman DA. Robust and objective decomposition and mapping of bifurcating vessels. IEEE Transactions on Medical Imaging, 23(6): 704-713, June 2004.&lt;br /&gt;
* Antiga L, Ene-Iordache B and Remuzzi A. Computational geometry for patient-specific reconstruction and meshing of blood vessels from MR and CT angiography. IEEE Transactions on Medical Imaging, 22(5): 674-684, May 2003.&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=User:Lantiga&amp;diff=33176</id>
		<title>User:Lantiga</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=User:Lantiga&amp;diff=33176"/>
		<updated>2008-12-10T18:57:25Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Progress in 2008 ==&lt;br /&gt;
&lt;br /&gt;
The NAMIC - Mario Negri Institute external collaboration has brought the following contributions to Slicer and the NAMIC kit:&lt;br /&gt;
&lt;br /&gt;
* Python in Slicer&lt;br /&gt;
** background: in 2007, Dan Blezek produced the first implementation of Python interface in Slicer, providing a method to access Slicer instances from Python through Tcl.&lt;br /&gt;
** during the 2008 January project week in SLC, several sample Python command-line (i.e. non-interactive) modules have been implemented, and the vtkScriptedModule module has been extended to handle Python in addition to Tcl as a scripting language. This allowed the implementation of interactive modules in Python. &lt;br /&gt;
** during the 2008 June project week in Boston, the Python interface has been largely improved (keeping Dan's original code as the core), in order to provide Slicer Python objects as real Python class instances, rather than thin wrappers around Tcl objects. This way, coding Python modules has become very close to coding Python-wrapped VTK.&lt;br /&gt;
** during August 2008, the Python/Numpy interface has been improved, allowing seamless integration of Numpy objects within the Slicer Python interface.&lt;br /&gt;
&lt;br /&gt;
* VMTK Slicer&lt;br /&gt;
** background: during 2007, functionality for turning vmtk command lines into Slicer command-line modules had been implemented. However, need for interactive modules based on vmtk was still needed.&lt;br /&gt;
** during 2008, a first implementation of some of the interactive components of VMTK segmentation has been created, although no code has been committed to the sandbox yet. Rather, this work will be integrated with the work of Daniel Haehn during the January 2009 project week in SLC. In this context, the addition of a vtkMRMLLevelSet node will be proposed (derived from vtkMRMLScalarVolumeNode with a poly data display node).&lt;br /&gt;
** in the meantime, VMTK has been largely improved and now provides vessel enhancement and surface and volume mesh generation capabilities. Therefore, the integration of VMTK in Slicer will readily bring these functionalities to Slicer. In addition, the Mario Negri Institute has implemented and validated a computational fluid dynamics solver that could be interfaced with Slicer and the NAMIC kit.&lt;br /&gt;
&lt;br /&gt;
* ITK&lt;br /&gt;
** during the first half of 2008, the extension of the level set framework to (moderately) anisotropic voxel spacings has been committed to ITK. Work is underway to extend the sparse field level set framework to severely anisotropic spacings.&lt;br /&gt;
** during August 2008, a first draft implementation of a modular level set framework with pluggable terms has been coded, and will tentatively be commited to the NAMIC sandbox during the January 2009 project week.&lt;br /&gt;
&lt;br /&gt;
* Project weeks&lt;br /&gt;
** during the 2008 January AHM in SLC, a presentation was given at the [[2008_Winter_Project_Week_Geometry_and_Topology_processing_of_Meshes | Geometry and Topology Processing of Meshes]] breakout session.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Extending ITK finite difference and level set filters to anisotropic spacing ==&lt;br /&gt;
&lt;br /&gt;
This is the (tentative) list of classes that assume that spacing is isotropic (i.e. they give incorrect results for anisotropic spacings).&lt;br /&gt;
The plan is to go in and extend them to properly account for anisotropic spacings. This addresses BUG [http://public.kitware.com/Bug/view.php?id=6156 ITK 6156].&lt;br /&gt;
&lt;br /&gt;
* Insight/Code/Common:&lt;br /&gt;
** itkLevelSetFunction - FIXED&lt;br /&gt;
** itkSegmentationLevelSetFunction - FIXED&lt;br /&gt;
&lt;br /&gt;
* Insight/Code/BasicFilters:&lt;br /&gt;
** itkLevelSetFunctionWithRefitTerm&lt;br /&gt;
** itkNormalVectorDiffusionFunction&lt;br /&gt;
** itkParallelSparseFieldLevelSetImageFilter&lt;br /&gt;
** itkSparseFieldFourthOrderLevelSetImageFilter&lt;br /&gt;
** itkSparseFieldLevelSetImageFilter - FIXED&lt;br /&gt;
&lt;br /&gt;
Insight/Code/Algorithms:&lt;br /&gt;
** itkBinaryMinMaxCurvatureFlowFunction&lt;br /&gt;
** tkCurvatureFlowFunction - FIXED&lt;br /&gt;
** itkLevelSetNeighborhoodExtractor&lt;br /&gt;
** itkLevelSetVelocityNeighborhoodExtractor&lt;br /&gt;
** itkReinitializeLevelSetImageFilter&lt;br /&gt;
** itkShapePriorSegmentationLevelSetFunction&lt;br /&gt;
&lt;br /&gt;
== 2008 Winter Project Week ==&lt;br /&gt;
&lt;br /&gt;
* Python modules: Python support, existing modules and new modules&lt;br /&gt;
* Transform hardening in MRML (should be finished on a local copy before the project week)&lt;br /&gt;
* Localized command line modules using MRML transform hardening&lt;br /&gt;
* Breakout: Geometry and Topology processing of Meshes&lt;br /&gt;
* vmtk module&lt;br /&gt;
&lt;br /&gt;
== Python modules ==&lt;br /&gt;
&lt;br /&gt;
Below is a list of Python modules that will be implemented using the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation:Python Python script plugin] functionality.&lt;br /&gt;
&lt;br /&gt;
===Done===&lt;br /&gt;
* SurfaceConnectivity.py (color by connected regions or extract the connected surface closest to a fiducial) (issue: crash with more than one fiducial on the Mac?)&lt;br /&gt;
* SurfaceToolbox.py (decimation + smoothing + normals + cleaner, with individual &amp;quot;Enable&amp;quot; switches)&lt;br /&gt;
* PythonScript.py (takes a surface and/or an image, runs Python code on it loading it from a file, and output the result. Fast way of using Slicer through Python and prototyping modules) (why does it fail with multiple inputs/outputs on the Mac?)&lt;br /&gt;
* GradientAnisotropicDiffusion.py (by Dan)&lt;br /&gt;
* SurfaceICPRegistration.py&lt;br /&gt;
&lt;br /&gt;
===In the works===&lt;br /&gt;
* SurfaceTransformHardening.py&lt;br /&gt;
&lt;br /&gt;
===Ideas===&lt;br /&gt;
* MarchingCubes.py&lt;br /&gt;
* ArrayCalculator.py&lt;br /&gt;
* Glyphs.py&lt;br /&gt;
* ShortestPath.py (use new Djikstra path)&lt;br /&gt;
* Reference system handling&lt;br /&gt;
&lt;br /&gt;
== Ideas for Slicer3 ==&lt;br /&gt;
&lt;br /&gt;
=== vmtk ===&lt;br /&gt;
&lt;br /&gt;
* figure out an official way to use vmtk within slicer and provide concrete examples and several modules:&lt;br /&gt;
** vessel enhancement&lt;br /&gt;
** vessel segmentation&lt;br /&gt;
** geometric analysis&lt;br /&gt;
** meshing for CFD&lt;br /&gt;
** visualization of CFD data&lt;br /&gt;
* check if any of the vmtk C++ classes can be used for stand-alone C++ modules  (e.g. centerline computation, finite elements)&lt;br /&gt;
* running modules in a localized space is vital: one solution has been implemented in Boston, but a more general approach would have a broader impact (see below)&lt;br /&gt;
* output fiducials would be useful (see below) but not vital for vmtk integration, can be circumvented using world points&lt;br /&gt;
* multistage modules would be useful (see below) but not essential&lt;br /&gt;
* packaging is tricky, but can be postponed for now&lt;br /&gt;
* future developments: vmtk through Tcl, or vmtk through Python through Tcl&lt;br /&gt;
&lt;br /&gt;
=== Modules in localized space ===&lt;br /&gt;
* the rationale is to give command line modules a chance to run in a space where images are oriented as X Y Z (i.e. fully specified by a vtkImageData) but still have correct information available as to image origin, spacing and up/down, left/right, front/back consistency. &lt;br /&gt;
* the solution implemented in Boston consists in computing the transform from the localized space (the XYZ one) to Slicer's RAS for the first image in the CLI. All other CLI arguments (images, surfaces, fiducials and ROIs) are transformed using that transform before being written to command line. Upon completion, Slicer reads the results (which have been generated in localized space) and puts them in the scene as children of the RAStoLocal transform. &lt;br /&gt;
* nicer (more general) solution: there should be a localization mechanism by which Slicer3 creates a miniscene relative to a transformable node (image, model, transform, etc) and runs the module using that miniscene. This involves that all inputs, fiducials, ROIs, etc are first transformed to that miniscene root transform node. The outputs would also be reimported as children of the miniscene. &lt;br /&gt;
** if the CLI module is MRML-aware, Slicer3 will let the module deal with the mini scene&lt;br /&gt;
** if the CLI module is not MRML-aware, Slicer3 will take care of hardening the transforms up to the miniscene's root on the images, surfaces, fiducials, etc, exporting the hardened nodes (which are now direct descendants of the miniscene root), reimporting the results and transferring the mini scene contents to the main scene. &lt;br /&gt;
&lt;br /&gt;
=== Hardening transforms ===&lt;br /&gt;
&lt;br /&gt;
* a user should be able to harden transforms on nodes. In the MRML tree, if a user moves a node and changes its parent (say, from a parent trasform to root), this can have two different meanings:&lt;br /&gt;
** the basis changes, the data doesn't (the way it works now): the effect is that the node changes its position and orientation in the 3D window. &lt;br /&gt;
** the basis doesn't change, the data does: the effect is now that the position and orientation of the node are unchanged, but the node is now child of a different transform (this is what I'd call hardening). This is essential for non-MRML aware command line modules: e.g. if an input image is a child of some transform, it should be hardened (i.e. the IJKToRAS should be composed with the parent transform) before it's written to command line.&lt;br /&gt;
&lt;br /&gt;
=== Output fiducials ===&lt;br /&gt;
&lt;br /&gt;
* currently outputs can be data (images, models) and transforms. However, I also see a need for output fiducials (and ROIs). For example, a module could run in two stages: 1) identification of feature points; 2) operation performed on the feature points. Between 1) and 2) the user should be able to manipulate the fiducials (here I'm thinking at centerline computation: 1) could identify possible endpoints, 2) could trace centerlines between user-selected pairs of enpoints). Therefore, 1) should spit fiducials (with text) as output. &lt;br /&gt;
* output fiducials with text to be placed in scene: probably either through a vtkMRMLFiducialStorageNode that outputs a vtp file or through an XML data structure sent to output as a file or on stdout; the solution of XML description in a XML file is probably the best.&lt;br /&gt;
&lt;br /&gt;
=== Python ===&lt;br /&gt;
* write some sample modules;&lt;br /&gt;
* extend scripted modules to Python?&lt;br /&gt;
&lt;br /&gt;
=== DBPs ===&lt;br /&gt;
&lt;br /&gt;
* vascular (vmtk): segmentation, analysis, meshing, CFD for atherosclerosis, cerebral aneurysms, AAAs.&lt;br /&gt;
* segmentation and registration in PKD (polycystic kidney disease);&lt;br /&gt;
* functional renal imaging;&lt;br /&gt;
* functional brain imaging;&lt;br /&gt;
&lt;br /&gt;
=== Multistage modules ===&lt;br /&gt;
&lt;br /&gt;
Below is a thread on the mailing list on multistage modules. The discussion took place in Boston.&lt;br /&gt;
&lt;br /&gt;
It's sorted according to positive time.&lt;br /&gt;
&lt;br /&gt;
==== Luca ====&lt;br /&gt;
&lt;br /&gt;
Hi everyone,&lt;br /&gt;
I've got a couple of thoughts regarding command line modules.&lt;br /&gt;
Currently Slicer processes command line modules by looking in the  modules directory, choosing files that could either be executables or  shared libraries, peeking into them to see if they are well behaved  and later querying them for their XML description.&lt;br /&gt;
Another possible design (somewhat closer to what Paraview uses) could  have been to have executables (or shared libraries) accompanied by  XML files containing the description of both the executable (or the  shared library) and the GUI parameters.&lt;br /&gt;
The disadvantage would have been to have two files per plugin instead  of one. The advantages would be avoiding peeking into executables or  shared libraries (the XML file could contain that information  already), possibly also speeding up module discovery times. Another  advantage would be making it easier to add other kinds of command  line modules (I'm thinking about Python classes) without messing too  much with the module discovery phase.&lt;br /&gt;
This solution would be come with an additional advantage: multi- staged command line modules.&lt;br /&gt;
Very often a module has the need of doing some processing, asking the  user for info, then processing, then asking for info, and so on.&lt;br /&gt;
This is now possible in Slicer by breaking up a program in several  command line modules, but it would be neat to have a tabbed or wizard  GUI that guides you through the process.&lt;br /&gt;
What I'm thinking is that a single command line module plugin could  be made up of several executables called at each step of a wizard  built using the XML file.&lt;br /&gt;
Separating XML descriptions and executables (or shared libraries)  would make this easier, since one XML file could contain a reference  to several executables, while the current design of asking the  executable for its XML description would make this more complicated.&lt;br /&gt;
Just to clarify: it's not my intention to spread confusion and mess  with a solid and already well established design, but I figured I  would share this thoughts.&lt;br /&gt;
Thanks and see you soon&lt;br /&gt;
Luca&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Steve ====&lt;br /&gt;
&lt;br /&gt;
Hi Luca -&lt;br /&gt;
&lt;br /&gt;
That's a very interesting idea.... it seems to me that could coexist what the current paradigm nicely.&lt;br /&gt;
&lt;br /&gt;
There's another way of creating modules currently supported in slicer3, which we haven't pushed much because it's somewhat experimental.  I'm referring to the ScriptedModule approach used by the Editor module - it's analogous to the CommandLineModule in that modules are discovered at startup, but instead of defining the GUI indirectly with XML, the ScriptedModule can use the tcl API to create it's own GUI and interact with MRML directly.  But I like what you are proposing too because it can retain more of the flexibility to run as either command line tools or as module.&lt;br /&gt;
&lt;br /&gt;
It'll be fun to discuss these options when we get together.&lt;br /&gt;
&lt;br /&gt;
-Steve&lt;br /&gt;
&lt;br /&gt;
==== Bill ====&lt;br /&gt;
&lt;br /&gt;
Interesting ideas, Luca!&lt;br /&gt;
&lt;br /&gt;
I have found myself wanting a bit more interactivity in the command-line&lt;br /&gt;
modules, too. My ambitions are not as lofty as Luca's, however. It would&lt;br /&gt;
be nice to have an input parameter be a 2-way parameter, and to have&lt;br /&gt;
another special execution mode run from the command line so that the&lt;br /&gt;
module could accept the input parameter values, compute some value that&lt;br /&gt;
derived from these inputs, set the value of one or more of the 2-way&lt;br /&gt;
parameters, and then return to Slicer and have Slicer display the&lt;br /&gt;
computed values. This could be mediated by one or more new XML&lt;br /&gt;
command-line options like &amp;lt;cmd&amp;gt;update-params&amp;lt;/cmd&amp;gt; or some such.&lt;br /&gt;
&lt;br /&gt;
Another thing that I have wanted is some more flexibility in how the GUI&lt;br /&gt;
is built for command-line modules. I am working on an application that&lt;br /&gt;
would really benefit from having sliders in the GUI, but if I read the&lt;br /&gt;
Execution Model docs correctly, that only works for built-in modules,&lt;br /&gt;
not for command line modules.&lt;br /&gt;
&lt;br /&gt;
Finally, and this is a biggy -- I wonder if it would be possible to&lt;br /&gt;
implement the interface between Slicer3 and the command line modules so&lt;br /&gt;
that parameters and data could be passed in memory instead of in&lt;br /&gt;
temporary files on disk? This might be possible if pipes are substituted&lt;br /&gt;
for disk files; the API for reading and writing to pipes is pretty&lt;br /&gt;
similar to file I/O, and most systems implement pipes as shared memory&lt;br /&gt;
transfer. Just a thought.&lt;br /&gt;
&lt;br /&gt;
-Bill Leue&lt;br /&gt;
&lt;br /&gt;
==== Raul ====&lt;br /&gt;
&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;br /&gt;
I want to join to the great ideas of Luca and Bill to extend the &lt;br /&gt;
interactivity of the command-line-module.&lt;br /&gt;
In the same direction, it would be nice to be able to have more control &lt;br /&gt;
(for projects that required some advanced customization) before and &lt;br /&gt;
after the module execution in the Slicer execution environment. For &lt;br /&gt;
example, for tensors, it would be great to have the chance to set up &lt;br /&gt;
MRML nodes according to the outputs to assigned a mask and a DWI to the &lt;br /&gt;
tensor MRML node.&lt;br /&gt;
This would equate to be able to prescribe two virtual methods, &lt;br /&gt;
BeforeUpdate and AfterUpdate, from the XML description that would &lt;br /&gt;
generate the appropriate code in the Command Line Interface part. I'm &lt;br /&gt;
thinking something like:&lt;br /&gt;
&amp;lt;code, method=AfterUpdate&amp;gt;&lt;br /&gt;
&amp;lt;method&amp;gt;&lt;br /&gt;
//output1Node is a vtkMRMLDiffusionTensorNode&lt;br /&gt;
output1Node-&amp;gt;SetAndObserveDiffusionWeightedVolume(inputNode-&amp;gt;GetID());&lt;br /&gt;
&amp;lt;/method&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
/Raul&lt;br /&gt;
&lt;br /&gt;
= Misc comments =&lt;br /&gt;
&lt;br /&gt;
* Transforms and CLI: &lt;br /&gt;
** the rationale is to give command line modules a chance not to worry about transforms but still have correct information available as to spacing and up/down, left/right, front/back consistency&lt;br /&gt;
** the image passed to a command line module should be in normalized orientation space, i.e.: real origin, real spacing, &lt;br /&gt;
** reference node specified in XML (either tag of the reference node or tag of child nodes to the reference - the latter allows many references in the same command line). Images in normalized orientation space.&lt;br /&gt;
** the reference transform should be just a rigid transformation bringing the axes to XYZ (by looking at projections, but not necessarily). Therefore, from the node transform, a RASToLocalMatrix should be extracted, containing only the cosines that bring the axes to XYZ.&lt;br /&gt;
** for each XML node, specify what's its reference node. The default is patient space (identity matrix), but in general it could be another node. So the current node matrix should be multiplied by the inverse of the reference node matrix before being written out. Correspondingly, when the command line module has executed, all results have to be multiplied by the corresponding reference node matrix. A reference node could be the node itself, meaning that the node transform wil be multiplied by the inverse of its reference transform.&lt;br /&gt;
** find ways to harden transforms for specific MRML nodes&lt;br /&gt;
** in the end: the writer of a command line module or Python scripted module etc. has to be put in the condition of not knowing anything about transforms, and still deal with legal vtkImageData objects (with their own spacing and right-handedness)&lt;br /&gt;
&lt;br /&gt;
* Multi-stage CLI:&lt;br /&gt;
** wizard or tabbed interface with content generated one page per command line module, and user control is returned from one page to the next.&lt;br /&gt;
** one XML that puts command line modules together. This way command line modules can be either used alone or in a wizard.&lt;br /&gt;
** change the way CLI are specified: XML files are discovered first, each XML describes how's the module is going to be (executable, shared library, Python class, etc). This saves time for module discovery (at least on OSX), and (as suggested by Raoul) it makes it easy for a developer to know how that CLI is going to behave and to develop against it.&lt;br /&gt;
&lt;br /&gt;
* Fix vtkITK CMakeLists.txt (generate vtkITKTCL.so separately from vtkITK.so).&lt;br /&gt;
&lt;br /&gt;
* XML module GUI:&lt;br /&gt;
** give possibility to build a GUI from XML in ScriptedModules (either from Tcl or Python) or even everywhere in Slicer3, even from C++.&lt;br /&gt;
&lt;br /&gt;
* Python: &lt;br /&gt;
** try wrapping VTK. What happens when Python through Tcl is used and ShallowCopy to a true VTK module is called?&lt;br /&gt;
&lt;br /&gt;
* Annotation widget&lt;br /&gt;
** do it for command line modules (like: put this string at this point in the scene)&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33175</id>
		<title>2009 Winter Project Week Python</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week_Python&amp;diff=33175"/>
		<updated>2008-12-10T18:28:35Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: New page: {| |Project Week Main Page ]] |}   __NOTOC__   ===Key Investigators=== * Luca Antiga (Medical Imaging Unit, Biomedi...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:NAMIC-SLC.jpg|thumb|320px|Return to [[2009_Winter_Project_Week|Project Week Main Page]] ]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Luca Antiga (Medical Imaging Unit, Biomedical Engineering Department, Mario Negri Institute)&lt;br /&gt;
* Steve Piper (Isomics)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
TODO&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TODO.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
TO:&amp;lt;br&amp;gt;&lt;br /&gt;
- DO&amp;lt;br&amp;gt;&lt;br /&gt;
- ...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week&amp;diff=33174</id>
		<title>2009 Winter Project Week</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week&amp;diff=33174"/>
		<updated>2008-12-10T18:26:07Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Other NA-MIC Projects */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[Project Events]], [[AHM_2009]], [[Events]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction to NA-MIC Project Week==&lt;br /&gt;
&lt;br /&gt;
Please read an introduction about these events [[Project_Events#Introduction|here]].&lt;br /&gt;
&lt;br /&gt;
== Dates.Venue.Registration ==&lt;br /&gt;
&lt;br /&gt;
Please [[AHM_2009#Dates._Venue._Registration| click here for Dates, Venue, and Registration]] for this event.&lt;br /&gt;
&lt;br /&gt;
== Agenda==&lt;br /&gt;
&lt;br /&gt;
Please [[AHM_2009#Agenda|click here for the agenda for AHM 2009 and Project Week]].&lt;br /&gt;
&lt;br /&gt;
==Projects==&lt;br /&gt;
Please note:&lt;br /&gt;
*Please use the [[2009_Winter_Project_Week_Template|'''2009 Project Week Template''']] to create a page for your project(s)&lt;br /&gt;
*[[2008_Summer_Project_Week#Projects|Last Event's Projects as a reference]]&lt;br /&gt;
*For hosting projects, we are planning to make use of the NITRC resources.  See [[NA-MIC_and_NITRC | Information about NITRC Collaboration]]&lt;br /&gt;
*Next Project Week is at MIT -- June 22-26, 2009&lt;br /&gt;
The following is a list of all projects that will be pursued at this meeting.&lt;br /&gt;
&lt;br /&gt;
===NA-MIC DBP Roadmap Projects===&lt;br /&gt;
Please note that these projects correspond to four clinical Roadmap application projects that will be pursued in focused parallel tracks at the meeting, each corresponding to a DBP problem.  &lt;br /&gt;
&lt;br /&gt;
#[[DBP2:Harvard:Brain_Segmentation_Roadmap|Harvard Roadmap Project: Stochastic Tractography for VCFS]]&lt;br /&gt;
##[[2009_Winter_Project_Week:GT_TubularSurfaceSeg|Tubular Surface Segmentation for fiber bundle extraction]] (Vandana Mohan GATech, Allen Tannenbaum GATech, Marek Kubicki BWH)&lt;br /&gt;
##[[2009_Winter_Project_Week_StochasticTractography |Stochastic Tractograhy Tool for Slicer]] (Marek Kubicki BWH, Julien de Siebenthal BWH) &lt;br /&gt;
##[[2009_Winter_Project_Week_Slicer3Functioning |Evaluation of basic Slicer 3.0 Functionality from a User Perspective]] (Doug Terry BWH, Marek Kubicki BWH) &lt;br /&gt;
#[[DBP2:UNC:Cortical_Thickness_Roadmap|UNC Roadmap Project: Cortical Thickness Measurement for Autism]]&lt;br /&gt;
#[[DBP2:MIND:Roadmap|MIND Roadmap Project: Brain Lesion Analysis in Lupus]]&lt;br /&gt;
#[[DBP2:JHU:Roadmap|JHU Roadmap Project: Segmentation and Registration for Robotic Prostate Intervention]]&lt;br /&gt;
&lt;br /&gt;
===Other NA-MIC Projects===&lt;br /&gt;
#Fluid mechanics tractography and visualization (Nathan Hageman UCLA)&lt;br /&gt;
#UCLA BrainLab/Slicer Neurosurgery Preoperative Tumor Planning - using Slicer and its link to BrainLab to investigate whether different tractography methods aid in preoperative planning of tumor resection.(Nathan Hageman UCLA)&lt;br /&gt;
#Development of FEM / FVM solver library in ITK/VTK (and/or Python?) (Nathan Hageman UCLA, Vince, Luca, Steve)&lt;br /&gt;
#[[2009_Winter_Project_Week_Transform_Management | Transform Management]](Jim Miller)&lt;br /&gt;
#Interactive 3D Widgets - Introduce new interactors into Slicer (Karthik)&lt;br /&gt;
#[[2009_Winter_Project_Week_vtkITK_Pipeline | Using ITK in VTK Pipelines]] (Jim, Steve)&lt;br /&gt;
#User Interface Flexible Layouts (Wendy, Jim, Steve)&lt;br /&gt;
#[[2009_Winter_Project_Week_Python | Python interface completion and packaging - Fortran and openssl problems]] (Luca, Steve)&lt;br /&gt;
#Two-tensor tractography in Slicer using Python and Teem (Madeleine Seeland, C-F Westin)&lt;br /&gt;
#[[2009_Winter_Project_Week_Rotation_Tangents | Diffusion Tensor Invariant gradients and rotation tangents in Python and Teem]] (Peter Savadjiev, C-F Westin and Gordon Kindlmann)&lt;br /&gt;
#xnat and batchmake integration (Julien, Dan Marcus)&lt;br /&gt;
#Automated GUI testing (Sebastien, Interested User: Vince)&lt;br /&gt;
#Slicer Colors Module update (Nicole)&lt;br /&gt;
#Volume Rendering (Alex, Curt, Nicholas)&lt;br /&gt;
#XNAT Dekstop &amp;amp; File Repository prototypes (Dan Marcus, Wendy Plesniak)&lt;br /&gt;
#Cortical correspondence using DTI (Ipek, Martin)&lt;br /&gt;
#[[2009_Winter_Project_Week_Command_Line_Program_Testing |Command Line Program Testing]] (Lorensen, NA-MIC)&lt;br /&gt;
#[[2009_Winter_Project_Week_Slicer_VMTK |Vessel Segmentation in Slicer using VMTK]] ([[User:haehn|Daniel Haehn]], Luca Antiga)&lt;br /&gt;
#[[2009_Winter_Project_Week_fMRI_Clustering |Exploring Functional Connectivity in fMRI via Clustering]] (Archana Venkataraman, Marek Kubicki, Polina Golland)&lt;br /&gt;
#[[2009_Winter_Project_Week_Compiler_Warnings:Slicer3_Graffiti |Compiler Warnings:Slicer3's Graffiti]] (Lorensen, NA-MIC)&lt;br /&gt;
&lt;br /&gt;
===External Collaborations===&lt;br /&gt;
* [[Iowa Meshing Tutorial]] &lt;br /&gt;
** (the work is likely to be completed by the AHM)&lt;br /&gt;
*Wake Forest - Virginia Tech&lt;br /&gt;
** [[2009_Winter_Project_Week_WFU1 | Move to All Slicer3 Workflow]]&lt;br /&gt;
** [[2009_Winter_Project_Week_WFU2 | Development of deformation based morphometry module]]&lt;br /&gt;
*Georgetown U: Prototype RF Lesion Ablation Workflow prototyped in Slicer&lt;br /&gt;
*UNC: &lt;br /&gt;
**[[2009_UNC_HAMMER | MR-image registration algorithm to be extended and added to namic kit]]&lt;br /&gt;
**[[2009_UNC_White_Matter_Lesion | white matter lesion segmentation]]&lt;br /&gt;
*Mario Negri&lt;br /&gt;
*Stanford SIMBIOS: segmentation of knee joint&lt;br /&gt;
* [[2009_Winter_Project_Week_MRSI | MRSI Module for Slicer (Bjoern Menze)]]&lt;br /&gt;
&lt;br /&gt;
=== Preparation ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
# Please make sure that you are on the [http://public.kitware.com/cgi-bin/mailman/listinfo/na-mic-project-week na-mic-project-week mailing list]&lt;br /&gt;
# Starting Thursday, October 16th, part of the weekly Thursday 3pm NA-MIC Engineering TCON will be used to prepare for this meeting.  The schedule for these preparatory calls is as follows:&lt;br /&gt;
#*October 16: Engineering Infrastructure Projects&lt;br /&gt;
#*October 23: Funded External Collaboration Projects&lt;br /&gt;
#*November 6: DPB Projects &lt;br /&gt;
#*November 20: New Collaborations&lt;br /&gt;
#*December 4: Other Projects&lt;br /&gt;
#*December 18: Loose Ends&lt;br /&gt;
#By December 17, 2008: [[2009_Winter_Project_Week_Template|Complete a templated wiki page for your project]]. Please do not edit the template page itself, but create a new page for your project and cut-and-paste the text from this template page.  If you have questions, please send an email to tkapur at bwh.harvard.edu.&lt;br /&gt;
# By December 17, 2008: Create a directory for each project on the [[Engineering:SandBox|NAMIC Sandbox]] (Zack)&lt;br /&gt;
##[https://www.kitware.com/Admin/SendPassword.cgi Ask Zack for a Sandbox account]&lt;br /&gt;
## Commit on each sandbox directory the code examples/snippets that represent our first guesses of appropriate methods. (Luis and Steve will help with this, as needed)&lt;br /&gt;
## Gather test images in any of the Data sharing resources we have (e.g. the BIRN). These ones don't have to be many. At least three different cases, so we can get an idea of the modality-specific characteristics of these images. Put the IDs of these data sets on the wiki page. (the participants must do this.)&lt;br /&gt;
## Setup nightly tests on a separate Dashboard, where we will run the methods that we are experimenting with. The test should post result images and computation time. (Zack)&lt;br /&gt;
# FINAL TCON: December 18th 3pm ET to tie loose ends&lt;br /&gt;
# Please note that by the time we get to the project event, we should be trying to close off a project milestone rather than starting to work on one...&lt;br /&gt;
&lt;br /&gt;
== Previous Project Events ==&lt;br /&gt;
&lt;br /&gt;
A history of all the programming/project events in NA-MIC is available by following [[Project Events|this link]].&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week&amp;diff=33173</id>
		<title>2009 Winter Project Week</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2009_Winter_Project_Week&amp;diff=33173"/>
		<updated>2008-12-10T18:24:28Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Other NA-MIC Projects */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[Project Events]], [[AHM_2009]], [[Events]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction to NA-MIC Project Week==&lt;br /&gt;
&lt;br /&gt;
Please read an introduction about these events [[Project_Events#Introduction|here]].&lt;br /&gt;
&lt;br /&gt;
== Dates.Venue.Registration ==&lt;br /&gt;
&lt;br /&gt;
Please [[AHM_2009#Dates._Venue._Registration| click here for Dates, Venue, and Registration]] for this event.&lt;br /&gt;
&lt;br /&gt;
== Agenda==&lt;br /&gt;
&lt;br /&gt;
Please [[AHM_2009#Agenda|click here for the agenda for AHM 2009 and Project Week]].&lt;br /&gt;
&lt;br /&gt;
==Projects==&lt;br /&gt;
Please note:&lt;br /&gt;
*Please use the [[2009_Winter_Project_Week_Template|'''2009 Project Week Template''']] to create a page for your project(s)&lt;br /&gt;
*[[2008_Summer_Project_Week#Projects|Last Event's Projects as a reference]]&lt;br /&gt;
*For hosting projects, we are planning to make use of the NITRC resources.  See [[NA-MIC_and_NITRC | Information about NITRC Collaboration]]&lt;br /&gt;
*Next Project Week is at MIT -- June 22-26, 2009&lt;br /&gt;
The following is a list of all projects that will be pursued at this meeting.&lt;br /&gt;
&lt;br /&gt;
===NA-MIC DBP Roadmap Projects===&lt;br /&gt;
Please note that these projects correspond to four clinical Roadmap application projects that will be pursued in focused parallel tracks at the meeting, each corresponding to a DBP problem.  &lt;br /&gt;
&lt;br /&gt;
#[[DBP2:Harvard:Brain_Segmentation_Roadmap|Harvard Roadmap Project: Stochastic Tractography for VCFS]]&lt;br /&gt;
##[[2009_Winter_Project_Week:GT_TubularSurfaceSeg|Tubular Surface Segmentation for fiber bundle extraction]] (Vandana Mohan GATech, Allen Tannenbaum GATech, Marek Kubicki BWH)&lt;br /&gt;
##[[2009_Winter_Project_Week_StochasticTractography |Stochastic Tractograhy Tool for Slicer]] (Marek Kubicki BWH, Julien de Siebenthal BWH) &lt;br /&gt;
##[[2009_Winter_Project_Week_Slicer3Functioning |Evaluation of basic Slicer 3.0 Functionality from a User Perspective]] (Doug Terry BWH, Marek Kubicki BWH) &lt;br /&gt;
#[[DBP2:UNC:Cortical_Thickness_Roadmap|UNC Roadmap Project: Cortical Thickness Measurement for Autism]]&lt;br /&gt;
#[[DBP2:MIND:Roadmap|MIND Roadmap Project: Brain Lesion Analysis in Lupus]]&lt;br /&gt;
#[[DBP2:JHU:Roadmap|JHU Roadmap Project: Segmentation and Registration for Robotic Prostate Intervention]]&lt;br /&gt;
&lt;br /&gt;
===Other NA-MIC Projects===&lt;br /&gt;
#Fluid mechanics tractography and visualization (Nathan Hageman UCLA)&lt;br /&gt;
#UCLA BrainLab/Slicer Neurosurgery Preoperative Tumor Planning - using Slicer and its link to BrainLab to investigate whether different tractography methods aid in preoperative planning of tumor resection.(Nathan Hageman UCLA)&lt;br /&gt;
#Development of FEM / FVM solver library in ITK/VTK (and/or Python?) (Nathan Hageman UCLA, Vince, Luca, Steve)&lt;br /&gt;
#[[2009_Winter_Project_Week_Transform_Management | Transform Management]](Jim Miller)&lt;br /&gt;
#Interactive 3D Widgets - Introduce new interactors into Slicer (Karthik)&lt;br /&gt;
#[[2009_Winter_Project_Week_vtkITK_Pipeline | Using ITK in VTK Pipelines]] (Jim, Steve)&lt;br /&gt;
#User Interface Flexible Layouts (Wendy, Jim, Steve)&lt;br /&gt;
#[[2009_Winter_Project_Week_Python Python wrapping and packaging Python Interface - Fortran and openssl problems]] (Luca, Steve)&lt;br /&gt;
#Two-tensor tractography in Slicer using Python and Teem (Madeleine Seeland, C-F Westin)&lt;br /&gt;
#[[2009_Winter_Project_Week_Rotation_Tangents | Diffusion Tensor Invariant gradients and rotation tangents in Python and Teem]] (Peter Savadjiev, C-F Westin and Gordon Kindlmann)&lt;br /&gt;
#xnat and batchmake integration (Julien, Dan Marcus)&lt;br /&gt;
#Automated GUI testing (Sebastien, Interested User: Vince)&lt;br /&gt;
#Slicer Colors Module update (Nicole)&lt;br /&gt;
#Volume Rendering (Alex, Curt, Nicholas)&lt;br /&gt;
#XNAT Dekstop &amp;amp; File Repository prototypes (Dan Marcus, Wendy Plesniak)&lt;br /&gt;
#Cortical correspondence using DTI (Ipek, Martin)&lt;br /&gt;
#[[2009_Winter_Project_Week_Command_Line_Program_Testing |Command Line Program Testing]] (Lorensen, NA-MIC)&lt;br /&gt;
#[[2009_Winter_Project_Week_Slicer_VMTK |Vessel Segmentation in Slicer using VMTK]] ([[User:haehn|Daniel Haehn]], Luca Antiga)&lt;br /&gt;
#[[2009_Winter_Project_Week_fMRI_Clustering |Exploring Functional Connectivity in fMRI via Clustering]] (Archana Venkataraman, Marek Kubicki, Polina Golland)&lt;br /&gt;
#[[2009_Winter_Project_Week_Compiler_Warnings:Slicer3_Graffiti |Compiler Warnings:Slicer3's Graffiti]] (Lorensen, NA-MIC)&lt;br /&gt;
&lt;br /&gt;
===External Collaborations===&lt;br /&gt;
* [[Iowa Meshing Tutorial]] &lt;br /&gt;
** (the work is likely to be completed by the AHM)&lt;br /&gt;
*Wake Forest - Virginia Tech&lt;br /&gt;
** [[2009_Winter_Project_Week_WFU1 | Move to All Slicer3 Workflow]]&lt;br /&gt;
** [[2009_Winter_Project_Week_WFU2 | Development of deformation based morphometry module]]&lt;br /&gt;
*Georgetown U: Prototype RF Lesion Ablation Workflow prototyped in Slicer&lt;br /&gt;
*UNC: &lt;br /&gt;
**[[2009_UNC_HAMMER | MR-image registration algorithm to be extended and added to namic kit]]&lt;br /&gt;
**[[2009_UNC_White_Matter_Lesion | white matter lesion segmentation]]&lt;br /&gt;
*Mario Negri&lt;br /&gt;
*Stanford SIMBIOS: segmentation of knee joint&lt;br /&gt;
* [[2009_Winter_Project_Week_MRSI | MRSI Module for Slicer (Bjoern Menze)]]&lt;br /&gt;
&lt;br /&gt;
=== Preparation ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
# Please make sure that you are on the [http://public.kitware.com/cgi-bin/mailman/listinfo/na-mic-project-week na-mic-project-week mailing list]&lt;br /&gt;
# Starting Thursday, October 16th, part of the weekly Thursday 3pm NA-MIC Engineering TCON will be used to prepare for this meeting.  The schedule for these preparatory calls is as follows:&lt;br /&gt;
#*October 16: Engineering Infrastructure Projects&lt;br /&gt;
#*October 23: Funded External Collaboration Projects&lt;br /&gt;
#*November 6: DPB Projects &lt;br /&gt;
#*November 20: New Collaborations&lt;br /&gt;
#*December 4: Other Projects&lt;br /&gt;
#*December 18: Loose Ends&lt;br /&gt;
#By December 17, 2008: [[2009_Winter_Project_Week_Template|Complete a templated wiki page for your project]]. Please do not edit the template page itself, but create a new page for your project and cut-and-paste the text from this template page.  If you have questions, please send an email to tkapur at bwh.harvard.edu.&lt;br /&gt;
# By December 17, 2008: Create a directory for each project on the [[Engineering:SandBox|NAMIC Sandbox]] (Zack)&lt;br /&gt;
##[https://www.kitware.com/Admin/SendPassword.cgi Ask Zack for a Sandbox account]&lt;br /&gt;
## Commit on each sandbox directory the code examples/snippets that represent our first guesses of appropriate methods. (Luis and Steve will help with this, as needed)&lt;br /&gt;
## Gather test images in any of the Data sharing resources we have (e.g. the BIRN). These ones don't have to be many. At least three different cases, so we can get an idea of the modality-specific characteristics of these images. Put the IDs of these data sets on the wiki page. (the participants must do this.)&lt;br /&gt;
## Setup nightly tests on a separate Dashboard, where we will run the methods that we are experimenting with. The test should post result images and computation time. (Zack)&lt;br /&gt;
# FINAL TCON: December 18th 3pm ET to tie loose ends&lt;br /&gt;
# Please note that by the time we get to the project event, we should be trying to close off a project milestone rather than starting to work on one...&lt;br /&gt;
&lt;br /&gt;
== Previous Project Events ==&lt;br /&gt;
&lt;br /&gt;
A history of all the programming/project events in NA-MIC is available by following [[Project Events|this link]].&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=NA-MIC_VMTK_Collaboration&amp;diff=33170</id>
		<title>NA-MIC VMTK Collaboration</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=NA-MIC_VMTK_Collaboration&amp;diff=33170"/>
		<updated>2008-12-10T18:21:10Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Goals of the Project */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Collaboration with [http://villacamozzi.marionegri.it/~luca/ Luca Antiga] of the [http://www.marionegri.it Mario Negri Institute].&lt;br /&gt;
&lt;br /&gt;
Back to [[NA-MIC_External_Collaborations]]&lt;br /&gt;
&lt;br /&gt;
[[Image:VmtkSlicerModule.jpg]]&lt;br /&gt;
[[Image:VoronoiVortices lowres.png]]&lt;br /&gt;
&lt;br /&gt;
===Goals of the Project===&lt;br /&gt;
To create a Slicer-based platform for segmentation of vascular segments from angiographic images (CTA, MRA, ...), analysis of vascular geometry, mesh generation and hemodynamic simulation (CFD) and visualization.&lt;br /&gt;
&lt;br /&gt;
Since many of these functionalities are already provided by the Vascular Modeling Toolkit ([http://www.vmtk.org www.vmtk.org]) as command-line tools, the plan is to integrate vmtk scripts within Slicer as command-line modules for the non-interactive tasks, and to create ad-hoc GUI modules for the more interactive tasks (i.e. segmentation).&lt;br /&gt;
&lt;br /&gt;
===Current progress===&lt;br /&gt;
* vmtk script for automated conversion of vmtk command line pipes to Slicer command-line modules (DONE)&lt;br /&gt;
* Slicer LevelSetSegment module for interactive level set segmentation (IN PROGRESS)&lt;br /&gt;
&lt;br /&gt;
=== References ===&lt;br /&gt;
&lt;br /&gt;
[http://vmtk.sourceforge.net vmtk.sourceforge.net]&lt;br /&gt;
&lt;br /&gt;
[[Collaboration/VMTK | 2007 Project Week at MIT]]&lt;br /&gt;
&lt;br /&gt;
=== Citations ===&lt;br /&gt;
* Lee SW, Antiga L, Spence JD and Steinman DA. Geometry of the carotid bifurcation predicts its exposure to disturbed flow. Stroke. Accepted.&lt;br /&gt;
* Thomas JB, Antiga L, Che S, Milner JS, Hangan Steinman DA, Spence JD, Rutt BK and Steinman DA. Variation in the carotid bifurcation geometry of young vs. older adults: Implications for &amp;quot;geometric risk&amp;quot; of atherosclerosis. Stroke, 36(11): 2450-2456, Nov 2005.&lt;br /&gt;
* Antiga L, Steinman DA. Robust and objective decomposition and mapping of bifurcating vessels. IEEE Transactions on Medical Imaging, 23(6): 704-713, June 2004.&lt;br /&gt;
* Antiga L, Ene-Iordache B and Remuzzi A. Computational geometry for patient-specific reconstruction and meshing of blood vessels from MR and CT angiography. IEEE Transactions on Medical Imaging, 22(5): 674-684, May 2003.&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=Engineering:TCON_2008&amp;diff=32286</id>
		<title>Engineering:TCON 2008</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=Engineering:TCON_2008&amp;diff=32286"/>
		<updated>2008-11-20T20:19:02Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* 2008-11-20 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[TCON:Main|TCON:Main]]&lt;br /&gt;
__NOTOC__&lt;br /&gt;
== Slicer 3 Dartboard ==&lt;br /&gt;
Link to the Slicer 3 Dartboard [http://public.kitware.com/dashboard.php?name=slicer3 here]&lt;br /&gt;
&lt;br /&gt;
==2008-11-20==&lt;br /&gt;
*Attendees: Jim, Tina, Katie, Curt, Will, Daniel, Vince, Wendy, Xiaodong, Nicole, Allen, Luca&lt;br /&gt;
Agenda: to discuss potential external collaborations.&lt;br /&gt;
*Daniel H - vessel segmentation collaboration with Luca and Raul&lt;br /&gt;
*Python and [http://neuroimaging.scipy.org/ NiPy] Collaboration Opportunities - Luca, Steve, Matthew Brett, Fernando Perez&lt;br /&gt;
*residual item from last week's call: jhu DBP - gabor, allen, katie&lt;br /&gt;
*Breakout session:&lt;br /&gt;
** Meshing Tutorial (Nicole, Vince, Curt, Steve)&lt;br /&gt;
** Python Modules (Demian, Luca?) &lt;br /&gt;
** GUI Testing and Developing Test Modules for Slicer  (Sebastien)&lt;br /&gt;
** How to use NITRC and slicer(Steve, Terry)&lt;br /&gt;
** how to use batchmake and xnat to process larger studies (Julien and Dan Marcus) &lt;br /&gt;
** DTI (sonia, randy, others?)&lt;br /&gt;
&lt;br /&gt;
==2008-11-13==&lt;br /&gt;
*Attendees: wendy, sebastien, Tina, vince, jim, steve&lt;br /&gt;
&lt;br /&gt;
Agenda:&lt;br /&gt;
*Which external collaborators need to be contacted for next week's tcon?&lt;br /&gt;
**daniel haehn at bwh - vessel seg project&lt;br /&gt;
**berkeley numerical python&lt;br /&gt;
*JHU didn't make last week's call&lt;br /&gt;
*Breakout session:&lt;br /&gt;
** Meshing Tutorial (Nicole, Vince, Curt, Steve)&lt;br /&gt;
** Python Modules (Demian, Luca?) &lt;br /&gt;
** GUI Testing and Developing Test Modules for Slicer  (Sebastien)&lt;br /&gt;
** How to use NITRC and slicer(Steve, Terry)&lt;br /&gt;
** how to use batchmake and xnat to process larger studies (Julien and Dan Marcus) &lt;br /&gt;
* Grok? http://www.slicer.org/source/xref/&lt;br /&gt;
&lt;br /&gt;
==2008-11-06==&lt;br /&gt;
'''DBP Projects Planning'''&lt;br /&gt;
&lt;br /&gt;
Attendees: Martin, Cedric, Clement, Jim, Steve, Nicole, Will, Curt, Katie, Mark, Dan, Jeremy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*[[AHM2009:Mind|MIND team]]: Jeremy, Mark, Ross, Steve &lt;br /&gt;
**Agenda Items for discussion&lt;br /&gt;
***status of co-registration&lt;br /&gt;
***status of brain extraction&lt;br /&gt;
***status of bias field correction&lt;br /&gt;
*[[AHM2009:UNC|UNC team]]: Heather, Jim, Martin, Clement&lt;br /&gt;
*[[AHM2009:JHU|JHU team]]: Gabor, Katie, Allen&lt;br /&gt;
*[[AHM2009:PNL|PNL team]] held on Monday Nov 3, 3pm ET&lt;br /&gt;
**Attendees: Marek, Polina, Brad, Guido, Jim, Steve, Tracy, Sylvain, Tina&lt;br /&gt;
**Q to dbp team: what are good alternatives to compare with, and what is a good way to compare?&lt;br /&gt;
**Q: how best to cover all the projects of DBP beyond the roadmap.&lt;br /&gt;
**Suggestion: increase tutorial time to 1 hour to allow coverage of projects with tutorials that have not been covered in DBP presentations&lt;br /&gt;
&lt;br /&gt;
'''Call Notes:'''&lt;br /&gt;
&lt;br /&gt;
*UNC Visit Dates:  December 15th visit for Will, Steve, and Julian&lt;br /&gt;
* AHM Planning: All participants need to start updating the Wiki.  Tina wants to remind all the DBPs that they have a timeslot for presentations during the AHM in January. The Wiki pages for projects need  to be filled out.  There will a presentation that is an overview of NA-MIC before the DBP.  This is under discussion on what it will contain.  Ross gave a NA-MIC overview at the NCBC meeting which could be a good guideline.  There is a new format for the DBP presentations where each team has 10 minutes.  &lt;br /&gt;
*Each roadmap project needs to have a tutorial that walks users through reproducable results.&lt;br /&gt;
*There is a contest for tutorials with the possibility of a prize awarded to the best tutorial.  The message to NIH should be about generating tools that help users to generate answers and results, not just new algorithms.  There is a focus on what are people doing with it. &lt;br /&gt;
&lt;br /&gt;
'''Specific Questions by the DBPs'''&lt;br /&gt;
* How should the cortical thickness module be integrated with Slicer?  An atlas is needed.  Should it be stored on NITRC, on the pub-db on SPL, or where?  NITRC is attractive because of its download support.  The Slicer modules are external modules.  The module would be on the Subversion archive on NITRC, the atlases would be additional files (not in SVN).  Discussion of how to make the module and the users aware of the atlases.  &lt;br /&gt;
*Discussion on Slicer integration: The Cortical Thickness Module is currently a single external module, which calls external application with a separate GUI.  These applications call other applications during processing.  There are five different modules.  For this AHM, users will have to download all required modules, but we should look at how to bundle them together later (via dependencies) or create the concept of a package of modules.  Details of how to organize the modules and store them in NITRC was discussed. &lt;br /&gt;
*Tutorial Datasets and Tutorial document should be placed on NITRC next to the module.  Add a link to the Slicer Tutorial page referencing the NITRC page.  &lt;br /&gt;
*BatchMake is used by Slicer modules.  How to create the BatchMake .bmm files so that the modules will initialize the BatchMake config files.  This is solved by the two-step Slicer initialization process.  The environment variables should be queried to find appropriate paths.&lt;br /&gt;
&lt;br /&gt;
==2008-10-30==&lt;br /&gt;
Agenda:&lt;br /&gt;
*3-3:30: Algorithm Core lead projects (confirmed callers: Allen, Martin, Ross, Marcel/Casey for Guido)&lt;br /&gt;
*http://wiki.na-mic.org/Wiki/index.php/AHM2009:JHU&lt;br /&gt;
Attendees: Jim, Will, Tina, Steve, Ross, Marcel (for Guido), Allen, Martin, Nicole, Katie, Dan Marcus, Vince&lt;br /&gt;
&lt;br /&gt;
Highlights:&lt;br /&gt;
*AHM agenda suggestions:&lt;br /&gt;
**increase Ross' talk to 30 minutes and add materials to it to ensure that highlights of activities beyond the core 3 roadmap projects are also included in the meeting&lt;br /&gt;
**Ross will circulate his talk to the group and solicit input+updated materials (an earlier version was presented in AUgust to all NCBC mtg)&lt;br /&gt;
**Include training and dissemination slides (a couple) into the same talk, and a couple of slides on the NA-MIC Kit&lt;br /&gt;
**Next week will be DBP specific talks: Monday 3pm ET PNL DBP, and Thursday 3pm ET JHU, UNC, MIND&lt;br /&gt;
&lt;br /&gt;
==2008-10-23==&lt;br /&gt;
Attendees: Jim, Chris, Brad, Katie, Tina, Vidya, Noby, Vince, Dingang, Kevin, Ziv, Dan Marcus&lt;br /&gt;
&lt;br /&gt;
External Collaborators:&lt;br /&gt;
*UNC Dinggang Shen, Jim Miller 3pm&lt;br /&gt;
*Wake Forest, Chris Wyatt, Brad Davis, Dan Marcus 3:15pm &lt;br /&gt;
** [[2009_Winter_Project_Week_WFU1 | Move to All Slicer3 Workflow]]&lt;br /&gt;
** [[2009_Winter_Project_Week_WFU2 | Development of deformation based morphometry module]]&lt;br /&gt;
*Georgetown Kevin Cleary, Ziv Yanev, Noby Hata 3:30pm&lt;br /&gt;
*University of Iowa - Meshing Project (Vince and Nicole) 3:45pm&lt;br /&gt;
**Update [http://www.na-mic.org/Wiki/index.php/Voxel_Meshing_Module Voxel Meshing] code to conform to new meshing data structures. &lt;br /&gt;
**Integrate [http://www.na-mic.org/Wiki/index.php/Mapped_Hexahedral_Meshing FE Based Mapped Meshing] as a command line module.&lt;br /&gt;
**Document the integration of a standalone [http://www.ccad.uiowa.edu/mimx/IA-FEMesh/ KWWidgets application] into Slicer3&lt;br /&gt;
&lt;br /&gt;
Highlights:&lt;br /&gt;
*Dingang w/ Jim: two types of software development. MR-image registration algorithm will be extended and added to NA-MIC Kit. Second is for white matter lesion segmentation in MR images. Kickoff mtg will take place within team before January to identify which infrastructure changes need to be made to ITK and Slicer. This will get coordinated with visit to Martin. Team will also look at synergy with Lupus DBP.&lt;br /&gt;
*Chris: EM segmenter is working well.  At project week, would like to make it an all-slicer workflow. Dan Marcus will help before project week to get data into xnat central server (data is public).&lt;br /&gt;
*Ziv: work has been divided into IGT Project Week (Dec 8-12) and NA-MIC Project week. The goal is to get a workflow prototyped in Slicer.&lt;br /&gt;
*Vince: meshing is more than likely to be integrated by the time of the project week.&lt;br /&gt;
&lt;br /&gt;
==2008-10-16==&lt;br /&gt;
&lt;br /&gt;
* Kickoff TCON. Discuss Infrastructure Projects.&lt;br /&gt;
*Attendees: Will, Steve, Ron, Jim, Tina, Nicole, Vince, Wendy&lt;br /&gt;
'''Core 2 lead Project Proposals'''&lt;br /&gt;
#Fluid mechanics tractography and visualization (Nathan Hageman UCLA)&lt;br /&gt;
#UCLA BrainLab/Slicer Neurosurgery Preoperative Tumor Planning - using Slicer and its link to BrainLab to investigate whether different tractography methods aid in preoperative planning of tumor resection.(Nathan Hageman UCLA)&lt;br /&gt;
#Development of FEM / FVM solver library in ITK/vTK(Nathan Hageman UCLA, Vince, Luca, Steve)&lt;br /&gt;
#Transform Management(Jim Miller)&lt;br /&gt;
#Interactive 3D Widgets - Introduce new interactors into Slicer (Karthik)&lt;br /&gt;
#VTK-ITK Pipeline (Jim, Steve)&lt;br /&gt;
#User Interface Flexible Layouts (Wendy, Jim, Steve)&lt;br /&gt;
#Packaging Python Interface - Fortran and openssl problems(Luca, Steve)&lt;br /&gt;
#xnat and batchmake integration (Julien, Dan Marcus)&lt;br /&gt;
#Automated GUI testing (Sebastien)&lt;br /&gt;
#Slicer Colors Module update (Nicole)&lt;br /&gt;
#Volume Rendering Debug (Alex, Curt)&lt;br /&gt;
&lt;br /&gt;
==2008-10-09==&lt;br /&gt;
Attendees: Steve, Katie, Tina, Jim, Dan Marcus, Nicole, Sebastien, Yumin, Ron&lt;br /&gt;
&lt;br /&gt;
*CTest for Teem (Gordon Kindlmann, Steve Pieper, CTest Expert TBN): we'd like to do this one before the AHM if possible.&lt;br /&gt;
*Q for Kitware: VIsualStudio bug in ITKLandmarkTransformInitializer (in the RegisterImages module)&lt;br /&gt;
* Wendy working on XNAT UI&lt;br /&gt;
* Who's going to claim the .xcat extension? Let's have the Wiki specify the correct MIME-TYPE for xcat files, so that at least the file is downloaded automatically, and let the user which application to use (note that Slicer3 should open a .xcat file on the desktop).&lt;br /&gt;
&lt;br /&gt;
==2008-10-02==&lt;br /&gt;
Agenda:&lt;br /&gt;
*RSNA tutorial Planning (Ron, Steve, Sonia confirmed)&lt;br /&gt;
** See bug reports on data saving http://na-mic.org/Mantis/view.php?id=321 http://na-mic.org/Mantis/view.php?id=322&lt;br /&gt;
*New SaveDataWidget design: http://www.slicer.org/slicerWiki/index.php/User:Barre/TODO#Draft5&lt;br /&gt;
&lt;br /&gt;
==2008-09-25==&lt;br /&gt;
Attendees: Xiaodong, Katie, Steve, Tina, Curt, Ron&lt;br /&gt;
&lt;br /&gt;
Agenda:&lt;br /&gt;
&lt;br /&gt;
*Unstructured Grid support to be added to Slicer trunk soon -  vtkUnstructuredGrid datatypes are a subtype of slicer models.  There will be some changes to the slicer model viewers and hierarchy viewers to allow display and control over these datatypes.  This was put in to support the finite element meshing module to be incorporated in Slicer in advance of the January 2008 All-hands meeting. &lt;br /&gt;
&lt;br /&gt;
* Meshing Module into Slicer - Curtis is working on integration of the standalone Univ. of Iowa meshing application as a Slicer module.  Integration is working through MRML but the GUI is not integrated in Slicer's window yet.  Sebastien has offered debugging help.  Curt will be delivering a code sample to Sebastien during the next week for assistance in KWWindows integration. &lt;br /&gt;
&lt;br /&gt;
* GPGPU RayCasting - There is an open-source ray casting algorithm using OpenGL shaders that is experimentally being integrated with Slicer.  If this is successful, the algorithm will be integrated into the Volume Rendering module and be available for use by the NA-MIC community.&lt;br /&gt;
&lt;br /&gt;
==2008-09-18==&lt;br /&gt;
Attendees: Jim, Xiadong, Steve, Vince, Sebastian, Tina, Wendy, Ron&lt;br /&gt;
&lt;br /&gt;
Agenda:&lt;br /&gt;
*Breakout session Ideas for Winter Project Week&lt;br /&gt;
**Meshing (Nicole, Vince, Curt, Steve)&lt;br /&gt;
**ITK (Luis)&lt;br /&gt;
**IGT (Noby)&lt;br /&gt;
**Setting up Development and Testing Environment (Kitware)&lt;br /&gt;
**Python Modules (Demian, Luca?)&lt;br /&gt;
*Conference calls for project week prep:&lt;br /&gt;
**December 18: Loose Ends&lt;br /&gt;
**December 4: Other Projects&lt;br /&gt;
**November 20: New Collaborations&lt;br /&gt;
**November 13: New Collaborations  &lt;br /&gt;
**November 6: DPB Projects (2)&lt;br /&gt;
**October 30: DPB Projects (2)&lt;br /&gt;
**October 23: Funded External Collaboration Projects&lt;br /&gt;
**October 16: Kickoff TCON. Discuss Infrastructure Projects.&lt;br /&gt;
* Review of recent python development.  See [http://www.slicer.org/slicerWiki/index.php/Slicer3::Python#Where_to_go_from_here Demian Wassermann's slides and examples from his recent lecture series at Harvard]&lt;br /&gt;
** For example, here's a Hausdorff distance between to fiber tracts:&lt;br /&gt;
 dist2 = lambda i,j : numpy.sqrt(((i-j)**2).sum(j.ndim-1))&lt;br /&gt;
 dist_hausdorff_asym_mean = lambda i,j: numpy.apply_along_axis( lambda k: dist2(k,j).min(),  1,i).mean()&lt;br /&gt;
 dist_hausdorff_min = lambda i,j : numpy.min(dist_hausdorff_asym_mean(i,j),dist_hausdorff_asym_mean(j,i))&lt;br /&gt;
&lt;br /&gt;
* Download modules from [http://www.nitrc.org/ NITRC] by an end user&lt;br /&gt;
**Where does this stand - Sebastian has committed the code to the Slicer3 tree.&lt;br /&gt;
**Sebastian will be happy to help someone push this forward&lt;br /&gt;
**How to pack modules to have Slicer3 install and find the modules?&lt;br /&gt;
**What infrastructure is needed- particularly for Windows to check for the proper compiler and build type. Possibly have CPack generate keys that check this.&lt;br /&gt;
**Slicer3 should provide the user with a list of modules that can be downloaded and installed.&lt;br /&gt;
**Sebastian will work with Modules to create their own package for installation.&lt;br /&gt;
&lt;br /&gt;
==2008-09-12==&lt;br /&gt;
&lt;br /&gt;
Attendees: Jim, Sebastien, Tina, Curt, Dan Marcus, Will, Ron,  Wendy &lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
Agenda:&lt;br /&gt;
&lt;br /&gt;
*Curt - Working on the integration of a standalone KWWidgets/VTK application as a loadable Slicer module.  This standalone application does lots of callbacks to the RenderWindow and creates its own KWWindow and  KWUserInterfacePanel.  Therefore, this is a complicated example to integrate into Slicer's Module panel.  At the current time, the widget creation seems to occur without warnings, but the panels never show up in Slicer.  Sebastian and Wendy indicated that the management of the InterfacePanels and Slicer's UserInterfaceManager is intricate and that there is probably a relatively easy fix, but Sebastian would have to review some of the source code to comment further.  Curt will make the source code and screenshots available to Sebastian for a follow up call later. &lt;br /&gt;
&lt;br /&gt;
*Sebastian - Evaluation of GUI-testing for KWWidgets and QT is ongoing.  Sebastian is working on this as well as the requested tree control widget. &lt;br /&gt;
&lt;br /&gt;
*VTK bugs (Will)  There were three VTK bugs reported last week in the TCon.   Karthik solved all of the bugs.  Kitware has fixed these and the fix is in the VTK CVS head already. The bug information is listed below: &lt;br /&gt;
&lt;br /&gt;
**http://vtk.org/Bug/view.php?id=7512&lt;br /&gt;
**http://vtk.org/Bug/view.php?id=7511&lt;br /&gt;
**http://vtk.org/Bug/view.php?id=7518&lt;br /&gt;
&lt;br /&gt;
*Work is beginning on the planning for the All-hands Meeting in January.  There will be another party.   Ron and Will are working on the agenda already.  We should put up the draft projects template soon. &lt;br /&gt;
&lt;br /&gt;
*XNAT visit followup discussion.   The Web Services API is stable and it will be tested as the Slicer use case (written by Wendy) is implemented.   There was discussion of the use of Slicer tutorial data to populate the use case.  Wendy is developing a Slicer module to query the XNAT Desktop Services.  There are is a set of minimal, required tags. The required ones are all that is necessary at first for the use case, unless there are others needed by the Use Case requirements.  &lt;br /&gt;
&lt;br /&gt;
*MICCAI comments -  One of the Slicer images received second place in the Visualization competition.   There was a Slicer plug-in workshop offered and an IGT workshop given at MICCAI.  Vince was helpful in making the Slicer tutorial possible.&lt;br /&gt;
&lt;br /&gt;
==2008-09-04==&lt;br /&gt;
Attendees: Dan, Xiaodong, Wendy, Vincent, Curtis, Nicole, Tina&lt;br /&gt;
&lt;br /&gt;
*VTK Bugs in 5.2 - These are issues with the integration of the meshing tools&lt;br /&gt;
**0007518 - vtkDataReader Memory Errors causes a seg fault&lt;br /&gt;
**0007511 - Bug in vtkSmoothPolyDataFilter causes a seg fault&lt;br /&gt;
**0007512 - vtkPlaneWidget Sphere Resizing - This is simply an annoyance&lt;br /&gt;
&lt;br /&gt;
*Slicer/XNAT update&lt;br /&gt;
**Reading multiple files from a single data needed in Slicer&lt;br /&gt;
**Building out the UI and workflow for talking to XNAT&lt;br /&gt;
**Expected to have prototype Slicer/XNAT File Repository integration by October&lt;br /&gt;
**Expected to have prototype Slicer/XNAT Enterprise integration by January, 2009&lt;br /&gt;
&lt;br /&gt;
*Sadness all around at the lack of a Kitware representative to disucss VTK bugs&lt;br /&gt;
&lt;br /&gt;
*Great joy at being set free after only 20 minutes&lt;br /&gt;
&lt;br /&gt;
==2008-08-28==&lt;br /&gt;
&lt;br /&gt;
* [[Events:August2008XNATDesktop#Plan_for_supporting_initial_use_case|Plan for XNAT/Slicer interaction]]: 9: Sebastien, Katie, Wendy, Nicole, Jim, Vince, Steve, Curt, Dan&lt;br /&gt;
* XNAT Desktop, Web Services Use cases (Wendy review of last weeks meeting notes)&lt;br /&gt;
** Web services file repository api is currently on XND, but will also be supported on XNAT Enterprise (by January).&lt;br /&gt;
** Sebastien and Yumin are working on the current save dialog box and will think about how the remote repository should look for that.&lt;br /&gt;
** discussion of how extra data file names are handled in ITK (which files are actually written when you save a particular archetype).&lt;br /&gt;
*** idea:  save to temp dir to get file names.  Rather than changing all ITK io factory code to keep track of which files it wrote, the slicer code can keep track of what files are in the save directory before and after the Write method executes (this assumes that each factory will only save files in the single directory, but that seems like a valid assumption for all known code).&lt;br /&gt;
** discussion of refining upload uri also how to keep track of metadata to store with derived data&lt;br /&gt;
*** how much can be kept track of automatically in mrml?  Maybe a lot...&lt;br /&gt;
&lt;br /&gt;
==2008-08-21==&lt;br /&gt;
&lt;br /&gt;
Attendees: Xiaodong, Steve, Curt, Ron, Nicole, Marco, Katie&lt;br /&gt;
&lt;br /&gt;
*[[2008-08-15-email-atlas-generation|Ron]]: Atlas generation for the EM segmenter. We need to develop an end-user capability to create atlases to drive the EM segmenter.&lt;br /&gt;
** what is the right approach?&lt;br /&gt;
** where is leverage with existing infrastructure?&lt;br /&gt;
** what needs to be done&lt;br /&gt;
** who will do it?&lt;br /&gt;
** Need to schedule a followup discussion with Brad, Kilian, Polina, Guido, Stephen, Jim, Ross (possibly at MICCAI)&lt;br /&gt;
* Report on NCI Slicer Course by Curt&lt;br /&gt;
** NIST BioChange 2008 challenge may be suitable for Kilian's change detection module&lt;br /&gt;
* NIH personnel told Ron that the wiki pages are not as up to date as they expected&lt;br /&gt;
** Everyone should be sure the wiki reflects the current state of their NA-MIC work&lt;br /&gt;
* Update from Marco on BatchMake coordination with GWE&lt;br /&gt;
** Plan is to wrap GWE for use with BatchMake and Julien is working on it&lt;br /&gt;
** Waiting for Kilian's updates for scripts&lt;br /&gt;
** Ron says we need users to be actively using tools so we have a clear story for renewal - Marco to look at the NA-MIC DBP projects and see which are good fits with GWE and Ron can help facilitate connection&lt;br /&gt;
&lt;br /&gt;
==2008-08-15==&lt;br /&gt;
Attendees: Jim, Steve, Wendy, Xiaodong, Nicole, Vince, Tina&lt;br /&gt;
&lt;br /&gt;
*Filebrowser update by Steve.&lt;br /&gt;
&lt;br /&gt;
==2008-08-07==&lt;br /&gt;
&lt;br /&gt;
Attendees: Tina, Jim, Steve, Katie, Nicole, Wendy, Vince&lt;br /&gt;
&lt;br /&gt;
Agenda:&lt;br /&gt;
*CompareView questions about slice layer logic and slice nodes&lt;br /&gt;
** Nicole notes that switching to compare view loses FG, BG, Label settings she expects to have. Jim says this is the preferred behavior for now but is open to ideas.&lt;br /&gt;
** Compare view aspect ratio? Check problem with panning, zooming in 3D view and changing the compare view fov by mistake. Compare view Field of View. Also lightbox seems to have broken in conventional layout (maybe after compare view).&lt;br /&gt;
*Slicer 3.2 release&lt;br /&gt;
**CLI load time on Mac&lt;br /&gt;
**ModelMaker bugs - string memory problem, maybe in model storage nodes.&lt;br /&gt;
**Xcede / Xnat catalog loading/importing bug&lt;br /&gt;
* Slicer Developer Meetings&lt;br /&gt;
** Many new people working on new Slicer stuff and have requested slicer developer meetings -- may also join tcons in the future. More face to face meetings will be helpful to get them up to speed.&lt;br /&gt;
**James Ross is now working on the COPD project, will be porting an airway inspector tool (www.airwayinspector.org) to slicer3.&lt;br /&gt;
** New PNL person (Julien) working on stochastic tractography with Sylvain.&lt;br /&gt;
** New SPL students in town&lt;br /&gt;
* Vince would like to add new pages to application settings menu specific to their module. Discuss a slicer-level API to the app settings for individual modules. Should this stuff be saved in the registry? Vince will spec it out a little and we'll discuss putting methods in Slicer base classes that create and delete app settings page for a module.&lt;br /&gt;
* VTK disappearing actor fixes? (Karthic is working on this fix.)&lt;br /&gt;
&lt;br /&gt;
==2008-07-31==&lt;br /&gt;
&lt;br /&gt;
Attendees: Nicole, Xiaodong, Steve, Ron, Wendy, Vince, Sonja, Jim, Dan, Will&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Agenda:&lt;br /&gt;
*Upcoming training tutorials at NCBC, NCI, Stanford, MICCAI&lt;br /&gt;
*Plans for improving Slicer towards RSNA event&lt;br /&gt;
**Data Saving / File browser [http://www.slicer.org/slicerWiki/index.php/User:Barre/TODO See here for some info]&lt;br /&gt;
**Xnat download&lt;br /&gt;
**Bug fixes needed before these events&lt;br /&gt;
**Branch Slicer a ~month prior to RSNA and BWH workshops (10/15/2008)&lt;br /&gt;
*Dicom browser&lt;br /&gt;
** Subseries groupings are not accessible from vtkITK&lt;br /&gt;
** Tags now available from vtkITK&lt;br /&gt;
** Steve to build GUI&lt;br /&gt;
** Can we use xnat desktop to cache series/subseries information?&lt;br /&gt;
*xnat desktop&lt;br /&gt;
** see [http://slicer.spl.harvard.edu/slicerWiki/index.php/Slicer3:XCEDE_use_cases#XCEDE_REST_Interface XCEDE use cases]&lt;br /&gt;
*[http://www.na-mic.org/Bug/view.php?id=291 VTK bug?]&lt;br /&gt;
**Fiducials + 2D slice plane disappearance&lt;br /&gt;
**Turn backface culling off?&lt;br /&gt;
*Transforms requiring inversion between Slicer and CLI&lt;br /&gt;
** Built in module to delegate to CLI modules?&lt;br /&gt;
*Non-linear transforms, resampling DTI&lt;br /&gt;
** vtkITKBSplineTransform, itkDeformationFieldTransform&lt;br /&gt;
** Need extension to itkTransform to support encoding/compressing parameters.&lt;br /&gt;
&lt;br /&gt;
==2008-07-24==&lt;br /&gt;
&lt;br /&gt;
Attendees: Xiaodong, Tina, Ron, Vince, Steve, Marco&lt;br /&gt;
&lt;br /&gt;
Agenda:&lt;br /&gt;
* URGENT: http://wiki.na-mic.org/Wiki/index.php/2008_Progress_Report_NIH_QnA&lt;br /&gt;
*FYI http://wiki.na-mic.org/Wiki/index.php/Events:TutorialContestJan2009&lt;br /&gt;
* Slicer 3.2 release&lt;br /&gt;
*XNAT visit in Boston&lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* Color image will work with Editor module (not there yet).&lt;br /&gt;
* Four working days (due July 30, 5PM) till the response to 2008_Progress_Report_NIH Questions due.&lt;br /&gt;
* Contest to encourage people to make more tutorial. More details will be work out in the next two weeks before it is announced.&lt;br /&gt;
* Slicer 3.2 release is scheduled soon.&lt;br /&gt;
&lt;br /&gt;
==2008-07-17==&lt;br /&gt;
attendees: jim, nicole, wendy, katie, dan, xiaodong&lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* Wendy has nearly fixed the packing issue introduced with the Compare View.&lt;br /&gt;
* Xiaodong has added capabilities to vtkITKArchetype..Reader to identify &amp;quot;sub-series&amp;quot;. This is necessary for time series data where the all the timepoints are stored in one series. Steve to build a UI to select sub-series or load them all. Perhaps XNAT desktop can help in storing meta data of registered data for fast browsing.&lt;br /&gt;
* Selecting models and volumes for manipulation.  Can we tie &amp;quot;active viewers&amp;quot; to the module panel (so the modules show information from the &amp;quot;background&amp;quot; volume, etc.)?&lt;br /&gt;
* Release date? Before NCBC meeting?&lt;br /&gt;
* Jim is off the grid the next week :)&lt;br /&gt;
&lt;br /&gt;
==2008-07-10==&lt;br /&gt;
attendees: jim, nicole, tina, steve, ron, wendy&lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
*FYI [[Events:August_2008_NCBC_AHM]]&lt;br /&gt;
*FYI [[2008_July_Slicer_IGT_VV_Link_Session_II]]&lt;br /&gt;
*Xenios from Yale at BWH on Wednesday, July 23rd to continue work on Slicer IGT+vvlink integration&lt;br /&gt;
*Dan Marcus to come to boston in late July to continue xnat integration&lt;br /&gt;
&lt;br /&gt;
==2008-07-03==&lt;br /&gt;
* Discussion of DICOM options for time series and other situations where directories contain files from multiple series.&lt;br /&gt;
* Xenios from Yale is looking a visiting BWH for a day in late July to work on OpenIGTLink and VVLink in collaboration with NA-MIC and NCIGT.&lt;br /&gt;
* One or more of Dan/Misha/Tim from WashU are looking to come to BWH to work on XNAT Desktop and XCEDE Web Services.&lt;br /&gt;
* The USA will be 232 years old tomorrow!&lt;br /&gt;
&lt;br /&gt;
==2008-06-19==&lt;br /&gt;
*Agenda: svn repository switchover finalized for when?  Wednesday morning?&lt;br /&gt;
**Engr Business: Do we need any announcements for the &lt;br /&gt;
**3-3:30pm: [[Mesh Discussion for Core 1]]&lt;br /&gt;
**3:30-4pm: [[IGT Projects Discussion]]&lt;br /&gt;
&lt;br /&gt;
==2008-06-12==&lt;br /&gt;
Agenda: Discuss NEW EXTERNAL Collaboration projects for project week&lt;br /&gt;
*3:00-3:15pm Rutgers (Jinghao)&lt;br /&gt;
*3:15-3:30pm UIowa (Gary Christensen)&lt;br /&gt;
*3:30-3:40 GAP - NAMIC ENGR Core business&lt;br /&gt;
*3:40-3:45 Mario Negri Institute &amp;amp; Univ of Verona (Luca Antiga)&lt;br /&gt;
*3:45-3:50 Upenn (Ragini Verma from Christos Davatzikos' group, UPenn)&lt;br /&gt;
*3:50-4:00pm regular NAMIC engr business&lt;br /&gt;
&lt;br /&gt;
Attendees:  Brad, Jim, Katie, Raul, Tina, Will, Nicole, Gary, Alex, Andrey, Dimitri, Jhingao, Paul, Stephen, Luca, Ragini+2 students, Xiaodong&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Highlights:&lt;br /&gt;
*Rutgers group project: Lung cancer detection and segmentation.  Will be ported to NA-MIC Kit.  Page will be create for project week.  Jim Miller will be on team.&lt;br /&gt;
*Iowa Christensen group: 9 people attending the week!  All project pages in place.  Need to schedule two focus-groups for them: one with Sebastien for Kwwidgets, and one with Bill/Julien on setting up CDASH.  &lt;br /&gt;
*Non-rigid registration breakout: Luis to run.  Topic suggested: regression testing of registration algorithms using cmake and cdash.&lt;br /&gt;
*William and Mary: project is non-rigid registration for neurosurgery.  Interested in focus session on validation, and access to non-rigid neurosurgery data from BWH.  Dan Markus, Tina Kapur, Gary Christensen will be on team.  Graz paper on validation from Insight Journal should be reviewed and discussed.&lt;br /&gt;
*Mesh discussion next week 3-3:30pm.&lt;br /&gt;
*Verona: vmtk integration with Slicer.  Dan Blezek will be on team.&lt;br /&gt;
*UPenn: will be present on Tuesday.  Working on fixing a bug in Slicer at CF's request, and integrating their 5yr+ sw as a command-line module. Will create a page.  Need a session with Steve Pieper.&lt;br /&gt;
&lt;br /&gt;
==2008-06-05==&lt;br /&gt;
Agenda: Discuss FUNDED EXTERNAL Collaboration projects for project week&lt;br /&gt;
*3:00-3:15pm Meshing Collaboration (Iowa)&lt;br /&gt;
*3:15-3:30pm RF Ablation Liver Collaboration (Georgetown)&lt;br /&gt;
*3:30-3:45pm Vervet EM Segmentation Collaboration (WFU/VT)&lt;br /&gt;
*3:45-4:00pm regular NAMIC engr business&lt;br /&gt;
**Mesh discussion requested by Core 1. Core 1 would like to start working with meshes seriously and would like to assess mesh infrastructure in ITK with Will Schroeder and Aylward. The goal is to figure out  what's there and what needs to be done to make meshes usable for algorithm development.  When can this discussion be held?&lt;br /&gt;
**95 project week participants signed up already.  No more room left. Please send checks in time for Donna to get them before Friday, June 13th.&lt;br /&gt;
** (Steve:) Any vista users who can test the slicer3.2 release candidates?  We have one test machine that cannot run it, but also reports from Sebastien that an earlier build (very similar) worked for him.&lt;br /&gt;
&lt;br /&gt;
Attendees: Brad, Ron, Steve, Katie, Vince, Jim, Tina, Nicole, Alex, Xiadong, Chris Wyatt, Dan Marcus, Marco, Kilian, Kevin Cleary.&lt;br /&gt;
&lt;br /&gt;
Highlights:&lt;br /&gt;
*Iowa mesh code will be checked in at Project Week by Curt.  It is built primarily in VTK.&lt;br /&gt;
*We will schedule mesh tcon with core 1 and relevant folks in Core 2 including vince, andrey fedorov.&lt;br /&gt;
*Georgetown - Ziv will attend project week on Wed/Thurs.  50 liver data sets that gp will consider making public using XNAT.&lt;br /&gt;
*Wakeforest/VT -&lt;br /&gt;
**Kilian and Vidya have been exchanging parameters for EM seg&lt;br /&gt;
**Kilian needs faster registration - Ron's suggestion to try AFFINE with less than 10s runtime for volumetric data (256 cube)&lt;br /&gt;
**Kilian will work during project week with Carlos to install van Leemput bias correction method into EM Segmentation.  Will need input from MIND team as well.&lt;br /&gt;
&lt;br /&gt;
==2008-05-29==&lt;br /&gt;
Agenda: Discuss ALGORITHM CORE lead projects for project week&lt;br /&gt;
*3:00-3:15pm &lt;br /&gt;
*3:15-3:30pm&lt;br /&gt;
*3:30-3:45pm&lt;br /&gt;
*3:45-4:00pm&lt;br /&gt;
* Status of Slicer 3.2: Steve Pieper et al.&lt;br /&gt;
** Status&lt;br /&gt;
** Bug squashing&lt;br /&gt;
&lt;br /&gt;
'''Attendees:''' Casey, Marcel, Will, Sebastien, Nathan, Nicole, Katie, Vincent, Alex Steve Jim M., Polina, Tina, Sonia, Tom, Ron, Dan M., Michael, John M., &lt;br /&gt;
&lt;br /&gt;
'''Notes:'''&lt;br /&gt;
&lt;br /&gt;
Core1 people go over projects listed on Summer Project Week page: MIT, Utah, GATech, UNC.&lt;br /&gt;
Polina (MIT) will work with on Brad Davis and Dan Marcus.&lt;br /&gt;
John (GATech) will need more core2 help on the optimal transport registration project... will add additional titles to the project week page.&lt;br /&gt;
&lt;br /&gt;
* Info: [http://wiki.na-mic.org/Wiki/index.php/Relative_Roles_Core1_Core2_Core3  Relative roles of Core 1, Core 2, Core 3]&lt;br /&gt;
&lt;br /&gt;
* Need chaining and workflow session at project week. Feedback from core1 - core 3 meeting: Chaining, batch processing strongly discussed at the meeting. Core1 and Core 2 should address these topics. &lt;br /&gt;
&lt;br /&gt;
* Tina wants a title for all projects on the project week page by end of day today.&lt;br /&gt;
&lt;br /&gt;
* Sonia is preparing for the Germany Training event. Made a munich2008 branch of Slicer3 subversion repository. Still fixing bugs on main trunk. Will create a release branch tomorrow end-of-day.&lt;br /&gt;
 &lt;br /&gt;
* Slicer3 release: developers should check mantis and squash as many bugs as possible in prep for release.&lt;br /&gt;
&lt;br /&gt;
* Ron's [http://www.slicer.org/slicerWiki/index.php/Announcements:Slicer3.2  press release ]&lt;br /&gt;
&lt;br /&gt;
* Steve encourages all to include impressive pix on the announcements page where people will be directed.&lt;br /&gt;
&lt;br /&gt;
* Request for a stable KWW target that Slicer can build against. --Sebastien will tag it.&lt;br /&gt;
&lt;br /&gt;
* Discussion of HelloWorld (Tutorial) and HelloSlicer (for testing)&lt;br /&gt;
&lt;br /&gt;
==2008-05-22==&lt;br /&gt;
[[Image:Slicer3Dashboard-5-20.png||thumb|right|Dashboard]]&lt;br /&gt;
Agenda:&lt;br /&gt;
* &amp;lt;big&amp;gt;'''A round of applause for Sebastian, Steve and all the code freezers'''&amp;lt;/big&amp;gt;&lt;br /&gt;
*http://www.slicer.org/slicerWiki/index.php/Announcements:Slicer3.2 documentation assignments and schedule for the 3.2 release:&lt;br /&gt;
**Outstanding issues in release&lt;br /&gt;
***EM Segment Wizard - Button Issues&lt;br /&gt;
***EM Segment Command line is in the wrong directory - should be put in bin&lt;br /&gt;
***EM Segment Template Builders&lt;br /&gt;
****First, second and 3rd steps do not work correctly - pull down list&lt;br /&gt;
****Possible issue with MRML manager changes&lt;br /&gt;
***Feature Request&lt;br /&gt;
****Can not changes the name of the parameters because it references the node ID and not the name&lt;br /&gt;
****EM Segment simple - images are specified by XML type file and not image - requires reloading and does not use images loaded within Slicer3&lt;br /&gt;
****Loading parameter set - Add a hierarchy of the nodes for better visualization of parameters&lt;br /&gt;
**registration, &lt;br /&gt;
**loadable modules, &lt;br /&gt;
**interactive editor, &lt;br /&gt;
**volume rendering&lt;br /&gt;
*New Slice Control Widget added by Wendy - last GUI based change&lt;br /&gt;
*Issues with Resize of Slicer and 3D Widgets&lt;br /&gt;
*Discuss Engineering Core Projects for the Project Week&lt;br /&gt;
*Discuss Jeremy's request to add Support Vector Machine library to NA-MIC Kit. http://www.csie.ntu.edu.tw/~cjlin/libsvm/&lt;br /&gt;
&lt;br /&gt;
Highlights:&lt;br /&gt;
*Attendees: Will, Sebastien, katie, tina, brad, steve, xiadong, vince, jim, nicole, dan marcus, Ron, Sonia.&lt;br /&gt;
&lt;br /&gt;
==2008-05-15==&lt;br /&gt;
Agenda:&lt;br /&gt;
*DBP II update and plans for project week.  2 DBPs and engr+algo core liaisons should attend.&lt;br /&gt;
**3-3:20 Harvard. Marek, Brad, Polina confirmed.&lt;br /&gt;
**3:20-3:40 UNC. Heather confirmed.  Jim, Martin, Heather, Clement held offline mtg already.&lt;br /&gt;
**3:40-4pm regular NAMIC engr business&lt;br /&gt;
***Slicer code freeze and release&lt;br /&gt;
***Focus during the upcoming months on &amp;quot;ruggedizing&amp;quot; Slicer&lt;br /&gt;
&lt;br /&gt;
Attendees: Tina, Katie, Nicole, Vince, Will, Marek, Sylvain, Polina, Clement, Brad, Ron, Alex, Sebastien&lt;br /&gt;
&lt;br /&gt;
Highlights:&lt;br /&gt;
*Harvard DBP projects for Project Week&lt;br /&gt;
*#Probabilistic Tractography - on hold since Tri left&lt;br /&gt;
*#Slicer3 - Need bug fix for why Slicer 3 can't load and run UNC data that Martin tried&lt;br /&gt;
*#EPI Distortion correction (Sylvain, Tauseef GATech)&lt;br /&gt;
*#Eddy CUrrent distortion correction (Sylvain, Ran Tao Utah)&lt;br /&gt;
*# Parcellation - need help parametrization (Sylvain, Brad)&lt;br /&gt;
*# fmri - apply polina's algorithm to Marek's data (Marek, Bryce Kim)&lt;br /&gt;
*# Finsler method (John Melonakos, Eric Melonakos)&lt;br /&gt;
*# Group Analysis on DTI (Casey Goodlett, Marek)&lt;br /&gt;
*Code Freeze: scheduled for tomorrow&lt;br /&gt;
*RSNA Demo&lt;br /&gt;
*#editor, lightbox, data fusion&lt;br /&gt;
*#Sonia is developing the curriculum for course&lt;br /&gt;
*UNC DBP Projects&lt;br /&gt;
*#Cortical thickness pipeline&lt;br /&gt;
*#workflow module&lt;br /&gt;
*#NITRC - need to talk to Steve pieper&lt;br /&gt;
*#batchmake pipeline in Slicer&lt;br /&gt;
*#use Bspline module in ITK&lt;br /&gt;
&lt;br /&gt;
==2008-05-08==&lt;br /&gt;
Agenda:&lt;br /&gt;
*DBP II update and plans for project week.  2 DBPs  and engr+algo core liaisons should attend.&lt;br /&gt;
**3:00-3:20 MIND. Jeremy, Ross, Steve Confirmed.&lt;br /&gt;
*** Testing lots of methods.  None working well.&lt;br /&gt;
*** Bayesian labeling seems to be working the best.&lt;br /&gt;
*** Close the look on itkEMS method&lt;br /&gt;
**3:20-3:40 JHU. David G, Allen T., Katie H. confirmed.&lt;br /&gt;
*** Prostate really difficult task&lt;br /&gt;
*** Delphine's work was originally on prostate.&lt;br /&gt;
*** Optimal mass transport registration project at project week&lt;br /&gt;
**3:40-4pm: regular na-mic engr core business&lt;br /&gt;
*** Short update on UNC DBP needs: registration, module chaining&lt;br /&gt;
*** Discussion on plans for chaining.  Prototype for project week?&lt;br /&gt;
&lt;br /&gt;
==2008-05-01==&lt;br /&gt;
&lt;br /&gt;
Attendees: Steve, Jim, Will, Tina, Xiaodong, Katie, Danielle, Sebastian, Sonia, &lt;br /&gt;
&lt;br /&gt;
* Slicer 3 stable release schedule planning (Slicer 3.2)&lt;br /&gt;
** We would like a stable version before the [[Events:June-Germany | Mid-June German training event]] that includes all the latest namic technology (CMake 2.6, ITK 3.6, VTK 5.2, Tcl/Tk 8.5, KWWidgets...).  Some problems were fixed this week for ITK3.6 and VTK 5.2; Slicer3 was successfully built using CMake 2.6 against VTK 5.2, ITK 3.6, and Tcl/TK on Linux, Windows, and Mac (by Sebastien). Need more coverage on Slicer. TODOs: Developing tutorial material for the new Slicer release. Testing, automated part plus user interaction part. &lt;br /&gt;
** [[2008_Summer_Project_Week | Project Week]] projects can go into the trunk after the release is branched. GUI changes to show &amp;quot;axial&amp;quot;, &amp;quot;sagittal&amp;quot;, &amp;quot;coronal&amp;quot; slices in the acquisition orientation.&lt;br /&gt;
** Proposed schedule:&lt;br /&gt;
*** May 16: Feature Freeze of the trunk followed by group debugging/testing &lt;br /&gt;
*** May 23: Create Release Branch for Slicer 3.2&lt;br /&gt;
*Danielle Pace @ Robarts Inst. joined NCIGT/SNR to develop [[LEGO_IGT_and_Medical_Robotics_Tutorial | Slicer IGT Tutorial]].&lt;br /&gt;
&lt;br /&gt;
==2008-04-24==&lt;br /&gt;
&lt;br /&gt;
Attendees: Steve, Katie, Nicole, Tina, Nathan, Jim, Vince, Brad, Louis, Marco&lt;br /&gt;
&lt;br /&gt;
Agenda&lt;br /&gt;
* Slicer3D Wikipedia page discussion.  Check it out [http://en.wikipedia.org/wiki/Slicer here].&lt;br /&gt;
** Need to tone it down a little so it sounds less like ad copy.&lt;br /&gt;
** Needs more pawprints on it from unique editors/authors for Wikipedia to keep it online.&lt;br /&gt;
&lt;br /&gt;
* Nathan&lt;br /&gt;
** Helical phantom available to LONI web service.&lt;br /&gt;
** Should we make the link available through Slicer or not?&lt;br /&gt;
&lt;br /&gt;
* Project pages need to be updated.&lt;br /&gt;
** Deadline: May 15th for NA-MIC, a week earlier is preferred&lt;br /&gt;
** [[2008_Annual_Scientific_Report | Progress report link]]&lt;br /&gt;
** Project week pages need to be linked off the progress report (indirectly)&lt;br /&gt;
&lt;br /&gt;
* Waiting for CMake and ITK releases to be finalized&lt;br /&gt;
** Probably will be cut tomorrow&lt;br /&gt;
&lt;br /&gt;
* Set up special T-con time for Oz&lt;br /&gt;
&lt;br /&gt;
* What's the deal with the CMake Policy Change warnings?&lt;br /&gt;
** Copy three lines before CMAKE_MINIMAL_REQUIRED&lt;br /&gt;
** Ask the CMake list&lt;br /&gt;
&lt;br /&gt;
==2008-04-17==&lt;br /&gt;
&lt;br /&gt;
Attendees: Jim, Dan Marcus, Xiaodong, Nicole, Tina, Steve, Katie, Jeff, Sebastien, Vince&lt;br /&gt;
&lt;br /&gt;
Topics:&lt;br /&gt;
&lt;br /&gt;
*[[2008_Annual_Scientific_Report]]&lt;br /&gt;
*[[2008_Summer_Project_Week]]&lt;br /&gt;
*VTK (5.2) and CMake (2.6) release schedules&lt;br /&gt;
**VTK Plan on branching next week&lt;br /&gt;
**CMake is on RC8, guessing will branch in 1-2 weeks&lt;br /&gt;
*VTK (5.2) performance issues when rendering&lt;br /&gt;
**In the meshing project we have seen a significant reduction in the rendering of a large number of vtkSphereSource and vtkPointWidgets in 5.2 as compared to 5.0&lt;br /&gt;
***100x performance hit in debug mode on Linux&lt;br /&gt;
***Jeff added code to make sure the check doesn't happen more than once/sec.&lt;br /&gt;
***Still 25% slower, but not 100x slower&lt;br /&gt;
**Rendering time has been increased by an order of magnitude&lt;br /&gt;
* OK for Kitware to put Slicer3 screenshots on Flickr? (see [http://flickr.com/photos/kitware/ Kitware's Flickr account])&lt;br /&gt;
** =&amp;gt; I (Seb) did a quick pass at the files uploaded in 2008, and copied them to a [http://flickr.com/photos/kitware/sets/72157604594177467/detail/ Slicer3 photoset].&lt;br /&gt;
&lt;br /&gt;
==2008-04-03==&lt;br /&gt;
&lt;br /&gt;
Jim, Curt, Tina, Nicole, Wendy, Steve, Brad, Xiaodong, Vince, Ron, Nathan&lt;br /&gt;
&lt;br /&gt;
Agenda&lt;br /&gt;
* discussion of xcede web services and mBIRN&lt;br /&gt;
* [[2008_Engineering_review_at_Utah:FollowUp]]&lt;br /&gt;
* New! [http://www.slicer.org/slicerWiki/index.php/Slicer3:DTMRI glyphs on slices movie!]&lt;br /&gt;
** made using wink from http://www.debugmode.com/wink/&lt;br /&gt;
** add something like the following to your wiki page after uploading the .swf file to the wiki&lt;br /&gt;
 &amp;lt;pre&amp;gt;&amp;lt;flash&amp;gt;file=dti_glyphs.swf|width=800|height=600|quality=best|loop=true|play=true&amp;lt;/flash&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
* CMake 2.6 release candidates have been cut with .rpm and .deb output targets!&lt;br /&gt;
** Will will work with Katie on this&lt;br /&gt;
* Jim is going to visit Kitware to talk about BSpline registration&lt;br /&gt;
&lt;br /&gt;
==2008-03-27==&lt;br /&gt;
Attendees: Steve, Will, Xiaodong, Nathan, Katie, Wendy, Tina, Nicole, Marco, Sebastien&lt;br /&gt;
* Nathan will discuss presentation of fluid mechanics projects.&lt;br /&gt;
* Update from Core 1 + Core 2 [[2008_Engineering_review_at_Utah | meetings in Utah]] earlier this week.&lt;br /&gt;
* [http://www.slicer.org/slicerWiki/index.php/Slicer3:Chain_CLMs Discussion of Module Chaining] (Marco and All)&lt;br /&gt;
** Requested by Core 1 to systematize common use case&lt;br /&gt;
** Need several steps in an analysis process to act like a single command&lt;br /&gt;
** Would like something akin to the EMSegment workflow wizard, but as command line module rather than built-in module&lt;br /&gt;
&lt;br /&gt;
Highlights:&lt;br /&gt;
&lt;br /&gt;
Nathan's overview: discussing visualization options for his fluid velocity vector fields for tractography algorithm. Steve mentions a few options: &lt;br /&gt;
* A LDDMM module in Slicer2 that does animated vector field visualization (work done in collaboration with Johns Hopkins: Anthony Kolasny, Mike Miller, et al.). &lt;br /&gt;
* Another option would be to try using ParaView as a way to flesh out specifics, and then build a more custom tool for tractography later. Will will point Nathan to documentation for file formats, data formats, etc. or help with any questions, and Nathan will try this out.&lt;br /&gt;
&lt;br /&gt;
Discussion of these topics at the engineering review in Utah:&lt;br /&gt;
&lt;br /&gt;
* chaining modules together&lt;br /&gt;
* grid wizard (Marco) for grid and batch computing&lt;br /&gt;
* Bspline registration&lt;br /&gt;
* setting up repositories for collecting slicer modules (as technology transition mechanism)&lt;br /&gt;
* how this will fit into the slicer build process&lt;br /&gt;
* diffusion weighted imaging, shape analysis, and segmentation&lt;br /&gt;
* dicom to nrrd converter...&lt;br /&gt;
&lt;br /&gt;
Milestones were set for April-end, Project week, and AHM.&lt;br /&gt;
&lt;br /&gt;
Module chaining discussion (see link above):&lt;br /&gt;
&lt;br /&gt;
* Java version as first goal -- eventually C++ implementation. &lt;br /&gt;
* Discussion about module discovery process and how will chained modules be packaged: (c++ stub programs? or &lt;br /&gt;
or discovery find chain-descriptor xml files? shell scripts? (cross-platform issues)...)&lt;br /&gt;
* Goal: By project week in June we would like to be able to chain modules developed by Core 1.&lt;br /&gt;
&lt;br /&gt;
Sebastien's update on module building: Wiki will be updated today with status. (link)&lt;br /&gt;
&lt;br /&gt;
==2008-03-20==&lt;br /&gt;
Attendees: Tina, Jim, Will, Wendy, Xiaodong, Nathan, Martin, Marco&lt;br /&gt;
* [[2008_Annual_Scientific_Report|Progress Report]] - read over the assignments. We will look for progress from June 1, 2007 to May 30, 2008.&lt;br /&gt;
* June 23-27 is the summer project week.  We will make first pass on projects in late April.&lt;br /&gt;
* Module discussion: Martin wanted to understand the state of module creation and usage within Slicer. Sebastien is working on modules that are built against an installed module. Terry is working on built-in modules for Slicer. Jim is working on modules using CMake in the NTRIC repository.&lt;br /&gt;
* Nathan- write a command line, Slicer module that is a wrapper to a web service. Nathan thinks he can get this done prior to the June AHM. We referred to Jim's presentation at the Utah SLC Core 1/Core 2 meeting.&lt;br /&gt;
* We will talk about grid wizard next week at SLC&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==2008-03-13==&lt;br /&gt;
Attendees: Jim, Nicole, Dan, Xiaodong, Vince, Sebastian, Alex, Curt, Steve, Will, Terry&lt;br /&gt;
* Update on [http://www.slicer.org/slicerWiki/index.php/Slicer3:Loadable_Modules Slicer3:Loadable_Modules |Loadable Modules] project (Terry) and [http://www.slicer.org/slicerWiki/index.php/Slicer3:Build/Modules CMake updates for module builds] (Sebastien)&lt;br /&gt;
* [[2008_Engineering_review_at_Utah | Engineering trip to Utah]]&lt;br /&gt;
* We are starting to use Categories to bin our pages.  [[SuggestedCategories]] - suggestions?&lt;br /&gt;
&lt;br /&gt;
==2008-03-06==&lt;br /&gt;
Attendees: Steve, Jim, Katie, Nicole, Tina, Xiaodong, Marco, Ron&lt;br /&gt;
&lt;br /&gt;
Highlights:&lt;br /&gt;
*Slicer page on wikipedia - http://en.wikipedia.org/wiki/3DSlicer.  All engineering core members should visit this page and edit as needed.  ASAP.&lt;br /&gt;
*dicom to nrrd converter in progress.  Xiaodong working on it and expecting to complete in a few weeks.&lt;br /&gt;
* [[2008_Engineering_review_at_Utah|March 24-26 Meeting in Utah]]&lt;br /&gt;
&lt;br /&gt;
==2008-02-28==&lt;br /&gt;
&lt;br /&gt;
* Attendees: Jim, Steve, Wendy, Katie, Tina, Jeff, and Marco (Grid Wizard Guy)&lt;br /&gt;
* Discussion on time series analysis (viewer, scene markup). Initial viewer will be a general tool for comparing images.&lt;br /&gt;
* Avalanche of new features in [http://gridwizard.org/gwe/index.html grid wizard and GSlicer3]&lt;br /&gt;
** Proxy around Command Line Modules&lt;br /&gt;
** Extends command line with specifications for ranges of values as well as specify remote resources (data) that need to be transferred to/from the grid.&lt;br /&gt;
** Uses Velocity for parameter template engine&lt;br /&gt;
** Grid selection and authentication still being refined for Slicer&lt;br /&gt;
** Could be extended to other grid types (LSF, etc.)&lt;br /&gt;
** Lots of information on the website.  Instructions for installation.  A bit daunting for non-grid people.  Some of us will have to work through the instructions step by step to evaluate.&lt;br /&gt;
&lt;br /&gt;
==2008-02-21==&lt;br /&gt;
&lt;br /&gt;
* Attendees: Xiaodong, Jim, Katie, Nicole, Will, Steve, Nathan, Tina, Ron, Padma, Marco&lt;br /&gt;
&lt;br /&gt;
- Nathan brought us up to date on fluid mechanics tractography&lt;br /&gt;
&lt;br /&gt;
- Padma Sundaram: SCIrun environment supports EEG processing&lt;br /&gt;
&lt;br /&gt;
- Marco is releasing Grid Wizard alpha version&lt;br /&gt;
&lt;br /&gt;
- Nathan brought up the helical digital phantom web service. Currently the thinking is that it can be accessed through a web service. We suggested that Nathan write a wrapper, consistent with Slicer's execution module, to invoke the web service. However, since it is not available in source form, NAMIC cannot accept it as part of the NAMIC Kit proper. We can guide Nathan in the execution of this module.&lt;br /&gt;
&lt;br /&gt;
==2008-02-14==&lt;br /&gt;
* Attendees: Xiaodong, Katie, Will, Sebastien, Steve, Mike, Wendy, Haiyi, Dan, Curt, Tina &lt;br /&gt;
&lt;br /&gt;
=== Other NA-MIC Projects ===&lt;br /&gt;
&lt;br /&gt;
16 - CPack (Katie): Slicer3 compiles and packs using the new C-tools with some bug fixes. Using CMake to select desired modules, using something similar to cygwin. Official Slicer3 snapshot tagged. Different Tcl/Tk versions are currently used for different platform. This need to be addressed.&lt;br /&gt;
&lt;br /&gt;
17 - Slicer GUI Style Guide and Cookbook {Wendy}: This will be a long term effort. During the programming week, the design and implementation details were discussed. The Cookbook will be launched from Slicer, act like KWWidget tour.  &lt;br /&gt;
&lt;br /&gt;
18 - Volume rendering (Steve): UI is fairly stable.&lt;br /&gt;
 &lt;br /&gt;
19 - Volume rendering using Cuda (Steve):  &lt;br /&gt;
&lt;br /&gt;
20 - 3D W Widgets and Picking (Will): found a list of candidates of widgets for Slicer. A few bug fixes for VTK.&lt;br /&gt;
&lt;br /&gt;
21 - XNAT Integration (Dan): Requirements were gathered for a XNAT application that organizes files and caches files from XNAT repositories. Some XML format issues have been addressed.  &lt;br /&gt;
&lt;br /&gt;
22 - KWWidgets Roadmap (Sebastien): Gathered requirements. Been working down the list of the feature requirements.&lt;br /&gt;
&lt;br /&gt;
=== External Collaboration ===&lt;br /&gt;
&lt;br /&gt;
1 - Astronomical coordinate system support [Harvard IIC] (Mike): Astronomical datasets are quite different from medical dataset. Wendy helped with re-centering data. Made progress in converting between coordinate systems (Cartesian to Spherical).&lt;br /&gt;
&lt;br /&gt;
2 - New Meshing Techniques into NA-MIC [Univ. of Iowa]&lt;br /&gt;
 &lt;br /&gt;
3 - Meshing Workflow into Slicer [Univ. of Iowa] (Curt): Will be integrated into Slicer soon. Command line program using VTK. &lt;br /&gt;
 &lt;br /&gt;
4 - Evaluating NA-MIC Tools for Small Animal Imaging Workflows [NCI] (Curt): &lt;br /&gt;
 &lt;br /&gt;
5 - IGSTK-Slicer [Georgetown] (Haiyi): Successful tracking data using IGSTK.&lt;br /&gt;
&lt;br /&gt;
6 - Japanese Intelligent Surgical Instrument Project [AIST]&lt;br /&gt;
 &lt;br /&gt;
7 - GoFigure:High-Level Microscopy Image analysis Application and Algorithms [CalTech-Harvard Medical School] &lt;br /&gt;
&lt;br /&gt;
8 - Doing microscopy image analysis with Slicer3 [The Ohio State University] &lt;br /&gt;
&lt;br /&gt;
9 - fMRI Analysis with Slicer 3 [The Ohio State University]&lt;br /&gt;
&lt;br /&gt;
10 - Resampling DTIs with Slicer 3 [BWH]&lt;br /&gt;
 &lt;br /&gt;
11 - Analyzing fMRI and concurrent EEG with Slicer and SCIRun [BWH] &lt;br /&gt;
 &lt;br /&gt;
12 - Bayesian hierarchical models for fMRI variance components analysis [BWH]&lt;br /&gt;
&lt;br /&gt;
==2008-02-07==&lt;br /&gt;
* Attendees: Ron, Will, Steve, Wendy, Nicole, David G, Mark S., Casey, Sebastien, Curt, Luca&lt;br /&gt;
&lt;br /&gt;
* Look at [http://www.vtk.org/Wiki/VTK_Widget_Examples upcoming VTK 3D widgets]&lt;br /&gt;
* Review of projects from SLC AHM 2008 http://wiki.na-mic.org/Wiki/index.php/2008_Winter_Project_Week&lt;br /&gt;
&lt;br /&gt;
===DBPs===&lt;br /&gt;
&lt;br /&gt;
1 - Stochastic Tractography in Schizophrenia (need to be invited to follow-up TCon) &lt;br /&gt;
&lt;br /&gt;
2 - Cortical thickness analysis - testing EM segmenter to their data.  They estimated parameters and tested during the week.  The goal now is to compare ITK-MS and EM segment module to see how these two tools compare for cortical thickness.  They are reviewing the tools using the same patient data.  &lt;br /&gt;
&lt;br /&gt;
3 - (Mark Scully) Legion segmentation using EM segmenter and other options - worked with Brad using 2 channels of data.  Flare as 3rd channel caused problems.  Desired to have T1/T2/Flair together as three channel dataset.  Marcel is going to deliver his segmentation algorithm software to them to compare results. &lt;br /&gt;
&lt;br /&gt;
4 - Robotic Prostate Interventions - (David Gobbi) Working on transrectal biopsy module for Slicer.  They had a previous module for transcranial biopsies.  One of the most exciting developments was a new prototol &amp;quot;open IGT-Link&amp;quot; which will replace navitrack inside Slicer.  Image transfer is working over this protocol.  A simulator is being developed for the robot.  A few VTK bugs may have been discovered during this process, but it isn't on the top priority list right now. &lt;br /&gt;
&lt;br /&gt;
5 - Prostate Cancer - Wrote new ITK filter that has been submitted to the Sandbox.  They are looking at spherical wavelets for shape segmentation.  The wiki page will be updated soon.&lt;br /&gt;
&lt;br /&gt;
=== Other NA-MIC Projects ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1 - Groupwise Registration - (Casey) New Bspline registration method is being developed here.  It has been used for another project by Casey (#6).   Page needs to be updated. &lt;br /&gt;
&lt;br /&gt;
2 -  (Need to be invited to follow-up TCon)&lt;br /&gt;
&lt;br /&gt;
3 - (Need to be invited to follow-up TCon)) &lt;br /&gt;
&lt;br /&gt;
4 - (Need to be invited to follow-up TCon).  Page needs to be updated&lt;br /&gt;
&lt;br /&gt;
5 - Incorporating DTI tools into NAMIC toolkit - They are gathering a dataset that has both structural and DTI data in agreement.  Previous dataset was missing part of cortex.  UNCDB2 dataset has full coverage of the brain.  Resolution is a bit lower, but full coverage is an advantage.  Page is close to up to data.  Just submitted a paper to ISBI 2008 and working on MICCAI paper, as well.  &lt;br /&gt;
&lt;br /&gt;
* NITRIC is g-forge and would be a good place for automated build process for Slicer modules.  This could make it easier to configure Slicer in client labs without need to build from source. This is still being developed by the NA-MIC core team.  There is an entry on the collaboration section of the NA-MIC website.  Also www.slicer.org/Documentation link. &lt;br /&gt;
&lt;br /&gt;
6 - (Casey) Worked with Serdar using groupwise registration tool.  They are currently evaluating results of this study.  More images will be added.  &lt;br /&gt;
&lt;br /&gt;
7 - (John Melanakos) Spent last week working with collaborators on the MICCAI paper.  Project page is well filled. &lt;br /&gt;
&lt;br /&gt;
8 - (Need to be invited to follow-up TCon)&lt;br /&gt;
&lt;br /&gt;
9 - (Need to be invited to follow-up TCon)&lt;br /&gt;
&lt;br /&gt;
10 - MRML scenes for execution model.  Some of the issues Brad was having have been resolved.  Alex is making adjustments to MRML library as needed for the EM segmentation model. &lt;br /&gt;
&lt;br /&gt;
11  - (Curt) Unstructured Grids in Slicer - Finite Element modeling process was originally in a standalone VTK application.  The first Slicer module integration did not use MRML based storage.  We are now creating subclasses of Model and Unstructured grid data for storage and display in Slicer.  Some minor issues need to be worked out, but the MRML extensions for UnstructuredGrid datatypes are working. &lt;br /&gt;
&lt;br /&gt;
12 - Python (Luca) MatPlotLib plots are close to happening within Slicer.  Steve believes it is 80% complete.  Python command line modules are working now. Multiple arguments had to be worked by Luca.  He has developed Python-based CLI modules.   The event broker is discussed here because it affects the interaction with Python, because a Mutex lock has to be placed on the MRML scene.   Dan has been helping with metamodules - a single Python module which calls other mothers  (hierarchical execution, recipes, etc.).  &lt;br /&gt;
&lt;br /&gt;
* Ron asked about using this scripting technique for the ModelMaker.  Some of the parameter setting, etc. could be set in the top module.   Nicole will look at this.  Kilian said that he wanted to call the &amp;quot;modelmaker&amp;quot; from another module.  &lt;br /&gt;
&lt;br /&gt;
* A need was identified for new wiki pages:  (1) scripted modules, (2) metamodules, (2) python scripted modules&lt;br /&gt;
&lt;br /&gt;
13 - (Luca) Transform hardening - Sometimes images are not XYZ alligned.  How will command line modules treat an object if it is the child of a transform.  The module needs to be able to apply xforms to data (after hierarchy is flattened) to get xformed data.  Jim and Steve talked through this lately becomes of the transforms access two-directions (from parents / to parents, etc.)  They are looking at how to change the model. &lt;br /&gt;
&lt;br /&gt;
14 - (Steve) MRML support for out-of-core processing - Steve put a link to a new page.  Dan, Jim, Wendy, Steve, etc.  working through NAC renewal grant (5 years).  Multiresolution and asynchronous data are likely targets for this effort, but it will be a long-term effort.  &lt;br /&gt;
&lt;br /&gt;
15 - Event Broker discussion - Steve has made process on this, but this wiki page is older.  See the event broker page.  (look at link under Objective).  New term &amp;quot;observation&amp;quot; :  completely introspectable.  A full dependency between objects is implemented.  When a subject issues a &amp;quot;modified&amp;quot; event,  Delete events are maintained.  Complete &amp;quot;relationship&amp;quot; management of the interaction between objects.  This helps by allowing asynchronous event processing.  MRML has been converted to use the event broker with asynchronous events managed by the Slicer GUI (async events invoked after GUI events are done).  This hasn't broken anything so far, but should improve scalability.   Dot logfile format can be generated for inter-object dependencies.  This can be used to help provide &amp;quot;who called who&amp;quot; traces.    Some special magic is done in MRML Display nodes.  They set &amp;quot;observation nodes&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Next Week ===&lt;br /&gt;
Continue through project review.  Request missing project members to attend.  Review wiki pages.&lt;br /&gt;
&lt;br /&gt;
==2008-01-31==&lt;br /&gt;
Attendees: Jim, Steve, Stephen, Wendy, Xiaodong, Nicole, Katie, Ron&lt;br /&gt;
* Project week follow-up&lt;br /&gt;
** Half of tcon on Feb 7&lt;br /&gt;
** Half of tcon on Feb 14&lt;br /&gt;
* Registration&lt;br /&gt;
** Viola-Wells optimizations need to be enabled&lt;br /&gt;
** Stephen needs to check-in and publish recent changes&lt;br /&gt;
** Stephen needs to update the wiki&lt;br /&gt;
** Luis continues to make optimizations (main focus is memory reduction)&lt;br /&gt;
* BatchMake&lt;br /&gt;
** Grid Wizard - meeting on Monday&lt;br /&gt;
** Integration with Slicer delivered via getbuildtest2&lt;br /&gt;
* New webpages&lt;br /&gt;
** http://slicer.org&lt;br /&gt;
** Uses wiki-to-web&lt;br /&gt;
** Feel free to edit/improve&lt;br /&gt;
* Slicer-specific wiki&lt;br /&gt;
** Migrating appropriate info from Na-mic to slicer&lt;br /&gt;
** Hold off on adding to Slicer-wiki until notified&lt;br /&gt;
*** Continue using Na-mic wiki&lt;br /&gt;
* New Nitrc project&lt;br /&gt;
** Jim Miller is leading&lt;br /&gt;
** &amp;quot;Slicer3 plug-in examples&amp;quot; project&lt;br /&gt;
** http://nitrc.org - search for slicer3&lt;br /&gt;
*** Includes demo/stub for ITK filtering data, etc.&lt;br /&gt;
** Collection associated with an ITK course being taught&lt;br /&gt;
** Requires CVS version of ITK&lt;br /&gt;
** Works with Slicer build and Slicer install&lt;br /&gt;
** Steve P is the liaison with NITRC&lt;br /&gt;
* Slicer tutorial at UNC, April 14th&lt;br /&gt;
** Working with UNC's BRIC (http://www.bric.unc.edu)&lt;br /&gt;
** Sonja, Randy, Martin, Stephen&lt;br /&gt;
* User-level Slicer training - Feb 20 at BWH&lt;br /&gt;
** 1249 Boyleston&lt;br /&gt;
** Release version of Slicer3 &lt;br /&gt;
&lt;br /&gt;
==2008-01-24==&lt;br /&gt;
Attendees: Jim, Steve, Wendy, Xiaodong, Nicole, Katie, Alex, Luis, Ron, Will&lt;br /&gt;
* Project week follow-up (Next week?)&lt;br /&gt;
** Will will send email invitations for first half of projects for next week's tcon&lt;br /&gt;
* Loadable modules&lt;br /&gt;
** Alex and Terry are rearranging Slicer3.cxx to support loadable modules&lt;br /&gt;
** Separate branch for built-in module discovery process&lt;br /&gt;
** Sebastien is working on build issues for modules whose code is outside Slicer3&lt;br /&gt;
* GenerateCLP - Thanks Hans for changes to support building modules&lt;br /&gt;
** Hans is running a class this semester where the students will build Slicer CLI modules.&lt;br /&gt;
** Jim is working on an ExampleModule for people to use as a template for building modules outside of Slicer3.  Perhaps NITRC.&lt;br /&gt;
* XML library&lt;br /&gt;
** What to do with libaries that are too big to include in the source directory?&lt;br /&gt;
* AHM 2009, Jan 5-9, 2009&lt;br /&gt;
* Summer Project Week, Jun 23-27, 2008&lt;br /&gt;
* New server architecture for wiki, svn, publication database&lt;br /&gt;
&lt;br /&gt;
==2008-01-17==&lt;br /&gt;
Attendees: Jim, Katie, Sebastien, Stephen, Luis, Steve, Wendy, Will&lt;br /&gt;
&lt;br /&gt;
* Luis and Bill Hoffman are making progress in making ITK installation relocatable.  This is needed to finish the work on building plugins from an installation.&lt;br /&gt;
* What's in VTK 5.2?&lt;br /&gt;
** Infovis - Tables, Graphs, Views, IO&lt;br /&gt;
** Refinements to WWidgets. Client/Server connections within the widgets. Event translation. New widgets (text, caption, affine, checkerboard, rectilinear wipe, annotation, key frame, contour, measurement, point/placer, plot)&lt;br /&gt;
** Build now? Or wait until 5.2 released?&lt;br /&gt;
** Repository freeze in March&lt;br /&gt;
** Release on April 1, 2008&lt;br /&gt;
* ITK release&lt;br /&gt;
** Patches to ITK 3.4&lt;br /&gt;
*** Nine component/six component tensor conversion in IO has been patched to ITK 3.4&lt;br /&gt;
** 1/19-2/1 moving contributions on Insight Journal for ITK 3.6&lt;br /&gt;
** Move items from Review directory to main tree (QuadMesh, TransformIO) for ITK 3.6&lt;br /&gt;
** Freeze repository 2/29 for ITK 3.6&lt;br /&gt;
** Slicer3 will need to build against the Review directory.&lt;br /&gt;
* CMake release&lt;br /&gt;
** Version 2.6 on the horizon - release candidate in 3 weeks.&lt;br /&gt;
* Tcl/Tk 8.5&lt;br /&gt;
** Sebastien has a Windows build&lt;br /&gt;
** Steve will try it out&lt;br /&gt;
** Wait to switch to 8.5 until we have a good reason&lt;br /&gt;
* Loadable modules&lt;br /&gt;
** Sebastien - working on CMake issues on building modules as loadable modules&lt;br /&gt;
** Terry - working on loading modules and reworking Slicer3.cxx&lt;br /&gt;
* [http://www.slicer.org/slicerWiki/index.php/Slicer3:EventBroker Slicer3:EventBroker | Event Broker]&lt;br /&gt;
* DWI DICOM as part of the Load Volume.  Xiaodong is working on it.&lt;br /&gt;
* ITKFactories directory in build and installs to hold ImageIO plugin libraries. Should increase the speed of executable plugins on the Mac.&lt;br /&gt;
* OpenIGTLink&lt;br /&gt;
** Protocol on the wiki (message format)&lt;br /&gt;
** Put code in Sandbox, SourceForge, NITRC, Google Code???&lt;br /&gt;
* Will schedule a time to go over the Project Week results&lt;br /&gt;
&lt;br /&gt;
==2008-01-10==&lt;br /&gt;
No tcon due to AHM&lt;br /&gt;
&lt;br /&gt;
==2008-01-03==&lt;br /&gt;
* Attendees: Jim, Steve, Will, Brad Davis&lt;br /&gt;
* Topics:&lt;br /&gt;
** Jim and Will talked about leading the Monday and Friday sessions, and who would do what.&lt;br /&gt;
** We are going to send out reminders to the project leads to ensure that their project descriptions are up to date&lt;br /&gt;
** We discussed the software process project to make sure that we have a chance to address the Slicer build process, dashboards, etc.&lt;br /&gt;
** We decided not to hold the project wrap-up presentation at AHM; we will do that later at subsequent TCons. (We decided that we needed the time to actually work. We are concerned that we are starting to see too many break-outs and not enough time to work.)&lt;br /&gt;
** We keenly missed Tina and hope that she and her family are doing well.&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=NA-MIC/Projects/External_Collaboration/Slicer3-vmtk_Integration&amp;diff=27709</id>
		<title>NA-MIC/Projects/External Collaboration/Slicer3-vmtk Integration</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=NA-MIC/Projects/External_Collaboration/Slicer3-vmtk_Integration&amp;diff=27709"/>
		<updated>2008-06-27T13:24:55Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Key Investigators */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:ProjectWeek-2008.png|thumb|320px|Return to [[2008_Summer_Project_Week|Project Week Main Page]] ]]&lt;br /&gt;
|[[Image:VmtkSlicerModule.jpg|thumb|320px|Vmtk working inside Slicer3.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Mario Negri Institute, University of Verona: Luca Antiga&lt;br /&gt;
* Dan Blezek&lt;br /&gt;
* Mike Halle&lt;br /&gt;
* Steve Piper&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
To create a Slicer-based platform for segmentation of vascular segments from angiographic images (CTA, MRA, ...), analysis of vascular geometry, mesh generation, computational hemodynamics (CFD) and visualization.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
To integrate vmtk scripts within Slicer as command-line modules for the non-interactive tasks, and to create ad-hoc GUI modules for the more interactive tasks (i.e. segmentation).&lt;br /&gt;
&lt;br /&gt;
The plan for the project week is to finalize the implementation of an interactive LevelSetSegment module that replicates (and improves) the interactive segmentation tool currently in vmtk. Tentatively, LevelSetSegment will be a Python Scripted Module.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
During project weeks last year (see [[Collaboration/VMTK | 2007 Project Week at MIT]]), automated conversion of vmtk script pipes to Slicer command-line modules has been implemented.&lt;br /&gt;
&lt;br /&gt;
During June 2008 project week, the architecture of the new LevelSetSegment module has been finalized. &lt;br /&gt;
A new vtkMRMLLevelSetNode, subclass of vtkMRMLScalarVolumeNode, has been introduced. The corresponding display node directly displays the poly data corresponding to the level set surface.&lt;br /&gt;
The final implementation of the module (except the new MRML nodes) will be converted to a Python scripted module.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===References===&lt;br /&gt;
&lt;br /&gt;
* [http://vmtk.sourceforge.net vmtk.sourceforge.net]&lt;br /&gt;
* Lee SW, Antiga L, Spence JD and Steinman DA. Geometry of the carotid bifurcation predicts its exposure to disturbed flow. Stroke. Accepted.&lt;br /&gt;
* Thomas JB, Antiga L, Che S, Milner JS, Hangan Steinman DA, Spence JD, Rutt BK and Steinman DA. Variation in the carotid bifurcation geometry of young vs. older adults: Implications for &amp;quot;geometric risk&amp;quot; of atherosclerosis. Stroke, 36(11): 2450-2456, Nov 2005.&lt;br /&gt;
* Antiga L, Steinman DA. Robust and objective decomposition and mapping of bifurcating vessels. IEEE Transactions on Medical Imaging, 23(6): 704-713, June 2004.&lt;br /&gt;
* Antiga L, Ene-Iordache B and Remuzzi A. Computational geometry for patient-specific reconstruction and meshing of blood vessels from MR and CT angiography. IEEE Transactions on Medical Imaging, 22(5): 674-684, May 2003.&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=NA-MIC/Projects/External_Collaboration/Slicer3-vmtk_Integration&amp;diff=27343</id>
		<title>NA-MIC/Projects/External Collaboration/Slicer3-vmtk Integration</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=NA-MIC/Projects/External_Collaboration/Slicer3-vmtk_Integration&amp;diff=27343"/>
		<updated>2008-06-23T17:22:27Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Key Investigators */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:ProjectWeek-2008.png|thumb|320px|Return to [[2008_Summer_Project_Week|Project Week Main Page]] ]]&lt;br /&gt;
|[[Image:VmtkSlicerModule.jpg|thumb|320px|Vmtk working inside Slicer3.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Mario Negri Institute, University of Verona: Luca Antiga&lt;br /&gt;
* Dan Blezek&lt;br /&gt;
* Mike Halle&lt;br /&gt;
* Steve Piper&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
To create a Slicer-based platform for segmentation of vascular segments from angiographic images (CTA, MRA, ...), analysis of vascular geometry, mesh generation, computational hemodynamics (CFD) and visualization.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
To integrate vmtk scripts within Slicer as command-line modules for the non-interactive tasks, and to create ad-hoc GUI modules for the more interactive tasks (i.e. segmentation).&lt;br /&gt;
&lt;br /&gt;
The plan for the project week is to finalize the implementation of an interactive LevelSetSegment module that replicates (and improves) the interactive segmentation tool currently in vmtk. Tentatively, LevelSetSegment will be a Python Scripted Module.&lt;br /&gt;
&lt;br /&gt;
A new vtkMRMLLevelSetNode will be introduced (it will be derived from vtkMRMLScalarVolumeNode, and will have a poly data representation in the Display node) &lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
During project weeks last year (see [[Collaboration/VMTK | 2007 Project Week at MIT]]), automated conversion of vmtk script pipes to Slicer command-line modules has been implemented.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===References===&lt;br /&gt;
&lt;br /&gt;
* [http://vmtk.sourceforge.net vmtk.sourceforge.net]&lt;br /&gt;
* Lee SW, Antiga L, Spence JD and Steinman DA. Geometry of the carotid bifurcation predicts its exposure to disturbed flow. Stroke. Accepted.&lt;br /&gt;
* Thomas JB, Antiga L, Che S, Milner JS, Hangan Steinman DA, Spence JD, Rutt BK and Steinman DA. Variation in the carotid bifurcation geometry of young vs. older adults: Implications for &amp;quot;geometric risk&amp;quot; of atherosclerosis. Stroke, 36(11): 2450-2456, Nov 2005.&lt;br /&gt;
* Antiga L, Steinman DA. Robust and objective decomposition and mapping of bifurcating vessels. IEEE Transactions on Medical Imaging, 23(6): 704-713, June 2004.&lt;br /&gt;
* Antiga L, Ene-Iordache B and Remuzzi A. Computational geometry for patient-specific reconstruction and meshing of blood vessels from MR and CT angiography. IEEE Transactions on Medical Imaging, 22(5): 674-684, May 2003.&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2008_Summer_Project_Week:PythonInSlicer&amp;diff=27028</id>
		<title>2008 Summer Project Week:PythonInSlicer</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2008_Summer_Project_Week:PythonInSlicer&amp;diff=27028"/>
		<updated>2008-06-18T08:15:33Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* References */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:ProjectWeek-2008.png|thumb|320px|Return to [[2008_Summer_Project_Week|Project Week Main Page]] ]]&lt;br /&gt;
|[[Image:Python-logo.png |thumb|320px|[http://www.python.org]]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Luca Antiga&lt;br /&gt;
* Dan Blezek&lt;br /&gt;
* Mike Halle&lt;br /&gt;
* Steve Piper&lt;br /&gt;
* Demian Wasserman&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
To finalize the use of Python within Slicer for command-line modules, scripted modules and meta-modules (or module chaining). The main rework is needed for scripted modules.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
The plan for the project week is to get the status of Python within Slicer ready for release. This will involve some general code review and some rework on Python Scripted Module infrastructure.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
During the January 2008 project week, within [[Projects/Slicer3/2007_Project_Week_Python support in Slicer3|Python Support in Slicer 3]], preliminary Python support for Numpy/Scipy, command line modules (executed in the main thread), calling of all registered modules from Python and scripted modules have been added.   &lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===References===&lt;br /&gt;
&lt;br /&gt;
* [http://www.python.org www.python.org]&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2008_Summer_Project_Week:PythonInSlicer&amp;diff=27027</id>
		<title>2008 Summer Project Week:PythonInSlicer</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2008_Summer_Project_Week:PythonInSlicer&amp;diff=27027"/>
		<updated>2008-06-18T08:13:23Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: New page: {| |Project Week Main Page ]] |[http://www.python.org] |}   __NOTOC__...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:ProjectWeek-2008.png|thumb|320px|Return to [[2008_Summer_Project_Week|Project Week Main Page]] ]]&lt;br /&gt;
|[[Image:Python-logo.png |thumb|320px|[http://www.python.org]]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Luca Antiga&lt;br /&gt;
* Dan Blezek&lt;br /&gt;
* Mike Halle&lt;br /&gt;
* Steve Piper&lt;br /&gt;
* Demian Wasserman&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
To finalize the use of Python within Slicer for command-line modules, scripted modules and meta-modules (or module chaining). The main rework is needed for scripted modules.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
The plan for the project week is to get the status of Python within Slicer ready for release. This will involve some general code review and some rework on Python Scripted Module infrastructure.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
During the January 2008 project week, within [[Projects/Slicer3/2007_Project_Week_Python support in Slicer3|Python Support in Slicer 3]], preliminary Python support for Numpy/Scipy, command line modules (executed in the main thread), calling of all registered modules from Python and scripted modules have been added.   &lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===References===&lt;br /&gt;
&lt;br /&gt;
* [http://www.python.org]&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2008_Summer_Project_Week&amp;diff=27026</id>
		<title>2008 Summer Project Week</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2008_Summer_Project_Week&amp;diff=27026"/>
		<updated>2008-06-18T07:53:21Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Other Projects */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[Engineering:Programming_Events|Programming/Project Events]]&lt;br /&gt;
&lt;br /&gt;
[[Image:ProjectWeek-2008.png|thumb|220px|right|Summer 2008]]&lt;br /&gt;
&lt;br /&gt;
== Logistics ==&lt;br /&gt;
*'''Dates:''' June 23-27, 2008&lt;br /&gt;
*'''Location:''' MIT. [[Meeting_Locations:MIT_Grier_A_%26B|Grier Rooms A &amp;amp; B: 34-401A &amp;amp; 34-401B]].&lt;br /&gt;
*'''Registration Fee:''' $260 (covers the cost of breakfast, lunch and coffee breaks for the week). Due by Friday, June 13th, 2008. Please make checks out to &amp;quot;Massachusetts Institute of Technology&amp;quot; and mail to: Donna Kaufman, MIT, 77 Massachusetts Ave., 38-409a, Cambridge, MA 02139.  Receipts will be provided by email as checks are received.  Please send questions to dkauf at mit.edu. If you are attending for one day only, the registration fee is not required.&lt;br /&gt;
*'''Registration Method''' The event is full. [[User:Tkapur|Tkapur]] 18:12, 17 June 2008 (UTC)&lt;br /&gt;
*'''Hotel:''' We have a group rate of $239/night (plus tax) for a room with either 1 king or 2 queen beds at the [http://www.hotelatmit.com Hotel at MIT (now called Le Meridien)]. [http://www.starwoodmeeting.com/StarGroupsWeb/booking/reservation?id=0805167317&amp;amp;key=4FD1B  Please click here to reserve.] This rate is good only through June 1.&lt;br /&gt;
*Here is some information about several other Boston area hotels that are convenient to NA-MIC events: [[Boston_Hotels|Boston_Hotels]]. Summer is tourist season in Boston, so please book your rooms early.&lt;br /&gt;
*2008 Summer Project Week [[NA-MIC/Projects/Theme/Template|'''Template''']]&lt;br /&gt;
*[[2007_Programming/Project_Week_MIT#Projects|Last Year's Projects as a reference]]&lt;br /&gt;
*For hosting projects, we are planning to make use of the NITRC resources.  See [[NA-MIC_and_NITRC | Information about NITRC Collaboration]]&lt;br /&gt;
*Next Project Week in Utah -- January 5-9, 2009&lt;br /&gt;
&lt;br /&gt;
==Introduction to NA-MIC Project Week==&lt;br /&gt;
Please read an introduction about these events [[Project_Events#Introduction|here]].&lt;br /&gt;
&lt;br /&gt;
== Agenda==&lt;br /&gt;
* Monday &lt;br /&gt;
** noon-1pm lunch &lt;br /&gt;
**1pm: Welcome (Ron Kikinis)&lt;br /&gt;
** 1:05-3:30pm Introduce [[#Projects|Projects]] using templated wiki pages (all Project Leads) ([[NA-MIC/Projects/Theme/Template|Wiki Template]]) &lt;br /&gt;
** 3:30-5:30pm Start project work&lt;br /&gt;
* Tuesday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 9:00-9:45am: NA-MIC Software Process &lt;br /&gt;
** 10-10:30am [[Project Week 2008 Slicer 3.0 Update|Slicer 3.0 Update]] (Jim Miller, Steve Pieper)&lt;br /&gt;
** 11-12noon [[Project Week 2008 Slicer Tuning| Performance tuning for Slicer 3.2]] (Ron Kikinis)&lt;br /&gt;
** noon lunch&lt;br /&gt;
** 2:30-3:30pm: [[Project Week 2008 Special topic breakout: XNAT Database]] (Daniel Marcus) &lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Wednesday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 9:00-12pm [[Project Week 2008 Special topic breakout: ITK]] (Luis Ibanez)&lt;br /&gt;
** noon lunch&lt;br /&gt;
** 2:30-3:30pm: [[Project Week 2008 Special topic breakout: Non-rigid Registration]] (Stephen Aylward)&lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Thursday&lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** noon lunch&lt;br /&gt;
**2:30-3:30pm [[Project Week 2008 Special topic breakout: GWE]] (Marco Ruiz)&lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Friday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 10am-noon: Project Progress using update [[#Projects|Project Wiki pages]]&lt;br /&gt;
** noon lunch boxes and adjourn.  (Next one [[AHM_2009| in Utah the week of Jan 5, 2009]])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
===DBP II===&lt;br /&gt;
These are projects by the new set of DBPS:&lt;br /&gt;
#[[DBP2:Harvard|Velocardio Facial Syndrome (VCFS) as a Genetic Model for Schizophrenia]] (Harvard: Marek Kubicki, PI)&lt;br /&gt;
##EPI-DWI Distortion correction (Sylvain Bouix BWH, Tauseef Rehman GATech)&lt;br /&gt;
##[[2008_Summer_Project_Week:EddyCurrentCorrection|EPI-DWI Eddy Current distortion correction]] (Sylvain Bouix BWH, Ran Tao Utah)&lt;br /&gt;
##Lobe Parcellation of 3T MR data - need help parametrization (Sylvain Bouix BWH, Priya Srinivasan BWH, Brad Davis Kitware)&lt;br /&gt;
##Finsler method (John Melonakos GATech, Marek Kubicki BWH)&lt;br /&gt;
##[[2008_Summer_Project_Week:PopulationDTIApplication|Group Analysis of DTI]] (Casey Goodlett Utah, Marek Kubicki BWH)&lt;br /&gt;
#[[DBP2:UNC|Longitudinal MRI Study of Early Brain Development in Autism]] (UNC: Heather Hazlett, Joseph Piven, PI)&lt;br /&gt;
##[[2008_Summer_Project_Week:RegionalCorticalThicknessTool|Work Flow Tool for regional cortical thickness pipeline]] (Clement Vachet UNC)&lt;br /&gt;
##[[2008_Summer_Project_Week:NITRCRegistration|NITRC registration of cortical thickness modules]] (Clement Vachet UNC)&lt;br /&gt;
##[[2008_Summer_Project_Week:DWI-DTI_PrepTools|DWI DTI Prep Tools]] (Zhexing Liu UNC) &lt;br /&gt;
#[[DBP2:MIND|Analysis of Brain Lesions in Lupus]] (MIND/UNM: Jeremy Bockholt, Charles Gasparovic PI)&lt;br /&gt;
##[[DBP2:MIND:RoadmapProject|Finish Roadmap Project]]&lt;br /&gt;
##[[DBP2:MIND:LongitudinalRegistrationProject|Longitudinal Registration]]&lt;br /&gt;
##[[DBP2:MIND:BeyondLesionsProject|Beyond Lesions]]&lt;br /&gt;
#[[DBP2:JHU|Segmentation and Registration Tools for Robotic Prostate Intervention]] (Queens/JHU: Gabor Fichtinger, PI)&lt;br /&gt;
##[[2008_Summer_Project_Week:TransRectal_Prostate_Biopsy_Module|Trans-Rectal Prostate Biopsy module]] (David Gobbi, Gabor Fichtinger, Queens/JHU)&lt;br /&gt;
##[[2008_Summer_Project_Week:ProstateSegReg|Prostate Segmentation and Registration]] (Yi Gao GATech, Gabor Fichtinger JHU)&lt;br /&gt;
##[[2008_Summer_Project_Week:PerkStation|Hardware/software overlay for percutaneous intervention (PERK Station)]] (Siddharth Vikal, Gabor Fichtinger, Queens/JHU)&lt;br /&gt;
&lt;br /&gt;
===Other Projects===&lt;br /&gt;
#[[2008_Summer_Project_Week:EddyCurrentCorrection|Eddy current and head motion correction of DWIs]] (Ran Tao, Utah, Sylvain Bouix, BWH, Xiaodong Tao, GE, Tom Fletcher, Utah)&lt;br /&gt;
#[[2008_Summer_Project_Week:GroupwiseBSplineForDTI| Integraton of groupwise b-spline registration into atlas building]] (Casey Goodlett, Serdar Balci)&lt;br /&gt;
# CVS / SVN auto synchronization&lt;br /&gt;
# [[2008_Summer_Project_Week:3DWidgetsInSlicer|3D Widgets in Slicer]] (Nicole Aucoin, Will Schroeder)&lt;br /&gt;
## Issues with existing widgets&lt;br /&gt;
## Design of new widgets&lt;br /&gt;
# Batch processing in the NAMIC Kit (Julien, Marco, Steve, Jim)&lt;br /&gt;
#[[2008_Summer_Project_Week:ModuleChaining|Module Chaining]] (Marco, Jim, Steve, Dan B., Luca)&lt;br /&gt;
# Nonlinear transforms (Jim, Steve, Luis)&lt;br /&gt;
## TransformToWorld/TransformFromWorld, integration with slice viewing&lt;br /&gt;
# Slicer3, XNAT integration, and desigining XCEDE Web Services (Dan M., Steve, Julien, Dan B.)&lt;br /&gt;
## Review and enrich use cases&lt;br /&gt;
# [[2008_Summer_Project_Week:PythonInSlicer| Python in Slicer]] (Dan B., Michael Halle, Steve, Luca)&lt;br /&gt;
# [[2008_Summer_Project_Week:PerformanceTuningFiducials|Performance Tuning of Fiducials]] using the EventBroker and other tools (Nicole Aucoin, Alex Yarmarkovich, Steve Pieper, Will Schroeder)&lt;br /&gt;
# GUI Tweaking (Wendy, Sebastien) [http://www.na-mic.org/Bug/view.php?id=242]&lt;br /&gt;
# [[2008_Summer_Project_Week:fMRIconnectivity|fMRI connectivity]]  (Bryce Kim, MIT)&lt;br /&gt;
# [[2008_Summer_Project_Week:AtlasFreeSegmentation|Atlas free Segmentation]]  (Tammy Riklin-Raviv, MIT)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/EM Bias Field Correction | New Bias Field Correction in EM]] (Carlos Sánchez Mendoza, Kilian Pohl - SPL, Brad Davis - Kitware)&lt;br /&gt;
# [[2008_Summer_Project_Week:FluidMechanicsTractographyUCLA|Fluid Mechanics Based DTI Tractography]] (Nathan Hageman, UCLA)&lt;br /&gt;
&lt;br /&gt;
===External Collaborations===&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/UWA-Perth]] (Adam Wittek)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/MRSI Module for Slicer]] (Bjoern Menze)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/NIREP: Non-rigid Image Registration Evaluation]] (Gary Christensen Group)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/Lung Atlas]] (Gary Christensen Group)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/Non-rigid image registration]] (Gary Christensen Group)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/SARP phantom]] (Keith Gunderson)&lt;br /&gt;
#[[FMA (Protege) links to Slicer]] (Vish, Mike, Florin, Jim, Steve, Wendy)&lt;br /&gt;
#[[NA-MIC/Projects/External Collaboration/Measuring Alcohol and Stress Interaction]]&lt;br /&gt;
#[[NA-MIC/Projects/External Collaboration/Slicer3-vmtk Integration]] (Luca Antiga, Dan Blezek, Mike Halle, Steve Piper)&lt;br /&gt;
#[[NA-MIC/Projects/External Collaboration/Mesh Generation Summer 2008]] (Iowa Group)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/Carto_scar_BIDMC]] (Dana Peters Group)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/3D Ultrasound Module in Slicer3]] (Junichi, Haiying and Noby - SPL, David - Queen's), Danielle - Robarts) )&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/MGH RadOnc]] (Greg Sharp, MGH)&lt;br /&gt;
#[[NA-MIC/Projects/External Collaboration/W&amp;amp;M CRTC]] Non-rigid registration for neurosurgery (Nikos Chrisochoides, Andriy Fedorov, College of William&amp;amp;Mary)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/SBIA UPenn]] Non-rigid DTI Registration (Ragini Verma, SBIA Upenn)&lt;br /&gt;
&lt;br /&gt;
===Non-Medical Collaborations===&lt;br /&gt;
#[[NA-MIC/Projects/Non-Medical Collaborations/Astronomical Medicine|Astronomical Medicine]] (Harvard IIC: Douglas Alan, Michael Halle)&lt;br /&gt;
&lt;br /&gt;
== Preparation ==&lt;br /&gt;
&lt;br /&gt;
# Please make sure that you are on the http://public.kitware.com/cgi-bin/mailman/listinfo/na-mic-project-week mailing list&lt;br /&gt;
&lt;br /&gt;
# [[Engineering:TCON_2008|May 08 and May 15 TCON DBPs ONLY]] at 3pm ET to discuss NA-MIC DBP Projects ONLY. &lt;br /&gt;
# [[Engineering:TCON_2008|May 22 TCON#1]] at 3pm ET to discuss NA-MIC Engr Core Projects and Assign/Verify Teams&lt;br /&gt;
# [[Engineering:TCON_2008|May 29 TCON#2]] at 3pm ET to discuss NA-MIC ALGORITHMS Core Lead Projects.  Project leads should sign up for a slot [[Engineering:TCON_2008|here]]. Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 5 TCON#3]] at 3pm ET to discuss NA-MIC EXTERNAL Collaborations.  All NIH funded &amp;quot;collaborations with NCBC&amp;quot; leads should call. Project leads should sign up for a slot [[Engineering:TCON_2008|here]].  Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 12 TCON#4]] at 3pm ET to discuss NA-MIC EXTERNAL Collaborations.  All other collaboration leads should call. Project leads should sign up for a slot [[Engineering:TCON_2008|here]].  Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 19 TCON#5]] at 3pm ET to tie loose ends.  Anyone with un-addressed questions should call.&lt;br /&gt;
# By 3pm ET on June 12, 2008: [[NA-MIC/Projects/Theme/Template|Complete a templated wiki page for your project]]. Please do not edit the template page itself, but create a new page for your project and cut-and-paste the text from this template page.  If you have questions, please send an email to tkapur at bwh.harvard.edu.&lt;br /&gt;
# By 3pm on June 19, 2008: Create a directory for each project on the [[Engineering:SandBox|NAMIC Sandbox]] (Zack)&lt;br /&gt;
## Commit on each sandbox directory the code examples/snippets that represent our first guesses of appropriate methods. (Luis and Steve will help with this, as needed)&lt;br /&gt;
## Gather test images in any of the Data sharing resources we have (e.g. the BIRN). These ones don't have to be many. At least three different cases, so we can get an idea of the modality-specific characteristics of these images. Put the IDs of these data sets on the wiki page. (the participants must do this.)&lt;br /&gt;
## Setup nightly tests on a separate Dashboard, where we will run the methods that we are experimenting with. The test should post result images and computation time. (Zack)&lt;br /&gt;
# Please note that by the time we get to the project event, we should be trying to close off a project milestone rather than starting to work on one...&lt;br /&gt;
&lt;br /&gt;
==Pictures==&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=NA-MIC/Projects/External_Collaboration/Slicer3-vmtk_Integration&amp;diff=26800</id>
		<title>NA-MIC/Projects/External Collaboration/Slicer3-vmtk Integration</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=NA-MIC/Projects/External_Collaboration/Slicer3-vmtk_Integration&amp;diff=26800"/>
		<updated>2008-06-12T20:06:19Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Key Investigators */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:ProjectWeek-2008.png|thumb|320px|Return to [[2008_Summer_Project_Week|Project Week Main Page]] ]]&lt;br /&gt;
|[[Image:VmtkSlicerModule.jpg|thumb|320px|Vmtk working inside Slicer3.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Mario Negri Institute, University of Verona: Luca Antiga&lt;br /&gt;
* Dan Blezek&lt;br /&gt;
* Mike Halle&lt;br /&gt;
* Steve Piper&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
To create a Slicer-based platform for segmentation of vascular segments from angiographic images (CTA, MRA, ...), analysis of vascular geometry, mesh generation, computational hemodynamics (CFD) and visualization.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
To integrate vmtk scripts within Slicer as command-line modules for the non-interactive tasks, and to create ad-hoc GUI modules for the more interactive tasks (i.e. segmentation).&lt;br /&gt;
&lt;br /&gt;
The plan for the project week is to finalize the implementation of an interactive LevelSetSegment module that replicates (and improves) the interactive segmentation tool currently in vmtk. Tentatively, LevelSetSegment will be a Python Scripted Module.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
During project weeks last year (see [[Collaboration/VMTK | 2007 Project Week at MIT]]), automated conversion of vmtk script pipes to Slicer command-line modules has been implemented.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===References===&lt;br /&gt;
&lt;br /&gt;
* [http://vmtk.sourceforge.net vmtk.sourceforge.net]&lt;br /&gt;
* Lee SW, Antiga L, Spence JD and Steinman DA. Geometry of the carotid bifurcation predicts its exposure to disturbed flow. Stroke. Accepted.&lt;br /&gt;
* Thomas JB, Antiga L, Che S, Milner JS, Hangan Steinman DA, Spence JD, Rutt BK and Steinman DA. Variation in the carotid bifurcation geometry of young vs. older adults: Implications for &amp;quot;geometric risk&amp;quot; of atherosclerosis. Stroke, 36(11): 2450-2456, Nov 2005.&lt;br /&gt;
* Antiga L, Steinman DA. Robust and objective decomposition and mapping of bifurcating vessels. IEEE Transactions on Medical Imaging, 23(6): 704-713, June 2004.&lt;br /&gt;
* Antiga L, Ene-Iordache B and Remuzzi A. Computational geometry for patient-specific reconstruction and meshing of blood vessels from MR and CT angiography. IEEE Transactions on Medical Imaging, 22(5): 674-684, May 2003.&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2008_Summer_Project_Week&amp;diff=26799</id>
		<title>2008 Summer Project Week</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2008_Summer_Project_Week&amp;diff=26799"/>
		<updated>2008-06-12T20:04:53Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* External Collaborations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[Engineering:Programming_Events|Programming/Project Events]]&lt;br /&gt;
&lt;br /&gt;
[[Image:ProjectWeek-2008.png|thumb|220px|right|Summer 2008]]&lt;br /&gt;
&lt;br /&gt;
== Logistics ==&lt;br /&gt;
&lt;br /&gt;
'''Dates:''' June 23-27, 2008&lt;br /&gt;
&lt;br /&gt;
'''Location:''' MIT. [[Meeting_Locations:MIT_Grier_A_%26B|Grier Rooms A &amp;amp; B: 34-401A &amp;amp; 34-401B]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Registration Fee:''' $260 (this will cover the cost of breakfast, lunch and coffee breaks for the week). Due by Friday, June 13th, 2008. Please make checks out to &amp;quot;Massachusetts Institute of Technology&amp;quot; and mail to: Donna Kaufman, MIT, 77 Massachusetts Ave., 38-409a, Cambridge, MA 02139&lt;br /&gt;
&lt;br /&gt;
'''Registration Method''' Please add your name to the attendee list below (create namic wiki account if you don't have one, by clicking on the &amp;quot;login/create account&amp;quot; link on the top right corner of this page), and then mail a check to Donna Kaufman at the address above.&lt;br /&gt;
&lt;br /&gt;
If you are attending for one day only, the registration fee is not required.&lt;br /&gt;
&lt;br /&gt;
'''Hotel:''' We have a group rate of $239/night (plus tax) for a room with either 1 king or 2 queen beds at the [http://www.hotelatmit.com Hotel at MIT (now called Le Meridien)]. [http://www.starwoodmeeting.com/StarGroupsWeb/booking/reservation?id=0805167317&amp;amp;key=4FD1B  Please click here to reserve.]This rate is good only through June 1.&lt;br /&gt;
&lt;br /&gt;
Here is some information about several other Boston area hotels that are convenient to NA-MIC events: [[Boston_Hotels|Boston_Hotels]]. Summer is tourist season in Boston, so please book your rooms early.&lt;br /&gt;
&lt;br /&gt;
([[Project Week Logistics Checklist|This is a checklist for the onsite planning items]])&lt;br /&gt;
&lt;br /&gt;
==Introduction to NA-MIC Project Week==&lt;br /&gt;
&lt;br /&gt;
NA-MIC Project Week is a hands on activity -- programming using the [[NA-MIC-Kit|NA-MIC Kit]], algorithm design, and clinical application -- that has become one of the major events in the [[NA-MIC-Kit|NA-MIC Kit]] calendar. This event is the seventh of the [[Engineering:Programming_Events|'''series''']]. It is held in the summer at MIT (typically the last week of June), and a shorter version is held in Salt Lake City in the winter (typically the second week of January).  &lt;br /&gt;
The main goal of these events if to move forward the deliverables of NA-MIC. NA-MIC participants and their collaborators are welcome to attend.  &lt;br /&gt;
&lt;br /&gt;
* NA-MIC Members: Participation in this event is voluntary -- if you don't think this will help you move forward in your work, there is no obligation to attend.&lt;br /&gt;
* Ideal candidates are those who want to contribute to the [[NA-MIC-Kit|NA-MIC Kit]], and those who can help make it happen.&lt;br /&gt;
* This is not an introduction to the components of the [[NA-MIC-Kit|NA-MIC Kit]].&lt;br /&gt;
* NA-MIC Core 1 (Algorithms) - bring your algorithms and code to work on in the company of Core 2 engineers and Core 3 scientists.&lt;br /&gt;
* NA-MIC Core 2 (Engineering) - bring your code for infrastructure and applications to extend the [[NA-MIC-Kit|NA-MIC Kit]] capabilities, integrate Core 1 algorithms, and refine workflows for Core 3.&lt;br /&gt;
* NA-MIC Core 3 (DBP) - bring your data to work on with the [[NA-MIC-Kit|NA-MIC Kit]] and get assistance and provide feedback to Core 1 scientists and Core 2 engineers.&lt;br /&gt;
* External Collaborators - if you are working on a project that uses the [[NA-MIC-Kit|NA-MIC kit]], and want to participate to get help from NA-MIC Engineering, please send an email to Tina Kapur (tkapur at bwh.harvard.edu).  Please note that the event is open to people outside NA-MIC, subject to availability.&lt;br /&gt;
* Everyone should '''bring a laptop'''. We will have four projectors.&lt;br /&gt;
* About half the time will be spent working on projects and the other half in project related discussions.&lt;br /&gt;
* You '''do''' need to be actively working on a NA-MIC related project in order to make this investment worthwhile for everyone.&lt;br /&gt;
&lt;br /&gt;
== Agenda==&lt;br /&gt;
* Monday &lt;br /&gt;
** noon-1pm lunch &lt;br /&gt;
**1pm: Welcome (Ron Kikinis)&lt;br /&gt;
** 1:05-3:30pm Introduce [[#Projects|Projects]] using templated wiki pages (all Project Leads) ([[NA-MIC/Projects/Theme/Template|Wiki Template]]) &lt;br /&gt;
** 3:30-5:30pm Start project work&lt;br /&gt;
* Tuesday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 9:00-9:45am: NA-MIC Software Process &lt;br /&gt;
** 10-10:30am [[Project Week 2008 Slicer 3.0 Update|Slicer 3.0 Update]] (Jim Miller, Steve Pieper)&lt;br /&gt;
** 11-12noon [[Project Week 2008 Slicer Tuning| Performance tuning for Slicer 3.2]] (Ron Kikinis)&lt;br /&gt;
** noon lunch&lt;br /&gt;
** 2:30-3:30pm: [[Project Week 2008 Special topic breakout: XNAT Database]] (Daniel Marcus) &lt;br /&gt;
** TBD (Maybe on Tuesday or Wednesday) [[Project Week 2008 Special topic breakout: Non-rigid Registration]] (Stephen Aylward)&lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Wednesday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 9:00-12pm [[Project Week 2008 Special topic breakout: ITK]] (Luis Ibanez)&lt;br /&gt;
** noon lunch&lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Thursday&lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** noon lunch&lt;br /&gt;
**2:30-3:30pm [[Project Week 2008 Special topic breakout: GWE]] (Marco Ruiz)&lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Friday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 10am-noon: Project Progress using update [[#Projects|Project Wiki pages]]&lt;br /&gt;
** noon lunch boxes and adjourn.  (Next one [[AHM_2009| in Utah the week of Jan 5, 2009]])&lt;br /&gt;
&lt;br /&gt;
== Preparation ==&lt;br /&gt;
&lt;br /&gt;
# Please make sure that you are on the http://public.kitware.com/cgi-bin/mailman/listinfo/na-mic-project-week mailing list&lt;br /&gt;
&lt;br /&gt;
# [[Engineering:TCON_2008|May 08 and May 15 TCON DBPs ONLY]] at 3pm ET to discuss NA-MIC DBP Projects ONLY. &lt;br /&gt;
# [[Engineering:TCON_2008|May 22 TCON#1]] at 3pm ET to discuss NA-MIC Engr Core Projects and Assign/Verify Teams&lt;br /&gt;
# [[Engineering:TCON_2008|May 29 TCON#2]] at 3pm ET to discuss NA-MIC ALGORITHMS Core Lead Projects.  Project leads should sign up for a slot [[Engineering:TCON_2008|here]]. Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 5 TCON#3]] at 3pm ET to discuss NA-MIC EXTERNAL Collaborations.  All NIH funded &amp;quot;collaborations with NCBC&amp;quot; leads should call. Project leads should sign up for a slot [[Engineering:TCON_2008|here]].  Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 12 TCON#4]] at 3pm ET to discuss NA-MIC EXTERNAL Collaborations.  All other collaboration leads should call. Project leads should sign up for a slot [[Engineering:TCON_2008|here]].  Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 19 TCON#5]] at 3pm ET to tie loose ends.  Anyone with un-addressed questions should call.&lt;br /&gt;
# By 3pm ET on June 12, 2008: [[NA-MIC/Projects/Theme/Template|Complete a templated wiki page for your project]]. Please do not edit the template page itself, but create a new page for your project and cut-and-paste the text from this template page.  If you have questions, please send an email to tkapur at bwh.harvard.edu.&lt;br /&gt;
# By 3pm on June 19, 2008: Create a directory for each project on the [[Engineering:SandBox|NAMIC Sandbox]] (Zack)&lt;br /&gt;
## Commit on each sandbox directory the code examples/snippets that represent our first guesses of appropriate methods. (Luis and Steve will help with this, as needed)&lt;br /&gt;
## Gather test images in any of the Data sharing resources we have (e.g. the BIRN). These ones don't have to be many. At least three different cases, so we can get an idea of the modality-specific characteristics of these images. Put the IDs of these data sets on the wiki page. (the participants must do this.)&lt;br /&gt;
## Setup nightly tests on a separate Dashboard, where we will run the methods that we are experimenting with. The test should post result images and computation time. (Zack)&lt;br /&gt;
# Please note that by the time we get to the project event, we should be trying to close off a project milestone rather than starting to work on one...&lt;br /&gt;
&lt;br /&gt;
== A History in Wiki Links ==&lt;br /&gt;
&lt;br /&gt;
A history of all the programming/project events in NA-MIC is available by following [[Engineering:Programming_Events|this link]].&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
===DBP II===&lt;br /&gt;
These are projects by the new set of DBPS:&lt;br /&gt;
#[[DBP2:Harvard|Velocardio Facial Syndrome (VCFS) as a Genetic Model for Schizophrenia]] (Harvard: Marek Kubicki, PI)&lt;br /&gt;
##EPI-DWI Distortion correction (Sylvain Bouix BWH, Tauseef Rehman GATech)&lt;br /&gt;
##[[2008_Summer_Project_Week:EddyCurrentCorrection|EPI-DWI Eddy Current distortion correction]] (Sylvain Bouix BWH, Ran Tao Utah)&lt;br /&gt;
##Lobe Parcellation of 3T MR data - need help parametrization (Sylvain Bouix BWH, Priya Srinivasan BWH, Brad Davis Kitware)&lt;br /&gt;
##Finsler method (John Melonakos GATech, Marek Kubicki BWH)&lt;br /&gt;
##Group Analysis on DTI (Casey Goodlett Utah, Marek Kubicki BWH)&lt;br /&gt;
#[[DBP2:UNC|Longitudinal MRI Study of Early Brain Development in Autism]] (UNC: Heather Hazlett, Joseph Piven, PI)&lt;br /&gt;
##[[2008_Summer_Project_Week:RegionalCorticalThicknessTool|Work Flow Tool for regional cortical thickness pipeline]] (Clement Vachet UNC)&lt;br /&gt;
##[[2008_Summer_Project_Week:NITRCRegistration|NITRC registration of cortical thickness modules]] (Clement Vachet UNC)&lt;br /&gt;
##[[2008_Summer_Project_Week:DWI-DTI_PrepTools|DWI DTI Prep Tools]] (Zhexing Liu UNC) &lt;br /&gt;
#[[DBP2:MIND|Analysis of Brain Lesions in Lupus]] (MIND/UNM: Jeremy Bockholt, Charles Gasparovic PI)&lt;br /&gt;
##[[DBP2:MIND:RoadmapProject|Finish Roadmap Project]]&lt;br /&gt;
##[[DBP2:MIND:LongitudinalRegistrationProject|Longitudinal Registration]]&lt;br /&gt;
##[[DBP2:MIND:BeyondLesionsProject|Beyond Lesions]]&lt;br /&gt;
#[[DBP2:JHU|Segmentation and Registration Tools for Robotic Prostate Intervention]] (Queens/JHU: Gabor Fichtinger, PI)&lt;br /&gt;
##[[2008_Summer_Project_Week:TransRectal_Prostate_Biopsy_Module|Trans-Rectal Prostate Biopsy module]] (David Gobbi, Gabor Fichtinger, Queens/JHU)&lt;br /&gt;
##[[2008_Summer_Project_Week:ProstateSegReg|Prostate Segmentation and Registration]] (Yi Gao GATech, Gabor Fichtinger JHU)&lt;br /&gt;
##[[2008_Summer_Project_Week:PerkStation|Hardware/software overlay for percutaneous intervention (PERK Station)]] (Siddharth Vikal, Gabor Fichtinger, Queens/JHU)&lt;br /&gt;
&lt;br /&gt;
===Other Projects===&lt;br /&gt;
#[[2008_Summer_Project_Week:EddyCurrentCorrection|Eddy current and head motion correction of DWIs]] (Ran Tao, Utah, Sylvain Bouix, BWH, Xiaodong Tao, GE, Tom Fletcher, Utah)&lt;br /&gt;
#Integraton of groupwise b-spline registration into atlas building (Casey Goodlett, Serdar Balci)&lt;br /&gt;
# CVS / SVN auto synchronization&lt;br /&gt;
# [[2008_Summer_Project_Week:3DWidgetsInSlicer|3D Widgets in Slicer]] (Nicole Aucoin, Will Schroeder)&lt;br /&gt;
## Issues with existing widgets&lt;br /&gt;
## Design of new widgets&lt;br /&gt;
# Batch processing in the NAMIC Kit (Julien, Marco, Steve, Jim)&lt;br /&gt;
# Module Chaining (Marco, Jim, Steve, Dan B., Luca)&lt;br /&gt;
# Nonlinear transforms (Jim, Steve, Luis)&lt;br /&gt;
## TransformToWorld/TransformFromWorld, integration with slice viewing&lt;br /&gt;
# Slicer3, XNAT integration, and desigining XCEDE Web Services (Dan M., Steve, Julien, Dan B.)&lt;br /&gt;
## Review and enrich use cases&lt;br /&gt;
# Python in Slicer (Dan B., Michael Halle, Steve, Luca)&lt;br /&gt;
# [[2008_Summer_Project_Week:PerformanceTuningFiducials|Performance Tuning of Fiducials]] using the EventBroker and other tools (Nicole Aucoin, Alex Yarmarkovich, Steve Pieper, Will Schroeder)&lt;br /&gt;
# GUI Tweaking (Wendy, Sebastien) [http://www.na-mic.org/Bug/view.php?id=242]&lt;br /&gt;
# [[2008_Summer_Project_Week:fMRIconnectivity|fMRI connectivity]]  (Bryce Kim, MIT)&lt;br /&gt;
# [[2008_Summer_Project_Week:AtlasFreeSegmentation|Atlas free Segmentation]]  (Tammy Riklin-Raviv, MIT)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/EM Bias Field Correction | New Bias Field Correction in EM]] (Carlos Sánchez Mendoza, Kilian Pohl - SPL, Brad Davis - Kitware)&lt;br /&gt;
&lt;br /&gt;
===External Collaborations===&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/UWA-Perth]] (Adam Wittek)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/MRSI Module for Slicer]] (Bjoern Menze)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/NIREP: Non-rigid Image Registration Evaluation]] (Gary Christensen Group)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/Lung Atlas]] (Gary Christensen Group)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/Non-rigid image registration]] (Gary Christensen Group)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/SARP phantom]] (Keith Gunderson)&lt;br /&gt;
#FMA (Protege) links to Slicer (Vish, Mike, Florin, Jim, Steve, Wendy)&lt;br /&gt;
#[[NA-MIC/Projects/External Collaboration/Measuring Alcohol and Stress Interaction]]&lt;br /&gt;
#[[NA-MIC/Projects/External Collaboration/Slicer3-vmtk Integration]] (Luca Antiga, Dan Blezek, Mike Halle, Steve Piper)&lt;br /&gt;
#[[NA-MIC/Projects/External Collaboration/Mesh Generation Summer 2008]] (Iowa Group)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/Carto_scar_BIDMC]] (Dana Peters Group)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/3D Ultrasound Module in Slicer3]] (Junichi, Haiying and Noby - SPL, David - Queen's), Danielle - Robarts) )&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/MGH RadOnc]] (Greg Sharp, MGH)&lt;br /&gt;
&lt;br /&gt;
===Non-Medical Collaborations===&lt;br /&gt;
#[[NA-MIC/Projects/Non-Medical Collaborations/Astronomical Medicine|Astronomical Medicine]] (Harvard IIC: Douglas Alan, Michael Halle)&lt;br /&gt;
&lt;br /&gt;
==Attendee List==&lt;br /&gt;
# Ron Kikinis, BWH&lt;br /&gt;
# Carl-Fredrik Westin, BWH&lt;br /&gt;
# Gary Christensen, The University of Iowa&lt;br /&gt;
# Jeffrey Hawley, Gary Christensen's student&lt;br /&gt;
# Kate Raising, Gary Christensen's student&lt;br /&gt;
# Nathan Fritze, Gary Christensen's student&lt;br /&gt;
# Paul Song, Gary Christensen's student&lt;br /&gt;
# Cheng Zhang, Gary Christensen's student&lt;br /&gt;
# Ying Wei, Gary Christensen's student&lt;br /&gt;
# Nathan Burnette, The University of Iowa&lt;br /&gt;
# Hans Johnson, The University of Iowa&lt;br /&gt;
# Vincent Magnotta, The University of Iowa&lt;br /&gt;
# Keith Gunderson, The University of Iowa&lt;br /&gt;
# Steve Pieper, Isomics, Core 2/6&lt;br /&gt;
# Dana C. Peters, BIDMC Harvard Medical&lt;br /&gt;
# Jason Taclas, BIDMC Harvard Medical&lt;br /&gt;
# Nicole Aucoin, BWH, Core 2&lt;br /&gt;
# Will Schroeder, Kitware, Cores 2/4&lt;br /&gt;
# Sebastien Barre, Kitware, Core 2&lt;br /&gt;
# Julien Jomier, Kitware, Core 2&lt;br /&gt;
# Luis Ibanez, Kitware, Core 2&lt;br /&gt;
# Curtis Lisle, KnowledgeVis, Core 2&lt;br /&gt;
# Katie Hayes, BWH, Core 2&lt;br /&gt;
# Randy Gollub, MGH, Core 5&lt;br /&gt;
# Clement Vachet, UNC, Core 3&lt;br /&gt;
# Zhexing Liu, UNC, Core 1/3&lt;br /&gt;
# Casey Goodlett, Utah, Core 1&lt;br /&gt;
# Marcel Prastawa, Utah, Core 1&lt;br /&gt;
# Jeffrey Grethe, UCSD, Core 2&lt;br /&gt;
# Marco Ruiz, UCSD, Core 2&lt;br /&gt;
# Zhen Qian, Rutgers University&lt;br /&gt;
# Jinghao Zhou, Rutgers University&lt;br /&gt;
# Luca Antiga, Mario Negri Institute&lt;br /&gt;
# Adam Wittek, The University of Western Australia&lt;br /&gt;
# Grand Joldes, The University of Western Australia&lt;br /&gt;
# Jamie Berger, The University of Western Australia&lt;br /&gt;
# Serdar Balci, MIT, Core 1&lt;br /&gt;
# Bryce Kim, MIT, Core1&lt;br /&gt;
# Tina Kapur, BWH, Core 6&lt;br /&gt;
# Carling Cheung, Robarts Research Institute / The University of Western Ontario&lt;br /&gt;
# Danielle Pace, Robarts Research Institute / The University of Western Ontario&lt;br /&gt;
# Sean Megason, Dept of Systems Biology, Harvard Medical School&lt;br /&gt;
# Alex Gouaillard, Dept of Systems Biology, Harvard Medical School&lt;br /&gt;
# Kishore Mosaliganti, Dept of Systems Biology, Harvard Medical School&lt;br /&gt;
# Arnaud Gelas, Dept of Systems Biology, Harvard Medical School&lt;br /&gt;
# Sonia Pujol, Surgical Planning Laboratory, BWH&lt;br /&gt;
# Bjoern Menze, (then) Surgical Planning Laboratory, BWH&lt;br /&gt;
# Alex Yarmarkovich, Isomics, Core 2&lt;br /&gt;
# Sylvain Bouix, BWH, Core 3&lt;br /&gt;
# Priya Srinivasan, BWH, Core 3&lt;br /&gt;
# Chris Churas, UCSD, Core 2&lt;br /&gt;
# John Melonakos, Georgia Tech, Core 1&lt;br /&gt;
# Yi Gao, Georgia Tech, Core 1&lt;br /&gt;
# Tauseef Rehman, Georgia Tech, Core 1&lt;br /&gt;
# Clare Poynton, MIT, Core 1&lt;br /&gt;
# H. Jeremy Bockholt, MRN Lupus DBP Core 3&lt;br /&gt;
# Mark Scully, MRN Lupus DBP Core 3&lt;br /&gt;
# Gabor Fichtinger, Queen's, Core 3&lt;br /&gt;
# David Gobbi, Queen's, Core 3&lt;br /&gt;
# Purang Abolmaesumi, Queen's, Core 3, June 23-25&lt;br /&gt;
# Siddharth Vikal, Queen's, Core 3&lt;br /&gt;
# Daniel Blezek, Mayo&lt;br /&gt;
# Csaba Csoma, JHU, Core 3&lt;br /&gt;
# Ran Tao, University of Utah, Core 1&lt;br /&gt;
# Jim Miller, GE Research, Core 2&lt;br /&gt;
# Xiaodong Tao, GE Research, Core 2&lt;br /&gt;
# Dirk Padfield, GE Research, Core 2&lt;br /&gt;
# Viswanath Avasarala, GE Research, NAC&lt;br /&gt;
# Dan Marcus, Washington University  (Monday - Wednesday)&lt;br /&gt;
# Tim Olsen, Washington University   (Monday - Wednesday)&lt;br /&gt;
# Kevin Archie, Washington University   (Monday - Wednesday)&lt;br /&gt;
# Misha Milchenko, Washington University (Monday - Wednesday)&lt;br /&gt;
# Wendy Plesniak, BWH, Core 2&lt;br /&gt;
# Demian Wasserman, INRIA, LMI-collaborator&lt;br /&gt;
# Xenophon Papademetris, Yale, Collaborator&lt;br /&gt;
# Xenophon P's postdoc, Yale, Collaborator&lt;br /&gt;
# Xenophon P's student, Yale, Collaborator&lt;br /&gt;
# Vidya Rajagopalan, Virginia Tech, Student of Chris Wyatt, External Collaborator&lt;br /&gt;
# Greg Sharp, MGH, External Collaborator&lt;br /&gt;
# Marta Peroni, MGH, External Collaborator&lt;br /&gt;
# Toru Higaki, Hiroshima Univ., Japan, External collaborator (Hata)&lt;br /&gt;
# Jacek Kukluk, BWH,&lt;br /&gt;
# Nobuhiko Hata, BWH&lt;br /&gt;
# Junichi Tokuda, BWH&lt;br /&gt;
# Haying Liu, BWH&lt;br /&gt;
# Ragini Verma, UPenn (June 24)&lt;br /&gt;
# Luke Bloy, UPenn (Ragini Verma's student) (June 24)&lt;br /&gt;
# Yang Li, UPenn (Ragini's postdoc) (June 24)&lt;br /&gt;
# Jack Blevins, Acoustic Med, Collaborator&lt;br /&gt;
# Nikos Chrisochoides, College of William and Mary, External collaborator (June 23)&lt;br /&gt;
# Andriy Fedorov, College of William and Mary, External collaborator&lt;br /&gt;
# Carlos Sánchez Mendoza, BWH &lt;br /&gt;
# Kilian Pohl, BWH&lt;br /&gt;
# Pratik Patel, Brainlab, Collaborator&lt;br /&gt;
# Marianna Jakab, BWH&lt;br /&gt;
# Nathan Hageman, UCLA&lt;br /&gt;
# Douglas Alan, Harvard IIC, External Collaborator&lt;br /&gt;
# Tammy Riklin Raviv, MIT&lt;br /&gt;
# Peter Kazanzides, JHU, Collaborator (June 24)&lt;br /&gt;
# Scott Hoge, BWH, (Wed, Jun 25)&lt;br /&gt;
# Michael Halle, BWH&lt;br /&gt;
#*WE HAVE REACHED CAPACITY. REGISTRATION IS CLOSED. [[User:Tkapur|Tkapur]] 19:42, 6 June 2008 (UTC)&lt;br /&gt;
&lt;br /&gt;
==Pictures==&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=Engineering:TCON_2008&amp;diff=26744</id>
		<title>Engineering:TCON 2008</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=Engineering:TCON_2008&amp;diff=26744"/>
		<updated>2008-06-12T08:56:48Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* 2008-06-12 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[TCON:Main|TCON:Main]]&lt;br /&gt;
__NOTOC__&lt;br /&gt;
== Slicer 3 Dartboard ==&lt;br /&gt;
Link to the Slicer 3 Dartboard [http://www.na-mic.org/Dart/Slicer3/Dashboard/ here]&lt;br /&gt;
&lt;br /&gt;
==2008-06-19==&lt;br /&gt;
*Agenda: Project Week Prep Loose Ends&lt;br /&gt;
&lt;br /&gt;
==2008-06-12==&lt;br /&gt;
Agenda: Discuss NEW EXTERNAL Collaboration projects for project week&lt;br /&gt;
*3:00-3:15pm Rutgers (Jinghao)&lt;br /&gt;
*3:15-3:30pm UIowa (Gary Christensen)&lt;br /&gt;
*3:30-3:40pm W&amp;amp;M (Nikos Chrisochoides)&lt;br /&gt;
*3:40-3:45 Mario Negri Institute &amp;amp; Univ of Verona (Luca Antiga)&lt;br /&gt;
*3:45-3:50 Upenn (Ragini Verma from Christos Davatzikos' group, UPenn)&lt;br /&gt;
*3:50-4:00pm regular NAMIC engr business&lt;br /&gt;
&lt;br /&gt;
==2008-06-05==&lt;br /&gt;
Agenda: Discuss FUNDED EXTERNAL Collaboration projects for project week&lt;br /&gt;
*3:00-3:15pm Meshing Collaboration (Iowa)&lt;br /&gt;
*3:15-3:30pm RF Ablation Liver Collaboration (Georgetown)&lt;br /&gt;
*3:30-3:45pm Vervet EM Segmentation Collaboration (WFU/VT)&lt;br /&gt;
*3:45-4:00pm regular NAMIC engr business&lt;br /&gt;
**Mesh discussion requested by Core 1. Core 1 would like to start working with meshes seriously and would like to assess mesh infrastructure in ITK with Will Schroeder and Aylward. The goal is to figure out  what's there and what needs to be done to make meshes usable for algorithm development.  When can this discussion be held?&lt;br /&gt;
**95 project week participants signed up already.  No more room left. Please send checks in time for Donna to get them before Friday, June 13th.&lt;br /&gt;
** (Steve:) Any vista users who can test the slicer3.2 release candidates?  We have one test machine that cannot run it, but also reports from Sebastien that an earlier build (very similar) worked for him.&lt;br /&gt;
&lt;br /&gt;
Attendees: Brad, Ron, Steve, Katie, Vince, Jim, Tina, Nicole, Alex, Xiadong, Chris Wyatt, Dan Marcus, Marco, Kilian, Kevin Cleary.&lt;br /&gt;
&lt;br /&gt;
Highlights:&lt;br /&gt;
*Iowa mesh code will be checked in at Project Week by Curt.  It is built primarily in VTK.&lt;br /&gt;
*We will schedule mesh tcon with core 1 and relevant folks in Core 2 including vince, andrey fedorov.&lt;br /&gt;
*Georgetown - Ziv will attend project week on Wed/Thurs.  50 liver data sets that gp will consider making public using XNAT.&lt;br /&gt;
*Wakeforest/VT -&lt;br /&gt;
**Kilian and Vidya have been exchanging parameters for EM seg&lt;br /&gt;
**Kilian needs faster registration - Ron's suggestion to try AFFINE with less than 10s runtime for volumetric data (256 cube)&lt;br /&gt;
**Kilian will work during project week with Carlos to install van Leemput bias correction method into EM Segmentation.  Will need input from MIND team as well.&lt;br /&gt;
&lt;br /&gt;
==2008-05-29==&lt;br /&gt;
Agenda: Discuss ALGORITHM CORE lead projects for project week&lt;br /&gt;
*3:00-3:15pm &lt;br /&gt;
*3:15-3:30pm&lt;br /&gt;
*3:30-3:45pm&lt;br /&gt;
*3:45-4:00pm&lt;br /&gt;
* Status of Slicer 3.2: Steve Pieper et al.&lt;br /&gt;
** Status&lt;br /&gt;
** Bug squashing&lt;br /&gt;
&lt;br /&gt;
'''Attendees:''' Casey, Marcel, Will, Sebastien, Nathan, Nicole, Katie, Vincent, Alex Steve Jim M., Polina, Tina, Sonia, Tom, Ron, Dan M., Michael, John M., &lt;br /&gt;
&lt;br /&gt;
'''Notes:'''&lt;br /&gt;
&lt;br /&gt;
Core1 people go over projects listed on Summer Project Week page: MIT, Utah, GATech, UNC.&lt;br /&gt;
Polina (MIT) will work with on Brad Davis and Dan Marcus.&lt;br /&gt;
John (GATech) will need more core2 help on the optimal transport registration project... will add additional titles to the project week page.&lt;br /&gt;
&lt;br /&gt;
* Info: [http://wiki.na-mic.org/Wiki/index.php/Relative_Roles_Core1_Core2_Core3  Relative roles of Core 1, Core 2, Core 3]&lt;br /&gt;
&lt;br /&gt;
* Need chaining and workflow session at project week. Feedback from core1 - core 3 meeting: Chaining, batch processing strongly discussed at the meeting. Core1 and Core 2 should address these topics. &lt;br /&gt;
&lt;br /&gt;
* Tina wants a title for all projects on the project week page by end of day today.&lt;br /&gt;
&lt;br /&gt;
* Sonia is preparing for the Germany Training event. Made a munich2008 branch of Slicer3 subversion repository. Still fixing bugs on main trunk. Will create a release branch tomorrow end-of-day.&lt;br /&gt;
 &lt;br /&gt;
* Slicer3 release: developers should check mantis and squash as many bugs as possible in prep for release.&lt;br /&gt;
&lt;br /&gt;
* Ron's [http://www.slicer.org/slicerWiki/index.php/Announcements:Slicer3.2  press release ]&lt;br /&gt;
&lt;br /&gt;
* Steve encourages all to include impressive pix on the announcements page where people will be directed.&lt;br /&gt;
&lt;br /&gt;
* Request for a stable KWW target that Slicer can build against. --Sebastien will tag it.&lt;br /&gt;
&lt;br /&gt;
* Discussion of HelloWorld (Tutorial) and HelloSlicer (for testing)&lt;br /&gt;
&lt;br /&gt;
==2008-05-22==&lt;br /&gt;
[[Image:Slicer3Dashboard-5-20.png||thumb|right|Dashboard]]&lt;br /&gt;
Agenda:&lt;br /&gt;
* &amp;lt;big&amp;gt;'''A round of applause for Sebastian, Steve and all the code freezers'''&amp;lt;/big&amp;gt;&lt;br /&gt;
*http://www.slicer.org/slicerWiki/index.php/Announcements:Slicer3.2 documentation assignments and schedule for the 3.2 release:&lt;br /&gt;
**Outstanding issues in release&lt;br /&gt;
***EM Segment Wizard - Button Issues&lt;br /&gt;
***EM Segment Command line is in the wrong directory - should be put in bin&lt;br /&gt;
***EM Segment Template Builders&lt;br /&gt;
****First, second and 3rd steps do not work correctly - pull down list&lt;br /&gt;
****Possible issue with MRML manager changes&lt;br /&gt;
***Feature Request&lt;br /&gt;
****Can not changes the name of the parameters because it references the node ID and not the name&lt;br /&gt;
****EM Segment simple - images are specified by XML type file and not image - requires reloading and does not use images loaded within Slicer3&lt;br /&gt;
****Loading parameter set - Add a hierarchy of the nodes for better visualization of parameters&lt;br /&gt;
**registration, &lt;br /&gt;
**loadable modules, &lt;br /&gt;
**interactive editor, &lt;br /&gt;
**volume rendering&lt;br /&gt;
*New Slice Control Widget added by Wendy - last GUI based change&lt;br /&gt;
*Issues with Resize of Slicer and 3D Widgets&lt;br /&gt;
*Discuss Engineering Core Projects for the Project Week&lt;br /&gt;
*Discuss Jeremy's request to add Support Vector Machine library to NA-MIC Kit. http://www.csie.ntu.edu.tw/~cjlin/libsvm/&lt;br /&gt;
&lt;br /&gt;
Highlights:&lt;br /&gt;
*Attendees: Will, Sebastien, katie, tina, brad, steve, xiadong, vince, jim, nicole, dan marcus, Ron, Sonia.&lt;br /&gt;
&lt;br /&gt;
==2008-05-15==&lt;br /&gt;
Agenda:&lt;br /&gt;
*DBP II update and plans for project week.  2 DBPs and engr+algo core liaisons should attend.&lt;br /&gt;
**3-3:20 Harvard. Marek, Brad, Polina confirmed.&lt;br /&gt;
**3:20-3:40 UNC. Heather confirmed.  Jim, Martin, Heather, Clement held offline mtg already.&lt;br /&gt;
**3:40-4pm regular NAMIC engr business&lt;br /&gt;
***Slicer code freeze and release&lt;br /&gt;
***Focus during the upcoming months on &amp;quot;ruggedizing&amp;quot; Slicer&lt;br /&gt;
&lt;br /&gt;
Attendees: Tina, Katie, Nicole, Vince, Will, Marek, Sylvain, Polina, Clement, Brad, Ron, Alex, Sebastien&lt;br /&gt;
&lt;br /&gt;
Highlights:&lt;br /&gt;
*Harvard DBP projects for Project Week&lt;br /&gt;
*#Probabilistic Tractography - on hold since Tri left&lt;br /&gt;
*#Slicer3 - Need bug fix for why Slicer 3 can't load and run UNC data that Martin tried&lt;br /&gt;
*#EPI Distortion correction (Sylvain, Tauseef GATech)&lt;br /&gt;
*#Eddy CUrrent distortion correction (Sylvain, Ran Tao Utah)&lt;br /&gt;
*# Parcellation - need help parametrization (Sylvain, Brad)&lt;br /&gt;
*# fmri - apply polina's algorithm to Marek's data (Marek, Bryce Kim)&lt;br /&gt;
*# Finsler method (John Melonakos, Eric Melonakos)&lt;br /&gt;
*# Group Analysis on DTI (Casey Goodlett, Marek)&lt;br /&gt;
*Code Freeze: scheduled for tomorrow&lt;br /&gt;
*RSNA Demo&lt;br /&gt;
*#editor, lightbox, data fusion&lt;br /&gt;
*#Sonia is developing the curriculum for course&lt;br /&gt;
*UNC DBP Projects&lt;br /&gt;
*#Cortical thickness pipeline&lt;br /&gt;
*#workflow module&lt;br /&gt;
*#NITRC - need to talk to Steve pieper&lt;br /&gt;
*#batchmake pipeline in Slicer&lt;br /&gt;
*#use Bspline module in ITK&lt;br /&gt;
&lt;br /&gt;
==2008-05-08==&lt;br /&gt;
Agenda:&lt;br /&gt;
*DBP II update and plans for project week.  2 DBPs  and engr+algo core liaisons should attend.&lt;br /&gt;
**3:00-3:20 MIND. Jeremy, Ross, Steve Confirmed.&lt;br /&gt;
*** Testing lots of methods.  None working well.&lt;br /&gt;
*** Bayesian labeling seems to be working the best.&lt;br /&gt;
*** Close the look on itkEMS method&lt;br /&gt;
**3:20-3:40 JHU. David G, Allen T., Katie H. confirmed.&lt;br /&gt;
*** Prostate really difficult task&lt;br /&gt;
*** Delphine's work was originally on prostate.&lt;br /&gt;
*** Optimal mass transport registration project at project week&lt;br /&gt;
**3:40-4pm: regular na-mic engr core business&lt;br /&gt;
*** Short update on UNC DBP needs: registration, module chaining&lt;br /&gt;
*** Discussion on plans for chaining.  Prototype for project week?&lt;br /&gt;
&lt;br /&gt;
==2008-05-01==&lt;br /&gt;
&lt;br /&gt;
Attendees: Steve, Jim, Will, Tina, Xiaodong, Katie, Danielle, Sebastian, Sonia, &lt;br /&gt;
&lt;br /&gt;
* Slicer 3 stable release schedule planning (Slicer 3.2)&lt;br /&gt;
** We would like a stable version before the [[Events:June-Germany | Mid-June German training event]] that includes all the latest namic technology (CMake 2.6, ITK 3.6, VTK 5.2, Tcl/Tk 8.5, KWWidgets...).  Some problems were fixed this week for ITK3.6 and VTK 5.2; Slicer3 was successfully built using CMake 2.6 against VTK 5.2, ITK 3.6, and Tcl/TK on Linux, Windows, and Mac (by Sebastien). Need more coverage on Slicer. TODOs: Developing tutorial material for the new Slicer release. Testing, automated part plus user interaction part. &lt;br /&gt;
** [[2008_Summer_Project_Week | Project Week]] projects can go into the trunk after the release is branched. GUI changes to show &amp;quot;axial&amp;quot;, &amp;quot;sagittal&amp;quot;, &amp;quot;coronal&amp;quot; slices in the acquisition orientation.&lt;br /&gt;
** Proposed schedule:&lt;br /&gt;
*** May 16: Feature Freeze of the trunk followed by group debugging/testing &lt;br /&gt;
*** May 23: Create Release Branch for Slicer 3.2&lt;br /&gt;
*Danielle Pace @ Robarts Inst. joined NCIGT/SNR to develop [[LEGO_IGT_and_Medical_Robotics_Tutorial | Slicer IGT Tutorial]].&lt;br /&gt;
&lt;br /&gt;
==2008-04-24==&lt;br /&gt;
&lt;br /&gt;
Attendees: Steve, Katie, Nicole, Tina, Nathan, Jim, Vince, Brad, Louis, Marco&lt;br /&gt;
&lt;br /&gt;
Agenda&lt;br /&gt;
* Slicer3D Wikipedia page discussion.  Check it out [http://en.wikipedia.org/wiki/Slicer here].&lt;br /&gt;
** Need to tone it down a little so it sounds less like ad copy.&lt;br /&gt;
** Needs more pawprints on it from unique editors/authors for Wikipedia to keep it online.&lt;br /&gt;
&lt;br /&gt;
* Nathan&lt;br /&gt;
** Helical phantom available to LONI web service.&lt;br /&gt;
** Should we make the link available through Slicer or not?&lt;br /&gt;
&lt;br /&gt;
* Project pages need to be updated.&lt;br /&gt;
** Deadline: May 15th for NA-MIC, a week earlier is preferred&lt;br /&gt;
** [[2008_Annual_Scientific_Report | Progress report link]]&lt;br /&gt;
** Project week pages need to be linked off the progress report (indirectly)&lt;br /&gt;
&lt;br /&gt;
* Waiting for CMake and ITK releases to be finalized&lt;br /&gt;
** Probably will be cut tomorrow&lt;br /&gt;
&lt;br /&gt;
* Set up special T-con time for Oz&lt;br /&gt;
&lt;br /&gt;
* What's the deal with the CMake Policy Change warnings?&lt;br /&gt;
** Copy three lines before CMAKE_MINIMAL_REQUIRED&lt;br /&gt;
** Ask the CMake list&lt;br /&gt;
&lt;br /&gt;
==2008-04-17==&lt;br /&gt;
&lt;br /&gt;
Attendees: Jim, Dan Marcus, Xiaodong, Nicole, Tina, Steve, Katie, Jeff, Sebastien, Vince&lt;br /&gt;
&lt;br /&gt;
Topics:&lt;br /&gt;
&lt;br /&gt;
*[[2008_Annual_Scientific_Report]]&lt;br /&gt;
*[[2008_Summer_Project_Week]]&lt;br /&gt;
*VTK (5.2) and CMake (2.6) release schedules&lt;br /&gt;
**VTK Plan on branching next week&lt;br /&gt;
**CMake is on RC8, guessing will branch in 1-2 weeks&lt;br /&gt;
*VTK (5.2) performance issues when rendering&lt;br /&gt;
**In the meshing project we have seen a significant reduction in the rendering of a large number of vtkSphereSource and vtkPointWidgets in 5.2 as compared to 5.0&lt;br /&gt;
***100x performance hit in debug mode on Linux&lt;br /&gt;
***Jeff added code to make sure the check doesn't happen more than once/sec.&lt;br /&gt;
***Still 25% slower, but not 100x slower&lt;br /&gt;
**Rendering time has been increased by an order of magnitude&lt;br /&gt;
* OK for Kitware to put Slicer3 screenshots on Flickr? (see [http://flickr.com/photos/kitware/ Kitware's Flickr account])&lt;br /&gt;
** =&amp;gt; I (Seb) did a quick pass at the files uploaded in 2008, and copied them to a [http://flickr.com/photos/kitware/sets/72157604594177467/detail/ Slicer3 photoset].&lt;br /&gt;
&lt;br /&gt;
==2008-04-03==&lt;br /&gt;
&lt;br /&gt;
Jim, Curt, Tina, Nicole, Wendy, Steve, Brad, Xiaodong, Vince, Ron, Nathan&lt;br /&gt;
&lt;br /&gt;
Agenda&lt;br /&gt;
* discussion of xcede web services and mBIRN&lt;br /&gt;
* [[2008_Engineering_review_at_Utah:FollowUp]]&lt;br /&gt;
* New! [[Slicer3:DTMRI |glyphs on slices movie!]]&lt;br /&gt;
** made using wink from http://www.debugmode.com/wink/&lt;br /&gt;
** add something like the following to your wiki page after uploading the .swf file to the wiki&lt;br /&gt;
 &amp;lt;pre&amp;gt;&amp;lt;flash&amp;gt;file=dti_glyphs.swf|width=800|height=600|quality=best|loop=true|play=true&amp;lt;/flash&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
* CMake 2.6 release candidates have been cut with .rpm and .deb output targets!&lt;br /&gt;
** Will will work with Katie on this&lt;br /&gt;
* Jim is going to visit Kitware to talk about BSpline registration&lt;br /&gt;
&lt;br /&gt;
==2008-03-27==&lt;br /&gt;
Attendees: Steve, Will, Xiaodong, Nathan, Katie, Wendy, Tina, Nicole, Marco, Sebastien&lt;br /&gt;
* Nathan will discuss presentation of fluid mechanics projects.&lt;br /&gt;
* Update from Core 1 + Core 2 [[2008_Engineering_review_at_Utah | meetings in Utah]] earlier this week.&lt;br /&gt;
* [[Slicer3:Chain_CLMs | Discussion of Module Chaining]] (Marco and All)&lt;br /&gt;
** Requested by Core 1 to systematize common use case&lt;br /&gt;
** Need several steps in an analysis process to act like a single command&lt;br /&gt;
** Would like something akin to the EMSegment workflow wizard, but as command line module rather than built-in module&lt;br /&gt;
&lt;br /&gt;
Highlights:&lt;br /&gt;
&lt;br /&gt;
Nathan's overview: discussing visualization options for his fluid velocity vector fields for tractography algorithm. Steve mentions a few options: &lt;br /&gt;
* A LDDMM module in Slicer2 that does animated vector field visualization (work done in collaboration with Johns Hopkins: Anthony Kolasny, Mike Miller, et al.). &lt;br /&gt;
* Another option would be to try using ParaView as a way to flesh out specifics, and then build a more custom tool for tractography later. Will will point Nathan to documentation for file formats, data formats, etc. or help with any questions, and Nathan will try this out.&lt;br /&gt;
&lt;br /&gt;
Discussion of these topics at the engineering review in Utah:&lt;br /&gt;
&lt;br /&gt;
* chaining modules together&lt;br /&gt;
* grid wizard (Marco) for grid and batch computing&lt;br /&gt;
* Bspline registration&lt;br /&gt;
* setting up repositories for collecting slicer modules (as technology transition mechanism)&lt;br /&gt;
* how this will fit into the slicer build process&lt;br /&gt;
* diffusion weighted imaging, shape analysis, and segmentation&lt;br /&gt;
* dicom to nrrd converter...&lt;br /&gt;
&lt;br /&gt;
Milestones were set for April-end, Project week, and AHM.&lt;br /&gt;
&lt;br /&gt;
Module chaining discussion (see link above):&lt;br /&gt;
&lt;br /&gt;
* Java version as first goal -- eventually C++ implementation. &lt;br /&gt;
* Discussion about module discovery process and how will chained modules be packaged: (c++ stub programs? or &lt;br /&gt;
or discovery find chain-descriptor xml files? shell scripts? (cross-platform issues)...)&lt;br /&gt;
* Goal: By project week in June we would like to be able to chain modules developed by Core 1.&lt;br /&gt;
&lt;br /&gt;
Sebastien's update on module building: Wiki will be updated today with status. (link)&lt;br /&gt;
&lt;br /&gt;
==2008-03-20==&lt;br /&gt;
Attendees: Tina, Jim, Will, Wendy, Xiaodong, Nathan, Martin, Marco&lt;br /&gt;
* [[2008_Annual_Scientific_Report|Progress Report]] - read over the assignments. We will look for progress from June 1, 2007 to May 30, 2008.&lt;br /&gt;
* June 23-27 is the summer project week.  We will make first pass on projects in late April.&lt;br /&gt;
* Module discussion: Martin wanted to understand the state of module creation and usage within Slicer. Sebastien is working on modules that are built against an installed module. Terry is working on built-in modules for Slicer. Jim is working on modules using CMake in the NTRIC repository.&lt;br /&gt;
* Nathan- write a command line, Slicer module that is a wrapper to a web service. Nathan thinks he can get this done prior to the June AHM. We referred to Jim's presentation at the Utah SLC Core 1/Core 2 meeting.&lt;br /&gt;
* We will talk about grid wizard next week at SLC&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==2008-03-13==&lt;br /&gt;
Attendees: Jim, Nicole, Dan, Xiaodong, Vince, Sebastian, Alex, Curt, Steve, Will, Terry&lt;br /&gt;
* Update on [[Slicer3:Loadable_Modules |Loadable Modules]] project (Terry) and [[Slicer3:Build/Modules | CMake updates for module builds]] (Sebastien)&lt;br /&gt;
* [[2008_Engineering_review_at_Utah | Engineering trip to Utah]]&lt;br /&gt;
* We are starting to use Categories to bin our pages.  [[SuggestedCategories]] - suggestions?&lt;br /&gt;
&lt;br /&gt;
==2008-03-06==&lt;br /&gt;
Attendees: Steve, Jim, Katie, Nicole, Tina, Xiaodong, Marco, Ron&lt;br /&gt;
&lt;br /&gt;
Highlights:&lt;br /&gt;
*Slicer page on wikipedia - http://en.wikipedia.org/wiki/3DSlicer.  All engineering core members should visit this page and edit as needed.  ASAP.&lt;br /&gt;
*dicom to nrrd converter in progress.  Xiaodong working on it and expecting to complete in a few weeks.&lt;br /&gt;
* [[2008_Engineering_review_at_Utah|March 24-26 Meeting in Utah]]&lt;br /&gt;
&lt;br /&gt;
==2008-02-28==&lt;br /&gt;
&lt;br /&gt;
* Attendees: Jim, Steve, Wendy, Katie, Tina, Jeff, and Marco (Grid Wizard Guy)&lt;br /&gt;
* Discussion on time series analysis (viewer, scene markup). Initial viewer will be a general tool for comparing images.&lt;br /&gt;
* Avalanche of new features in [http://gridwizard.org/gwe/index.html grid wizard and GSlicer3]&lt;br /&gt;
** Proxy around Command Line Modules&lt;br /&gt;
** Extends command line with specifications for ranges of values as well as specify remote resources (data) that need to be transferred to/from the grid.&lt;br /&gt;
** Uses Velocity for parameter template engine&lt;br /&gt;
** Grid selection and authentication still being refined for Slicer&lt;br /&gt;
** Could be extended to other grid types (LSF, etc.)&lt;br /&gt;
** Lots of information on the website.  Instructions for installation.  A bit daunting for non-grid people.  Some of us will have to work through the instructions step by step to evaluate.&lt;br /&gt;
&lt;br /&gt;
==2008-02-21==&lt;br /&gt;
&lt;br /&gt;
* Attendees: Xiaodong, Jim, Katie, Nicole, Will, Steve, Nathan, Tina, Ron, Padma, Marco&lt;br /&gt;
&lt;br /&gt;
- Nathan brought us up to date on fluid mechanics tractography&lt;br /&gt;
&lt;br /&gt;
- Padma Sundaram: SCIrun environment supports EEG processing&lt;br /&gt;
&lt;br /&gt;
- Marco is releasing Grid Wizard alpha version&lt;br /&gt;
&lt;br /&gt;
- Nathan brought up the helical digital phantom web service. Currently the thinking is that it can be accessed through a web service. We suggested that Nathan write a wrapper, consistent with Slicer's execution module, to invoke the web service. However, since it is not available in source form, NAMIC cannot accept it as part of the NAMIC Kit proper. We can guide Nathan in the execution of this module.&lt;br /&gt;
&lt;br /&gt;
==2008-02-14==&lt;br /&gt;
* Attendees: Xiaodong, Katie, Will, Sebastien, Steve, Mike, Wendy, Haiyi, Dan, Curt, Tina &lt;br /&gt;
&lt;br /&gt;
=== Other NA-MIC Projects ===&lt;br /&gt;
&lt;br /&gt;
16 - CPack (Katie): Slicer3 compiles and packs using the new C-tools with some bug fixes. Using CMake to select desired modules, using something similar to cygwin. Official Slicer3 snapshot tagged. Different Tcl/Tk versions are currently used for different platform. This need to be addressed.&lt;br /&gt;
&lt;br /&gt;
17 - Slicer GUI Style Guide and Cookbook {Wendy}: This will be a long term effort. During the programming week, the design and implementation details were discussed. The Cookbook will be launched from Slicer, act like KWWidget tour.  &lt;br /&gt;
&lt;br /&gt;
18 - Volume rendering (Steve): UI is fairly stable.&lt;br /&gt;
 &lt;br /&gt;
19 - Volume rendering using Cuda (Steve):  &lt;br /&gt;
&lt;br /&gt;
20 - 3D W Widgets and Picking (Will): found a list of candidates of widgets for Slicer. A few bug fixes for VTK.&lt;br /&gt;
&lt;br /&gt;
21 - XNAT Integration (Dan): Requirements were gathered for a XNAT application that organizes files and caches files from XNAT repositories. Some XML format issues have been addressed.  &lt;br /&gt;
&lt;br /&gt;
22 - KWWidgets Roadmap (Sebastien): Gathered requirements. Been working down the list of the feature requirements.&lt;br /&gt;
&lt;br /&gt;
=== External Collaboration ===&lt;br /&gt;
&lt;br /&gt;
1 - Astronomical coordinate system support [Harvard IIC] (Mike): Astronomical datasets are quite different from medical dataset. Wendy helped with re-centering data. Made progress in converting between coordinate systems (Cartesian to Spherical).&lt;br /&gt;
&lt;br /&gt;
2 - New Meshing Techniques into NA-MIC [Univ. of Iowa]&lt;br /&gt;
 &lt;br /&gt;
3 - Meshing Workflow into Slicer [Univ. of Iowa] (Curt): Will be integrated into Slicer soon. Command line program using VTK. &lt;br /&gt;
 &lt;br /&gt;
4 - Evaluating NA-MIC Tools for Small Animal Imaging Workflows [NCI] (Curt): &lt;br /&gt;
 &lt;br /&gt;
5 - IGSTK-Slicer [Georgetown] (Haiyi): Successful tracking data using IGSTK.&lt;br /&gt;
&lt;br /&gt;
6 - Japanese Intelligent Surgical Instrument Project [AIST]&lt;br /&gt;
 &lt;br /&gt;
7 - GoFigure:High-Level Microscopy Image analysis Application and Algorithms [CalTech-Harvard Medical School] &lt;br /&gt;
&lt;br /&gt;
8 - Doing microscopy image analysis with Slicer3 [The Ohio State University] &lt;br /&gt;
&lt;br /&gt;
9 - fMRI Analysis with Slicer 3 [The Ohio State University]&lt;br /&gt;
&lt;br /&gt;
10 - Resampling DTIs with Slicer 3 [BWH]&lt;br /&gt;
 &lt;br /&gt;
11 - Analyzing fMRI and concurrent EEG with Slicer and SCIRun [BWH] &lt;br /&gt;
 &lt;br /&gt;
12 - Bayesian hierarchical models for fMRI variance components analysis [BWH]&lt;br /&gt;
&lt;br /&gt;
==2008-02-07==&lt;br /&gt;
* Attendees: Ron, Will, Steve, Wendy, Nicole, David G, Mark S., Casey, Sebastien, Curt, Luca&lt;br /&gt;
&lt;br /&gt;
* Look at [http://www.vtk.org/Wiki/VTK_Widget_Examples upcoming VTK 3D widgets]&lt;br /&gt;
* Review of projects from SLC AHM 2008 http://wiki.na-mic.org/Wiki/index.php/2008_Winter_Project_Week&lt;br /&gt;
&lt;br /&gt;
===DBPs===&lt;br /&gt;
&lt;br /&gt;
1 - Stochastic Tractography in Schizophrenia (need to be invited to follow-up TCon) &lt;br /&gt;
&lt;br /&gt;
2 - Cortical thickness analysis - testing EM segmenter to their data.  They estimated parameters and tested during the week.  The goal now is to compare ITK-MS and EM segment module to see how these two tools compare for cortical thickness.  They are reviewing the tools using the same patient data.  &lt;br /&gt;
&lt;br /&gt;
3 - (Mark Scully) Legion segmentation using EM segmenter and other options - worked with Brad using 2 channels of data.  Flare as 3rd channel caused problems.  Desired to have T1/T2/Flair together as three channel dataset.  Marcel is going to deliver his segmentation algorithm software to them to compare results. &lt;br /&gt;
&lt;br /&gt;
4 - Robotic Prostate Interventions - (David Gobbi) Working on transrectal biopsy module for Slicer.  They had a previous module for transcranial biopsies.  One of the most exciting developments was a new prototol &amp;quot;open IGT-Link&amp;quot; which will replace navitrack inside Slicer.  Image transfer is working over this protocol.  A simulator is being developed for the robot.  A few VTK bugs may have been discovered during this process, but it isn't on the top priority list right now. &lt;br /&gt;
&lt;br /&gt;
5 - Prostate Cancer - Wrote new ITK filter that has been submitted to the Sandbox.  They are looking at spherical wavelets for shape segmentation.  The wiki page will be updated soon.&lt;br /&gt;
&lt;br /&gt;
=== Other NA-MIC Projects ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1 - Groupwise Registration - (Casey) New Bspline registration method is being developed here.  It has been used for another project by Casey (#6).   Page needs to be updated. &lt;br /&gt;
&lt;br /&gt;
2 -  (Need to be invited to follow-up TCon)&lt;br /&gt;
&lt;br /&gt;
3 - (Need to be invited to follow-up TCon)) &lt;br /&gt;
&lt;br /&gt;
4 - (Need to be invited to follow-up TCon).  Page needs to be updated&lt;br /&gt;
&lt;br /&gt;
5 - Incorporating DTI tools into NAMIC toolkit - They are gathering a dataset that has both structural and DTI data in agreement.  Previous dataset was missing part of cortex.  UNCDB2 dataset has full coverage of the brain.  Resolution is a bit lower, but full coverage is an advantage.  Page is close to up to data.  Just submitted a paper to ISBI 2008 and working on MICCAI paper, as well.  &lt;br /&gt;
&lt;br /&gt;
* NITRIC is g-forge and would be a good place for automated build process for Slicer modules.  This could make it easier to configure Slicer in client labs without need to build from source. This is still being developed by the NA-MIC core team.  There is an entry on the collaboration section of the NA-MIC website.  Also www.slicer.org/Documentation link. &lt;br /&gt;
&lt;br /&gt;
6 - (Casey) Worked with Serdar using groupwise registration tool.  They are currently evaluating results of this study.  More images will be added.  &lt;br /&gt;
&lt;br /&gt;
7 - (John Melanakos) Spent last week working with collaborators on the MICCAI paper.  Project page is well filled. &lt;br /&gt;
&lt;br /&gt;
8 - (Need to be invited to follow-up TCon)&lt;br /&gt;
&lt;br /&gt;
9 - (Need to be invited to follow-up TCon)&lt;br /&gt;
&lt;br /&gt;
10 - MRML scenes for execution model.  Some of the issues Brad was having have been resolved.  Alex is making adjustments to MRML library as needed for the EM segmentation model. &lt;br /&gt;
&lt;br /&gt;
11  - (Curt) Unstructured Grids in Slicer - Finite Element modeling process was originally in a standalone VTK application.  The first Slicer module integration did not use MRML based storage.  We are now creating subclasses of Model and Unstructured grid data for storage and display in Slicer.  Some minor issues need to be worked out, but the MRML extensions for UnstructuredGrid datatypes are working. &lt;br /&gt;
&lt;br /&gt;
12 - Python (Luca) MatPlotLib plots are close to happening within Slicer.  Steve believes it is 80% complete.  Python command line modules are working now. Multiple arguments had to be worked by Luca.  He has developed Python-based CLI modules.   The event broker is discussed here because it affects the interaction with Python, because a Mutex lock has to be placed on the MRML scene.   Dan has been helping with metamodules - a single Python module which calls other mothers  (hierarchical execution, recipes, etc.).  &lt;br /&gt;
&lt;br /&gt;
* Ron asked about using this scripting technique for the ModelMaker.  Some of the parameter setting, etc. could be set in the top module.   Nicole will look at this.  Kilian said that he wanted to call the &amp;quot;modelmaker&amp;quot; from another module.  &lt;br /&gt;
&lt;br /&gt;
* A need was identified for new wiki pages:  (1) scripted modules, (2) metamodules, (2) python scripted modules&lt;br /&gt;
&lt;br /&gt;
13 - (Luca) Transform hardening - Sometimes images are not XYZ alligned.  How will command line modules treat an object if it is the child of a transform.  The module needs to be able to apply xforms to data (after hierarchy is flattened) to get xformed data.  Jim and Steve talked through this lately becomes of the transforms access two-directions (from parents / to parents, etc.)  They are looking at how to change the model. &lt;br /&gt;
&lt;br /&gt;
14 - (Steve) MRML support for out-of-core processing - Steve put a link to a new page.  Dan, Jim, Wendy, Steve, etc.  working through NAC renewal grant (5 years).  Multiresolution and asynchronous data are likely targets for this effort, but it will be a long-term effort.  &lt;br /&gt;
&lt;br /&gt;
15 - Event Broker discussion - Steve has made process on this, but this wiki page is older.  See the event broker page.  (look at link under Objective).  New term &amp;quot;observation&amp;quot; :  completely introspectable.  A full dependency between objects is implemented.  When a subject issues a &amp;quot;modified&amp;quot; event,  Delete events are maintained.  Complete &amp;quot;relationship&amp;quot; management of the interaction between objects.  This helps by allowing asynchronous event processing.  MRML has been converted to use the event broker with asynchronous events managed by the Slicer GUI (async events invoked after GUI events are done).  This hasn't broken anything so far, but should improve scalability.   Dot logfile format can be generated for inter-object dependencies.  This can be used to help provide &amp;quot;who called who&amp;quot; traces.    Some special magic is done in MRML Display nodes.  They set &amp;quot;observation nodes&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Next Week ===&lt;br /&gt;
Continue through project review.  Request missing project members to attend.  Review wiki pages.&lt;br /&gt;
&lt;br /&gt;
==2008-01-31==&lt;br /&gt;
Attendees: Jim, Steve, Stephen, Wendy, Xiaodong, Nicole, Katie, Ron&lt;br /&gt;
* Project week follow-up&lt;br /&gt;
** Half of tcon on Feb 7&lt;br /&gt;
** Half of tcon on Feb 14&lt;br /&gt;
* Registration&lt;br /&gt;
** Viola-Wells optimizations need to be enabled&lt;br /&gt;
** Stephen needs to check-in and publish recent changes&lt;br /&gt;
** Stephen needs to update the wiki&lt;br /&gt;
** Luis continues to make optimizations (main focus is memory reduction)&lt;br /&gt;
* BatchMake&lt;br /&gt;
** Grid Wizard - meeting on Monday&lt;br /&gt;
** Integration with Slicer delivered via getbuildtest2&lt;br /&gt;
* New webpages&lt;br /&gt;
** http://slicer.org&lt;br /&gt;
** Uses wiki-to-web&lt;br /&gt;
** Feel free to edit/improve&lt;br /&gt;
* Slicer-specific wiki&lt;br /&gt;
** Migrating appropriate info from Na-mic to slicer&lt;br /&gt;
** Hold off on adding to Slicer-wiki until notified&lt;br /&gt;
*** Continue using Na-mic wiki&lt;br /&gt;
* New Nitrc project&lt;br /&gt;
** Jim Miller is leading&lt;br /&gt;
** &amp;quot;Slicer3 plug-in examples&amp;quot; project&lt;br /&gt;
** http://nitrc.org - search for slicer3&lt;br /&gt;
*** Includes demo/stub for ITK filtering data, etc.&lt;br /&gt;
** Collection associated with an ITK course being taught&lt;br /&gt;
** Requires CVS version of ITK&lt;br /&gt;
** Works with Slicer build and Slicer install&lt;br /&gt;
** Steve P is the liaison with NITRC&lt;br /&gt;
* Slicer tutorial at UNC, April 14th&lt;br /&gt;
** Working with UNC's BRIC (http://www.bric.unc.edu)&lt;br /&gt;
** Sonja, Randy, Martin, Stephen&lt;br /&gt;
* User-level Slicer training - Feb 20 at BWH&lt;br /&gt;
** 1249 Boyleston&lt;br /&gt;
** Release version of Slicer3 &lt;br /&gt;
&lt;br /&gt;
==2008-01-24==&lt;br /&gt;
Attendees: Jim, Steve, Wendy, Xiaodong, Nicole, Katie, Alex, Luis, Ron, Will&lt;br /&gt;
* Project week follow-up (Next week?)&lt;br /&gt;
** Will will send email invitations for first half of projects for next week's tcon&lt;br /&gt;
* Loadable modules&lt;br /&gt;
** Alex and Terry are rearranging Slicer3.cxx to support loadable modules&lt;br /&gt;
** Separate branch for built-in module discovery process&lt;br /&gt;
** Sebastien is working on build issues for modules whose code is outside Slicer3&lt;br /&gt;
* GenerateCLP - Thanks Hans for changes to support building modules&lt;br /&gt;
** Hans is running a class this semester where the students will build Slicer CLI modules.&lt;br /&gt;
** Jim is working on an ExampleModule for people to use as a template for building modules outside of Slicer3.  Perhaps NITRC.&lt;br /&gt;
* XML library&lt;br /&gt;
** What to do with libaries that are too big to include in the source directory?&lt;br /&gt;
* AHM 2009, Jan 5-9, 2009&lt;br /&gt;
* Summer Project Week, Jun 23-27, 2008&lt;br /&gt;
* New server architecture for wiki, svn, publication database&lt;br /&gt;
&lt;br /&gt;
==2008-01-17==&lt;br /&gt;
Attendees: Jim, Katie, Sebastien, Stephen, Luis, Steve, Wendy, Will&lt;br /&gt;
&lt;br /&gt;
* Luis and Bill Hoffman are making progress in making ITK installation relocatable.  This is needed to finish the work on building plugins from an installation.&lt;br /&gt;
* What's in VTK 5.2?&lt;br /&gt;
** Infovis - Tables, Graphs, Views, IO&lt;br /&gt;
** Refinements to WWidgets. Client/Server connections within the widgets. Event translation. New widgets (text, caption, affine, checkerboard, rectilinear wipe, annotation, key frame, contour, measurement, point/placer, plot)&lt;br /&gt;
** Build now? Or wait until 5.2 released?&lt;br /&gt;
** Repository freeze in March&lt;br /&gt;
** Release on April 1, 2008&lt;br /&gt;
* ITK release&lt;br /&gt;
** Patches to ITK 3.4&lt;br /&gt;
*** Nine component/six component tensor conversion in IO has been patched to ITK 3.4&lt;br /&gt;
** 1/19-2/1 moving contributions on Insight Journal for ITK 3.6&lt;br /&gt;
** Move items from Review directory to main tree (QuadMesh, TransformIO) for ITK 3.6&lt;br /&gt;
** Freeze repository 2/29 for ITK 3.6&lt;br /&gt;
** Slicer3 will need to build against the Review directory.&lt;br /&gt;
* CMake release&lt;br /&gt;
** Version 2.6 on the horizon - release candidate in 3 weeks.&lt;br /&gt;
* Tcl/Tk 8.5&lt;br /&gt;
** Sebastien has a Windows build&lt;br /&gt;
** Steve will try it out&lt;br /&gt;
** Wait to switch to 8.5 until we have a good reason&lt;br /&gt;
* Loadable modules&lt;br /&gt;
** Sebastien - working on CMake issues on building modules as loadable modules&lt;br /&gt;
** Terry - working on loading modules and reworking Slicer3.cxx&lt;br /&gt;
* [[Slicer3:EventBroker | Event Broker]]&lt;br /&gt;
* DWI DICOM as part of the Load Volume.  Xiaodong is working on it.&lt;br /&gt;
* ITKFactories directory in build and installs to hold ImageIO plugin libraries. Should increase the speed of executable plugins on the Mac.&lt;br /&gt;
* OpenIGTLink&lt;br /&gt;
** Protocol on the wiki (message format)&lt;br /&gt;
** Put code in Sandbox, SourceForge, NITRC, Google Code???&lt;br /&gt;
* Will schedule a time to go over the Project Week results&lt;br /&gt;
&lt;br /&gt;
==2008-01-10==&lt;br /&gt;
No tcon due to AHM&lt;br /&gt;
&lt;br /&gt;
==2008-01-03==&lt;br /&gt;
* Attendees: Jim, Steve, Will, Brad Davis&lt;br /&gt;
* Topics:&lt;br /&gt;
** Jim and Will talked about leading the Monday and Friday sessions, and who would do what.&lt;br /&gt;
** We are going to send out reminders to the project leads to ensure that their project descriptions are up to date&lt;br /&gt;
** We discussed the software process project to make sure that we have a chance to address the Slicer build process, dashboards, etc.&lt;br /&gt;
** We decided not to hold the project wrap-up presentation at AHM; we will do that later at subsequent TCons. (We decided that we needed the time to actually work. We are concerned that we are starting to see too many break-outs and not enough time to work.)&lt;br /&gt;
** We keenly missed Tina and hope that she and her family are doing well.&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2008_Summer_Project_Week&amp;diff=26343</id>
		<title>2008 Summer Project Week</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2008_Summer_Project_Week&amp;diff=26343"/>
		<updated>2008-06-03T12:41:40Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* NA-MIC Kit - Slicer 3 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[Engineering:Programming_Events|Programming/Project Events]]&lt;br /&gt;
&lt;br /&gt;
[[Image:ProjectWeek-2008.png|thumb|220px|right|Summer 2008]]&lt;br /&gt;
&lt;br /&gt;
== Logistics ==&lt;br /&gt;
&lt;br /&gt;
'''Dates:''' June 23-27, 2008&lt;br /&gt;
&lt;br /&gt;
'''Location:''' MIT. [[Meeting_Locations:MIT_Grier_A_%26B|Grier Rooms A &amp;amp; B: 34-401A &amp;amp; 34-401B]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Registration Fee:''' $260 (this will cover the cost of breakfast, lunch and coffee breaks for the week). Due by Friday, June 13th, 2008. Please make checks out to &amp;quot;Massachusetts Institute of Technology&amp;quot; and mail to: Donna Kaufman, MIT, 77 Massachusetts Ave., 38-409a, Cambridge, MA 02139&lt;br /&gt;
&lt;br /&gt;
'''Registration Method''' Please add your name to the attendee list below (create namic wiki account if you don't have one, by clicking on the &amp;quot;login/create account&amp;quot; link on the top right corner of this page), and then mail a check to Donna Kaufman at the address above.&lt;br /&gt;
&lt;br /&gt;
If you are attending for one day only, the registration fee is not required.&lt;br /&gt;
&lt;br /&gt;
'''Hotel:''' We have a group rate of $239/night (plus tax) for a room with either 1 king or 2 queen beds at the [http://www.hotelatmit.com Hotel at MIT (now called Le Meridien)]. [http://www.starwoodmeeting.com/StarGroupsWeb/booking/reservation?id=0805167317&amp;amp;key=4FD1B  Please click here to reserve.]This rate is good only through June 1.&lt;br /&gt;
&lt;br /&gt;
Here is some information about several other Boston area hotels that are convenient to NA-MIC events: [[Boston_Hotels|Boston_Hotels]]. Summer is tourist season in Boston, so please book your rooms early.&lt;br /&gt;
&lt;br /&gt;
([[Project Week Logistics Checklist|This is a checklist for the onsite planning items]])&lt;br /&gt;
&lt;br /&gt;
==Introduction to NA-MIC Project Week==&lt;br /&gt;
&lt;br /&gt;
NA-MIC Project Week is a hands on activity -- programming using the [[NA-MIC-Kit|NA-MIC Kit]], algorithm design, and clinical application -- that has become one of the major events in the [[NA-MIC-Kit|NA-MIC Kit]] calendar. This event is the seventh of the [[Engineering:Programming_Events|'''series''']]. It is held in the summer at MIT (typically the last week of June), and a shorter version is held in Salt Lake City in the winter (typically the second week of January).  &lt;br /&gt;
The main goal of these events if to move forward the deliverables of NA-MIC. NA-MIC participants and their collaborators are welcome to attend.  &lt;br /&gt;
&lt;br /&gt;
* NA-MIC Members: Participation in this event is voluntary -- if you don't think this will help you move forward in your work, there is no obligation to attend.&lt;br /&gt;
* Ideal candidates are those who want to contribute to the [[NA-MIC-Kit|NA-MIC Kit]], and those who can help make it happen.&lt;br /&gt;
* This is not an introduction to the components of the [[NA-MIC-Kit|NA-MIC Kit]].&lt;br /&gt;
* NA-MIC Core 1 (Algorithms) - bring your algorithms and code to work on in the company of Core 2 engineers and Core 3 scientists.&lt;br /&gt;
* NA-MIC Core 2 (Engineering) - bring your code for infrastructure and applications to extend the [[NA-MIC-Kit|NA-MIC Kit]] capabilities, integrate Core 1 algorithms, and refine workflows for Core 3.&lt;br /&gt;
* NA-MIC Core 3 (DBP) - bring your data to work on with the [[NA-MIC-Kit|NA-MIC Kit]] and get assistance and provide feedback to Core 1 scientists and Core 2 engineers.&lt;br /&gt;
* External Collaborators - if you are working on a project that uses the [[NA-MIC-Kit|NA-MIC kit]], and want to participate to get help from NA-MIC Engineering, please send an email to Tina Kapur (tkapur at bwh.harvard.edu).  Please note that the event is open to people outside NA-MIC, subject to availability.&lt;br /&gt;
* Everyone should '''bring a laptop'''. We will have four projectors.&lt;br /&gt;
* About half the time will be spent working on projects and the other half in project related discussions.&lt;br /&gt;
* You '''do''' need to be actively working on a NA-MIC related project in order to make this investment worthwhile for everyone.&lt;br /&gt;
&lt;br /&gt;
== Agenda==&lt;br /&gt;
* Monday &lt;br /&gt;
** noon-1pm lunch &lt;br /&gt;
**1pm: Welcome (Ron Kikinis)&lt;br /&gt;
** 1:05-3:30pm Introduce [[#Projects|Projects]] using templated wiki pages (all Project Leads) ([[NA-MIC/Projects/Theme/Template|Wiki Template]]) &lt;br /&gt;
** 3:30-5:30pm Start project work&lt;br /&gt;
* Tuesday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 9:00-9:45am: NA-MIC Software Process &lt;br /&gt;
** 10-10:30am [[Project Week 2008 Slicer 3.0 Update|Slicer 3.0 Update]] (Jim Miller, Steve Pieper)&lt;br /&gt;
** noon lunch&lt;br /&gt;
** 2:30-3:30pm: [[Project Week 2008 Special topic breakout: Non-Linear Registration]] &lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Wednesday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 9:00-12pm [[Project Week 2008 Special topic breakout: ITK]] (Luis Ibanez)&lt;br /&gt;
** noon lunch&lt;br /&gt;
** 2:30-3:30pm: [[Project Week 2008 Special topic breakout: XNAT Database]] (Daniel Marcus)&lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Thursday&lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** noon lunch&lt;br /&gt;
**2:30-3:30pm [[Project Week 2008 Special topic breakout: GWE]] (Marco Ruiz)&lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Friday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 10am-noon: Project Progress using update [[#Projects|Project Wiki pages]]&lt;br /&gt;
** noon lunch boxes and adjourn.  (Next one [[AHM_2009| in Utah the week of Jan 5, 2009]])&lt;br /&gt;
&lt;br /&gt;
== Preparation ==&lt;br /&gt;
&lt;br /&gt;
# Please make sure that you are on the http://public.kitware.com/cgi-bin/mailman/listinfo/na-mic-project-week mailing list&lt;br /&gt;
&lt;br /&gt;
# [[Engineering:TCON_2008|May 08 and May 15 TCON DBPs ONLY]] at 3pm ET to discuss NA-MIC DBP Projects ONLY. &lt;br /&gt;
# [[Engineering:TCON_2008|May 22 TCON#1]] at 3pm ET to discuss NA-MIC Engr Core Projects and Assign/Verify Teams&lt;br /&gt;
# [[Engineering:TCON_2008|May 29 TCON#2]] at 3pm ET to discuss NA-MIC ALGORITHMS Core Lead Projects.  Project leads should sign up for a slot [[Engineering:TCON_2008|here]]. Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 5 TCON#3]] at 3pm ET to discuss NA-MIC EXTERNAL Collaborations.  All NIH funded &amp;quot;collaborations with NCBC&amp;quot; leads should call. Project leads should sign up for a slot [[Engineering:TCON_2008|here]].  Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 12 TCON#4]] at 3pm ET to discuss NA-MIC EXTERNAL Collaborations.  All other collaboration leads should call. Project leads should sign up for a slot [[Engineering:TCON_2008|here]].  Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 19 TCON#5]] at 3pm ET to tie loose ends.  Anyone with un-addressed questions should call.&lt;br /&gt;
# By 3pm ET on June 12, 2008: [[NA-MIC/Projects/Theme/Template|Complete a templated wiki page for your project]]. Please do not edit the template page itself, but create a new page for your project and cut-and-paste the text from this template page.  If you have questions, please send an email to tkapur at bwh.harvard.edu.&lt;br /&gt;
# By 3pm on June 19, 2008: Create a directory for each project on the [[Engineering:SandBox|NAMIC Sandbox]] (Zack)&lt;br /&gt;
## Commit on each sandbox directory the code examples/snippets that represent our first guesses of appropriate methods. (Luis and Steve will help with this, as needed)&lt;br /&gt;
## Gather test images in any of the Data sharing resources we have (e.g. the BIRN). These ones don't have to be many. At least three different cases, so we can get an idea of the modality-specific characteristics of these images. Put the IDs of these data sets on the wiki page. (the participants must do this.)&lt;br /&gt;
## Setup nightly tests on a separate Dashboard, where we will run the methods that we are experimenting with. The test should post result images and computation time. (Zack)&lt;br /&gt;
# Please note that by the time we get to the project event, we should be trying to close off a project milestone rather than starting to work on one...&lt;br /&gt;
&lt;br /&gt;
== A History in Wiki Links ==&lt;br /&gt;
&lt;br /&gt;
A history of all the programming/project events in NA-MIC is available by following [[Engineering:Programming_Events|this link]].&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
===DBP II===&lt;br /&gt;
These are projects by the new set of DBPS:&lt;br /&gt;
#[[DBP2:Harvard|Velocardio Facial Syndrome (VCFS) as a Genetic Model for Schizophrenia]] (Harvard: Marek Kubicki, PI)&lt;br /&gt;
##EPI-DWI Distortion correction (Sylvain Bouix BWH, Tauseef Rehman GATech)&lt;br /&gt;
##[[2008_Summer_Project_Week:EddyCurrentCorrection|EPI-DWI Eddy Current distortion correction]] (Sylvain Bouix BWH, Ran Tao Utah)&lt;br /&gt;
##Lobe Parcellation of 3T MR data - need help parametrization (Sylvain Bouix BWH, Priya Srinivasan BWH, Brad Davis Kitware)&lt;br /&gt;
##Finsler method (John Melonakos GATech, Marek Kubicki BWH)&lt;br /&gt;
##Group Analysis on DTI (Casey Goodlett Utah, Marek Kubicki BWH)&lt;br /&gt;
#[[DBP2:UNC|Longitudinal MRI Study of Early Brain Development in Autism]] (UNC: Heather Hazlett, Joseph Piven, PI)&lt;br /&gt;
##Work Flow Tool for regional cortical thickness pipeline (Clement Vachet UNC)&lt;br /&gt;
##NITRC registration of cortical thickness modules (Clement Vachet UNC)&lt;br /&gt;
##DTI tools for a) DWI preparation and b) DTI atlas building (Zhexing Liu UNC) &lt;br /&gt;
#[[DBP2:MIND|Analysis of Brain Lesions in Lupus]] (MIND/UNM: Jeremy Bockholt, Charles Gasparovic PI)&lt;br /&gt;
##[[DBP2:MIND:RoadmapProject|Finish Roadmap Project]]&lt;br /&gt;
##[[DBP2:MIND:LongitudinalRegistrationProject|Longitudinal Registration]]&lt;br /&gt;
##[[DBP2:MIND:BeyondLesionsProject|Beyond Lesions]]&lt;br /&gt;
#[[DBP2:JHU|Segmentation and Registration Tools for Robotic Prostate Intervention]] (Queens/JHU: Gabor Fichtinger, PI)&lt;br /&gt;
##[[Projects:ProstateSegmentation|Prostate Segmentation and Registration (Yi Gao GATech, Gabor Fichtinger JHU)]]&lt;br /&gt;
&lt;br /&gt;
===Structural Analysis===&lt;br /&gt;
&lt;br /&gt;
===Diffusion Image Analysis===&lt;br /&gt;
#[[2008_Summer_Project_Week:EddyCurrentCorrection|Eddy current and head motion correction of DWIs]] (Ran Tao, Utah, Sylvain Bouix, BWH, Xiaodong Tao, GE, Tom Fletcher, Utah)&lt;br /&gt;
#Integraton of groupwise b-spline registration into atlas building (Casey Goodlett, Serdar Balci)&lt;br /&gt;
&lt;br /&gt;
===Calibration/Validation===&lt;br /&gt;
&lt;br /&gt;
===NA-MIC Kit - Slicer 3===&lt;br /&gt;
# CVS / SVN auto synchronization&lt;br /&gt;
# 3D Widgets in Slicer&lt;br /&gt;
## Issues with existing widgets&lt;br /&gt;
## Design of new widgets&lt;br /&gt;
# Batch processing in the NAMIC Kit (Julien, Marco, Steve, Jim)&lt;br /&gt;
# Module Chaining (Marco, Jim, Steve, Dan B., Luca)&lt;br /&gt;
# Nonlinear transforms (Jim, Steve, Luis)&lt;br /&gt;
## TransformToWorld/TransformFromWorld, integration with slice viewing&lt;br /&gt;
# Slicer3, XNAT integration, and desigining XCEDE Web Services (Dan M., Steve, Julien)&lt;br /&gt;
## Review and enrich use cases&lt;br /&gt;
# Python in Slicer (Dan B., Michael Halle, Steve, Luca)&lt;br /&gt;
&lt;br /&gt;
===External Collaborations===&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/UWA-Perth]] (Adam Wittek)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/MRSI Module for Slicer]] (Bjoern Menze)&lt;br /&gt;
#NIREP: Non-rigid Image Registration Evaluation (Gary Christensen Group)&lt;br /&gt;
#Lung Atlas (Gary Christensen Group)&lt;br /&gt;
#Non-rigid image registration (Gary Christensen Group)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/SARP phantom]] (Keith Gunderson)&lt;br /&gt;
#FMA (Protege) links to Slicer (Vish, Mike, Florin, Jim, Steve, Wendy)&lt;br /&gt;
#[[NA-MIC/Projects/External Collaboration/Measuring Alcohol and Stress Interaction]]&lt;br /&gt;
#[[NA-MIC/Projects/External Collaboration/Slicer3-vmtk Integration]] (Luca Antiga)&lt;br /&gt;
&lt;br /&gt;
===Non-Medical Collaborations===&lt;br /&gt;
&lt;br /&gt;
==Attendee List==&lt;br /&gt;
# Ron Kikinis, BWH&lt;br /&gt;
# Carl-Fredrik Westin, BWH&lt;br /&gt;
# Gary Christensen, The University of Iowa&lt;br /&gt;
# Jeffrey Hawley, Gary Christensen's student&lt;br /&gt;
# Kate Raising, Gary Christensen's student&lt;br /&gt;
# Nathan Fritze, Gary Christensen's student&lt;br /&gt;
# Paul Song, Gary Christensen's student&lt;br /&gt;
# Cheng Zhang, Gary Christensen's student&lt;br /&gt;
# Ying Wei, Gary Christensen's student&lt;br /&gt;
# Nathan Burnette, The University of Iowa&lt;br /&gt;
# Hans Johnson, The University of Iowa&lt;br /&gt;
# Vincent Magnotta, The University of Iowa&lt;br /&gt;
# Keith Gunderson, The University of Iowa&lt;br /&gt;
# Steve Pieper, Isomics, Core 2/6&lt;br /&gt;
# Dana C. Peters, BIDMC Harvard Medical&lt;br /&gt;
# Jason Taclas, BIDMC Harvard Medical&lt;br /&gt;
# Nicole Aucoin, BWH, Core 2&lt;br /&gt;
# Will Schroeder, Kitware, Cores 2/4&lt;br /&gt;
# Sebastien Barre, Kitware, Core 2&lt;br /&gt;
# Julien Jomier, Kitware, Core 2&lt;br /&gt;
# Luis Ibanez, Kitware, Core 2&lt;br /&gt;
# Curtis Lisle, KnowledgeVis, Core 2&lt;br /&gt;
# Katie Hayes, BWH, Core 2&lt;br /&gt;
# Randy Gollub, MGH, Core 5&lt;br /&gt;
# Clement Vachet, UNC, Core 3&lt;br /&gt;
# Zhexing Liu, UNC, Core 1/3&lt;br /&gt;
# Casey Goodlett, Utah, Core 1&lt;br /&gt;
# Marcel Prastawa, Utah, Core 1&lt;br /&gt;
# Jeffrey Grethe, UCSD, Core 2&lt;br /&gt;
# Marco Ruiz, UCSD, Core 2&lt;br /&gt;
# Zhen Qian, Rutgers University&lt;br /&gt;
# Jinghao Zhou, Rutgers University&lt;br /&gt;
# Luca Antiga, Mario Negri Institute&lt;br /&gt;
# Adam Wittek, The University of Western Australia&lt;br /&gt;
# Grand Joldes, The University of Western Australia&lt;br /&gt;
# Jamie Berger, The University of Western Australia&lt;br /&gt;
# Serdar Balci, MIT, Core 1&lt;br /&gt;
# Bryce Kim, MIT, Core1&lt;br /&gt;
# Tina Kapur, BWH, Core 6&lt;br /&gt;
# Carling Cheung, Robarts Research Institute / The University of Western Ontario&lt;br /&gt;
# Danielle Pace, Robarts Research Institute / The University of Western Ontario&lt;br /&gt;
# Sean Megason, Dept of Systems Biology, Harvard Medical School&lt;br /&gt;
# Alex Gouaillard, Dept of Systems Biology, Harvard Medical School&lt;br /&gt;
# Kishore Mosaliganti, Dept of Systems Biology, Harvard Medical School&lt;br /&gt;
# Arnaud Gelas, Dept of Systems Biology, Harvard Medical School&lt;br /&gt;
# Sonia Pujol, Surgical Planning Laboratory, BWH&lt;br /&gt;
# Bjoern Menze, (then) Surgical Planning Laboratory, BWH&lt;br /&gt;
# Alex Yarmarkovich, Isomics, Core 2&lt;br /&gt;
# Sylvain Bouix, BWH, Core 3&lt;br /&gt;
# Priya Srinivasan, BWH, Core 3&lt;br /&gt;
# Chris Churas, UCSD, Core 2&lt;br /&gt;
# John Melonakos, Georgia Tech, Core 1&lt;br /&gt;
# Yi Gao, Georgia Tech, Core 1&lt;br /&gt;
# Tauseef Rehman, Georgia Tech, Core 1&lt;br /&gt;
# Clare Poynton, MIT, Core 1&lt;br /&gt;
# H. Jeremy Bockholt, MRN Lupus DBP Core 3&lt;br /&gt;
# Mark Scully, MRN Lupus DBP Core 3&lt;br /&gt;
# Gabor Fichtinger, Queen's, Core 2&lt;br /&gt;
# David Gobbi, Queen's, Core 2&lt;br /&gt;
# Purang Abolmaesumi, Queen's, Core 2&lt;br /&gt;
# Siddharth Vikal, Queen's, Core 2&lt;br /&gt;
# Daniel Blezek, Mayo&lt;br /&gt;
# Csaba Csoma, JHU, Core 2&lt;br /&gt;
# Ran Tao, University of Utah, Core 1&lt;br /&gt;
# Jim Miller, GE Research, Core 2&lt;br /&gt;
# Xiaodong Tao, GE Research, Core 2&lt;br /&gt;
# Dirk Padfield, GE Research, Core 2&lt;br /&gt;
# Viswanath Avasarala, GE Research, NAC&lt;br /&gt;
# Dan Marcus, Washington University   &lt;br /&gt;
# Tim Olsen, Washington University   &lt;br /&gt;
# Kevin Archie, Washington University   &lt;br /&gt;
# Misha Milchenko, Washington University&lt;br /&gt;
# Wendy Plesniak, BWH, Core 2&lt;br /&gt;
# Demian Wasserman, INRIA, LMI-collaborator&lt;br /&gt;
#Xenophon Papademetris, Yale, Collaborator&lt;br /&gt;
#Xenophon P's postdoc, Yale, Collaborator&lt;br /&gt;
#Xenophon P's student, Yale, Collaborator&lt;br /&gt;
#Vidya Rajagopalan, Virginia Tech, Student of Chris Wyatt, External Collaborator&lt;br /&gt;
# Greg Sharp, MGH, External Collaborator&lt;br /&gt;
# Marta Peroni, MGH, External Collaborator&lt;br /&gt;
#Toru Higaki, Hiroshima Univ., Japan, External collaborator (Hata)&lt;br /&gt;
#Jacek Kukluk, BWH,&lt;br /&gt;
#Nobuhiko Hata, BWH&lt;br /&gt;
#Junichi Tokuda, BWH&lt;br /&gt;
#Haying Liu, BWH&lt;br /&gt;
#Ragini Verma, UPenn (June 24)&lt;br /&gt;
#Luke Bloy, UPenn (Ragini Verma's student) (June 24)&lt;br /&gt;
#Yang Li, UPenn (Ragini's postdoc) (June 24)&lt;br /&gt;
#Jack Blevins, Acoustic Med, Collaborator&lt;br /&gt;
&lt;br /&gt;
==Pictures==&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=NA-MIC/Projects/External_Collaboration/Slicer3-vmtk_Integration&amp;diff=26338</id>
		<title>NA-MIC/Projects/External Collaboration/Slicer3-vmtk Integration</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=NA-MIC/Projects/External_Collaboration/Slicer3-vmtk_Integration&amp;diff=26338"/>
		<updated>2008-06-03T10:52:18Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: New page: {| |Project Week Main Page ]] |Vmtk working inside Slicer3. |}   ...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|&lt;br /&gt;
|[[Image:ProjectWeek-2008.png|thumb|320px|Return to [[2008_Summer_Project_Week|Project Week Main Page]] ]]&lt;br /&gt;
|[[Image:VmtkSlicerModule.jpg|thumb|320px|Vmtk working inside Slicer3.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key Investigators===&lt;br /&gt;
* Mario Negri Institute, University of Verona: Luca Antiga&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 20px;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Objective&amp;lt;/h1&amp;gt;&lt;br /&gt;
To create a Slicer-based platform for segmentation of vascular segments from angiographic images (CTA, MRA, ...), analysis of vascular geometry, mesh generation, computational hemodynamics (CFD) and visualization.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 27%; float: left; padding-right: 3%;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Approach, Plan&amp;lt;/h1&amp;gt;&lt;br /&gt;
To integrate vmtk scripts within Slicer as command-line modules for the non-interactive tasks, and to create ad-hoc GUI modules for the more interactive tasks (i.e. segmentation).&lt;br /&gt;
&lt;br /&gt;
The plan for the project week is to finalize the implementation of an interactive LevelSetSegment module that replicates (and improves) the interactive segmentation tool currently in vmtk. Tentatively, LevelSetSegment will be a Python Scripted Module.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width: 40%; float: left;&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;Progress&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
During project weeks last year (see [[Collaboration/VMTK | 2007 Project Week at MIT]]), automated conversion of vmtk script pipes to Slicer command-line modules has been implemented.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear: both;&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===References===&lt;br /&gt;
&lt;br /&gt;
* [http://vmtk.sourceforge.net vmtk.sourceforge.net]&lt;br /&gt;
* Lee SW, Antiga L, Spence JD and Steinman DA. Geometry of the carotid bifurcation predicts its exposure to disturbed flow. Stroke. Accepted.&lt;br /&gt;
* Thomas JB, Antiga L, Che S, Milner JS, Hangan Steinman DA, Spence JD, Rutt BK and Steinman DA. Variation in the carotid bifurcation geometry of young vs. older adults: Implications for &amp;quot;geometric risk&amp;quot; of atherosclerosis. Stroke, 36(11): 2450-2456, Nov 2005.&lt;br /&gt;
* Antiga L, Steinman DA. Robust and objective decomposition and mapping of bifurcating vessels. IEEE Transactions on Medical Imaging, 23(6): 704-713, June 2004.&lt;br /&gt;
* Antiga L, Ene-Iordache B and Remuzzi A. Computational geometry for patient-specific reconstruction and meshing of blood vessels from MR and CT angiography. IEEE Transactions on Medical Imaging, 22(5): 674-684, May 2003.&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2008_Summer_Project_Week&amp;diff=26337</id>
		<title>2008 Summer Project Week</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2008_Summer_Project_Week&amp;diff=26337"/>
		<updated>2008-06-03T10:42:00Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* External Collaborations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[Engineering:Programming_Events|Programming/Project Events]]&lt;br /&gt;
&lt;br /&gt;
[[Image:ProjectWeek-2008.png|thumb|220px|right|Summer 2008]]&lt;br /&gt;
&lt;br /&gt;
== Logistics ==&lt;br /&gt;
&lt;br /&gt;
'''Dates:''' June 23-27, 2008&lt;br /&gt;
&lt;br /&gt;
'''Location:''' MIT. [[Meeting_Locations:MIT_Grier_A_%26B|Grier Rooms A &amp;amp; B: 34-401A &amp;amp; 34-401B]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Registration Fee:''' $260 (this will cover the cost of breakfast, lunch and coffee breaks for the week). Due by Friday, June 13th, 2008. Please make checks out to &amp;quot;Massachusetts Institute of Technology&amp;quot; and mail to: Donna Kaufman, MIT, 77 Massachusetts Ave., 38-409a, Cambridge, MA 02139&lt;br /&gt;
&lt;br /&gt;
'''Registration Method''' Please add your name to the attendee list below (create namic wiki account if you don't have one, by clicking on the &amp;quot;login/create account&amp;quot; link on the top right corner of this page), and then mail a check to Donna Kaufman at the address above.&lt;br /&gt;
&lt;br /&gt;
If you are attending for one day only, the registration fee is not required.&lt;br /&gt;
&lt;br /&gt;
'''Hotel:''' We have a group rate of $239/night (plus tax) for a room with either 1 king or 2 queen beds at the [http://www.hotelatmit.com Hotel at MIT (now called Le Meridien)]. [http://www.starwoodmeeting.com/StarGroupsWeb/booking/reservation?id=0805167317&amp;amp;key=4FD1B  Please click here to reserve.]This rate is good only through June 1.&lt;br /&gt;
&lt;br /&gt;
Here is some information about several other Boston area hotels that are convenient to NA-MIC events: [[Boston_Hotels|Boston_Hotels]]. Summer is tourist season in Boston, so please book your rooms early.&lt;br /&gt;
&lt;br /&gt;
([[Project Week Logistics Checklist|This is a checklist for the onsite planning items]])&lt;br /&gt;
&lt;br /&gt;
==Introduction to NA-MIC Project Week==&lt;br /&gt;
&lt;br /&gt;
NA-MIC Project Week is a hands on activity -- programming using the [[NA-MIC-Kit|NA-MIC Kit]], algorithm design, and clinical application -- that has become one of the major events in the [[NA-MIC-Kit|NA-MIC Kit]] calendar. This event is the seventh of the [[Engineering:Programming_Events|'''series''']]. It is held in the summer at MIT (typically the last week of June), and a shorter version is held in Salt Lake City in the winter (typically the second week of January).  &lt;br /&gt;
The main goal of these events if to move forward the deliverables of NA-MIC. NA-MIC participants and their collaborators are welcome to attend.  &lt;br /&gt;
&lt;br /&gt;
* NA-MIC Members: Participation in this event is voluntary -- if you don't think this will help you move forward in your work, there is no obligation to attend.&lt;br /&gt;
* Ideal candidates are those who want to contribute to the [[NA-MIC-Kit|NA-MIC Kit]], and those who can help make it happen.&lt;br /&gt;
* This is not an introduction to the components of the [[NA-MIC-Kit|NA-MIC Kit]].&lt;br /&gt;
* NA-MIC Core 1 (Algorithms) - bring your algorithms and code to work on in the company of Core 2 engineers and Core 3 scientists.&lt;br /&gt;
* NA-MIC Core 2 (Engineering) - bring your code for infrastructure and applications to extend the [[NA-MIC-Kit|NA-MIC Kit]] capabilities, integrate Core 1 algorithms, and refine workflows for Core 3.&lt;br /&gt;
* NA-MIC Core 3 (DBP) - bring your data to work on with the [[NA-MIC-Kit|NA-MIC Kit]] and get assistance and provide feedback to Core 1 scientists and Core 2 engineers.&lt;br /&gt;
* External Collaborators - if you are working on a project that uses the [[NA-MIC-Kit|NA-MIC kit]], and want to participate to get help from NA-MIC Engineering, please send an email to Tina Kapur (tkapur at bwh.harvard.edu).  Please note that the event is open to people outside NA-MIC, subject to availability.&lt;br /&gt;
* Everyone should '''bring a laptop'''. We will have four projectors.&lt;br /&gt;
* About half the time will be spent working on projects and the other half in project related discussions.&lt;br /&gt;
* You '''do''' need to be actively working on a NA-MIC related project in order to make this investment worthwhile for everyone.&lt;br /&gt;
&lt;br /&gt;
== Agenda==&lt;br /&gt;
* Monday &lt;br /&gt;
** noon-1pm lunch &lt;br /&gt;
**1pm: Welcome (Ron Kikinis)&lt;br /&gt;
** 1:05-3:30pm Introduce [[#Projects|Projects]] using templated wiki pages (all Project Leads) ([[NA-MIC/Projects/Theme/Template|Wiki Template]]) &lt;br /&gt;
** 3:30-5:30pm Start project work&lt;br /&gt;
* Tuesday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 9:00-9:45am: NA-MIC Software Process &lt;br /&gt;
** 10-10:30am [[Project Week 2008 Slicer 3.0 Update|Slicer 3.0 Update]] (Jim Miller, Steve Pieper)&lt;br /&gt;
** noon lunch&lt;br /&gt;
** 2:30-3:30pm: [[Project Week 2008 Special topic breakout: Non-Linear Registration]] &lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Wednesday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 9:00-12pm [[Project Week 2008 Special topic breakout: ITK]] (Luis Ibanez)&lt;br /&gt;
** noon lunch&lt;br /&gt;
** 2:30-3:30pm: [[Project Week 2008 Special topic breakout: XNAT Database]] (Daniel Marcus)&lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Thursday&lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** noon lunch&lt;br /&gt;
**2:30-3:30pm [[Project Week 2008 Special topic breakout: GWE]] (Marco Ruiz)&lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Friday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 10am-noon: Project Progress using update [[#Projects|Project Wiki pages]]&lt;br /&gt;
** noon lunch boxes and adjourn.  (Next one [[AHM_2009| in Utah the week of Jan 5, 2009]])&lt;br /&gt;
&lt;br /&gt;
== Preparation ==&lt;br /&gt;
&lt;br /&gt;
# Please make sure that you are on the http://public.kitware.com/cgi-bin/mailman/listinfo/na-mic-project-week mailing list&lt;br /&gt;
&lt;br /&gt;
# [[Engineering:TCON_2008|May 08 and May 15 TCON DBPs ONLY]] at 3pm ET to discuss NA-MIC DBP Projects ONLY. &lt;br /&gt;
# [[Engineering:TCON_2008|May 22 TCON#1]] at 3pm ET to discuss NA-MIC Engr Core Projects and Assign/Verify Teams&lt;br /&gt;
# [[Engineering:TCON_2008|May 29 TCON#2]] at 3pm ET to discuss NA-MIC ALGORITHMS Core Lead Projects.  Project leads should sign up for a slot [[Engineering:TCON_2008|here]]. Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 5 TCON#3]] at 3pm ET to discuss NA-MIC EXTERNAL Collaborations.  All NIH funded &amp;quot;collaborations with NCBC&amp;quot; leads should call. Project leads should sign up for a slot [[Engineering:TCON_2008|here]].  Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 12 TCON#4]] at 3pm ET to discuss NA-MIC EXTERNAL Collaborations.  All other collaboration leads should call. Project leads should sign up for a slot [[Engineering:TCON_2008|here]].  Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 19 TCON#5]] at 3pm ET to tie loose ends.  Anyone with un-addressed questions should call.&lt;br /&gt;
# By 3pm ET on June 12, 2008: [[NA-MIC/Projects/Theme/Template|Complete a templated wiki page for your project]]. Please do not edit the template page itself, but create a new page for your project and cut-and-paste the text from this template page.  If you have questions, please send an email to tkapur at bwh.harvard.edu.&lt;br /&gt;
# By 3pm on June 19, 2008: Create a directory for each project on the [[Engineering:SandBox|NAMIC Sandbox]] (Zack)&lt;br /&gt;
## Commit on each sandbox directory the code examples/snippets that represent our first guesses of appropriate methods. (Luis and Steve will help with this, as needed)&lt;br /&gt;
## Gather test images in any of the Data sharing resources we have (e.g. the BIRN). These ones don't have to be many. At least three different cases, so we can get an idea of the modality-specific characteristics of these images. Put the IDs of these data sets on the wiki page. (the participants must do this.)&lt;br /&gt;
## Setup nightly tests on a separate Dashboard, where we will run the methods that we are experimenting with. The test should post result images and computation time. (Zack)&lt;br /&gt;
# Please note that by the time we get to the project event, we should be trying to close off a project milestone rather than starting to work on one...&lt;br /&gt;
&lt;br /&gt;
== A History in Wiki Links ==&lt;br /&gt;
&lt;br /&gt;
A history of all the programming/project events in NA-MIC is available by following [[Engineering:Programming_Events|this link]].&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
===DBP II===&lt;br /&gt;
These are projects by the new set of DBPS:&lt;br /&gt;
#[[DBP2:Harvard|Velocardio Facial Syndrome (VCFS) as a Genetic Model for Schizophrenia]] (Harvard: Marek Kubicki, PI)&lt;br /&gt;
##EPI-DWI Distortion correction (Sylvain Bouix BWH, Tauseef Rehman GATech)&lt;br /&gt;
##[[2008_Summer_Project_Week:EddyCurrentCorrection|EPI-DWI Eddy Current distortion correction]] (Sylvain Bouix BWH, Ran Tao Utah)&lt;br /&gt;
##Lobe Parcellation of 3T MR data - need help parametrization (Sylvain Bouix BWH, Priya Srinivasan BWH, Brad Davis Kitware)&lt;br /&gt;
##Finsler method (John Melonakos GATech, Marek Kubicki BWH)&lt;br /&gt;
##Group Analysis on DTI (Casey Goodlett Utah, Marek Kubicki BWH)&lt;br /&gt;
#[[DBP2:UNC|Longitudinal MRI Study of Early Brain Development in Autism]] (UNC: Heather Hazlett, Joseph Piven, PI)&lt;br /&gt;
##Work Flow Tool for regional cortical thickness pipeline (Clement Vachet UNC)&lt;br /&gt;
##NITRC registration of cortical thickness modules (Clement Vachet UNC)&lt;br /&gt;
##DTI tools for a) DWI preparation and b) DTI atlas building (Zhexing Liu UNC) &lt;br /&gt;
#[[DBP2:MIND|Analysis of Brain Lesions in Lupus]] (MIND/UNM: Jeremy Bockholt, Charles Gasparovic PI)&lt;br /&gt;
##[[DBP2:MIND:RoadmapProject|Finish Roadmap Project]]&lt;br /&gt;
##[[DBP2:MIND:LongitudinalRegistrationProject|Longitudinal Registration]]&lt;br /&gt;
##[[DBP2:MIND:BeyondLesionsProject|Beyond Lesions]]&lt;br /&gt;
#[[DBP2:JHU|Segmentation and Registration Tools for Robotic Prostate Intervention]] (Queens/JHU: Gabor Fichtinger, PI)&lt;br /&gt;
##[[Projects:ProstateSegmentation|Prostate Segmentation and Registration (Yi Gao GATech, Gabor Fichtinger JHU)]]&lt;br /&gt;
&lt;br /&gt;
===Structural Analysis===&lt;br /&gt;
&lt;br /&gt;
===Diffusion Image Analysis===&lt;br /&gt;
#[[2008_Summer_Project_Week:EddyCurrentCorrection|Eddy current and head motion correction of DWIs]] (Ran Tao, Utah, Sylvain Bouix, BWH, Xiaodong Tao, GE, Tom Fletcher, Utah)&lt;br /&gt;
#Integraton of groupwise b-spline registration into atlas building (Casey Goodlett, Serdar Balci)&lt;br /&gt;
&lt;br /&gt;
===Calibration/Validation===&lt;br /&gt;
&lt;br /&gt;
===NA-MIC Kit - Slicer 3===&lt;br /&gt;
# CVS / SVN auto synchronization&lt;br /&gt;
# 3D Widgets in Slicer&lt;br /&gt;
## Issues with existing widgets&lt;br /&gt;
## Design of new widgets&lt;br /&gt;
# Batch processing in the NAMIC Kit (Julien, Marco, Steve, Jim)&lt;br /&gt;
# Module Chaining (Marco, Jim, Steve, Dan B., Luca)&lt;br /&gt;
# Nonlinear transforms (Jim, Steve, Luis)&lt;br /&gt;
## TransformToWorld/TransformFromWorld, integration with slice viewing&lt;br /&gt;
# Slicer3, XNAT integration, and desigining XCEDE Web Services (Dan M., Steve, Julien)&lt;br /&gt;
## Review and enrich use cases&lt;br /&gt;
&lt;br /&gt;
===External Collaborations===&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/UWA-Perth]] (Adam Wittek)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/MRSI Module for Slicer]] (Bjoern Menze)&lt;br /&gt;
#NIREP: Non-rigid Image Registration Evaluation (Gary Christensen Group)&lt;br /&gt;
#Lung Atlas (Gary Christensen Group)&lt;br /&gt;
#Non-rigid image registration (Gary Christensen Group)&lt;br /&gt;
#[[NA-MIC/Projects/Collaboration/SARP phantom]] (Keith Gunderson)&lt;br /&gt;
#FMA (Protege) links to Slicer (Vish, Mike, Florin, Jim, Steve, Wendy)&lt;br /&gt;
#[[NA-MIC/Projects/External Collaboration/Measuring Alcohol and Stress Interaction]]&lt;br /&gt;
#[[NA-MIC/Projects/External Collaboration/Slicer3-vmtk Integration]] (Luca Antiga)&lt;br /&gt;
&lt;br /&gt;
===Non-Medical Collaborations===&lt;br /&gt;
&lt;br /&gt;
==Attendee List==&lt;br /&gt;
# Ron Kikinis, BWH&lt;br /&gt;
# Carl-Fredrik Westin, BWH&lt;br /&gt;
# Gary Christensen, The University of Iowa&lt;br /&gt;
# Jeffrey Hawley, Gary Christensen's student&lt;br /&gt;
# Kate Raising, Gary Christensen's student&lt;br /&gt;
# Nathan Fritze, Gary Christensen's student&lt;br /&gt;
# Paul Song, Gary Christensen's student&lt;br /&gt;
# Cheng Zhang, Gary Christensen's student&lt;br /&gt;
# Ying Wei, Gary Christensen's student&lt;br /&gt;
# Nathan Burnette, The University of Iowa&lt;br /&gt;
# Hans Johnson, The University of Iowa&lt;br /&gt;
# Vincent Magnotta, The University of Iowa&lt;br /&gt;
# Keith Gunderson, The University of Iowa&lt;br /&gt;
# Steve Pieper, Isomics, Core 2/6&lt;br /&gt;
# Dana C. Peters, BIDMC Harvard Medical&lt;br /&gt;
# Jason Taclas, BIDMC Harvard Medical&lt;br /&gt;
# Nicole Aucoin, BWH, Core 2&lt;br /&gt;
# Will Schroeder, Kitware, Cores 2/4&lt;br /&gt;
# Sebastien Barre, Kitware, Core 2&lt;br /&gt;
# Julien Jomier, Kitware, Core 2&lt;br /&gt;
# Luis Ibanez, Kitware, Core 2&lt;br /&gt;
# Curtis Lisle, KnowledgeVis, Core 2&lt;br /&gt;
# Katie Hayes, BWH, Core 2&lt;br /&gt;
# Randy Gollub, MGH, Core 5&lt;br /&gt;
# Clement Vachet, UNC, Core 3&lt;br /&gt;
# Zhexing Liu, UNC, Core 1/3&lt;br /&gt;
# Casey Goodlett, Utah, Core 1&lt;br /&gt;
# Marcel Prastawa, Utah, Core 1&lt;br /&gt;
# Jeffrey Grethe, UCSD, Core 2&lt;br /&gt;
# Marco Ruiz, UCSD, Core 2&lt;br /&gt;
# Zhen Qian, Rutgers University&lt;br /&gt;
# Jinghao Zhou, Rutgers University&lt;br /&gt;
# Luca Antiga, Mario Negri Institute&lt;br /&gt;
# Adam Wittek, The University of Western Australia&lt;br /&gt;
# Grand Joldes, The University of Western Australia&lt;br /&gt;
# Jamie Berger, The University of Western Australia&lt;br /&gt;
# Serdar Balci, MIT, Core 1&lt;br /&gt;
# Bryce Kim, MIT, Core1&lt;br /&gt;
# Tina Kapur, BWH, Core 6&lt;br /&gt;
# Carling Cheung, Robarts Research Institute / The University of Western Ontario&lt;br /&gt;
# Danielle Pace, Robarts Research Institute / The University of Western Ontario&lt;br /&gt;
# Sean Megason, Dept of Systems Biology, Harvard Medical School&lt;br /&gt;
# Alex Gouaillard, Dept of Systems Biology, Harvard Medical School&lt;br /&gt;
# Kishore Mosaliganti, Dept of Systems Biology, Harvard Medical School&lt;br /&gt;
# Arnaud Gelas, Dept of Systems Biology, Harvard Medical School&lt;br /&gt;
# Sonia Pujol, Surgical Planning Laboratory, BWH&lt;br /&gt;
# Bjoern Menze, (then) Surgical Planning Laboratory, BWH&lt;br /&gt;
# Alex Yarmarkovich, Isomics, Core 2&lt;br /&gt;
# Sylvain Bouix, BWH, Core 3&lt;br /&gt;
# Priya Srinivasan, BWH, Core 3&lt;br /&gt;
# Chris Churas, UCSD, Core 2&lt;br /&gt;
# John Melonakos, Georgia Tech, Core 1&lt;br /&gt;
# Yi Gao, Georgia Tech, Core 1&lt;br /&gt;
# Tauseef Rehman, Georgia Tech, Core 1&lt;br /&gt;
# Clare Poynton, MIT, Core 1&lt;br /&gt;
# H. Jeremy Bockholt, MRN Lupus DBP Core 3&lt;br /&gt;
# Mark Scully, MRN Lupus DBP Core 3&lt;br /&gt;
# Gabor Fichtinger, Queen's, Core 2&lt;br /&gt;
# David Gobbi, Queen's, Core 2&lt;br /&gt;
# Purang Abolmaesumi, Queen's, Core 2&lt;br /&gt;
# Siddharth Vikal, Queen's, Core 2&lt;br /&gt;
# Daniel Blezek, Mayo&lt;br /&gt;
# Csaba Csoma, JHU, Core 2&lt;br /&gt;
# Ran Tao, University of Utah, Core 1&lt;br /&gt;
# Jim Miller, GE Research, Core 2&lt;br /&gt;
# Xiaodong Tao, GE Research, Core 2&lt;br /&gt;
# Dirk Padfield, GE Research, Core 2&lt;br /&gt;
# Viswanath Avasarala, GE Research, NAC&lt;br /&gt;
# Dan Marcus, Washington University   &lt;br /&gt;
# Tim Olsen, Washington University   &lt;br /&gt;
# Kevin Archie, Washington University   &lt;br /&gt;
# Misha Milchenko, Washington University&lt;br /&gt;
# Wendy Plesniak, BWH, Core 2&lt;br /&gt;
# Demian Wasserman, INRIA, LMI-collaborator&lt;br /&gt;
#Xenophon Papademetris, Yale, Collaborator&lt;br /&gt;
#Xenophon P's postdoc, Yale, Collaborator&lt;br /&gt;
#Xenophon P's student, Yale, Collaborator&lt;br /&gt;
#Vidya Rajagopalan, Virginia Tech, Student of Chris Wyatt, External Collaborator&lt;br /&gt;
# Greg Sharp, MGH, External Collaborator&lt;br /&gt;
# Marta Peroni, MGH, External Collaborator&lt;br /&gt;
#Toru Higaki, Hiroshima Univ., Japan, External collaborator (Hata)&lt;br /&gt;
#Jacek Kukluk, BWH,&lt;br /&gt;
#Nobuhiko Hata, BWH&lt;br /&gt;
#Junichi Tokuda, BWH&lt;br /&gt;
#Haying Liu, BWH&lt;br /&gt;
#Ragini Verma, UPenn (June 24)&lt;br /&gt;
#Luke Bloy, UPenn (Ragini Verma's student) (June 24)&lt;br /&gt;
#Yang Li, UPenn (Ragini's postdoc) (June 24)&lt;br /&gt;
#Jack Blevins, Acoustic Med, Collaborator&lt;br /&gt;
&lt;br /&gt;
==Pictures==&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=2008_Summer_Project_Week&amp;diff=24506</id>
		<title>2008 Summer Project Week</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=2008_Summer_Project_Week&amp;diff=24506"/>
		<updated>2008-05-09T07:51:33Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Attendee List */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[Engineering:Programming_Events|Programming/Project Events]]&lt;br /&gt;
&lt;br /&gt;
[[Image:ProjectWeek-2008.png|thumb|220px|right|Summer 2008]]&lt;br /&gt;
&lt;br /&gt;
== Logistics ==&lt;br /&gt;
&lt;br /&gt;
'''Dates:''' June 23-27, 2008&lt;br /&gt;
&lt;br /&gt;
'''Location:''' MIT. [[Meeting_Locations:MIT_Grier_A_%26B|Grier Rooms A &amp;amp; B: 34-401A &amp;amp; 34-401B]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Registration Fee:''' $260 (this will cover the cost of breakfast, lunch and coffee breaks for the week). Due by Friday, June 13th, 2008. Please make checks out to &amp;quot;Massachusetts Institute of Technology&amp;quot; and mail to: Donna Kaufman, MIT, 77 Massachusetts Ave., 38-409b, Cambridge, MA 02139&lt;br /&gt;
&lt;br /&gt;
If you are attending for one day only, the registration fee is not required.&lt;br /&gt;
&lt;br /&gt;
'''Hotel:''' We have a group rate of TBD/night at the [http://www.hotelatmit.com Hotel at MIT]. (Use group code NAM.) Here is some information about several other Boston area hotels that are convenient to NA-MIC events: [[Boston_Hotels|Boston_Hotels]]. Summer is tourist season in Boston, so please book your rooms early.&lt;br /&gt;
&lt;br /&gt;
([[Project Week Logistics Checklist|This is a checklist for the onsite planning items]])&lt;br /&gt;
&lt;br /&gt;
==Introduction to NA-MIC Project Week==&lt;br /&gt;
&lt;br /&gt;
NA-MIC Project Week is a hands on activity -- programming using the [[NA-MIC-Kit|NA-MIC Kit]], algorithm design, and clinical application -- that has become one of the major events in the [[NA-MIC-Kit|NA-MIC Kit]] calendar. This event is the seventh of the [[Engineering:Programming_Events|'''series''']]. It is held in the summer at MIT (typically the last week of June), and a shorter version is held in Salt Lake City in the winter (typically the second week of January).  &lt;br /&gt;
The main goal of these events if to move forward the deliverables of NA-MIC. NA-MIC participants and their collaborators are welcome to attend.  &lt;br /&gt;
&lt;br /&gt;
* NA-MIC Members: Participation in this event is voluntary -- if you don't think this will help you move forward in your work, there is no obligation to attend.&lt;br /&gt;
* Ideal candidates are those who want to contribute to the [[NA-MIC-Kit|NA-MIC Kit]], and those who can help make it happen.&lt;br /&gt;
* This is not an introduction to the components of the [[NA-MIC-Kit|NA-MIC Kit]].&lt;br /&gt;
* NA-MIC Core 1 (Algorithms) - bring your algorithms and code to work on in the company of Core 2 engineers and Core 3 scientists.&lt;br /&gt;
* NA-MIC Core 2 (Engineering) - bring your code for infrastructure and applications to extend the [[NA-MIC-Kit|NA-MIC Kit]] capabilities, integrate Core 1 algorithms, and refine workflows for Core 3.&lt;br /&gt;
* NA-MIC Core 3 (DBP) - bring your data to work on with the [[NA-MIC-Kit|NA-MIC Kit]] and get assistance and provide feedback to Core 1 scientists and Core 2 engineers.&lt;br /&gt;
* External Collaborators - if you are working on a project that uses the [[NA-MIC-Kit|NA-MIC kit]], and want to participate to get help from NA-MIC Engineering, please send an email to Tina Kapur (tkapur at bwh.harvard.edu).  Please note that the event is open to people outside NA-MIC, subject to availability.&lt;br /&gt;
* Everyone should '''bring a laptop'''. We will have four projectors.&lt;br /&gt;
* About half the time will be spent working on projects and the other half in project related discussions.&lt;br /&gt;
* You '''do''' need to be actively working on a NA-MIC related project in order to make this investment worthwhile for everyone.&lt;br /&gt;
&lt;br /&gt;
=== Agenda===&lt;br /&gt;
* Monday &lt;br /&gt;
** noon-1pm lunch &lt;br /&gt;
**1pm: Welcome (Ron Kikinis)&lt;br /&gt;
** 1:05-3:30pm Introduce [[#Projects|Projects]] using templated wiki pages (all Project Leads) ([[NA-MIC/Projects/Theme/Template|Wiki Template]]) &lt;br /&gt;
** 3:30-5:30pm Start project work&lt;br /&gt;
* Tuesday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 9:00-9:45am: NA-MIC Software Process &lt;br /&gt;
** 10-10:30am [[Project Week 2008 Slicer 3.0 Update|Slicer 3.0 Update]] (Jim Miller, Steve Pieper)&lt;br /&gt;
** noon lunch&lt;br /&gt;
** 2:30-3:30pm: [[Project Week 2008 Special topic breakout: Non-Linear Registration]] &lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Wednesday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 9:00-12pm [[Project Week 2008 Special topic breakout: ITK]] (Luis Ibanez)&lt;br /&gt;
** noon lunch&lt;br /&gt;
** 2:30-3:30pm: [[Project Week 2008 Special topic breakout: XNAT Database]] (Daniel Marcus)&lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Thursday&lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** noon lunch&lt;br /&gt;
** 5:30pm adjourn for day&lt;br /&gt;
* Friday &lt;br /&gt;
** 8:30am breakfast&lt;br /&gt;
** 10am-noon: Project Progress using update [[#Projects|Project Wiki pages]]&lt;br /&gt;
** noon lunch boxes and adjourn.  (Next one [[AHM_2009| in Utah the week of Jan 5, 2009]])&lt;br /&gt;
&lt;br /&gt;
=== Preparation ===&lt;br /&gt;
&lt;br /&gt;
# Please make sure that you are on the http://public.kitware.com/cgi-bin/mailman/listinfo/na-mic-project-week mailing list&lt;br /&gt;
&lt;br /&gt;
# [[Engineering:TCON_2008|May 08 and May 15 TCON DBPs ONLY]] at 3pm ET to discuss NA-MIC DBP Projects ONLY. &lt;br /&gt;
# [[Engineering:TCON_2008|May 22 TCON#1]] at 3pm ET to discuss NA-MIC Engr Core Projects and Assign/Verify Teams&lt;br /&gt;
# [[Engineering:TCON_2008|May 29 TCON#2]] at 3pm ET to discuss NA-MIC ALGORITHMS Core Lead Projects.  Project leads should sign up for a slot [[Engineering:TCON_2008|here]]. Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 5 TCON#3]] at 3pm ET to discuss NA-MIC EXTERNAL Collaborations.  All NIH funded &amp;quot;collaborations with NCBC&amp;quot; leads should call. Project leads should sign up for a slot [[Engineering:TCON_2008|here]].  Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 12 TCON#4]] at 3pm ET to discuss NA-MIC EXTERNAL Collaborations.  All other collaboration leads should call. Project leads should sign up for a slot [[Engineering:TCON_2008|here]].  Projects will be discussed in order of the signups. &lt;br /&gt;
# [[Engineering:TCON_2008|June 12 TCON#4]] at 3pm ET to tie loose ends.  Anyone with un-addressed questions should call.&lt;br /&gt;
# By 3pm ET on June 12, 2008: [[NA-MIC/Projects/Theme/Template|Complete a templated wiki page for your project]]. Please do not edit the template page itself, but create a new page for your project and cut-and-paste the text from this template page.  If you have questions, please send an email to tkapur at bwh.harvard.edu.&lt;br /&gt;
# By 3pm on June 19, 2008: Create a directory for each project on the [[Engineering:SandBox|NAMIC Sandbox]] (Zack)&lt;br /&gt;
## Commit on each sandbox directory the code examples/snippets that represent our first guesses of appropriate methods. (Luis and Steve will help with this, as needed)&lt;br /&gt;
## Gather test images in any of the Data sharing resources we have (e.g. the BIRN). These ones don't have to be many. At least three different cases, so we can get an idea of the modality-specific characteristics of these images. Put the IDs of these data sets on the wiki page. (the participants must do this.)&lt;br /&gt;
## Setup nightly tests on a separate Dashboard, where we will run the methods that we are experimenting with. The test should post result images and computation time. (Zack)&lt;br /&gt;
# Please note that by the time we get to the project event, we should be trying to close off a project milestone rather than starting to work on one...&lt;br /&gt;
&lt;br /&gt;
== A History in Wiki Links ==&lt;br /&gt;
&lt;br /&gt;
A history of all the programming/project events in NA-MIC is available by following [[Engineering:Programming_Events|this link]].&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
===DBP II===&lt;br /&gt;
These are projects by the new set of DBPS:&lt;br /&gt;
#[[DBP2:Harvard|Velocardio Facial Syndrome (VCFS) as a Genetic Model for Schizophrenia]] (Harvard: Marek Kubicki, PI)&lt;br /&gt;
#[[DBP2:UNC|Longitudinal MRI Study of Early Brain Development in Autism]] (UNC: Heather Hazlett, Joseph Piven, PI)&lt;br /&gt;
#[[DBP2:MIND|Analysis of Brain Lesions in Lupus]] (MIND/UNM: Jeremy Bockholt, Charles Gasparovic PI)&lt;br /&gt;
#[[DBP2:JHU|Segmentation and Registration Tools for Robotic Prostate Intervention]] (Queens/JHU: Gabor Fichtinger, PI)&lt;br /&gt;
&lt;br /&gt;
===Structural Analysis===&lt;br /&gt;
&lt;br /&gt;
===Diffusion Image Analysis===&lt;br /&gt;
&lt;br /&gt;
===Calibration/Validation===&lt;br /&gt;
This is a new category of projects jointly led by team members in Core 1, Core 3 and Core 5&lt;br /&gt;
# [[Projects/Diffusion/2007_Project_Week_Contrasting_Tractography_Measures]] (Westin, Gollub, Gerig, Whitaker, Pujol)&lt;br /&gt;
&lt;br /&gt;
===NA-MIC Kit - Slicer 3===&lt;br /&gt;
&lt;br /&gt;
===External Collaborations===&lt;br /&gt;
&lt;br /&gt;
===Non-Medical Collaborations===&lt;br /&gt;
&lt;br /&gt;
==Attendee List==&lt;br /&gt;
# Ron Kikinis, SPL&lt;br /&gt;
# Gary Christensen, The University of Iowa&lt;br /&gt;
# Jeffrey Hawley, Gary Christensen's student&lt;br /&gt;
# Kate Raising, Gary Christensen's student&lt;br /&gt;
# Nathan Fritze, Gary Christensen's student&lt;br /&gt;
# Paul Song, Gary Christensen's student&lt;br /&gt;
# Cheng Zhang, Gary Christensen's student&lt;br /&gt;
# Ying Wei, Gary Christensen's student&lt;br /&gt;
# Nathan Burnette, The University of Iowa&lt;br /&gt;
# Steve Pieper, Isomics, Core 2/6&lt;br /&gt;
# Dana C. Peters, BIDMC Harvard Medical&lt;br /&gt;
# Jason Taclas, Student, BIDMC Harvard Medical&lt;br /&gt;
# Nicole Aucoin, BWH, Core 2&lt;br /&gt;
# Will Schroeder, Kitware, Cores 2/4&lt;br /&gt;
# Sebastien Barre, Kitware, Core 2&lt;br /&gt;
# Julien Jomier, Kitware, Core 2&lt;br /&gt;
# Curtis Lisle, KnowledgeVis, Core 2&lt;br /&gt;
# Katie Hayes, BWH, Core 2&lt;br /&gt;
# Randy Gollub, MGH, Core 5&lt;br /&gt;
# Clement Vachet, UNC, Core 3&lt;br /&gt;
# Tauseef Rehman, GA Tech, Core 1&lt;br /&gt;
# Jeffrey Grethe, UCSD, Core 2&lt;br /&gt;
# Marco Ruiz, UCSD, Core 2&lt;br /&gt;
# Zhen Qian, Rutgers University&lt;br /&gt;
# Jinghao Zhou, Rutgers University&lt;br /&gt;
# Luca Antiga, Mario Negri Institute&lt;br /&gt;
&lt;br /&gt;
==Pictures==&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=NA-MIC_External_Collaborations&amp;diff=22799</id>
		<title>NA-MIC External Collaborations</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=NA-MIC_External_Collaborations&amp;diff=22799"/>
		<updated>2008-03-10T18:53:55Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /* Additional External Collaborations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[NA-MIC_Collaborations|NA-MIC Collaborations]]&lt;br /&gt;
&lt;br /&gt;
=Projects funded by &amp;quot;Collaborations with NCBC PAR&amp;quot;=&lt;br /&gt;
&lt;br /&gt;
This section describes external collaborations with NA-MIC that are funded by NIH under the &amp;quot;Collaboration with NCBC&amp;quot; PAR. (Details for this funding mechanism are provided [[Collaborator:Resources|&amp;lt;big&amp;gt;&amp;lt;big&amp;gt;here&amp;lt;/big&amp;gt;&amp;lt;/big&amp;gt;]]).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| style=&amp;quot;width:10%&amp;quot; | [[Image:Cli-mesh-quality-small-062607.png|thumb|left|300px|PAR-05-063: R01EB005973 Automated FE Mesh Development]]&lt;br /&gt;
| style=&amp;quot;width:90%&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== [[NA-MIC_NCBC_Collaboration:Automated_FE_Mesh_Development|PAR-05-063: R01EB005973 Automated FE Mesh Development]] ==&lt;br /&gt;
&lt;br /&gt;
This project is funded under an NCBC collaboration grant to PIs Nicole Grosland and Vincent Magnotta at UIowa. The goal of this project is to integrate and expand methods to automate the development of specimen- / patient-specific finite element (FE) models into the [[NA-MIC-Kit|NA-MIC kit]]. [[NA-MIC_NCBC_Collaboration:Automated_FE_Mesh_Development|More...]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| | [[Image:NhpATOCPic.jpg|thumb|left|300px]]&lt;br /&gt;
| |&lt;br /&gt;
&lt;br /&gt;
==[[NA-MIC_NCBC_Collaboration:Measuring_Alcohol_and_Stress_Interaction|PAR-07-249: R01AA016748 Measuring Alcohol and Stress Interaction with Structural and Perfusion MRI]]==&lt;br /&gt;
&lt;br /&gt;
This project is funded under an NCBC collaboration grant to PIs James Daunais, Robert Kraft, and Chris Wyatt.  The goal of this project is to examine the the effects of chronic alcohol self- administration on brain structure and function the monkey brain. MRI image analysis tools from the  [[NA-MIC-Kit|NA-MIC kit]] will be adapted for use with the monkey brain datasets. [[NA-MIC_NCBC_Collaboration:Measuring_Alcohol_and_Stress_Interaction|More...]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| | [[Image:LiverRFAPhantom.png|thumb|left|300px]]&lt;br /&gt;
| |&lt;br /&gt;
&lt;br /&gt;
==[[NA-MIC_NCBC_Collaboration:An Integrated System for Image-Guided Radiofrequency Ablation of Liver Tumors|PAR-05-063: R01CA124377 An Integrated System for Image-Guided Radiofrequency Ablation of Liver Tumors]]==&lt;br /&gt;
&lt;br /&gt;
This project is funded under an NCBC collaboration grant to PI Kevin Cleary at Georgetown University. The goal of this project is to develop and validate an integrated system based on open source software for improved visualization and probe placement during radiofrequency ablation (RFA) of liver tumors.[[NA-MIC_NCBC_Collaboration:An Integrated System for Image-Guided Radiofrequency Ablation of Liver Tumors|More...]]&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Additional External Collaborations=&lt;br /&gt;
&lt;br /&gt;
This section describes external collaborations with NA-MIC that are funded by other mechanisms:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| style=&amp;quot;width:10%&amp;quot; | [[Image:BRAINS.gif|thumb|left|300px]]&lt;br /&gt;
| style=&amp;quot;width:90%&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[[NA-MIC Brains Collaboration| PAR-05-057: BRAINS Morphology and Image Analysis]]==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This project is a funded under a Continued Development and Maintenance of Software grant to PIs Vincent Magnotta, Hans Johnson, Jeremy Bockholt, and Nancy Andreasen at the University of Iowa. The goal of this project is to update the '''BRAINS''' image analysis software developed at the University of Iowa. [[NA-MIC Brains Collaboration|More...]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| | [[Image:LevelSetSegmentGUIModule_alpha.png|thumb|left|300px]]&lt;br /&gt;
| |&lt;br /&gt;
&lt;br /&gt;
==[[NA-MIC VMTK Collaboration | Vascular Modeling Toolkit Collaboration]]==&lt;br /&gt;
&lt;br /&gt;
Slicer as a platform for segmentation and geometric analysis of vascular segments and image-based computational fluid dynamics (CFD). [[NA-MIC VMTK Collaboration|More...]]&lt;br /&gt;
&lt;br /&gt;
Collaboration with [http://villacamozzi.marionegri.it/~luca/ Luca Antiga] of the [http://www.marionegri.it Mario Negri Institute].&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| | [[Image:27y-leftabdcan-T6SQ-voltage-withheart4.png |thumb|left|300px]]&lt;br /&gt;
| |&lt;br /&gt;
&lt;br /&gt;
==[[NA-MIC Childrens Collaboration| Children's Pediatric Cardiology Collaboration with SCI/SPL/Northeastern]]==&lt;br /&gt;
&lt;br /&gt;
Collaboration with John Triedman, Matt Jolley, Dana Brooks, SCI.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| | [[Image:NITRC.png|thumb|left|300px]]&lt;br /&gt;
| |&lt;br /&gt;
==[[NA-MIC and NITRC| NA-MIC Collaboration with NITRC]]==&lt;br /&gt;
&lt;br /&gt;
The NA-MIC Project is working to make NA-MIC neuroimaging software available through the [http://www.nitrc.org/ NITRC web site].  Supplemental support is helping to create the [[Slicer3:Loadable_Modules | Slicer3 Loadable Modules]] project so that slicer plugins can be hosted on NITRC, allowing greater scalability for developers and users of Slicer.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| | [[Image:Logo_nac.gif|thumb|left|100px|[http://nac.spl.harvard.edu NAC website]]]&lt;br /&gt;
| |&lt;br /&gt;
&lt;br /&gt;
==[[Collaboration:NAC| NA-MIC Collaboration with NAC]]==&lt;br /&gt;
&lt;br /&gt;
NAC, the neuroimage analysis center, is a national resource center. NAC is relying on the NA-MIC kit for its general software environment. The mission of NAC is to develop novel concepts for the analysis of images of the brain and develop and disseminate tools based on those concepts.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| | [[Image:Ncigtlogo.gif|thumb|left|100px]]&lt;br /&gt;
| |&lt;br /&gt;
&lt;br /&gt;
==[[Collaboration:NCIGT| NA-MIC Collaboration with NCIGT]]==&lt;br /&gt;
&lt;br /&gt;
Here are a couple of sentences to summarize the nature of the NA-MIC Collaboration with NCIGT.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:AISTlogo.gif|thumb|left|100px]]&lt;br /&gt;
&lt;br /&gt;
==[[Collaboration:AIST| NA-MIC Collaboration with Research and Development Project on Intelligent Surgical Instruments]]==&lt;br /&gt;
&lt;br /&gt;
Intelligent Surgical Instruments Projects uses Open-source software engineering tools developed by NA-MIC, and leverage it to surgical robotics.&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=File:LevelSetSegmentGUIModule_alpha.png&amp;diff=22797</id>
		<title>File:LevelSetSegmentGUIModule alpha.png</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=File:LevelSetSegmentGUIModule_alpha.png&amp;diff=22797"/>
		<updated>2008-03-10T18:52:56Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
	<entry>
		<id>https://www.na-mic.org/w/index.php?title=NA-MIC_External_Collaborations&amp;diff=22794</id>
		<title>NA-MIC External Collaborations</title>
		<link rel="alternate" type="text/html" href="https://www.na-mic.org/w/index.php?title=NA-MIC_External_Collaborations&amp;diff=22794"/>
		<updated>2008-03-10T18:35:29Z</updated>

		<summary type="html">&lt;p&gt;Lantiga: /*  Vascular Modeling Toolkit */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[NA-MIC_Collaborations|NA-MIC Collaborations]]&lt;br /&gt;
&lt;br /&gt;
=Projects funded by &amp;quot;Collaborations with NCBC PAR&amp;quot;=&lt;br /&gt;
&lt;br /&gt;
This section describes external collaborations with NA-MIC that are funded by NIH under the &amp;quot;Collaboration with NCBC&amp;quot; PAR. (Details for this funding mechanism are provided [[Collaborator:Resources|&amp;lt;big&amp;gt;&amp;lt;big&amp;gt;here&amp;lt;/big&amp;gt;&amp;lt;/big&amp;gt;]]).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| style=&amp;quot;width:10%&amp;quot; | [[Image:Cli-mesh-quality-small-062607.png|thumb|left|300px|PAR-05-063: R01EB005973 Automated FE Mesh Development]]&lt;br /&gt;
| style=&amp;quot;width:90%&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== [[NA-MIC_NCBC_Collaboration:Automated_FE_Mesh_Development|PAR-05-063: R01EB005973 Automated FE Mesh Development]] ==&lt;br /&gt;
&lt;br /&gt;
This project is funded under an NCBC collaboration grant to PIs Nicole Grosland and Vincent Magnotta at UIowa. The goal of this project is to integrate and expand methods to automate the development of specimen- / patient-specific finite element (FE) models into the [[NA-MIC-Kit|NA-MIC kit]]. [[NA-MIC_NCBC_Collaboration:Automated_FE_Mesh_Development|More...]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| | [[Image:NhpATOCPic.jpg|thumb|left|300px]]&lt;br /&gt;
| |&lt;br /&gt;
&lt;br /&gt;
==[[NA-MIC_NCBC_Collaboration:Measuring_Alcohol_and_Stress_Interaction|PAR-07-249: R01AA016748 Measuring Alcohol and Stress Interaction with Structural and Perfusion MRI]]==&lt;br /&gt;
&lt;br /&gt;
This project is funded under an NCBC collaboration grant to PIs James Daunais, Robert Kraft, and Chris Wyatt.  The goal of this project is to examine the the effects of chronic alcohol self- administration on brain structure and function the monkey brain. MRI image analysis tools from the  [[NA-MIC-Kit|NA-MIC kit]] will be adapted for use with the monkey brain datasets. [[NA-MIC_NCBC_Collaboration:Measuring_Alcohol_and_Stress_Interaction|More...]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| | [[Image:LiverRFAPhantom.png|thumb|left|300px]]&lt;br /&gt;
| |&lt;br /&gt;
&lt;br /&gt;
==[[NA-MIC_NCBC_Collaboration:An Integrated System for Image-Guided Radiofrequency Ablation of Liver Tumors|PAR-05-063: R01CA124377 An Integrated System for Image-Guided Radiofrequency Ablation of Liver Tumors]]==&lt;br /&gt;
&lt;br /&gt;
This project is funded under an NCBC collaboration grant to PI Kevin Cleary at Georgetown University. The goal of this project is to develop and validate an integrated system based on open source software for improved visualization and probe placement during radiofrequency ablation (RFA) of liver tumors.[[NA-MIC_NCBC_Collaboration:An Integrated System for Image-Guided Radiofrequency Ablation of Liver Tumors|More...]]&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Additional External Collaborations=&lt;br /&gt;
&lt;br /&gt;
This section describes external collaborations with NA-MIC that are funded by other mechanisms:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| style=&amp;quot;width:10%&amp;quot; | [[Image:BRAINS.gif|thumb|left|300px]]&lt;br /&gt;
| style=&amp;quot;width:90%&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[[NA-MIC Brains Collaboration| PAR-05-057: BRAINS Morphology and Image Analysis]]==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This project is a funded under a Continued Development and Maintenance of Software grant to PIs Vincent Magnotta, Hans Johnson, Jeremy Bockholt, and Nancy Andreasen at the University of Iowa. The goal of this project is to update the '''BRAINS''' image analysis software developed at the University of Iowa. [[NA-MIC Brains Collaboration|More...]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| | [[Image:VmtkRefSys1.jpg|thumb|left|300px]]&lt;br /&gt;
| |&lt;br /&gt;
&lt;br /&gt;
==[[NA-MIC VMTK Collaboration | Vascular Modeling Toolkit Collaboration]]==&lt;br /&gt;
&lt;br /&gt;
Slicer as a platform for segmentation and geometric analysis of vascular segments and image-based computational fluid dynamics (CFD). [[NA-MIC VMTK Collaboration|More...]]&lt;br /&gt;
&lt;br /&gt;
Collaboration with [http://villacamozzi.marionegri.it/~luca/ Luca Antiga] of the [http://www.marionegri.it Mario Negri Institute].&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| | [[Image:27y-leftabdcan-T6SQ-voltage-withheart4.png |thumb|left|300px]]&lt;br /&gt;
| |&lt;br /&gt;
&lt;br /&gt;
==[[NA-MIC Childrens Collaboration| Children's Pediatric Cardiology Collaboration with SCI/SPL/Northeastern]]==&lt;br /&gt;
&lt;br /&gt;
Collaboration with John Triedman, Matt Jolley, Dana Brooks, SCI.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| | [[Image:NITRC.png|thumb|left|300px]]&lt;br /&gt;
| |&lt;br /&gt;
==[[NA-MIC and NITRC| NA-MIC Collaboration with NITRC]]==&lt;br /&gt;
&lt;br /&gt;
The NA-MIC Project is working to make NA-MIC neuroimaging software available through the [http://www.nitrc.org/ NITRC web site].  Supplemental support is helping to create the [[Slicer3:Loadable_Modules | Slicer3 Loadable Modules]] project so that slicer plugins can be hosted on NITRC, allowing greater scalability for developers and users of Slicer.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| | [[Image:Logo_nac.gif|thumb|left|100px|[http://nac.spl.harvard.edu NAC website]]]&lt;br /&gt;
| |&lt;br /&gt;
&lt;br /&gt;
==[[Collaboration:NAC| NA-MIC Collaboration with NAC]]==&lt;br /&gt;
&lt;br /&gt;
NAC, the neuroimage analysis center, is a national resource center. NAC is relying on the NA-MIC kit for its general software environment. The mission of NAC is to develop novel concepts for the analysis of images of the brain and develop and disseminate tools based on those concepts.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| | [[Image:Ncigtlogo.gif|thumb|left|100px]]&lt;br /&gt;
| |&lt;br /&gt;
&lt;br /&gt;
==[[Collaboration:NCIGT| NA-MIC Collaboration with NCIGT]]==&lt;br /&gt;
&lt;br /&gt;
Here are a couple of sentences to summarize the nature of the NA-MIC Collaboration with NCIGT.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:AISTlogo.gif|thumb|left|100px]]&lt;br /&gt;
&lt;br /&gt;
==[[Collaboration:AIST| NA-MIC Collaboration with Research and Development Project on Intelligent Surgical Instruments]]==&lt;br /&gt;
&lt;br /&gt;
Intelligent Surgical Instruments Projects uses Open-source software engineering tools developed by NA-MIC, and leverage it to surgical robotics.&lt;/div&gt;</summary>
		<author><name>Lantiga</name></author>
		
	</entry>
</feed>