Difference between revisions of "Slicer3:UIDesign:WorkingProblems:SlicerUsabilityInTractography:Registration"
From Slicer Wiki
Line 27: | Line 27: | ||
=== 6. Automatic Registration === | === 6. Automatic Registration === | ||
+ | Lots of registration methods but hard for a user to know which one to use and when. '''Suggestion:''' helper questions could guide the process -- this is rough, can we find a valid decision tree?: | ||
+ | * Are target and reference the same case? Y/N | ||
+ | ** if N: | ||
+ | *** Is one an atlas, a different patient, a different modality, or a different date? (select one) | ||
+ | ** if Y: | ||
+ | *** Is one a different modality? Y/N | ||
+ | |||
+ | Based on selections, recommend an Automatic registration method, or a set of them to try. | ||
=== idea: flexible registration 'guide' === | === idea: flexible registration 'guide' === |
Revision as of 19:03, 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
Lots of registration methods but hard for a user to know which one to use and when. Suggestion: helper questions could guide the process -- this is rough, can we find a valid decision tree?:
- Are target and reference the same case? Y/N
- if N:
- Is one an atlas, a different patient, a different modality, or a different date? (select one)
- if Y:
- Is one a different modality? Y/N
- if N:
Based on selections, recommend an Automatic registration method, or a set of them to try.
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?