Difference between revisions of "Documentation/Labs/Slicer Visualization module"

From Slicer Wiki
Jump to: navigation, search
Line 19: Line 19:
  
 
<big>'''<big>Details</big>'''</big><br />
 
<big>'''<big>Details</big>'''</big><br />
 +
 +
The user will have the choice between the 2D and the 3D visualization module.
 +
First we will focus on the 3D module.
  
 
'''''User Inputs (3 ASCII files):'''''
 
'''''User Inputs (3 ASCII files):'''''
 
*Volume file
 
*Volume file
*Node file  
+
*Node file (and maybe add and option for the user to be able to edit the node characterization ;for example with labels)
 
*Edge file  
 
*Edge file  
 
The Node file and the Edge file will have to be adaptable formats, that is the reason why we want to use ASCII files.  
 
The Node file and the Edge file will have to be adaptable formats, that is the reason why we want to use ASCII files.  
The Node file should include information about where the node is located.  
+
The Node file should include information about where the node is located. <br />
 +
The file extension could either be a Landmark Registration format (existing module in Slicer)or a Jason file (including a node description file (x,y,z coordinates and node color index) and a node magnitude file(with just the size of a node)).  
  
 
'''''Features:'''''
 
'''''Features:'''''
 
* Python module (using VTK) and maybe C++
 
* Python module (using VTK) and maybe C++
 +
* Implement a 3D visualization tool that is faster than the BrainNetViewer and CIVILITY (based on Matlab).
 +
*
 +
 
* Implement a 2D spherical graph visualization (may apply Hierarchical Edge Bundling), using matrices  
 
* Implement a 2D spherical graph visualization (may apply Hierarchical Edge Bundling), using matrices  
 
* Custom graph view representing the associated matrix <br />
 
* Custom graph view representing the associated matrix <br />
 
(possible options: vtkMRMLGraphMarkupNode,vtkSlicerGraphRepresentation3D and associated widget (looking at vtkMRMLMarkupsCurveNode, vtkSlicerCurveRepresentation and vtkSlicerCurveWidget))
 
(possible options: vtkMRMLGraphMarkupNode,vtkSlicerGraphRepresentation3D and associated widget (looking at vtkMRMLMarkupsCurveNode, vtkSlicerCurveRepresentation and vtkSlicerCurveWidget))
* Implement a 3D visualization tool that is faster than the BrainNetViewer and CIVILITY (based on Matlab).
+
 
 
* The 3D visualization module should offer the possibility to rotate around the connectome and zoom for more precision.
 
* The 3D visualization module should offer the possibility to rotate around the connectome and zoom for more precision.
 
* Impose a minimum strength on the connectome connections
 
* Impose a minimum strength on the connectome connections

Revision as of 20:19, 14 August 2019

Home < Documentation < Labs < Slicer Visualization module

Overview

This is a page introducing the Slicer Connectome Visualization project for adding new visualization extensions into 3DSlicer.

What do we want to visualize?
Visualizations are based on symmetric and normalized matrices with connectivity values that may be obtained from diffusion connectivity or resting state connectivity studies (region-to-region values).
The matrices represent a graph, where the edges are the connectivity values and the nodes are brain regions.

What do we mean by connectome?
The mapping of all neural connections within the brain is what we call a connectome.
Each connection is defined by its strength (visually it represents the thickness of the connection between two nodes) and this value is found in the matrices (edge files).

Goal

Implement two different modules into Slicer:

  • 2D graph visualization of brain connectome
  • 3D shape visualization of brain connectome


Details

The user will have the choice between the 2D and the 3D visualization module. First we will focus on the 3D module.

User Inputs (3 ASCII files):

  • Volume file
  • Node file (and maybe add and option for the user to be able to edit the node characterization ;for example with labels)
  • Edge file

The Node file and the Edge file will have to be adaptable formats, that is the reason why we want to use ASCII files. The Node file should include information about where the node is located.
The file extension could either be a Landmark Registration format (existing module in Slicer)or a Jason file (including a node description file (x,y,z coordinates and node color index) and a node magnitude file(with just the size of a node)).

Features:

  • Python module (using VTK) and maybe C++
  • Implement a 3D visualization tool that is faster than the BrainNetViewer and CIVILITY (based on Matlab).
  • Implement a 2D spherical graph visualization (may apply Hierarchical Edge Bundling), using matrices
  • Custom graph view representing the associated matrix

(possible options: vtkMRMLGraphMarkupNode,vtkSlicerGraphRepresentation3D and associated widget (looking at vtkMRMLMarkupsCurveNode, vtkSlicerCurveRepresentation and vtkSlicerCurveWidget))

  • The 3D visualization module should offer the possibility to rotate around the connectome and zoom for more precision.
  • Impose a minimum strength on the connectome connections