Difference between revisions of "Events:Registration Summit August 2009"

From NAMIC Wiki
Jump to: navigation, search
Line 60: Line 60:
 
* kidney MR to CT -- will make available
 
* kidney MR to CT -- will make available
 
* pet CT to Pet CT -- [[File:2009-08-PETCT.zip|see here]] question: what changed between the two time points. Load scene and move the slider in slice views panel.
 
* pet CT to Pet CT -- [[File:2009-08-PETCT.zip|see here]] question: what changed between the two time points. Load scene and move the slider in slice views panel.
 +
* knee registration for Simbios project -- http://slicer.spl.harvard.edu/slicerWiki/index.php/Stanford_Simbios_group
  
 
== Slicer-compatible add-on registration modules ==
 
== Slicer-compatible add-on registration modules ==

Revision as of 17:39, 21 August 2009

Home < Events:Registration Summit August 2009

Agenda

  • Attendees: Casey Goodlett, Steve Pieper, Dominik Meier, Andriy Fedorov, Ron Kikinis, Sylvain Jaume
  • Date and place: Friday, August 21, 1249 Boylston, 2nd floor conference room
  • Schedule
  1. 09:00-12:00 Review of registration in Slicer:
    1. What input is the user asked to provide and in what form.
    2. Does a standard user understand what they are supposed to provide?
    3. What does the user expect registration results to look like?
    4. Bias correction
    5. histogram normalization
    6. handling image distortion (EPI)
    7. capture range and start pose
    8. ROI/VOI
    9. greyscale versus segmentation (binaries, surface models)
    10. inter subject versus intrasubject
    11. List of modules:
      1. transformation module
      2. linear registration
      3. rigid registration
      4. affine registration
      5. b-spline registration
      6. register images
      7. Utah b-spline
      8. VMTK/Python ICP
      9. ACPC registration
  2. 12:00-01:00 Lunch
  3. 01:00-05:00 Making plans, use case scenarios, sample data sets, plan larger registration summit

Other items:

  • Workflow with Wendy
  • CUDA Implementation with Yogesh

Needs

  • Robust solutions
  • Clinical APIs as opposed to engineering APIs
  • Good default parameters
  • Modality recorded in the image class to automate use case and parameter selection
  • Fast techniques for interactive investigations
  • Non-interactive techniques can run longer
  • Transform IO to all modules (mapping RAS to LPS as needed)
  • Ability to apply estimated transforms to other types of data
  • Region of interest registration (anything from a brain mask to a structure segmentation)
  • Validation datasets
  • Regression testing of registration accuracy

References

Bundled Registration and Tests

Some Sample data

Slicer-compatible add-on registration modules

Comprehensive evaluations of registration tools

In-house evaluations of registration tools