[Olympus developers 159]: Re: no_understanding handling

Antoine Raux antoine.raux at gmail.com
Thu Sep 17 12:32:35 EDT 2009


Hi Nikos,

System behavior on non-understandings is part of the grounding 
mechanisms handled by RavenClaw. You shouldn't need to modify any code 
(except your task specification) but add some config files, etc.
Although I'm not sure if it's 100% up-to-date (or complete), 
http://wiki.speech.cs.cmu.edu/olympus/index.php/Grounding_in_RavenClaw 
should get you started (look at Turn Grounding). You can also check one 
of the example systems (e.g. MeetingLine) since they all have some 
behavior coded for non-understandings (smarter than just waiting).

Hope this helps,
antoine

Νίκος Κατσαούνος wrote:
> Hello,
>  
> I have build-up a small dialog application based on RavenClaw/Olympus 
> application.
> _My "problem"_: I noticed that whenvever I say something that cannot 
> be recognized (eg say a word that is not included in my dictionary), 
> system is still waiting for my input. Ravenclaw dialog "continues" 
> only when I say an utternace that can be recognized (so dialog 
> continues to the next step) or when a time interval is reached up (I 
> think about 60secs- so dialog repeats its last state).
> _My "target":_ I want to make my dialog continue to the next step even 
> when I say something that cannot be recognized. In other words I want 
> to make my dialog continue to the next step as soon as the 
> end-utterance is reached-up, even when recognition has no available 
> results.
>  
> So..
> How can I do this?
> --Is there any configuration I can make inside a.cfg file (eg 
> Apollo.cfg) in order to have the above described behaviour?
> --Is there any Ravenclaw commands I can use inside my dialog 
> (DialogTask.cpp) in order to have the above described behaviour? (eg 
> section for no_understanding issues).
> --Do I have to modify some piece of code and where?
>  
> Thanks in advance
>  
> Nikos Katsaounos
> University of Patra-Greece
> Wireless Communication Laboratory
>  
>  
>
>  
>



More information about the Olympus-developers mailing list