Difference between revisions of "Slicer3:MiniRetreat February 5-7, 2008"

From NAMIC Wiki
Jump to: navigation, search
Line 10: Line 10:
 
** Need a VTK transform to wrap an ITK B-spline transform
 
** Need a VTK transform to wrap an ITK B-spline transform
 
** Modeling transforms verses imaging transforms.  What transform should Slicer have in the scene? Should volumes be placed under transforms automatically?
 
** Modeling transforms verses imaging transforms.  What transform should Slicer have in the scene? Should volumes be placed under transforms automatically?
 +
** Need to ensure that the Slicer GUI experience with the registration modules and transforms is "consistent" with the Slicer command line experience.
 
* ModuleFactoryTest hanging
 
* ModuleFactoryTest hanging
 
** FIXED.  Path issue when exec'ing modules with --xml
 
** FIXED.  Path issue when exec'ing modules with --xml
 
* <More on Steve's paper checklist...>
 
* <More on Steve's paper checklist...>

Revision as of 21:57, 5 February 2008

Home < Slicer3:MiniRetreat February 5-7, 2008

Jim Miller will meet with Steve Pieper and company on Feb. 5-7, 2007 for a mini-retreat. This will be a detailed work session focusing on the following topics:

  • Time series visualization
    • More Slice Viewers than (red, green, yellow) + specific layout of the screen + more control over linked parameters
  • Layout manager
    • More options for user to pick/define layouts (number and layout of screen areas, what to show in an area)
  • B-spline transform and registration support
    • Need to fix B-spline CLI module
    • Need a MRML node for B-spline transforms
    • Need a VTK transform to wrap an ITK B-spline transform
    • Modeling transforms verses imaging transforms. What transform should Slicer have in the scene? Should volumes be placed under transforms automatically?
    • Need to ensure that the Slicer GUI experience with the registration modules and transforms is "consistent" with the Slicer command line experience.
  • ModuleFactoryTest hanging
    • FIXED. Path issue when exec'ing modules with --xml
  • <More on Steve's paper checklist...>