<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
p.Reference, li.Reference, div.Reference
{margin:0in;
margin-bottom:.0001pt;
text-align:justify;
font-size:11.0pt;
font-family:Garamond;
color:red;
font-weight:bold;
font-style:italic;}
p.VariableorCode, li.VariableorCode, div.VariableorCode
{margin-top:6.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:1.0in;
text-align:justify;
font-size:9.0pt;
font-family:"Courier New";}
p.VariableorCodeCxSpFirst, li.VariableorCodeCxSpFirst, div.VariableorCodeCxSpFirst
{mso-style-type:export-only;
margin-top:6.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:1.0in;
margin-bottom:.0001pt;
text-align:justify;
font-size:9.0pt;
font-family:"Courier New";}
p.VariableorCodeCxSpMiddle, li.VariableorCodeCxSpMiddle, div.VariableorCodeCxSpMiddle
{mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:1.0in;
margin-bottom:.0001pt;
text-align:justify;
font-size:9.0pt;
font-family:"Courier New";}
p.VariableorCodeCxSpLast, li.VariableorCodeCxSpLast, div.VariableorCodeCxSpLast
{mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:1.0in;
text-align:justify;
font-size:9.0pt;
font-family:"Courier New";}
span.emailstyle21
{font-family:Arial;
color:navy;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:595.3pt 841.9pt;
margin:99.25pt 85.05pt 85.05pt 85.05pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Hi Antoine, Svetlana, <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Antoine, thanks a lot for answering all
these questions that Svetlana had about RavenClaw. Sorry I haven’t been
able to be more responsive, I’ve been really busy preparing job talks,
etc. In any case, Svetlana, if you have more questions or need more help
regarding helios and the confidence annotation model it uses, please let us
know. I will try to be better at responding :)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Hope things are well,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Cheers,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Dan, <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
ravenclaw-developers-bounces@LOGANBERRY.srv.cs.cmu.edu
[mailto:ravenclaw-developers-bounces@LOGANBERRY.srv.cs.cmu.edu] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Antoine Raux<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, November 09, 2006
10:19 AM<br>
<b><span style='font-weight:bold'>To:</span></b>
ravenclaw-developers@cs.cmu.edu<br>
<b><span style='font-weight:bold'>Subject:</span></b> [RavenclawDev 189] Re:
grounding_manager_configuration settinginconfig file of DM</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Okay, let me reclarify this ;)</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>There is no “hard” assumption
about getting a single parse in Helios. What happens is that from the data it
has been trained on, Helios *<b><span style='font-weight:bold'>learned</span></b>*
that when you have more than one top-level node, it is more likely that your recognition
hypothesis has errors (same thing for when you have words not covered by the
parse). So rather than a requirement of Helios, this is an artifact of the
training data we used in it. This means that once you get data for your system,
you can retrain Helios to estimate confidence *<b><span style='font-weight:
bold'>given</span></b>* your grammar. This answers your last question: the full
system, including Helios and RavenClaw could work with a keyword spotting like
grammar. Whether this would work better or worse than a full fledge NL grammar needs
to be seen empirically (this is quite an interesting question actually)…</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Of course the problem is that you need a
system to get data in the first place… One approach to get to that is to
start by basically ignoring confidence altogether in RavenClaw. This is done by
first setting the rejection threshold to 0 in your dialogue specification
(sorry I don’t have access to my source code here but I think you need to
add something like DEFAULT_REJECTION_THRESHOLD(0) to the CORE_CONFIGURATION
section). The second thing you need to do is to use a heuristic-based grounding
policy (this is what we do in Let’s Go). This requires a little more
changes and potentially getting the latest version of RavenClaw (I’m not
sure which one you have). I’ll get back to you on that later.</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>antoine</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font><o:p></o:p></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Svetlana
Stenchikova [mailto:svetastenchikova@gmail.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, November 09, 2006
9:36 AM<br>
<b><span style='font-weight:bold'>To:</span></b> Antoine Raux<br>
<b><span style='font-weight:bold'>Cc:</span></b>
ravenclaw-developers@cs.cmu.edu<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [RavenclawDev 184]
Re: grounding_manager_configuration setting inconfig file of DM</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>Thank you Antoine, this
clarifies the things.<br>
<br>
So, currently Helios assumes that there should be a single parse for an
utterance. I can make these changes.<br>
<br>
Do you think that if Helios did not have this requirement, the recognition
would deteriorate?<br>
<br>
I though that since in RavenClaw you can set the nodes of the dialog tree where
a concept is recognized, this limits the number of concepts that are in focus
at each point and recognition of a full sentence may not be necessary to disambiguate
between hypotheses. <br>
<br>
I think it would be interesting to investigate if RavenClaw would work with
simple grammars that pick out concepts from an utterance. (Assuming Helios is
modified to allow this). Or do you think there is a flaw in this idea?<br>
<br>
thanks,<br>
Svetlana<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><span class=gmailquote><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>On 11/8/06, <b><span style='font-weight:bold'>Antoine
Raux</span></b> <<a href="mailto:antoine@cs.cmu.edu">antoine@cs.cmu.edu</a>>
wrote:</span></font></span><o:p></o:p></p>
<div link=blue vlink=blue>
<div>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>I see. I assume [Question] and [EventTypeSpec] are top-level
slots in your grammar right? The "IS" in "WHERE IS CLASS"
doesn't get covered by any parse? This looks like a key-phrase-spotting-like
approach. While this is perfectly okay in the sense that <st1:City w:st="on"><st1:place
w:st="on">Phoenix</st1:place></st1:City> will return the right semantic
structure, we try in general to get our grammars to cover as much as possible
of the input. The idea is that the fact that we get a full parse or a
fragmented parse gives an indication on how confident we should be in the
recognizer output (assuming your user speaks natural English, I'd be more
confident in an ASR result like "WHERE IS THE CLASS" than in "WHERE
CLASS" or "WHERE BLAHBLAH CLASS"). So in your case, you can
either extend your [where_event] rules to include an (optional) IS:</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'> </span></font><o:p></o:p></p>
<p style='margin-bottom:12.0pt'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>[where_event]<br>
(where *is)<br>
(at which location *is)<br>
(what is the location *is)<br>
(which location *is)<br>
(what location *is)<br>
;<o:p></o:p></span></font></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>or (even
better) you can create a top-level rule like:<o:p></o:p></span></font></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>[Question]<o:p></o:p></span></font></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>
([where_event] *is [EventType])<o:p></o:p></span></font></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>
([whattime_event] *is [EventType])<o:p></o:p></span></font></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>
([describe_event] [EventType])<o:p></o:p></span></font></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>;<o:p></o:p></span></font></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>This way
you can still bind [where_event] and [EventType] to different concepts (in
different agents) but your parse will cover more of your input, under a single
top-level slot (which means that you can be pretty confident that your input
was correctly recognized). Of course it requires more work to actually cover
most of what users might say (all the variants of "WHERE IS THE
MEETING", "IN WHICH ROOM IS THE MEETING", "WHERE WILL THE
MEETING BE HELD AT"…) but the best you can do that, the better your system
will behave, both in terms of understanding what the user means and in terms of
engaging in confirmations at the right time.<o:p></o:p></span></font></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'> </span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>Does that clarify things a bit?</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'> </span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>antoine</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'> </span></font><o:p></o:p></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p><b><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;
font-weight:bold'>From:</span></font></b><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'> Svetlana Stenchikova [mailto:<a
href="mailto:svetastenchikova@gmail.com" target="_blank">svetastenchikova@gmail.com</a>]
<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, November 08, 2006
9:17 PM<br>
<span class=q><b><span style='font-weight:bold'>To:</span></b> Antoine Raux</span><br>
<span class=q><b><span style='font-weight:bold'>Cc:</span></b> <a
href="mailto:ravenclaw-developers@cs.cmu.edu" target="_blank">ravenclaw-developers@cs.cmu.edu</a></span><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [RavenclawDev 184]
Re: grounding_manager_configuration setting inconfig file of DM</span></font><o:p></o:p></p>
</div>
<div><span id="q_10eca95d3abcd685_3">
<p><font size=3 face="Times New Roman"><span lang=FR style='font-size:12.0pt'> </span></font><o:p></o:p></p>
<p><font size=3 face="Times New Roman"><span lang=FR style='font-size:12.0pt'>Thanks
Antoine,<br>
<br>
Helios does not have access to the Phoenix grammar does it? It only gets
the string and the output parse, right?<br>
Here is my grammar excerpt. (the full grammar file is attached)<br>
<br>
I am binding Question and EventTypeSpec concepts in separate agents, so phoenix
outputs:<br>
(Maybe this is a problem?)<br>
<br>
[Question] ( [where_event] ( WHERE ) )<br>
Features<br>
[EventTypeSpec] ( [event_type] ( [event_type_singular] ( MEETING ) ) )<br>
<br>
Question and EventTypeSpec are declared in form<br>
<br>
<br>
[Question]<br>
([whattime_event]) <br>
([describe_event])<br>
([where_event])<br>
;<br>
<br>
[where_event]<br>
(where)<br>
(at which location)<br>
(what is the location)<br>
(which location)<br>
(what location)<br>
;<br>
<br>
# SS: I used to have this, but it did not matter:<br>
# (where *is *the *EVENT)<br>
# (*at which location *is *the *EVENT)<br>
<br>
<br>
[EventTypeSpec]<br>
([event_type])<br>
;</span></font><o:p></o:p></p>
<div>
<p><font size=3 face="Times New Roman"><span lang=FR style='font-size:12.0pt'>[event_type]<br>
([event_type_singular])<br>
([event_type_plural])<br>
;<br>
<br>
On 11/8/06, <b><span style='font-weight:bold'>Antoine Raux</span></b> <<a
href="mailto:antoine@cs.cmu.edu" target="_blank">antoine@cs.cmu.edu</a>>
wrote:</span></font><o:p></o:p></p>
<div link=blue vlink=blue>
<div>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>I think the problem is either in the grammar or in Helios.
Helios uses features such as "how many top level slots does the parse
contain", "how many words are covered by the parse", … and
combines them (along with more typical speech recognition features) to produce
the confidence score. What seems to be happening here is that the grammar is
such that the parse for "WHERE IS CLASS", while producing the right
concepts, leads to low confidence.</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>Three ways to solve this: 1) hack Helios to always give
perfect confidence for parsed input (that is *<b><span style='font-weight:bold'>not</span></b>*
a long term solution, I wouldn't recommend it), 2) fix your grammar so that it
produces parses that are more like what Helios expect, 3) fix the Helios model
to match your grammar. The problem with 3) is that the confidence model in
Helios is trained on data so you'd need data for your system before being able
to retrain Helios. So for now I'd try to go for 2).</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'> </span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>Could you send the parse for these two utterances and you
grammar?</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'> </span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>antoine</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'> </span></font><o:p></o:p></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p><b><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;
font-weight:bold'>From:</span></font></b><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'> Svetlana Stenchikova [mailto:<a
href="mailto:svetastenchikova@gmail.com" target="_blank">svetastenchikova@gmail.com</a>]
<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, November 08, 2006
5:45 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Antoine Raux<br>
<b><span style='font-weight:bold'>Cc:</span></b> <a
href="mailto:ravenclaw-developers@cs.cmu.edu" target="_blank">ravenclaw-developers@cs.cmu.edu</a><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [RavenclawDev 182]
Re: grounding_manager_configuration setting inconfig file of DM</span></font><o:p></o:p></p>
</div>
<div>
<p><font size=3 face="Times New Roman"><span lang=FR style='font-size:12.0pt'> </span></font><o:p></o:p></p>
<p style='margin-bottom:12.0pt'><font size=3 face="Times New Roman"><span
lang=FR style='font-size:12.0pt'>In the case of WHERE CLASS, the conversation
continues correctly, but in WHERE IS CLASS it it goes into default
explicit confirmation for CLASS (I just added it - thanks for the hint)<br>
<br>
I don't think it is the desirable behavior though. These typed (or perfectly
recognized) concepts. Why should it need to confirm them?<br>
<br>
thanks<br>
Svetlana</span></font><o:p></o:p></p>
<div>
<p><font size=3 face="Times New Roman"><span lang=FR style='font-size:12.0pt'>On
11/8/06, <b><span style='font-weight:bold'>Antoine Raux</span></b> <<a
href="mailto:antoine@cs.cmu.edu" target="_blank"> antoine@cs.cmu.edu</a>>
wrote:</span></font><o:p></o:p></p>
<div link=blue vlink=blue>
<div>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>What exactly is happening after you type either of those?</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>In the second case (WHERE IS CLASS) RC is trying to perform
an explicit confirmation "I think you said you wanted information about a
class. Is this correct?", whereas in the first case it's just trying to do
an implicit confirmation "Information about a class… <moves on to
the next task related question>".</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>For any of these to work properly, you need to have the
ExplicitConfirm.pm and ImplicitConfirm.pm updated in the NLG. They should map
the concept name to the proper confirmation prompt (these Rosetta modeuls work
the same as <a href="http://Inform.pm" target="_blank">Inform.pm</a> or <a
href="http://Request.pm" target="_blank">Request.pm</a>). Maybe the problem is
that you're missing those? It wouldn't be a major problem in the implicit
confirmation case because the dialog moves on anyway but it would in the
explicit confirmation case because RC waits for a user answer (it creates a new
request agent and puts it on top of the stack).</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'> </span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>So the thing is, when you start dealing with speech, you need
to have all those grounding models and their associated prompts in the NLG set
correctly. It takes a little while but then RC does the whole grounding job for
you…</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>I guess we really need some documentation about this
(Dan??)…</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'> </span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>Hope this helps…</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>antoine</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'> </span></font><o:p></o:p></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p><b><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;
font-weight:bold'>From:</span></font></b><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'> Svetlana Stenchikova [mailto:<a
href="mailto:svetastenchikova@gmail.com" target="_blank">svetastenchikova@gmail.com</a>]
<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, November 08, 2006
4:51 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Antoine Raux<br>
<b><span style='font-weight:bold'>Cc:</span></b> <a
href="mailto:ravenclaw-developers@cs.cmu.edu" target="_blank">ravenclaw-developers@cs.cmu.edu</a><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [RavenclawDev 179]
grounding_manager_configuration setting inconfig file of DM</span></font><o:p></o:p></p>
</div>
<div>
<p><font size=3 face="Times New Roman"><span lang=FR style='font-size:12.0pt'> </span></font><o:p></o:p></p>
<p style='margin-bottom:12.0pt'><font size=3 face="Times New Roman"><span
lang=FR style='font-size:12.0pt'>I am not sure which entry to look at. <br>
<br>
Could this be because I am binding multiple concepts?<br>
It is not a problem for me now as I can fix it by taking out
grounding_manager_configuration from config. <br>
I am just concerned that I will deal with these issues with speech.<br>
<br>
<br>
>From a first glance at the helios log:<br>
WHERE CLASS<br>
<br>
confidence 0.62288<br>
<br>
WHERE IS CLASS<br>
<br>
confidence 0.28883<br>
<br>
<br>
In the dialog.log I get entries:<br>
<br>
I think this is for WHERE CLASS:<br>
****************************************<br>
<br>
[GMX@16:11:10.083] Grounding model /RavenCalendar/question_type_string
[TYPE=concept_default;POLICY=expl;EM=greedy;EP=0.20]:<br>
Full state: <br>
grounded = false<br>
top_confidence = 0.622880<br>
updated = true<br>
Belief state: INACTIVE:0.00 CONFIDENT:0.62 UNCONFIDENT:0.38
GROUNDED:0.00 <br>
Action values (dumped below):<br>
ACCEPT:2.4576<br>
EXPL_CONF:0.6568<br>
<br>
Suggested action: ACCEPT<br>
<br>
[GMX@16:11:10.083] Concept /RavenCalendar/the_event.event_type dumped below:<br>
CLASS|0.62<br>
[GMX@16:11:10.083] Grounding model /RavenCalendar/the_event.event_type
[TYPE=concept_default;POLICY=expl_impl;EM=greedy;EP=0.20]:<br>
Full state: <br>
grounded = false<br>
top_confidence = 0.622880<br>
updated = true<br>
Belief state: INACTIVE:0.00 CONFIDENT:0.62 UNCONFIDENT:0.38
GROUNDED:0.00 <br>
Action values (dumped below):<br>
ACCEPT:-2.1822<br>
EXPL_CONF:0.6568<br>
IMPL_CONF:1.8856<br>
<br>
Suggested action: IMPL_CONF<br>
<br>
<br>
<br>
*****************************************<br>
<br>
and this for WHERE IS CLASS<br>
<br>
<br>
<br>
[GMX@16:11:13.314] Grounding model /RavenCalendar/question_type_string
[TYPE=concept_default;POLICY=expl;EM=greedy;EP=0.20]:<br>
Full state: <br>
grounded = false<br>
top_confidence = 0.000000<br>
updated = false<br>
Belief state: INACTIVE:1.00 CONFIDENT:0.00 UNCONFIDENT:0.00
GROUNDED:0.00 <br>
Action values (dumped below):<br>
ACCEPT:10.0000<br>
EXPL_CONF: -<br>
<br>
Suggested action: ACCEPT<br>
<br>
[GMX@16:11:13.314] Concept /RavenCalendar/the_event.event_type dumped below:<br>
<UNDEFINED><br>
[GMX@16:11:13.315] Grounding model /RavenCalendar/the_event.event_type
[TYPE=concept_default;POLICY=expl_impl;EM=greedy;EP=0.20]:<br>
Full state: <br>
grounded = false<br>
top_confidence = 0.000000<br>
<br>
<br>
[GMX@16:11:37.467] Concept /RavenCalendar/question_type_string dumped below:<br>
where|0.29<br>
[GMX@16:11:37.467] Grounding model /RavenCalendar/question_type_string
[TYPE=concept_default;POLICY=expl;EM=greedy;EP=0.20]:<br>
Full state: <br>
grounded = false<br>
top_confidence = 0.288830<br>
updated = true<br>
Belief state: INACTIVE:0.00 CONFIDENT:0.29 UNCONFIDENT:0.71
GROUNDED:0.00 <br>
Action values (dumped below):<br>
ACCEPT:-4.2234<br>
EXPL_CONF:5.6675<br>
<br>
Suggested action: EXPL_CONF<br>
<br>
<br>
</span></font><o:p></o:p></p>
<div>
<p><font size=3 face="Times New Roman"><span lang=FR style='font-size:12.0pt'>On
11/8/06, <b><span style='font-weight:bold'>Antoine Raux</span></b> <<a
href="mailto:antoine@cs.cmu.edu" target="_blank">antoine@cs.cmu.edu</a>>
wrote:</span></font><o:p></o:p></p>
<div link=blue vlink=purple>
<div>
<p><font size=2 color=navy face=Arial><span lang=FR style='font-size:10.0pt;
font-family:Arial;color:navy'>Hi Svetlana,</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span lang=FR style='font-size:10.0pt;
font-family:Arial;color:navy'> </span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>Have you looked at the confidence value for the input in both
cases? This is one of the features that Helios sends to the DM for each input.
It is possible that "where class" has a low confidence for some
reason (e.g. segmented parse…) and RC rejects it. Normally if your
grammar gives a full parse for "where class" that shouldn't happen
(at least on typed input) but…</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'> </span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'>antoine</span></font><o:p></o:p></p>
<p><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:
Arial;color:navy'> </span></font><o:p></o:p></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p><b><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;
font-weight:bold'>From:</span></font></b><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'> <a
href="mailto:ravenclaw-developers-bounces@LOGANBERRY.srv.cs.cmu.edu"
target="_blank">ravenclaw-developers-bounces@LOGANBERRY.srv.cs.cmu.edu</a>
[mailto:<a href="mailto:ravenclaw-developers-bounces@LOGANBERRY.srv.cs.cmu.edu"
target="_blank">ravenclaw-developers-bounces@LOGANBERRY.srv.cs.cmu.edu</a>] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Svetlana Stenchikova<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, November 08, 2006
2:50 PM<br>
<b><span style='font-weight:bold'>To:</span></b> <a
href="mailto:ravenclaw-developers@cs.cmu.edu" target="_blank">ravenclaw-developers@cs.cmu.edu</a><br>
<b><span style='font-weight:bold'>Subject:</span></b> [RavenclawDev 179] grounding_manager_configuration
setting inconfig file of DM</span></font><o:p></o:p></p>
</div>
<div>
<p><font size=3 face="Times New Roman"><span lang=FR style='font-size:12.0pt'> </span></font><o:p></o:p></p>
<p><font size=3 face="Times New Roman"><span lang=FR style='font-size:12.0pt'><br>
I have encountered an issue with binding a concept in DM depending on a user
utterance.<br>
<br>
in my DM I have a grammar mapping.
"@(...)[Question.where_event]>where,"<br>
<br>
<br>
The user can ask a question in multiple ways:<br>
where class<br>
where is class<br>
where is the class<br>
what is the location the class<br>
..<br>
<br>
for all of these entries PHOENIX produces identical parse<br>
<br>
[Question] ( [where_event] ( WHERE ) )<br>
Features<br>
[EventTypeSpec] ( [event_type] ( [event_type_singular] ( MEETING ) ) )<br>
<br>
" } )<br>
<br>
When a configuration file passed to the DM in -config has an entry:
grounding_manager_configuration =
turns:default;concepts:default;beliefupdatingmodel:npu<br>
<br>
<br>
if a user types:<br>
"where is the class" DM does not bind the concepts,
but if the user types <br>
"where
class"
DM binds the concepts.<br>
<br>
When the grounding_manager_configuration is taken out of DM, the binding
succeeds for both utterances.<br>
<br>
Can this be explained? Do you think there may be a problem with my
grammar or something in my DM? <br>
The grammar of the Phoenix parser should not matter because in all cases the
parses are identical, right?<br>
<br>
thank you<br>
<br>
Svetlana</span></font><o:p></o:p></p>
</div>
</div>
</div>
</div>
<p><font size=3 face="Times New Roman"><span lang=FR style='font-size:12.0pt'> </span></font><o:p></o:p></p>
</div>
</div>
</div>
</div>
<p><font size=3 face="Times New Roman"><span lang=FR style='font-size:12.0pt'> </span></font><o:p></o:p></p>
</div>
</div>
</div>
</div>
<p><font size=3 face="Times New Roman"><span lang=FR style='font-size:12.0pt'> </span></font><o:p></o:p></p>
</div>
</div>
</div>
</div>
</span>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
</body>
</html>