View source for 2015 BRAINSFit registration in SimpleITK

__NOTOC__
{|
| Case 9
|[[Image:pat9-ref.png‎ |thumb|300px|Reference intraop volume]] 
|[[Image:pat9-3_6.png|thumb|300px|Reg Result Slicer 3.6 with ITKv3]] 
|[[Image:pat9-4_4.png|thumb|300px|Reg Result Slicer 4.4 with ITKv4]] 
|}

==Key Investigators==
* Peter Behringer
* Andriy Fedorov

==Project Description==
<div style="margin: 20px;">
<div style="width: 27%; float: left; padding-right: 3%;">
<h3>Objective</h3>
* Our registration module for b-spline deformable registration of prostate MRI uses BRAINSFit in Slicer4/ITKv4. 
* One issue that we are getting with Slicer4/ITKv4 is that they are a lot more irregular and unrealistic than what we used to get in Slicer3/ITKv3 (see summary [http://www.na-mic.org/Wiki/index.php/BRAINSFit_prostate_registration here])
* The Slicer4/ITKv4 registration tool should be comparable with the functionality we had in Slicer3/ITKv3, which was evaluated [http://onlinelibrary.wiley.com/doi/10.1002/jmri.23688/abstract;jsessionid=F9AADC56E72CA73A422B9C09728F7E81.f01t03 here]

</div>
<div style="width: 27%; float: left; padding-right: 3%;">
<h3>Approach, Plan</h3>
* Implement a subset of BRAINSFit functionality used for supporting in-bore MRI-guided prostate biopsy in SimpleITK
* Get ideas from the community how the irregularity can be avoided and implemented in SimpleITK
</div>
<div style="width: 27%; float: left; padding-right: 3%;">
<h3>Progress</h3>
* Initialization and rigid registration is implemented using SimpleITK
</div>
</div>