Difference between revisions of "Slicer3:UIDesign:WorkingProblems:SlicerUsabilityInTractography:Registration"
From Slicer Wiki
Line 7: | Line 7: | ||
=== 5. Manual Registration === | === 5. Manual Registration === | ||
− | * | + | Need a helper or guide to promote best practices... |
+ | * Best practices: when and how to apply deformations? | ||
+ | * and When to resample? | ||
+ | |||
+ | <br> | ||
+ | |||
+ | Suggestions: | ||
+ | |||
+ | * choose a "reference" dataset | ||
+ | * Add a target dataset | ||
+ | * Choose to inherit another dataset's transform or start fresh | ||
+ | * would be good to be able to easily toggle colormap from color to grey and back. | ||
+ | |||
+ | Transform module specific suggestions: | ||
+ | * Transform module has confusing interface. | ||
+ | * Here, no sense of '''what''' a person is transforming. | ||
+ | * Would be good to slide translation or rotation scale by either course or fine increments | ||
=== 6. Automatic Registration === | === 6. Automatic Registration === |
Revision as of 19:01, 19 December 2008
Home < Slicer3:UIDesign:WorkingProblems:SlicerUsabilityInTractography:RegistrationBack to Slicer3 UI design
Back to Tractography project
5. Manual Registration
Need a helper or guide to promote best practices...
- Best practices: when and how to apply deformations?
- and When to resample?
Suggestions:
- choose a "reference" dataset
- Add a target dataset
- Choose to inherit another dataset's transform or start fresh
- would be good to be able to easily toggle colormap from color to grey and back.
Transform module specific suggestions:
- Transform module has confusing interface.
- Here, no sense of what a person is transforming.
- Would be good to slide translation or rotation scale by either course or fine increments
6. Automatic Registration
idea: flexible registration 'guide'
This is sketch following up an idea Steve Pieper had for guiding a user through available registration options. Below is a sketch of a tool that would pop up and move stepwise thru a set of registration sub-tasks, making recommendations along the way. A guide might have the following requirements:
- any step can be skipped
- any step can be repeated
- steps can have substeps (and sub-sub steps?)
- the guide handles navigating through the application GUI so that a user can also learn where functinality is as they are guided.
- undo?