[Olympus developers 160]: Re: no_understanding handling

[Νίκος Κατσαούνος]

Dear Antoine,
thanks for your answer!

I tried to "implement" your insrtuctions without success at the moment..
More specifically:
I tried to implement the "request_default" policy in my dialog. I attach the
Raveclaw.cfg file as well as the grounding.policies/request_default.pol
files. Inside my DialogTask.cpp file I write for the desired agent the
following code:
DEFINE_AGENCY( CMyGame,

IS_MAIN_TOPIC()

DEFINE_CONCEPTS(

...

)

DEFINE_SUBAGENTS(

SUBAGENT(RequestAction, CRequestAction, "request_default")

SUBAGENT(ExecuteBackendCall, CExecuteBackendCall, "")

)

..

When I ran my application,  I type init_session and RavenClaw module appears
the following error:

FATAL_ERROR at 15:42:23.841 (44)] Error in CGMRequestAgent::LoadPolicy().
Invalid state-space size (3 states expected, 0 found). <file
.\DMCore\Grounding\GroundingModels\GMRequestAgent.cpp, line 156>.

What is going wrong?

Well, I am not sure that I have understand the following section of
http://wiki.speech.cs.cmu.edu/olympus/index.php/Grounding_in_RavenClaw
you refer to

Policy files for agents have a similar structure. For a hand-written policy,
it first defines a small number of states using input features (mostly
features computed by Helios, starting with h4_...) in blocks like the
following. This example defines a state called UNDERSTANDING for any turn
that is not a non-understanding:
STATE[UNDERSTANDING]
 [h4_nonu] = 0
END
So..do I have to write something more in order to define the states refered
to request_default.pol(UNDERSTANDING, NONUNDERSTANDING, FAILED) ? If so,
where do I have to write such STATE definitions? Inside .pol file, inside
DialogTask.cpp or anywhere else? In which point/line?Thanks in advance!Nikos
Katsaounos ----- 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
>>
>>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: RavenClaw.cfg
Type: application/octet-stream
Size: 1657 bytes
Desc: not available
Url : http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090918/2f9b9a27/RavenClaw.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: request_default.pol
Type: application/octet-stream
Size: 1110 bytes
Desc: not available
Url : http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090918/2f9b9a27/request_default.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: grounding.policies
Type: application/octet-stream
Size: 107 bytes
Desc: not available
Url : http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090918/2f9b9a27/grounding.obj