Difference between revisions of "2013 Project Week:ColorHierarchies"
From NAMIC Wiki
Line 1: | Line 1: | ||
(to be templated) | (to be templated) | ||
− | + | __NOTOC__ | |
+ | <gallery> | ||
+ | Image:PW-SLC2013.png|[[2013_Winter_Project_Week#Projects|Projects List]] | ||
+ | <!--Image:yourimagehere.png| Image description--> | ||
+ | </gallery> | ||
+ | |||
+ | ==Key Investigators== | ||
+ | |||
+ | * Nicole Aucoin, BWH | ||
+ | |||
+ | ==Project Description== | ||
+ | |||
+ | <div style="margin: 20px;"> | ||
+ | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
+ | <h3>Objective</h3> | ||
* create a color table including color values for both models and model hierarchy groups. | * create a color table including color values for both models and model hierarchy groups. | ||
* update the model maker module to output a scene file that has a tree-like model hierarchy (instead of a flat one), with correct colors on the model and the hierarchy display nodes. | * update the model maker module to output a scene file that has a tree-like model hierarchy (instead of a flat one), with correct colors on the model and the hierarchy display nodes. | ||
− | + | </div> | |
+ | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
+ | <h3>Approach, Plan</h3> | ||
From Marianna: | From Marianna: | ||
− | * start from the Head and Neck Atlas model hierarchy: http://www.na-mic.org/publications/item/view/2256 | + | ** start from the Head and Neck Atlas model hierarchy: http://www.na-mic.org/publications/item/view/2256 |
− | * she will provide a text file with the necessary description of the model hierarchy | + | ** she will provide a text file with the necessary description of the model hierarchy |
− | |||
− | |||
Plan: | Plan: | ||
* create a data structure to save the new color table hierarchy (storable) | * create a data structure to save the new color table hierarchy (storable) | ||
Line 18: | Line 32: | ||
* future plans: create color table hierarchies for all anatomic based color tables | * future plans: create color table hierarchies for all anatomic based color tables | ||
− | Progress | + | </div> |
+ | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
+ | <h3>Progress</h3> | ||
* [[media:NeckAtlas2012-ColorHierarchy12-07-2012.doc| Head and Neck Atlas 2012 Color Hierarchy text file]] | * [[media:NeckAtlas2012-ColorHierarchy12-07-2012.doc| Head and Neck Atlas 2012 Color Hierarchy text file]] | ||
− | + | * Discussed this project during the NA-MIC Eng tcon Dec 27th: | |
− | + | **could think about a realtionship defining node to be the most general | |
− | + | **could load a scene that defines a hierarchy, then use it for the model maker | |
+ | *** extend the scene that's passed into the model maker and returned populated with models | ||
+ | ** each label could have a key value, so parent=labelX (could also change the color name to be a key value pair) | ||
+ | ** in the file, enforce leading spaces to show hierarchy? | ||
+ | *** or use JSON? | ||
+ | <pre> | ||
+ | { | ||
+ | label:100,name:skull,r:128,g:128,b:128,a:255,parent:201 | ||
+ | } | ||
+ | </pre> | ||
+ | * or lump colors together in one: | ||
+ | <pre> | ||
+ | color:{128,123,200,255} | ||
+ | </pre> | ||
+ | * extension .json? c++ library? vtk doesn't do it, python might, boost? there's JSON Spirit. or manual parsing (whitespace assumptions)? | ||
+ | ** need a reader and writer | ||
+ | * create the structure through GUI, or write a text file and make a script that converts it to a MRML structure? for end users who want to use a GUI versus edit a text file | ||
+ | * expand the mrml file that's passed to the model maker to include the full hierarchy and then fill it in | ||
+ | ** associate the hierarhcy with a color node so it's saved/restored? | ||
+ | </div> | ||
+ | </div> |
Revision as of 21:24, 27 December 2012
Home < 2013 Project Week:ColorHierarchies(to be templated)
Key Investigators
- Nicole Aucoin, BWH
Project Description
Objective
- create a color table including color values for both models and model hierarchy groups.
- update the model maker module to output a scene file that has a tree-like model hierarchy (instead of a flat one), with correct colors on the model and the hierarchy display nodes.
Approach, Plan
From Marianna:
- start from the Head and Neck Atlas model hierarchy: http://www.na-mic.org/publications/item/view/2256
- she will provide a text file with the necessary description of the model hierarchy
Plan:
- create a data structure to save the new color table hierarchy (storable)
- extend the color table?
- create a new module that will let users build a model hierarchy from a color table
- in the model maker, instead of having to create a new model heirarchy, select for example HeadAndNeckColorTableHierarchy
- make sure leave the "sample" hierachy available as a base for multiple runs of the model maker
- future plans: create color table hierarchies for all anatomic based color tables
Progress
- Head and Neck Atlas 2012 Color Hierarchy text file
- Discussed this project during the NA-MIC Eng tcon Dec 27th:
- could think about a realtionship defining node to be the most general
- could load a scene that defines a hierarchy, then use it for the model maker
- extend the scene that's passed into the model maker and returned populated with models
- each label could have a key value, so parent=labelX (could also change the color name to be a key value pair)
- in the file, enforce leading spaces to show hierarchy?
- or use JSON?
{ label:100,name:skull,r:128,g:128,b:128,a:255,parent:201 }
- or lump colors together in one:
color:{128,123,200,255}
- extension .json? c++ library? vtk doesn't do it, python might, boost? there's JSON Spirit. or manual parsing (whitespace assumptions)?
- need a reader and writer
- create the structure through GUI, or write a text file and make a script that converts it to a MRML structure? for end users who want to use a GUI versus edit a text file
- expand the mrml file that's passed to the model maker to include the full hierarchy and then fill it in
- associate the hierarhcy with a color node so it's saved/restored?