KWScene/Documentation/JHU Open Questions: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
No edit summary
No edit summary
 
(17 intermediate revisions by the same user not shown)
Line 1: Line 1:
=== Open Questions ===
= Open Questions =


== Planned use-cases under Paraview ==  
= Planned use-cases under Paraview =  


* VTK-based visualization feasible, but... Use-case for ITK-based image analysis? (Also Paraview-based?)
* VTK-based visualization feasible, but... Use-case for ITK-based image analysis? (Also Paraview-based?)
* Structure & use-case of writing classes?
* Structure & use-case of writing classes?
== Other general open questions ==
* Annotations: scenario evoked by Joe Hennessey involving .vti format. (What are JHU tasks, what are Kitware tasks?)
* Annotations: scenario evoked by Joe Hennessey involving .vti format. (What are JHU tasks, what are Kitware tasks?)
https://mail.google.com/a/kitware.com/#search/vti+file/127d01aa4fe98047
https://mail.google.com/a/kitware.com/#search/vti+file/127d01aa4fe98047
* Relevance Transform nodes? (JHU data seems to be in one common image-based reference space...)


== Remaining formats to develop and test ==  
= Remaining formats to develop and test =  


* Scalar-valued data  
* Scalar-valued data  
Line 23: Line 21:
* Landmarks
* Landmarks
** Comes in both .lmk and .vti file formats.  
** Comes in both .lmk and .vti file formats.  
**
 
* Annotations
* Annotations
** No data. Described by J. Hennessey as feasible in .vti file format.
** No data. Described by J. Hennessey as feasible in .vti file format.


== Successful Tests ==
= Integrating new readers: vtkAnalyzeReader, vtkTransformFileReader, itkBYUReader.txx =
* Some new readers needed for KWScene, e.g. vtkAnalyzeImageReader, vtkTransformFileReader, itkBYUReader.txx, may also be needed for Paraview.
* How to best integrate for both KWScene and Paraview?
 
= Valgrind =
* Just begun. Some issues with XML2 library.
 
= Doxygen =
*Just begun. Need to flesh out entry for existing classes.
 
= GIT =
* Transition from SVN to GIT?
 
= Other general open questions =
* Transform Nodes.
 
= Successful tests =


* Scalar-valued data  
* Scalar-valued data  
Line 44: Line 58:
*** kwsVTKAnalyzeImageGeneratorTest3
*** kwsVTKAnalyzeImageGeneratorTest3
**** coverage: same as wsVTKAnalyzeImageGeneratorTest2, but use mrml file with .hdr instead of .img references
**** coverage: same as wsVTKAnalyzeImageGeneratorTest2, but use mrml file with .hdr instead of .img references
**
**
** ITK Generators
** ITK Generators
*** Analyze image: ITK Generators.  
*** Analyze image: ITK Generators.  
*** kwsITKImageNodeGeneratorTestAnalyze
*** kwsITKFactoryBasedImageNodeGeneratorAnalyzeTest
**** open Analyze file of JHU right ventricle data, and report image size; fail if wrong size (not 256x256x256).
**** open Analyze file of JHU right ventricle data, and report image size; fail if wrong size (not 256x256x256).
 
***
== Integrating new readers: vtkAnalyzeReader, vtkTransformFileReader, itkBYUReader.txx ==
*** BYU surface: ITK Generators.  
** Some new readers needed for KWScene, e.g. vtkAnalyzeImageReader, vtkTransformFileReader, itkBYUReader.txx, may also be needed for Paraview.
*** kwsITKBYUSurfaceNodeGeneratorTest1
** How to best integrate for both KWScene and Paraview?
**** coverage: instantiate a BYU reader, add it to scene, use a node generator based on this scene that generates BYU surface node.
 
== Valgrind ==
Just begun. Some issues with XML2 library.
 
== Doxygen ==
*Just begun. Need to flesh out entry for existing classes.

Latest revision as of 13:52, 26 April 2010

Open Questions

Planned use-cases under Paraview

  • VTK-based visualization feasible, but... Use-case for ITK-based image analysis? (Also Paraview-based?)
  • Structure & use-case of writing classes?
  • Annotations: scenario evoked by Joe Hennessey involving .vti format. (What are JHU tasks, what are Kitware tasks?)

https://mail.google.com/a/kitware.com/#search/vti+file/127d01aa4fe98047

  • Relevance Transform nodes? (JHU data seems to be in one common image-based reference space...)

Remaining formats to develop and test

  • Scalar-valued data
    • BYU surface: ITK Generators
      • On-going.
  • Vector-valued data
    • VTP surface: VTK & ITK Generators
    • VTI image: VTK & ITK Generators
  • Landmarks
    • Comes in both .lmk and .vti file formats.
  • Annotations
    • No data. Described by J. Hennessey as feasible in .vti file format.

Integrating new readers: vtkAnalyzeReader, vtkTransformFileReader, itkBYUReader.txx

  • Some new readers needed for KWScene, e.g. vtkAnalyzeImageReader, vtkTransformFileReader, itkBYUReader.txx, may also be needed for Paraview.
  • How to best integrate for both KWScene and Paraview?

Valgrind

  • Just begun. Some issues with XML2 library.

Doxygen

  • Just begun. Need to flesh out entry for existing classes.

GIT

  • Transition from SVN to GIT?

Other general open questions

  • Transform Nodes.

Successful tests

  • Scalar-valued data
    • VTK Generators
      • BYU surface: VTK Generators.
      • kwsVTKBYUSurfaceGeneratorTest1
        • render all surfaces from JHU atlas, itself downloaded from MIDAS.
      • Analyze image: VTK Generators.
      • kwsVTKAnalyzeImageGeneratorTest1
        • volume-render JHU right ventricle data
      • kwsVTKAnalyzeImageGeneratorTest2
        • coverage: open synthetic Analyze files of various pixel-type successfully, and report image size.
      • kwsVTKAnalyzeImageGeneratorTest3
        • coverage: same as wsVTKAnalyzeImageGeneratorTest2, but use mrml file with .hdr instead of .img references
    • ITK Generators
      • Analyze image: ITK Generators.
      • kwsITKFactoryBasedImageNodeGeneratorAnalyzeTest
        • open Analyze file of JHU right ventricle data, and report image size; fail if wrong size (not 256x256x256).
      • BYU surface: ITK Generators.
      • kwsITKBYUSurfaceNodeGeneratorTest1
        • coverage: instantiate a BYU reader, add it to scene, use a node generator based on this scene that generates BYU surface node.