Difference between revisions of "Project Week 25/Slice-to-Volume Registration to Support MRI guided Interventions"

From NAMIC Wiki
Jump to: navigation, search
 
(4 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
==Key Investigators==
 
==Key Investigators==
 
<!-- Key Investigator bullet points -->
 
<!-- Key Investigator bullet points -->
*[http://isgwww.cs.uni-magdeburg.de/cas/team.php Gino Gulamhussene] (University of Magdeburg, Germany)
+
*[http://isgwww.cs.uni-magdeburg.de/isg/gulamhussene.html Gino Gulamhussene] (University of Magdeburg, Germany)
 
*[http://perk.cs.queensu.ca/users/lasso Andras Lasso] (Queen's University, Canada)
 
*[http://perk.cs.queensu.ca/users/lasso Andras Lasso] (Queen's University, Canada)
  
Line 24: Line 24:
  
 
|<!-- Progress and Next steps (fill out at the end of project week), bullet points -->
 
|<!-- Progress and Next steps (fill out at the end of project week), bullet points -->
 +
'''Progress'''
 
* discussed the motivation for non-regit registration of planing MRI/CT to iMRI/iCT
 
* discussed the motivation for non-regit registration of planing MRI/CT to iMRI/iCT
 
** reducing the need of contrast agend administration in both iMRI and iCT
 
** reducing the need of contrast agend administration in both iMRI and iCT
Line 32: Line 33:
 
* I got insights into the development with and for Slicer
 
* I got insights into the development with and for Slicer
 
* I started to implement a python Slicer Extension to automate the previously found workflow using several aspects of slicer (CLI, Python Scripting, simpleITK, sitkUtils)
 
* I started to implement a python Slicer Extension to automate the previously found workflow using several aspects of slicer (CLI, Python Scripting, simpleITK, sitkUtils)
 +
'''Next Steps'''
 +
* finishing the Slicer extension
 +
* implementing a way to generate ground truth (simulated respiration deformation in iMRI)
 +
* implementing the evaluation tools (visual inspection and computed metrics)
 
|}
 
|}
  
Line 37: Line 42:
 
<!-- https://www.slicer.org/img/Slicer4Announcement-HiRes.png -->
 
<!-- https://www.slicer.org/img/Slicer4Announcement-HiRes.png -->
 
<!-- <embedvideo service="youtube">https://www.youtube.com/watch?v=MKLWzD0PiIc</embedvideo> -->
 
<!-- <embedvideo service="youtube">https://www.youtube.com/watch?v=MKLWzD0PiIc</embedvideo> -->
 +
<gallery>
 +
File:SlicerSmall.png | non-regid transformation result
 +
</gallery>
  
 
==Background and References==
 
==Background and References==
 
<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->
 
<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->
 
* [[2011_Winter_Project_Week:Intra-ProceduralProstateMotion]]
 
* [[2011_Winter_Project_Week:Intra-ProceduralProstateMotion]]

Latest revision as of 13:57, 5 July 2017

Home < Project Week 25 < Slice-to-Volume Registration to Support MRI guided Interventions


Back to Projects List

Key Investigators

Project Description

Objective Approach and Plan Progress and Next Steps
  • The objective of this project is to drive the discussion under which circumstances medical image registration can be used to support MRI guided liver interventions.
  • Furthermore a simple implementation of a state of the art method to register iMRI to MRI shall show the principle possibility of such an approach.
  • discuss the applicability of Slice-to-Volume registration of intra-interventional MRI to pre-interventional MRI to support liver interventions. (insights from radiologists would be valuable)
  • give an overview of factors that determin the applicability of (StV) registration to support liver interventions in MRI
  • implement state of the art algorithm to register orthogonal iMRI slices to MRI volume

Progress

  • discussed the motivation for non-regit registration of planing MRI/CT to iMRI/iCT
    • reducing the need of contrast agend administration in both iMRI and iCT
    • providing any additional information that is either containt in planning data or added / annotated in its reference frame
    • providing additional information from other modalities like PET (Pre-fusing several planing volumes)
    • reducing mental effort for interventionalist
  • I got showed a manual workflow in Slicer to solve the basic task with state of the art methods
  • I got insights into the development with and for Slicer
  • I started to implement a python Slicer Extension to automate the previously found workflow using several aspects of slicer (CLI, Python Scripting, simpleITK, sitkUtils)

Next Steps

  • finishing the Slicer extension
  • implementing a way to generate ground truth (simulated respiration deformation in iMRI)
  • implementing the evaluation tools (visual inspection and computed metrics)

Illustrations

Background and References