Difference between revisions of "2014 Winter Project Week:Color Code Tables"

From NAMIC Wiki
Jump to: navigation, search
Line 26: Line 26:
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Progress</h3>
 
<h3>Progress</h3>
*
+
* Discussion on Tuesday morning:
 +
** looked at a vtk model with scalar overlay in Population Viewer and Slicer
 +
** defining color mappings via point scalar value and an RGB
 +
*** Population Viewer uses an xml file format to save
 +
*** Slicer doesn't have a prodecural color node storage node
 +
** identified some issues in Slicer:
 +
*** missing a red through green to blue continuous color table
 +
*** in the Models module, resetting the color table and active scalar is buggy
 +
*** in the Colors module, range is not updated to the scalar bar
 
</div>
 
</div>
  

Revision as of 18:35, 7 January 2014

Home < 2014 Winter Project Week:Color Code Tables

Key Investigators

  • University of Michigan: Vinicius Boen
  • University of North Carolina: Francois Budin
  • BWH: Nicole Aucoin
  • Isomics: Steve Pieper

Project Description

Objective

  • Understand how the rendering is done in a stand alone tool (3DMeshMetric) that creates color-coded table for vtk files, in order to be able to update the stand alone tool to be part of the Slicer's extensions.

Approach, Plan

  • Work in progress

Progress

  • Discussion on Tuesday morning:
    • looked at a vtk model with scalar overlay in Population Viewer and Slicer
    • defining color mappings via point scalar value and an RGB
      • Population Viewer uses an xml file format to save
      • Slicer doesn't have a prodecural color node storage node
    • identified some issues in Slicer:
      • missing a red through green to blue continuous color table
      • in the Models module, resetting the color table and active scalar is buggy
      • in the Colors module, range is not updated to the scalar bar

Reference