Difference between revisions of "2014 Project Week Breakout Session: Contours"
From NAMIC Wiki
(→Agenda) |
|||
Line 7: | Line 7: | ||
=Agenda= | =Agenda= | ||
− | * Present current state of contours (Adam) | + | * Present current state of contours (Adam) [[Media:2014-06-23-NAMIC Summer Contours.pptx | slides]] |
* Discussion on the features and implementation details | * Discussion on the features and implementation details | ||
** Change propagation - what happens when a repr. is changed? | ** Change propagation - what happens when a repr. is changed? |
Revision as of 13:54, 25 June 2014
Home < 2014 Project Week Breakout Session: ContoursBack to Summer Project Week 2014 Agenda
Introduction
- Purpose: Present purpose and current state of Contours data type in the SlicerRt extension with the hope of integrating them into the core, come to agreement in technical details and action plan
- Time: Wednesday 1:00-2:30
- Participants: Adam Rankin, Csaba Pinter, Andras Lasso, Steve Pieper, JC, Nicole, and everybody who is interested
Agenda
- Present current state of contours (Adam) slides
- Discussion on the features and implementation details
- Change propagation - what happens when a repr. is changed?
- Delete other repr. if nothing references them (ref. count)
- Re-convert those that are used
- Issue of the original ROI contour points
- Should we try to update it if we change some other repr?
- Is it just another repr or it's the "ground truth"?
- 2D display of contour
- Add contour object to the slice view control drop-down combobox
- Filled (labelmap), outline (model slice intersection)
- CLI contour support
- Contour selection widget
- Representations
- Storage
- Only save source representation or all?
- Representations in one file or more?
- In what format? Concealed standard files (different extension) or standard files with attributes specifying contour as target object?
- Change propagation - what happens when a repr. is changed?