Difference between revisions of "2016 Winter Project Week/Projects/SegmentationEditorWidget"
From NAMIC Wiki
Line 30: | Line 30: | ||
| | | | ||
<!-- Progress and Next steps bullet points (fill out at the end of project week --> | <!-- Progress and Next steps bullet points (fill out at the end of project week --> | ||
− | * C++ widget using | + | * C++ Qt widget using SegmentTable created |
** New mode for editor with single selection and only name and color shown | ** New mode for editor with single selection and only name and color shown | ||
* Decision made to re-implement Editor effects | * Decision made to re-implement Editor effects | ||
** Conceptual differences | ** Conceptual differences | ||
+ | *** Master volume is not absolutely necessary for segmentations (only a volume geometry) | ||
+ | *** Preferably create one effect object for each effect, not one for each slice view | ||
*** PaintOver function is a big conceptual difference that would necessitate using tricks | *** PaintOver function is a big conceptual difference that would necessitate using tricks | ||
− | |||
** Python adaptor is not less complex than re-implementation | ** Python adaptor is not less complex than re-implementation | ||
** Possibility of a nicer user interface | ** Possibility of a nicer user interface |
Revision as of 14:57, 8 January 2016
Home < 2016 Winter Project Week < Projects < SegmentationEditorWidgetKey Investigators
- Csaba Pinter, Queen's
- Andras Lasso, Queen's
- Andrey Fedorov, BWH
- Steve Pieper, Isomics
Project Description
Objective | Approach and Plan | Progress and Next Steps |
---|---|---|
|
|
|
Background and References
- Segmentations module page
- Segmentations Labs page containing information about design and implementation
- Code
- SegmentationCore containing pure VTK storage and algorithmic classes
- Segmentations module containing module widget, logic, MRML nodes, displayable manager, widgets, etc.