Difference between revisions of "Special topic breakout: ITK"

From NAMIC Wiki
Jump to: navigation, search
Line 2: Line 2:
  
 
= Topics =
 
= Topics =
 +
 +
====From Gary:====
 
*How do you efficiently integrate VTK and ITK with respect to reading and writing images?  Is there one class that can be used to hold data sets for both libraries?
 
*How do you efficiently integrate VTK and ITK with respect to reading and writing images?  Is there one class that can be used to hold data sets for both libraries?
 
*How to do FFTs in ITK?
 
*How to do FFTs in ITK?
Line 9: Line 11:
 
*How are XML/MRML files parced in ITK/VTK? We want to know how to use the vtkXMLparser and MRML objects to parse our XML files.
 
*How are XML/MRML files parced in ITK/VTK? We want to know how to use the vtkXMLparser and MRML objects to parse our XML files.
 
*What are the memory and performance issues with ITK?
 
*What are the memory and performance issues with ITK?
 +
 +
I'd like to talk about how we can have a reader/writer for reading/writing images and their associated history/descriptions.  The history/description of the files could possibly be coded in XML/MRML.
  
  

Revision as of 20:42, 21 June 2007

Home < Special topic breakout: ITK

Tutorial Session on ITK

Topics

From Gary:

  • How do you efficiently integrate VTK and ITK with respect to reading and writing images? Is there one class that can be used to hold data sets for both libraries?
  • How to do FFTs in ITK?
  • What type of coordinate space should be used, voxels vs. real space?
  • What type of image formats should be used?
  • Is there any standard way to read in coefficient files, i.e., algorithm specific parameters?
  • How are XML/MRML files parced in ITK/VTK? We want to know how to use the vtkXMLparser and MRML objects to parse our XML files.
  • What are the memory and performance issues with ITK?

I'd like to talk about how we can have a reader/writer for reading/writing images and their associated history/descriptions. The history/description of the files could possibly be coded in XML/MRML.


Participants

  • Jeff Hawley
  • Kunlin Cao
  • Kai Ding
  • Xiujuan Geng
  • James Harris
  • Gary Christensen
  • Paul Song
  • Jake Nickel
  • Nick Kiguta