<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="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]-->
<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.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.EmailStyle20
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
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 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'>RavenClaw can bind on any of the
attributes in the input. For instance, if you look at the “new input
arrived” line in a dialog log, below it you will have a dump of all the
attributes of the input and their values. You will notice that there are things
there which represent the various parse fragments such as [Yes] or
[Query.location] (which you normally bind on the dialog task). At the same
time, there are a number of other attributes starting with h3_ … these
are the various features that helios3 in fact uses in the confidence annotation
process. They are passed all the way to the DM. Among them, h3_hypothesis
contains the actual text of the recognition and h3_parse_str contains the full
parse of the current decoded result. You can therefore bind on [h3_hypothesis]
to get the text of the recognition. <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 this helps, but let me know if you
have other questions. <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>Svetlana Stenchikova<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, November 09, 2006
9:40 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> [RavenclawDev 188] Re:
bypassing the parser</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'>Hi Antoine (or Dan), <br>
<br>
did you, by any chance, remember the syntax for the grammar mapping to get text
instead of a parse in a request/expect agent?<br>
<br>
Thank you<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/5/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>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>Hi Svetlana,<br>
<br>
RavenClaw actually has access to the (recognized) text corresponding to<br>
each input, whether it's parsable or not. It's part of the set of<br>
features that Helios passes to the DM. I forgot exactly how to access <br>
these features but I believe it's basically a grammar mapping with a<br>
special prefix that indicates that you're not binding a grammar slot but<br>
a Helios input structure slot. Sorry I don't remember the exact syntax <br>
now... If nobody else (Dan?) replies with more precision, I'll find it<br>
out and email that later in the week. In any case, you might be able to<br>
get what you want (the text of the input) without modifying anything at <br>
all but your task specification (grammar mappings)...<br>
<br>
Otherwise, the second approach you are proposing (basically adding a<br>
second "parser") sounds definitely much better than the first one, in<br>
the sense that it preserves the integrity of the input line (which is <br>
important for many things in the DM like grounding, reference to<br>
previous turns....).<br>
<br>
I hope Dan will come up with a more precise answer soon :)<br>
<br>
antoine<br>
<br>
Svetlana Stenchikova wrote:<br>
<br>
> I just thought of another way to implement this without changing <br>
> RavenClaw:<br>
><br>
> Add another server ProcessRawData which receives the raw data input<br>
> (in parallel with the parser)<br>
> ProcessRawData outputs the input text in the format of the Parser:<br>
> <br>
> [RawText] ( the typed in text )<br>
><br>
> The output is passed to the
DialogManager.process_parse message<br>
><br>
> The the text will bind to all concept that are expected in the<br>
> [RawText] grammar mapping. <br>
><br>
> Please let me know your thoughts on this.<br>
><br>
> thank you<br>
> Svetlana<br>
><br>
><br>
> On 11/5/06, *Svetlana Stenchikova* <<a
href="mailto:svetastenchikova@gmail.com">svetastenchikova@gmail.com </a><br>
> <mailto:<a href="mailto:svetastenchikova@gmail.com">svetastenchikova@gmail.com</a>>>
wrote:<br>
><br>
> Dan, thank you for your answer. I have
another question.<br>
><br>
> We are interested in the functionality where a
free text can be <br>
> entered through TTY (or through free speech
recognition).<br>
><br>
> For example, a user can be asked to describe the
event. The<br>
> grammar for this description is not available, so
we want to store <br>
> all of the typed ( or recognized) text, and/or a
URL of the<br>
> recorded speech into the concept in a
dialog manager.<br>
><br>
> We need to bypass the parser. I would need to make
changes to the <br>
> RavenClaw to accommodate this, right?<br>
><br>
> Currently the user input from the TTY (or
ASR) is processed by<br>
> the parser.<br>
><br>
> The control flow is determined by the
.pgm file. This entry <br>
> causes it to call process_parse when an output
from the parser is<br>
> available:<br>
><br>
><br>
><br>
> ;; If we have a confidence annotated hypothesis,
but<br>
> ;; no parse, call phoenix to parse it <br>
> ;; ---<br>
> RULE: :confhyps & !:parses -->
phoenix.phoenixparse<br>
> IN: :confhyps :npow :pow :clip_info<br>
> OUT: :total_numparses :parses :input_source<br>
> LOG_OUT: :parses <br>
><br>
><br>
><br>
> So I plan to add another entry:<br>
><br>
> ;; If we have a confidence annotated
hypothesis, but<br>
> ;; no parse, call DM directly<br>
> ;; ---<br>
> RULE: :confhyps & !:parses -->
DM.process_raw<br>
> IN: :confhyps :npow :pow :clip_info<br>
> OUT:<br>
> LOG_OUT:<br>
><br>
><br>
><br>
> Add process_raw() to<br>
><br>
> Libraries/RavenClaw/DMInterfaces/GalaxyInterfaceFunctions.h&
<br>
> implement in GalaxyInterface.cpp<br>
><br>
><br>
> process_raw() function will be called whenever an
output from the<br>
> TTY (or ASR) is received. So, this output will go
to both parser<br>
> and DialogManager.process_raw.<br>
> process_raw() assigns the text to a
concept (but only in the case<br>
> when the concept is currently expected):<br>
> For every expected concept as compiled by<br>
> CDMCoreAgent::compileExpectationAgenda(): <br>
> If a concept is a "raw speech"
concept, set its value to the raw<br>
> text received in an input
frame to process_raw<br>
> I would have to add a type to a concept to
indicate that it allows <br>
> "raw text" input.<br>
><br>
><br>
> Does this implementation plan make sense?<br>
><br>
> Could you please make any suggestions?<br>
><br>
> Jahanzeb must have done something similar because
his application <br>
> can record user's input. Do you know how that was
implemented?<br>
><br>
><br>
><br>
> Thank you,<br>
> Svetlana<br>
><br>
><br>
><br>
><o:p></o:p></span></font></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>
</div>
</body>
</html>