Difference between revisions of "2014 Summer Project Week:Contours"
From NAMIC Wiki
Line 13: | Line 13: | ||
* [[2014_Winter_Project_Week:IntegrationOfContourObject|Winter Contour Discussion]] | * [[2014_Winter_Project_Week:IntegrationOfContourObject|Winter Contour Discussion]] | ||
+ | * Contours DisplayableManager and StorageNode SlicerRT ticket: [https://www.assembla.com/spaces/slicerrt/tickets/446#/activity/ticket: #446] | ||
+ | * Contours module [https://subversion.assembla.com/svn/slicerrt/trunk/SlicerRt/src/Contours/ source code] (module UI, Contours MRML, conversion utilities, Subject hierarchy plugin) | ||
==Project Description== | ==Project Description== | ||
Line 43: | Line 45: | ||
</div> | </div> | ||
</div> | </div> | ||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 14:24, 23 June 2014
Home < 2014 Summer Project Week:ContoursKey Investigators
- Adam Rankin (Queen's University)
- Csaba Pinter (Queen's University)
Background
- Winter Contour Discussion
- Contours DisplayableManager and StorageNode SlicerRT ticket: #446
- Contours module source code (module UI, Contours MRML, conversion utilities, Subject hierarchy plugin)
Project Description
Objective
- Ensure current implementation is satisfactory
- Some cleanup required (variable names, etc...)
- Current storage node implementation does not support Slicer packaged save
- Minor fix to use this->FileNameList instead of member variables
- Discuss any additional features to implement
- Determination of a source representation?
- Ideally the ROI points should always be source, and edits are propagated back to the ROI points
- ...
- Determination of a source representation?
- Prepare a pathway to core integration (maybe)
- Agree on the role of contours in the core
Approach, Plan
- Perform code cleanup, ensure passing tests
- Use breakout session as discussion platform
- Desired features
- Roadmap for core integration
- Implement discussed changes
Progress
- Slicer built. Sort of.