Summer ITKv4 ClinicalGroupMeetingNotes: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
No edit summary
No edit summary
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Lesion Sizing Toolkit ==
== Overlap and Similarity ==
Inputs: dicom
* Level of integration questions.
Outputs: measures of volumes, segmentations
* Bridges to 3rd party libs
* Distribution questions: How to build/package with 3rd party libs. How to distribute data.
 
== ITKv4 Features ==
* GPU
* Registration framework


* Already in ITK as an external module.  Contract is to reimplement with ITKv4 and distribute.
== 3D Real-Time Physics-Based Non-Rigid Registration for Image Guided Neurosurgery ==
The following is a rough pipeline of the method with proposed classes.
<br><br>
<b>Contributions:</b> New filters, classes.  Application?<br>
<b>Inputs:</b> a segmentation mask, a mesh
<b>Outputs:</b> deformation field, transformed image(s)<br>
# FeaturePointSelection3dFilter:  No dependencies.  Plan to start implementation with this filter.  
# BlockMatching3Dfilter: Similar to Penn FEM registration classes?  Perhaps only need to implement a new metric? Plan to use the GPU infrastructure, but also have a non GPU version.
# PBMSolver: PETSc dependence
# ImageWarp: Already in ITK


* Using spatial objects as inputs and outputs
<b>What support is needed?</b>
* Should some of these algorithms be migrated into ITK proper? (e.g. enhanced canny edge detection)
* CMake integration w/ PETSc and MPI.  Build / distribution issues.
* Further discussion and collaboration with the FEM, registration, and GPU groups.


What support it needed?
<b>Gaps:</b>
* Does ITK want a tighter integration of these classes, and in this same form? Does this cover more general concepts useful to other groups.
* Mesh generation. Tetmesh reader / converter?  Use Biomesh3D and bridge to ITK?
* Self-updating transform object
* PETSc & MPI within an ITK filter?


Gaps:
<b>Data:</b>
* Representing measures as a concept in ITK
* Sample dataset for testing.


Data: 60 datasets. Chest CT scans 1mm resolution. 200mb each. MIDAS? Store as DICOM?  Automatically download using CTest.
<b>Distribution:</b>
External module?


== 3D Real-Time Physics-Based Non-Rigid Registration for Image Guided Neurosurgery (PBMNRRegistration) ==
== Lesion Sizing Toolkit ==
<b>Contributions:</b> Functioning toolkit and application.  Possibly new ITK filters classes.  Data.
* Already in ITK as an external module.  Contract is to port to use ITKv4 and distribute.
* Using spatial objects as inputs and outputs <br>
<b>Inputs:</b> DICOM
<b>Outputs:</b> Lesion volume measurements and segmentations.<br>


The following is a rough pipeline of the method with proposed classes.
<b>What support is needed?</b>
(segmentation -> mesh gen -> registration -> petsc -> generate image (deformation field))
* Does ITK want a tighter integration of these classes, and in this same form?  Does this cover more general concepts useful to other groups.  e.g. Enhanced canny edge detection
Inputs: a mask, a mesh


1) FeaturePointSelection3dFilter(mask, fixed image): start with this filter
<b>Gaps:</b>
2) BlockMatching3Dfilter(fixed, moving, metrics,feature points) -- GPU, similar to penn fem registration classes, maybe metric plug in
* Representing measures as a concept in ITK
3) PBMSolver(displacement vector, mesh) --petsc dependence
* Annotations / metadata
4) ImageWarp--already in ITK


Outputs: deformation field, transformed image(s)
<b>Data:</b> 60 datasets. Chest CT scans 1mm resolution. 200mb each. MIDAS?  Store as DICOM?  Automatically download using CTest.


Gaps:
<b>Distribution:</b> Currently external module.  More integration?
* Mesh generation, tetmesh reader / converter: Biomesh3D and bridge to ITK?
* ITK Mesh
* Self-updating transform object
* Integration of solver
* MPI with ITK?


What support is needed?
== ITK Algorithms for Analyzing Time-Varying Shape with Application to Longitudinal Heart Modeling ==
* CMake integration w/ petsc (uses MPI). Build / distribution
<b>Contributions:</b> New ITK module (particle system), filters, classes.<br>
* Interface w/ FEM guys, registration & GPU guys
<b>Inputs:</b> Segmentations
<b>Outputs:</b> Point sets<br>


* Uses the core of an existing code base built from ITK: [http://www.nitrc.org/projects/shapeworks ShapeWorks NITRC Repository]
* Port significant portions to ITKv4
* New ParticleSystem module.  New ITK filter process objects.
* Procrustes registration
* Generic infrastructure for point-based surface representations
* Cross-sectional and longitudinal analysis


== ITK Algorithms for Analyzing Time-Varying Shape with Application to Longitudinal Heart Modeling ==
<b>What support is needed?</b>
* Logistics of integration and distribution, including data.
* Future: support for mesh representation, GPU


Data:  
<b>Data:</b>
* 25 longitudinal cardiac DE-MRI (1.25mm in-plane, 2.5mm thick) with segmentations of the left atrium.  2-4 datapoints each (pre ablation, 3mo, 6mo, 1 year)
* 25 longitudinal cardiac DE-MRI (1.25mm in-plane, 2.5mm thick) with segmentations of the left atrium.  2-4 datapoints each (pre ablation, 3mo, 6mo, 1 year)
* Need IRB to release image data
* Need IRB to release image data


Gaps:  
<b>Gaps:</b>
* Multivariate stats.
* Multivariate stats:  Bridge to R for complex statistical analysis without going to file system. Only implement what is needed for within ITK algorithms.
* Bridge to R for complex statistical analysis without going to file system.
 
<b>Distribution:</b>
ITK Module.  Test applications.  Integration with third party applications (ShapeWorks)

Latest revision as of 19:41, 27 June 2011

Overlap and Similarity

  • Level of integration questions.
  • Bridges to 3rd party libs
  • Distribution questions: How to build/package with 3rd party libs. How to distribute data.

ITKv4 Features

  • GPU
  • Registration framework

3D Real-Time Physics-Based Non-Rigid Registration for Image Guided Neurosurgery

The following is a rough pipeline of the method with proposed classes.

Contributions: New filters, classes. Application?
Inputs: a segmentation mask, a mesh Outputs: deformation field, transformed image(s)

  1. FeaturePointSelection3dFilter: No dependencies. Plan to start implementation with this filter.
  2. BlockMatching3Dfilter: Similar to Penn FEM registration classes? Perhaps only need to implement a new metric? Plan to use the GPU infrastructure, but also have a non GPU version.
  3. PBMSolver: PETSc dependence
  4. ImageWarp: Already in ITK

What support is needed?

  • CMake integration w/ PETSc and MPI. Build / distribution issues.
  • Further discussion and collaboration with the FEM, registration, and GPU groups.

Gaps:

  • Mesh generation. Tetmesh reader / converter? Use Biomesh3D and bridge to ITK?
  • Self-updating transform object
  • PETSc & MPI within an ITK filter?

Data:

  • Sample dataset for testing.

Distribution: External module?

Lesion Sizing Toolkit

Contributions: Functioning toolkit and application. Possibly new ITK filters classes. Data.

  • Already in ITK as an external module. Contract is to port to use ITKv4 and distribute.
  • Using spatial objects as inputs and outputs

Inputs: DICOM Outputs: Lesion volume measurements and segmentations.

What support is needed?

  • Does ITK want a tighter integration of these classes, and in this same form? Does this cover more general concepts useful to other groups. e.g. Enhanced canny edge detection

Gaps:

  • Representing measures as a concept in ITK
  • Annotations / metadata

Data: 60 datasets. Chest CT scans 1mm resolution. 200mb each. MIDAS? Store as DICOM? Automatically download using CTest.

Distribution: Currently external module. More integration?

ITK Algorithms for Analyzing Time-Varying Shape with Application to Longitudinal Heart Modeling

Contributions: New ITK module (particle system), filters, classes.
Inputs: Segmentations Outputs: Point sets

  • Uses the core of an existing code base built from ITK: ShapeWorks NITRC Repository
  • Port significant portions to ITKv4
  • New ParticleSystem module. New ITK filter process objects.
  • Procrustes registration
  • Generic infrastructure for point-based surface representations
  • Cross-sectional and longitudinal analysis

What support is needed?

  • Logistics of integration and distribution, including data.
  • Future: support for mesh representation, GPU

Data:

  • 25 longitudinal cardiac DE-MRI (1.25mm in-plane, 2.5mm thick) with segmentations of the left atrium. 2-4 datapoints each (pre ablation, 3mo, 6mo, 1 year)
  • Need IRB to release image data

Gaps:

  • Multivariate stats: Bridge to R for complex statistical analysis without going to file system. Only implement what is needed for within ITK algorithms.

Distribution: ITK Module. Test applications. Integration with third party applications (ShapeWorks)

Retrieved from "https://public.kitware.com/Wiki/index.php?title=Summer_ITKv4_ClinicalGroupMeetingNotes&oldid=41276"