[Olympus developers 161]: Re: no_understanding handling

Νίκος Κατσαούνος nkatsaounos at sch.gr
Mon Sep 21 10:49:13 EDT 2009


Dear Antoinne,

I also attach some messages that appear during loading of  grounding models, 
that I hadn't notice before..
I confirmed that the .pol files I use are stored into the correct path . I 
assume that something is wrong inside the .pol file..

Nikos Katsaounos

[GMS at 17:44:41.184 (47)] Loading grounding models ...
[GMS at 17:44:41.185 (48)] Loaded grounding model from expl_impl.pol .
[GMS at 17:44:41.185 (48)] Could not read grounding model from  expl_impl.pol
 .
[GMS at 17:44:41.185 (48)] Loaded grounding model from expl.pol .
[GMS at 17:44:41.185 (48)] Could not read grounding model from  expl.pol
 .
[GMS at 17:44:41.185 (48)] Loaded grounding model from request_default.pol .
[GMS at 17:44:41.185 (48)] Could not read grounding model from 
request_default.pol
 .
[GMS at 17:44:41.186 (49)] Loaded grounding model from request_lr.pol .
[GMS at 17:44:41.186 (49)] Could not read grounding model from  request_lr.pol 
.
[GMS at 17:44:41.186 (49)] 4 grounding model(s) loaded.
[CTH at 17:44:41.186 (49)] Auxiliary core dialog management agents created 
successfully.
[CTH at 17:44:41.186 (49)] Core initialization completed successfully.
[GMS at 17:44:41.186 (49)] Registering grounding action: NO_ACTION [NO_ACTION].
[GMS at 17:44:41.186 (49)] Registering grounding action: ACCEPT [ACCEPT].
[GMS at 17:44:41.186 (49)] Registering grounding action: EXPL_CONF [EXPL_CONF].
[GMS at 17:44:41.186 (49)] Registering grounding action: IMPL_CONF [IMPL_CONF].
[GMS at 17:44:41.186 (49)] Registering grounding action: ASK_REPEAT 
[ASK_REPEAT].
[GMS at 17:44:41.186 (49)] Registering grounding action: NOTIFY_AND_ASK_REPEAT 
[ASK_REPEAT].
[GMS at 17:44:41.186 (49)] Registering grounding action: ASK_REPHRASE 
[ASK_REPHRASE].
[GMS at 17:44:41.186 (49)] Registering grounding action: 
NOTIFY_AND_ASK_REPHRASE [ASK_REPHRASE].
[GMS at 17:44:41.186 (49)] Registering grounding action: REPEAT_PROMPT 
[REPEAT_PROMPT].
[GMS at 17:44:41.186 (49)] Registering grounding action: 
NOTIFY_AND_REPEAT_PROMPT [REPEAT_PROMPT].
[GMS at 17:44:41.186 (49)] Registering grounding action: EXPLAIN_MORE 
[EXPLAIN_MORE].
[GMS at 17:44:41.186 (49)] Registering grounding action: 
NOTIFY_AND_EXPLAIN_MORE [EXPLAIN_MORE].
[GMS at 17:44:41.186 (49)] Registering grounding action: FULL_HELP [FULL_HELP].
[GMS at 17:44:41.186 (49)] Registering grounding action: NOTIFY_AND_FULL_HELP 
[FULL_HELP].
[GMS at 17:44:41.186 (49)] Registering grounding action: WHAT_CAN_I_SAY 
[WHAT_CAN_I_SAY].
[GMS at 17:44:41.186 (49)] Registering grounding action: TERSE_WHAT_CAN_I_SAY 
[WHAT_CAN_I_SAY].
[GMS at 17:44:41.186 (49)] Registering grounding action: 
NOTIFY_AND_WHAT_CAN_I_SAY [WHAT_CAN_I_SAY].
[GMS at 17:44:41.186 (49)] Registering grounding action: 
NOTIFY_AND_TERSE_WHAT_CAN_I_SAY [WHAT_CAN_I_SAY].
[GMS at 17:44:41.186 (49)] Registering grounding action: 
TIPS_AND_WHAT_CAN_I_SAY [WHAT_CAN_I_SAY].
[GMS at 17:44:41.186 (49)] Registering grounding action: 
NOTIFY_NONUNDERSTANDING [NOTIFY_NONUNDERSTANDING].
[GMS at 17:44:41.187 (50)] Registering grounding action: YIELD_TURN 
[YIELD_TURN].
[GMS at 17:44:41.187 (50)] Registering grounding action: FAIL_REQUEST 
[FAIL_REQUEST].
[GMS at 17:44:41.187 (50)] Registering grounding action: ASK_STARTOVER 
[ASK_STARTOVER].
[GMS at 17:44:41.187 (50)] Registering grounding action: 
SPEAK_LESS_LOUD_AND_REPROMPT [SPEAKLESSLOUD_AND_REPROMPT].
[GMS at 17:44:41.187 (50)] Registering grounding action: 
ASK_SHORT_ANSWER_AND_REPROMPT [ASK_SHORT_ANSWER_AND_REPROMPT].
[GMS at 17:44:41.187 (50)] Registering grounding action: 
ASK_SHORT_ANSWER_AND_WHAT_CAN_I_SAY [ASK_SHORT_ANSWER_AND_WHAT_CAN_I_SAY].
[GMS at 17:44:41.187 (50)] Registering grounding action: INTERACTION_TIPS 
[INTERACTION_TIPS].
[GMS at 17:44:41.187 (50)] Registering grounding action: GIVE_UP [GIVE_UP].
[GMS at 17:44:41.187 (50)] Registering grounding action: MOVE_ON [MOVE_ON].
[DTT at 17:44:41.187 (50)] Starting Dialog Tree Creation Phase ..
----- Original Message ----- 
From: "Antoine Raux" <antoine.raux at gmail.com>
To: "Νίκος Κατσαούνος" <nkatsaounos at sch.gr>
Cc: <olympus-developers at cs.cmu.edu>
Sent: Thursday, September 17, 2009 7:32 PM
Subject: Re: [Olympus developers 158]: no_understanding handling


> 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