Difference between revisions of "2010 Winter Project Week RegistrationCaseLibrary"

From NAMIC Wiki
Jump to: navigation, search
Line 52: Line 52:
 
**[[2010_Winter_Project_Week_Spine_Segmentation_Module_in_Slicer3|Spine Segmentation Module in Slicer3]] (Martin Loepprich): Does this involve co-registration of an atlas?
 
**[[2010_Winter_Project_Week_Spine_Segmentation_Module_in_Slicer3|Spine Segmentation Module in Slicer3]] (Martin Loepprich): Does this involve co-registration of an atlas?
 
**[[2010_Winter_Project_Week_SegmentationWizard|High Level Wizard for Segmentation of Images]] (Mark Scully): uses register images to align atlas; functionality and compatibility considerations for RegisterImages redesign (both algorithm & GUI)
 
**[[2010_Winter_Project_Week_SegmentationWizard|High Level Wizard for Segmentation of Images]] (Mark Scully): uses register images to align atlas; functionality and compatibility considerations for RegisterImages redesign (both algorithm & GUI)
**[[2010_Winter_Project_Week_LongitudinalLupusAnalyses|Longitudinal Analyses of Lesions in Lupus]] (Mark Scully): uses ChangeTracker which in turn uses registration?
+
**[[2010_Winter_Project_Week_LongitudinalLupusAnalyses|Longitudinal Analyses of Lesions in Lupus]] (Mark Scully): uses ChangeTracker which in turn uses registration. From the  [http://www.slicer.org/slicerWiki/index.php/Modules:ChangeTracker-Documentation-3.4. documentation]: ChangeTracker is using Rigid Registration module through the CommandLineModule shared object invocation. Note, that there are two distinct rigid registration modules in Slicer, which have identical functionality: "Linear registration" and "Rigid registration". Both of these modules should be available in your build, but "Rigid registration" *must* be available for ChangeTracker to function properly.
 
**[[2010_Winter_Project_Week_ProstateSeg|Prostate segmentation using shape-based method]] (Andras Lasso): Does this involve co-registration of an atlas?
 
**[[2010_Winter_Project_Week_ProstateSeg|Prostate segmentation using shape-based method]] (Andras Lasso): Does this involve co-registration of an atlas?
 
**[[2010_Winter_Project_Week_SegmentationEpicardialWall|Epicardial Wall Segmentation]] (Behnood Gholami): employs its own shape-registration scheme: each shape is registered to a fixed arbitrary shape in the training set using a mean-square error registration scheme.
 
**[[2010_Winter_Project_Week_SegmentationEpicardialWall|Epicardial Wall Segmentation]] (Behnood Gholami): employs its own shape-registration scheme: each shape is registered to a fixed arbitrary shape in the training set using a mean-square error registration scheme.

Revision as of 21:06, 14 December 2009

Home < 2010 Winter Project Week RegistrationCaseLibrary

The 3DSlicer Registration Case Library Project

Key Investigators

  • BWH: Dominik Meier, Ron Kikinis
  • Kitware: Casey Goodlett

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.


We also have a Registration Breakout Session on Tuesday 1-2pm (Amethyst Room). If registration is on your processing list, please drop in, have a look at what's new, and share your thoughts.


Approach, Plan

The use case 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

  • List of contacts for new use cases: see below
  • insights/comments on registration settings/setting changes that made a difference go here
  • Notes re. user insights/comments/wishes on registration go here


Progress: Target Projects

The projects below have been tentatively identified as having 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.

References