Slicer3:UIDesign:WorkingProblems:SlicerUsabilityInTractography:Semantics

2008-12-22T14:52:18Z

Jjlemair: /* Priority items: (blocking project progress) */

Back to [[Slicer3:UIDesign | Slicer3 UI design]]

Back to [[Slicer3:UIDesign#Working_problem:_Slicer3_workflow_for_Tractography:_usability_issues.2C_design_.26_planning | 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.

{| border="1" cellpadding="5"
|- style="background:#c2c2c2; color:black" align="left"
| style="width:20%" | Slicer Terminology
| style="width:50%" | Suggested terminology
|-
| style="background:#cbe2e5; color:black"|Volume
| style="background:#ffffff; color:black"|ImageData
|-
| style="background:#cbe2e5; color:black"|ROI(3D)
| style="background:#ffffff; color:black"|Volume
|-
| style="background:#cbe2e5; color:black"|ROI
| style="background:#ffffff; color:black"|ROI (very general term -- could be pixel, pixels in slice, anatomic region, pixels in volume, set of pixels in multi-volumes)
|-
| style="background:#cbe2e5; color:black"|Scene
| style="background:#ffffff; color:black"|? All data and its configuration
|-
| style="background:#cbe2e5; color:black"|Label
| style="background:#ffffff; color:black"|Labeled ROI
|-
| style="background:#cbe2e5; color:black"|fiducial
| style="background:#ffffff; color:black"|marker
|-
| style="background:#cbe2e5; color:black"|Glyph
| style="background:#ffffff; color:black"|marker-type
|-
| style="background:#cbe2e5; color:black"|surface
| style="background:#ffffff; color:black"|?
|-
| style="background:#cbe2e5; color:black"|Model
| style="background:#ffffff; color:black"|?
|-
| style="background:#cbe2e5; color:black"|Volume rendering
| style="background:#ffffff; color:black"|type of data display
|-
| style="background:#cbe2e5; color:black"|Labelmap
| style="background:#ffffff; color:black"|Labeled overlay
|-
| style="background:#cbe2e5; color:black"|Overlay
| style="background:#ffffff; color:black"|Parametric overlay
|-
|}

== Priority items: (blocking project progress) ==
test

== Proposed plan for addressing issues ==

Slicer Wiki - User contributions [en]

Slicer3:UIDesign:WorkingProblems:SlicerUsabilityInTractography:Semantics