Difference between revisions of "2015 BRAINSFit registration in SimpleITK"

From NAMIC Wiki
Jump to: navigation, search
(Created page with '__NOTOC__ <gallery> Image:PW-Summer2015.png|Projects List </gallery> ==Key Investigators== * Peter Behringer * Andriy Fedorov ==Project De…')
 
Line 20: Line 20:
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Approach, Plan</h3>
 
<h3>Approach, Plan</h3>
* Present the module to interested members of the community
+
* Implement BRAINSFit functionality in SimpleITK
* Get feedback about the workflow and usability
+
* Get ideas from the community how the irregularity can be avoided and implemented in SimpleITK
* Identify potential additional use cases and functionalities that make the module more generic
 
 
</div>
 
</div>
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Progress</h3>
 
<h3>Progress</h3>
* Initialization and rigid registration phase is functional
+
* Initialization and rigid registration is implemented using SimpleITK
 
</div>
 
</div>
 
</div>
 
</div>

Revision as of 18:47, 4 June 2015

Home < 2015 BRAINSFit registration in SimpleITK

Key Investigators

  • Peter Behringer
  • Andriy Fedorov

Project Description

Objective

  • Our registration module for b-spline deformable registration of prostate MRI uses BRAINSFit in Slicer4/ITKv4.
  • One issue that we are getting with ITKv4 is that are a lot more irregular and unrealistic than what we used to get in ITKv3 (see summary here
  • The Slicer4/ITKv4 registration tool should be comparable with the functionality we had in Slicer3/ITKv3, which was evaluated here

Approach, Plan

  • Implement BRAINSFit functionality in SimpleITK
  • Get ideas from the community how the irregularity can be avoided and implemented in SimpleITK

Progress

  • Initialization and rigid registration is implemented using SimpleITK