Difference between revisions of "2016 Winter Project Week/Projects/Tractography format interoperability"

From NAMIC Wiki
Jump to: navigation, search
Line 18: Line 18:
 
|
 
|
 
* Aim 1: Develop DCMTK and Slicer support for DICOM tractography objects (supplement 181).
 
* Aim 1: Develop DCMTK and Slicer support for DICOM tractography objects (supplement 181).
* Aim 2: Develop Slicer support for DiPy's HDF5-based "dpy" tract format.
+
* Aim 2: Develop Slicer support for DiPy tractography i/o.
 
|
 
|
 
* Aim 1:  
 
* Aim 1:  
 
** planning emails and data exchange before project week.
 
** planning emails and data exchange before project week.
 
** prototype DCMTK support for supplement 181.
 
** prototype DCMTK support for supplement 181.
** implement Slicer interface to load objects and metadata from DCMTK into tractography nodes.
+
** (implement Slicer interface to load objects and metadata from DCMTK into tractography nodes?)
 
* Aim 2:  
 
* Aim 2:  
** utilize VTK's built-in HDF support to read and write dpy files.
+
** implement support for DPY and TrackVis tractography file formats.
** write adapters to interface data and metadata with tractography MRML nodes.
 
 
|
 
|
*
+
* Aim 1:
 +
** productive discussions explaining data processing and structure.
 +
** designed high-level DCMTK API for accessing tractography objects.
 +
* Aim 2:
 +
** Prototyped stand-alone TrackVis reader (custom binary format)
  
 
|}
 
|}

Revision as of 14:30, 8 January 2016

Home < 2016 Winter Project Week < Projects < Tractography format interoperability

Key Investigators

  • Michael Onken, OFFIS
  • Isaiah Norton, BWH
  • Lauren O'Donnell, BWH

Project Description

Objective Approach and Plan Progress and Next Steps
  • Aim 1: Develop DCMTK and Slicer support for DICOM tractography objects (supplement 181).
  • Aim 2: Develop Slicer support for DiPy tractography i/o.
  • Aim 1:
    • planning emails and data exchange before project week.
    • prototype DCMTK support for supplement 181.
    • (implement Slicer interface to load objects and metadata from DCMTK into tractography nodes?)
  • Aim 2:
    • implement support for DPY and TrackVis tractography file formats.
  • Aim 1:
    • productive discussions explaining data processing and structure.
    • designed high-level DCMTK API for accessing tractography objects.
  • Aim 2:
    • Prototyped stand-alone TrackVis reader (custom binary format)

Background and References

DICOM Supplement 181