40 likes | 381 Views
The good, the bad, and the ugly. Ugly: Most IS implement ad hoc solutions to T+C Good: Managing T+C is not the bottleneck in developing MIIS Many turn-taking / control issues can be solved by a priori analysis or explicit run-time negotiation Bad: Domain knowledge is still king.
E N D
The good, the bad, and the ugly • Ugly: • Most IS implement ad hoc solutions to T+C • Good: • Managing T+C is not the bottleneck in developing MIIS • Many turn-taking / control issues can be solved by a priori analysis or explicit run-time negotiation • Bad: • Domain knowledge is still king
Another snippet involving recovery • Later, in a similar context, the activity might go as follows: User presses the engage button. (mistake) Agent says “Whoops, you’ve made this mistake before.” Agent says “You take it from here.” User says “What next?” Agent says “Let’s recover from pressing the engage button.”
Context • Maintaining a representation of shared context is needed to: • Adapt as user goes from novice to expert • Keep a collaborator in sync • Control system behavior in general • CBR and user-modeling techniques tailored to MIIS
Multimodal MIIS • Speech becoming more common • Vision will be next • Key challenge: how to leverage additional data in order to “better” infer user’s intent, both in general and in regards to the user indicating attitudes about task and control • “better” could mean more accurate or could mean more easily expressed by the user