Back to Slicer3 UI design
Back to Tractography project
Comments about the differences between Slicer's semantics and that of other software:
Seems that Slicer's taxonomy of the entities that can comprise a scene can be confusing. We should try to at least define the concepts we use so users can understand how to regard the scene itself, and things that populate it.
- A new user may not understand what a scene is.
- An ROI is a general term in practice; Slicer uses it to mean an object that delimits the region.
- What distinguishes a fiducial and a glyph?
- What distinguishes a glyph with a defined dimension (diameter for instance) and an ROI?
- Is there a distinction between a manually defined painted region and predefined circle or sphere?
- What distinguishes a label map and a scalar overlay?
- What distinguishes the FG/BG layers and a label layer?
- Slicer's scene contains entities besides what users commonly regard as data. So would be good to clarify a taxonomy of entities for these things (camera, view, layout, parameter nodes, etc.) in a scene. Data objects, display configuration objects, algorithm parameterization objects? Any ideas about this?
Below is a table of confusing Slicer terms and what they map to in IGT user language.
|Slicer Terminology||Suggested terminology|
|ROI||ROI (very general term -- could be pixel, pixels in slice, anatomic region, pixels in volume, set of pixels in multi-volumes)|
|Scene||? All data and its configuration|
|Volume rendering||type of data display|
Priority items: (blocking project progress)