Difference between revisions of "2012 Summer Project Week:Nipype Integration"
From NAMIC Wiki
(Template) |
(Flushing out project page) |
||
Line 2: | Line 2: | ||
<gallery> | <gallery> | ||
Image:PW-MIT2012.png|[[2012_Summer_Project_Week#Projects|Projects List]] | Image:PW-MIT2012.png|[[2012_Summer_Project_Week#Projects|Projects List]] | ||
− | |||
− | |||
</gallery> | </gallery> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Key Investigators== | ==Key Investigators== | ||
− | * | + | * UIowa: Hans Johnson |
− | |||
<div style="margin: 20px;"> | <div style="margin: 20px;"> | ||
Line 21: | Line 11: | ||
<h3>Objective</h3> | <h3>Objective</h3> | ||
− | + | Nipype is a flexible, uniform interface to existing neuroimaging software that allows interaction between these packages within a single workflow. Our objective is to improve on Nipype's interaction with Slicer, with the goal of being able to pass scripts to Slicer's python interface that allow pipeline development within Slicer. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</div> | </div> | ||
Line 33: | Line 17: | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
− | + | TODO | |
− | |||
− | |||
− | |||
</div> | </div> | ||
Line 43: | Line 24: | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
− | + | N/A | |
− | |||
</div> | </div> | ||
</div> | </div> | ||
− | |||
− | |||
==Delivery Mechanism== | ==Delivery Mechanism== | ||
Line 63: | Line 41: | ||
==References== | ==References== | ||
− | * | + | * Nipype: http://nipy.sourceforge.net/nipype/ [http://nipy.sourceforge.net/nipype/] |
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 21:14, 22 May 2012
Home < 2012 Summer Project Week:Nipype IntegrationKey Investigators
- UIowa: Hans Johnson
Objective
Nipype is a flexible, uniform interface to existing neuroimaging software that allows interaction between these packages within a single workflow. Our objective is to improve on Nipype's interaction with Slicer, with the goal of being able to pass scripts to Slicer's python interface that allow pipeline development within Slicer.
Approach, Plan
TODO
Progress
N/A
Delivery Mechanism
This work will be delivered to the NA-MIC Kit as a (please select the appropriate options by noting YES against them below)
- ITK Module
- Slicer Module
- Built-in
- Extension -- commandline
- Extension -- loadable
- Other (Please specify)