KWScene/Documentation/JHU 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?

Other general open questions

• Annotations: scenario evoked by Joe Hennessey involving .vti format. (What is JHU, what is Kitware?)

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

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.

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.
    • kwsITKImageNodeGeneratorTestAnalyze
      • open Analyze file of JHU right ventricle data, and report image size; fail if wrong size (not 256x256x256).

Doxygen

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