Difference between revisions of "2014 Winter Project Week:Color Code Tables"
From NAMIC Wiki
Line 3: | Line 3: | ||
Image:PW-SLC2014.png|[[2014_Winter_Project_Week#Projects|Projects List]] | Image:PW-SLC2014.png|[[2014_Winter_Project_Week#Projects|Projects List]] | ||
Image:TMJErrorScalarInSlicer.jpg|New Red-Green-Blue color table in Slicer | Image:TMJErrorScalarInSlicer.jpg|New Red-Green-Blue color table in Slicer | ||
+ | Image:TMJErrorScalarInShapePopulation.jpg|Red-Green-Blue color table in ShapePopulationViewer | ||
</gallery> | </gallery> | ||
Revision as of 22:52, 9 January 2014
Home < 2014 Winter Project Week:Color Code TablesKey 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
- Medium term Slicer to do list:
- color transfer function gui element in the Colors module
- procedural color node storage node
- support csv and xml?
- Bug fixes in Slicer