<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><br>
The lattice-tool -write-ngram-index option was created for keyword
(and keyphrase) spotting, but would typically be used with
word-based lattices. However, you could write a phone ngram index
(using fairly high -order value) and then do approximate matching
of your pronunciation against this index. The output format is
described in the man page.<br>
<br>
In your case you might do better writing out a phone confusion
network (lattice-tool -write-mesh) and then match against that.<br>
<br>
Either way, you won't find a complete ready-made solution. You
have to postprocess the lattice-tool output using an appropriate
matching function.<br>
<br>
Andreas <br>
<br>
On 6/14/2012 2:55 AM, NEETI SONTH wrote:<br>
</div>
<blockquote
cite="mid:CABtJOhL+6DtHUA0LEU7HgOngSsF5XJ09F4CPQ6cUOTw742arxA@mail.gmail.com"
type="cite">Andreas<br>
I want to do keyword-spotting in srilm. I have a lattice-file in
htk-format generated from a single sentence utterance. The
lattice-file is phonetic lattice. Now I want to search/spot a word
in the lattice-file. I have the phonetic decomposition of the word
I am spotting for. Can you brief me with the necessary steps and
srilm commands for the same?<br>
I tried using <b>lattice-tool -read-htk -in-lattice
<filename1> -ppl <sentence.file></b> . <br>
<br>
<b>sentence.file </b>just contains the keyword I am spotting for.
But what I observed from one of your other user-mails, that <b>-ppl</b>
only works when the phonetic decomposition of the keyword exactly
matches with that of a path in the lattice. However, it is highly
improbable that : when I speak, the lattice file generated has a
phonetic path which exactly matches with the phonetic
decomposition of the keyword.<br>
How then would we spot a keyword?<br>
I also want to know how <b>" -write-ngram-index" option </b>helps
in keyword spotting?<br>
Please help.<br>
thanks<br>
<br>
with regards,<br>
Neeti Sonth<br>
<br>
<br>
<div class="gmail_quote">
On Wed, Jun 13, 2012 at 11:33 AM, Andreas Stolcke <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:stolcke@icsi.berkeley.edu" target="_blank">stolcke@icsi.berkeley.edu</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>On 6/9/2012 3:46 AM, NEETI SONTH wrote:<br>
</div>
<blockquote type="cite"><br>
<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>
<div>
<blockquote type="cite">Hi.</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
<div>When I run the command 'lattice-tool -max-time 4
-write-ngrams <filename> -in-lattice-list
<filename2>'</div>
<div> the command limits the maximum time of operation
for just the first lattice file in the list of lattice
files. For remaining lattice-files, it doesnt limit
the time of operation. The command says "LIMITS THE
MAXIMUM TIME OF OPERATION PER LATTICE" ... So why isnt
it doing so???</div>
<div><br>
</div>
<div>thanks.</div>
<div>Neeti Sonth</div>
</div>
<br>
</blockquote>
<br>
It seems that in Linux and compatible systems, unlike in
Solaris, where the code was originally developed, the
SIGALRM handler needs to use sigsetjmp/siglongjmp() instead
of just plain setjmp/longjmp, or else subsequent alarms
won't invoke the handler due to signal mask modification.
The effect was that lattice-tool -timeout would work only
for the first lattice triggering the timeout on Linux and
Cygwin systems.<br>
<br>
The attached patch should fix the problem.<span
class="HOEnZb"><font color="#888888"><br>
<br>
Andreas<br>
<br>
<br>
<br>
</font></span></div>
</blockquote>
</div>
<br>
</blockquote>
<br>
<br>
</body>
</html>