Difference between revisions of "2011 Winter Project Week:RegistrationCaseLibrary"

From NAMIC Wiki
Jump to: navigation, search
 
(4 intermediate revisions by the same user not shown)
Line 21: Line 21:
 
<h3>Approach, Plan</h3>
 
<h3>Approach, Plan</h3>
  
The use case library relies mainly on user contributions for content. There is an [[Projects:RegistrationDocumentation:UseCaseAdvertisement|'''official call for datasets''']]  to all slicer users to consider a unique time-limited service for any dataset/registration problem that is not yet in the library. Users who agree to share one '''anonymized''' dataset for the library will have that dataset registered by us and the solution and strategies posted.  [[Projects:RegistrationDocumentation:UseCaseExample1b|Look here for an example of a library entry.]]
+
The ''Slicer Registration Library'' relies mainly on user contributions for content. There is an [[Projects:RegistrationDocumentation:UseCaseAdvertisement|'''official call for datasets''']]  to all slicer users to consider a unique time-limited service for any dataset/registration problem that is not yet in the library. Users who agree to share one '''anonymized''' dataset for the library will have that dataset registered by us and the solution and strategies posted.  [[Projects:RegistrationDocumentation:UseCaseExample1b|Look here for an example of a library entry.]]
 
<br>
 
<br>
 
Our plan for the project week is to first  get a survey of all projects using registration. We hope to catch most of these projects from reviewing these project description pages, so it is important that if you use registration in your procedure, please make sure to mention explicitly.  We will collect as many example cases as possible, and select a few focus cases with particularly vexing registration challenges and begin to develop the appropriate tailored registration strategies.   
 
Our plan for the project week is to first  get a survey of all projects using registration. We hope to catch most of these projects from reviewing these project description pages, so it is important that if you use registration in your procedure, please make sure to mention explicitly.  We will collect as many example cases as possible, and select a few focus cases with particularly vexing registration challenges and begin to develop the appropriate tailored registration strategies.   
Line 31: Line 31:
  
 
<h3>Progress</h3>
 
<h3>Progress</h3>
*see below for list of projects/contacts for new use cases: [[2011_Winter_Project_Week:RegistrationCaseLibrary#Target Projects]]
+
* use of ITK registration cost function to validate FE-based model of intraoperative brainshift -> expose ITK cost function: develop a user module to measure/visualize MI over a specified region
 +
* DTI to freesurfer labelmap
 +
* atlas-based registration/classification (prodcedure for translating physical alignment to image-space congruence)
 
</div>
 
</div>
 
</div>
 
</div>
  
 
<div style="width: 97%; float: left;">
 
<div style="width: 97%; float: left;">
=== Progress: Target Projects ===
 
The following projects below have been tentatively identified as having strong registration ties. We will seek discussion with these projects during the week. If your project is listed here, I will try to discuss the registration aspects at some point during the week.  Type and length of discussion will vary greatly. Text next to each project below identifies the registration link.
 
 
  project links go here
 
  
 
=== Progress: Notes ===
 
=== Progress: Notes ===

Latest revision as of 14:47, 14 January 2011

Home < 2011 Winter Project Week:RegistrationCaseLibrary

Registration Case Library ____ Registration Case Library Table

The 3DSlicer Registration Case Library Project

Key Investigators

  • BWH: Dominik Meier, Ron Kikinis

Objective

This work is part of a 2-year effort to supplement the 3DSlicer Registration Module with extensive set of documentation, tutorials and use case scenarios. We seek to build a comprehensive library of use cases for every form of registration challenge using 3DSlicer. Each library entry will contain a dataset along with Registration Parameter Presets and a guided tutorial on how to successfully register the images.


Approach, Plan

The Slicer Registration Library relies mainly on user contributions for content. There is an official call for datasets to all slicer users to consider a unique time-limited service for any dataset/registration problem that is not yet in the library. Users who agree to share one anonymized dataset for the library will have that dataset registered by us and the solution and strategies posted. Look here for an example of a library entry.
Our plan for the project week is to first get a survey of all projects using registration. We hope to catch most of these projects from reviewing these project description pages, so it is important that if you use registration in your procedure, please make sure to mention explicitly. We will collect as many example cases as possible, and select a few focus cases with particularly vexing registration challenges and begin to develop the appropriate tailored registration strategies.

Progress

  • use of ITK registration cost function to validate FE-based model of intraoperative brainshift -> expose ITK cost function: develop a user module to measure/visualize MI over a specified region
  • DTI to freesurfer labelmap
  • atlas-based registration/classification (prodcedure for translating physical alignment to image-space congruence)