Algorithms:Core1Visit May06:Core2

Slicer 3

• Goals of Slicer 3
  • Address Legacy Issues
  • Simplify Module Writing
• What does Core 2 do for Core 1?
  • Core 2 provides an environment and fills gaps in that environment
  • Core 1 implements algorithms to that environment
  • Core 2 may do "last mile" integration.
  • Lot's of Core 1 frustration integrating with Slicer 2.x
    • Resulted in small focused applications - complete with GUI - being developed by Core 1 and deployed to Core 3
    • Need to fold these back into Slicer 3.x
• How to interface to other research platforms?
• How are Core 3 feature requests prioritized by Core 2?
• Command line execution model
  • "There must be something wrong with this..." - Polina
• License issues
  • Why not Qt?
    • KWWidgets license preferred over QT license
    • Should we document NA-MIC's position on Qt for Slicer?
  • How to contribute/distribute modules that are not licensed in a NA-MIC compatible way
    • Core 1 can develop algorithms in their preferred environment
    • Core 2 helps Core 1 migrate their algorithms into NA-MIC licensed modules
    • Need to define whos responsible for implementing algorithms as a NA-MIC deliverable
• Feature requests
  • Image Editor - Are there existing tools we can use? ITK-SNAP?
    • Is this a good use of resources?
• Autommated GUI development
• Middle level between UI driven processing and command line processing
  • UI driven processing (interaction) needs Core 2 support (Slicer resources)
  • Command line driven processing can be done by Core 1 alone once the infrastructure is finished
  • How many modules will fall in the middle ground?
• Need to integrate Xiaodong's tensor estimation into Slicer (coordinate frame issues)