Difference between revisions of "2015 BRAINSFit registration in SimpleITK"

From NAMIC Wiki
Jump to: navigation, search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 +
 
{|
 
{|
| Case 9
+
| Case 25
|[[Image:pat9-ref.png‎ |thumb|300px|Reference intraop volume]]  
+
|[[Image:HighIrregulation.gif‎ |thumb|400px|High irregulations in ITKv4]]  
|[[Image:pat9-3_6.png|thumb|300px|Reg Result Slicer 3.6 with ITKv3]]
+
|[[Image:fixedIrregulations.gif|thumb|400px|Resolved Irregulations ins ITKv4]]  
|[[Image:pat9-4_4.png|thumb|300px|Reg Result Slicer 4.4 with ITKv4]]  
 
 
|}
 
|}
  
Line 29: Line 29:
 
<h3>Progress</h3>
 
<h3>Progress</h3>
 
* Initialization and rigid registration is implemented using SimpleITK
 
* Initialization and rigid registration is implemented using SimpleITK
 +
* We tracked the issue down using various parameters
 +
* We used strongly dilated masks for the BSpline registration and results are looking much better
 
</div>
 
</div>
 
</div>
 
</div>

Latest revision as of 14:48, 24 June 2015

Home < 2015 BRAINSFit registration in SimpleITK


Case 25
High irregulations in ITKv4
Resolved Irregulations ins ITKv4

Key Investigators

  • Peter Behringer
  • Andriy Fedorov
  • Dženan Zukić

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 Slicer4/ITKv4 is that they are a lot more irregular and unrealistic than what we used to get in Slicer3/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 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

Progress

  • Initialization and rigid registration is implemented using SimpleITK
  • We tracked the issue down using various parameters
  • We used strongly dilated masks for the BSpline registration and results are looking much better