Difference between revisions of "Slicer3:UIDesign:WorkingProblems:SlicerUsabilityInTractography:Registration"
Line 55: | Line 55: | ||
[[Image:registrationWorkflowGuide.png]] | [[Image:registrationWorkflowGuide.png]] | ||
+ | |||
+ | |||
+ | == Priority items: (blocking project progress) == | ||
+ | |||
+ | |||
+ | == Proposed plan for addressing issues == |
Revision as of 21:30, 19 December 2008
Home < Slicer3:UIDesign:WorkingProblems:SlicerUsabilityInTractography:RegistrationBack to Slicer3 UI design
Back to Tractography project
Contents
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 for general common tools:
- 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:
- Choose one:
- A. Is reference an atlas?
- B. a different patient?
- C. same patient but different modality?
- D. same patient but different date?
- E. same patient, different modality and different date?
- Based on selection, recommend an Automatic registration method, or a set of them to try.
- Choose one:
- if Y:
- Choose one or more:
- a different modality?
- a different date?
- a different modality and date?
- Based on selection, recommend an Automatic registration method, or a set of them to try.
- Choose one or more:
- if N:
idea: flexible registration 'guide'
These are sketches to follow up an idea Steve Pieper had for guiding a user through available registration options. First is a Registration helper module that re-presents functionality from other modules:
Then 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 handles navigating through the application GUI so that a user can also learn where functionality is as they are guided.