Difference between revisions of "2014 Summer Project Week:Contours"
From NAMIC Wiki
| Line 17: | Line 17: | ||
==Project Description== | ==Project Description== | ||
| + | Continue on from the 2014 winter discussion and potentially integrate Contours into the core as the type responsible for ROI representation. | ||
<div style="margin: 20px;"> | <div style="margin: 20px;"> | ||
Revision as of 17:18, 23 June 2014
Home < 2014 Summer Project Week:Contours
Contour representations stored in the Contour object
Key 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
Continue on from the 2014 winter discussion and potentially integrate Contours into the core as the type responsible for ROI representation.
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.- Building in progress...
