From bfrisch at cs.cmu.edu  Mon Aug  3 19:41:40 2009
From: bfrisch at cs.cmu.edu (Benjamin Frisch)
Date: Mon, 3 Aug 2009 19:41:40 -0400
Subject: [Olympus developers 136]: Re: Problem regarding Olympus
In-Reply-To: <005901ca1192$6e3dc600$4ab95200$@a-star.edu.sg>
References: <000901ca10b3$85db4290$9191c7b0$@a-star.edu.sg> 
	<9C0D1A9F38D23E4290347EE31C22B0AF03549EE5@e2k3.srv.cs.cmu.edu> 
	<002e01ca10b6$aded1ad0$09c75070$@a-star.edu.sg>
	<bd80926e0907291843w4dd44a02xbbd16e648142fa4c@mail.gmail.com> 
	<005901ca1192$6e3dc600$4ab95200$@a-star.edu.sg>
Message-ID: <bd80926e0908031641o2d734265h51a9f726ce52da95@mail.gmail.com>

Hi Tran,
  Kalliope is configured in Configurations/Desktop-SAPI/KalliopeSAPI.cfg
inside of your example system directory to use the first adult male voice it
finds.  You could change the male to female in that configuration file, and
it will use the first female voice it finds, which will probably be Anna in
your case.  This will probably cause Kalliope to synthesize correctly, as if
the SAPI example run time application runs into an error with the male
voices, then Kalliope would as well.  I'm not sure why the voices seem to be
corrupted, but it could be a problem with the SAPI 5.1 SDK, which was
originally made for Windows xp, running on Windows Vista.  The current
Olympus trunk will detect the installation of the Windows SDK 6.1 "for
Windows Server 2008" which includes the SAPI 5.3 SDK.  I am also sorry to
hear that PocketSphinxEngine is crashing.  The PocketSphinxEngine in the
Olympus trunk was largely rewritten to support PocketSphinx 0.5.
  In light of the PocketSphinxEngine and Kalliope issues, and your use of
Windows Vista, I'd recommend that you try to use the Olympus trunk.  We are
probably a couple of weeks away from an Olympus 2.5 release from the Olympus
trunk.  As such the trunk is generally stable now.  You can download the
Windows SDK for Windows Server 2008, which includes SAPI 5.3 from
http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-9BE5-FA919850BDBF.
 You will also need to install CMake via the Win32 Installer from
http://cmake.org/cmake/resources/software.html .  The build scripts
currently cause CMake to generate the Visual Studio solution files in the
Build/cmake directory off of the Olympus Root and off the root of the
MeetingLine and soon to be added Madeline example system.
   Let me know if KalliopeSAPI ends up working with SAPI 5.3 SDK.  If it
still doesn't work (but doesn't crash), then I recommend that you use the
new KalliopeFlite support in the Olympus trunk instead, which you can use by
running OlympusRebuildFlite.pl in your Olympus trunk root and then running
SystemRunFlite.bat rather SystemRun.bat.  While I haven't recently
encountered a crash while running one of our systems for a while with the
trunk, if anything crashes for you or is not working, let me know so I can
do my best to fix it before the release.
   Thank you for sending in your changes to the grammar generation scripts
in the Tutorials.  I committed your changes, and I am sorry for the
trouble.

Thanks,
Ben Frisch
CMU Speech Lab Undergraduate Research Assistant for Summer 2009

On Thu, Jul 30, 2009 at 11:53 PM, Tran <tanhdung at i2r.a-star.edu.sg> wrote:

>  Hi Benjamin,
>
>
>
> I managed to run the TTY version of MyBus successfully. It was very good.
> However, for the SAPI version, there was error. When I init_session, the
> console output ?Welcome to MyBus?, but there is no voice from the system. I
> guess it is because of the Kalliope has some problems with speech synthesis.
> After sometimes, PocketSphinx crashes. I don?t know what is the cause. I ran
> an example of Microsoft Speech. It can talk with Anna voice, but Mary and
> Mike voice has error. Could that be a problem with the voice configuration
> in Kalliope? Please help me on this. Thanks
>
>
>
> I also found that, the source code on SVN cannot compile correctly if you
> don?t make some changes in the perl script. I attach a change log file for
> your reference. It is nice if you make these changes on the source to
> minimize the effort of other developers.
>
>
>
> Regards,
>
> Tran Anh Dung
>
> Research Officer
>
> Human Language Technology Department
>
> A*, Singapore
>
>
>
>
>
> *From:* bfrisch at gmail.com [mailto:bfrisch at gmail.com] *On Behalf Of *Benjamin
> Frisch
> *Sent:* Thursday, 30 July, 2009 9:44 AM
> *To:* Tran
> *Cc:* Alex Rudnicky
> *Subject:* Re: [Olympus developers 133]: Problem regarding Olympus
>
>
>
> Hi Tran,
>
>   At least from picture, it looks like you forgot to start the session
> first.  Just enter init_session and MyBus should start.  Let's us know if
> you have further questions.
>
>
>
> Thanks,
>
> Ben
>
> On Wed, Jul 29, 2009 at 9:40 PM, Tran <tanhdung at i2r.a-star.edu.sg> wrote:
>
> I forget to attached in previous email.
>
>
>
> *From:* Alex Rudnicky [mailto:Alex.Rudnicky at cs.cmu.edu]
> *Sent:* Thursday, 30 July, 2009 9:26 AM
> *To:* Tran; olympus-developers at cs.cmu.edu
> *Cc:* Benjamin Frisch
> *Subject:* RE: [Olympus developers 133]: Problem regarding Olympus
>
>
>
> These systems are pedagogical and follow the tutorial material.
>
> Have you tried to compile and use one of the example systems, such as
> MeetingLine?
>
>
>
>  - Alex Rudnicky
>
>
>
>
>
> *From:* olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu [mailto:
> olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu] *On Behalf Of *Tran
> *Sent:* Wednesday, July 29, 2009 9:18 PM
> *To:* olympus-developers at cs.cmu.edu
> *Subject:* [Olympus developers 133]: Problem regarding Olympus
>
>
>
> To whom it may concerns,
>
>
>
> We are doing research on Dialogue Management System. We found that Olympus
> is an interesting system. We downloaded and manage to compile the source
> code and tutorial 1/2 successfully. However, when we run it, there seems to
> be nothing happens (no interaction from system, no response while we
> talking). We do not know how to operate it. Hence, could you be able to help
> us to instruct how to use the system? We look forward to hear from you
>
>
>
> Regards,
>
> Tran Anh Dung
>
> Research Officer
>
> Human Language Technology Department
>
> A*, Singapore
>
>
>
> PS: all the source code is downloaded as instructed on the Olympus wiki
> page. The downloaded version is 2.2 (not the development version)
>
> Institute for Infocomm Research disclaimer: "This email is confidential and
> may be privileged. If you are not the intended recipient, please delete it
> and notify us immediately. Please do not copy or use it for any purpose, or
> disclose its contents to any other person. Thank you."
>
> Institute for Infocomm Research disclaimer: "This email is confidential and
> may be privileged. If you are not the intended recipient, please delete it
> and notify us immediately. Please do not copy or use it for any purpose, or
> disclose its contents to any other person. Thank you."
>
>
>   Institute for Infocomm Research disclaimer: "This email is confidential
> and may be privileged. If you are not the intended recipient, please delete
> it and notify us immediately. Please do not copy or use it for any purpose,
> or disclose its contents to any other person. Thank you."
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090803/69e25222/attachment.html

From bfrisch at cs.cmu.edu  Tue Aug 11 14:41:22 2009
From: bfrisch at cs.cmu.edu (Benjamin Frisch)
Date: Tue, 11 Aug 2009 13:41:22 -0500
Subject: [Olympus developers 137]:   Problem regarding Olympus
In-Reply-To: <000901ca1a62$09559000$1c00b000$@a-star.edu.sg>
References: <000901ca10b3$85db4290$9191c7b0$@a-star.edu.sg>
	<9C0D1A9F38D23E4290347EE31C22B0AF03549EE5@e2k3.srv.cs.cmu.edu>
	<002e01ca10b6$aded1ad0$09c75070$@a-star.edu.sg>
	<bd80926e0907291843w4dd44a02xbbd16e648142fa4c@mail.gmail.com>
	<005901ca1192$6e3dc600$4ab95200$@a-star.edu.sg>
	<bd80926e0908031641o2d734265h51a9f726ce52da95@mail.gmail.com>
	<000901ca1a62$09559000$1c00b000$@a-star.edu.sg>
Message-ID: <bd80926e0908111141u2e71b005t7c6ac580110f3bb7@mail.gmail.com>

Hi,
  Can you send me your build.log, and I'll take a look.

Thanks,
Ben

On Tue, Aug 11, 2009 at 3:59 AM, Tran <tanhdung at i2r.a-star.edu.sg> wrote:














Hi Ben,



Sorry for the late reply. I was in the ACL conference last week.



Thanks for your informative email. As the problem in Vista, I
recompiled the Olympus on Windows XP. The tutorial 1 & 2 are working fine.
Thanks for your great effort. There is only a minor issue about speech
recognition due to my accent. But I guess it should be improve if I provide
more training data.



On Windows Vista, I downloaded the trunk source code to compile.
But it seems not to work. There were error while compiling as in attached
image. I did some preliminary checking and found that some files are missing
such as Libraries\RavenClaw\DMCore\Agents\CoreAgents\InteractionEventManagerAgent.cpp.
This file causes error while compiling RavenClaw. I don?t know what is the
exact reason, but I think you are still doing on those source code and it might
cause the problem.



Once again, thanks for your help.



Tran Anh Dung





From: bfrisch at gmail.com
[mailto:bfrisch at gmail.com] On Behalf Of Benjamin Frisch
Sent: Tuesday, 4 August, 2009 7:42 AM
To: Tran
Cc: Olympus Developers
Subject: Re: [Olympus developers 133]: Problem regarding Olympus





Hi Tran,
? Kalliope is configured in Configurations/Desktop-SAPI/KalliopeSAPI.cfg
inside of your example system directory to use the first adult male voice it
finds.? You could change the male to female in that configuration file,
and it will use the first female voice it finds, which will probably be Anna in
your case.? This will probably cause Kalliope to synthesize correctly, as
if the SAPI example run time application runs into an error with the male
voices, then Kalliope would as well.? I'm not sure why the voices seem to
be corrupted, but it could be a problem with the SAPI 5.1 SDK, which was
originally made for Windows xp, running on Windows Vista.? The current
Olympus trunk will detect the installation of the Windows SDK 6.1 "for
Windows Server 2008" which includes the SAPI 5.3 SDK.? I am also
sorry to hear that PocketSphinxEngine is crashing.? The PocketSphinxEngine
in the Olympus trunk was largely rewritten to support PocketSphinx 0.5.
? In light of the PocketSphinxEngine and Kalliope issues, and your use of
Windows Vista, I'd recommend that you try to use the Olympus trunk.? We
are probably a couple of weeks away from an Olympus 2.5 release from the
Olympus trunk.? As such the trunk is generally stable now.? You can
download the Windows SDK for Windows Server 2008, which includes SAPI
5.3 from http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-9BE5-FA919850BDBF
.? You will also need to install CMake via the Win32 Installer from
http://cmake.org/cmake/resources/software.html
.? The build scripts currently cause CMake to generate the Visual Studio
solution files in the Build/cmake directory off of the Olympus Root and off the
root of the MeetingLine and soon to be added Madeline example system.
?? Let me know if KalliopeSAPI ends up working with SAPI 5.3
SDK.? If it still doesn't work (but doesn't crash), then I recommend that
you use the new KalliopeFlite support in the Olympus trunk instead, which you
can use by running OlympusRebuildFlite.pl in your Olympus trunk root and then
running SystemRunFlite.bat rather SystemRun.bat.? While I haven't recently
encountered a crash while running one of our systems for a while with the
trunk, if anything crashes for you or is not working, let me know so I can do
my best to fix it before the release.
?? Thank you for sending in your changes to the grammar generation
scripts in the Tutorials.? I committed your changes, and I am sorry for
the trouble.

Thanks,
Ben Frisch
CMU Speech Lab Undergraduate Research Assistant for Summer 2009



On Thu, Jul 30, 2009 at 11:53 PM, Tran <tanhdung at i2r.a-star.edu.sg>
wrote:





Hi Benjamin,



I managed to run the TTY
version of MyBus successfully. It was very good. However, for the SAPI version,
there was error. When I init_session, the console output ?Welcome to
MyBus?, but there is no voice from the system. I guess it is because of
the Kalliope has some problems with speech synthesis. After sometimes,
PocketSphinx crashes. I don?t know what is the cause. I ran an example of
Microsoft Speech. It can talk with Anna voice, but Mary and Mike voice has
error. Could that be a problem with the voice configuration in Kalliope? Please
help me on this. Thanks



I also found that, the source
code on SVN cannot compile correctly if you don?t make some changes in
the perl script. I attach a change log file for your reference. It is nice if
you make these changes on the source to minimize the effort of other
developers.





Regards,

Tran Anh Dung

Research Officer

Human Language Technology Department

A*, Singapore









From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin Frisch





Sent: Thursday, 30 July, 2009 9:44 AM
To: Tran
Cc: Alex Rudnicky



Subject: Re: [Olympus developers 133]: Problem
regarding Olympus









Hi Tran,



??At least from picture, it looks like you forgot to start the
session first. ?Just enter init_session and MyBus should start.
?Let's us know if you have further questions.











Thanks,





Ben



On Wed, Jul 29, 2009 at 9:40 PM, Tran <tanhdung at i2r.a-star.edu.sg>
wrote:





I forget to attached in previous email.







From: Alex Rudnicky [mailto:Alex.Rudnicky at cs.cmu.edu]

Sent: Thursday, 30 July, 2009 9:26 AM
To: Tran; olympus-developers at cs.cmu.edu
Cc: Benjamin Frisch
Subject: RE: [Olympus developers 133]: Problem regarding Olympus











These systems are pedagogical and
follow the tutorial material.

Have you tried to compile and use one
of the example systems, such as MeetingLine?



?- Alex Rudnicky









From: olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu
[mailto:olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu] On
Behalf Of Tran
Sent: Wednesday, July 29, 2009 9:18 PM
To: olympus-developers at cs.cmu.edu
Subject: [Olympus developers 133]: Problem regarding Olympus







To whom it may concerns,



We are doing research on Dialogue Management System. We found that Olympus
is an interesting system. We downloaded and manage to compile the source code
and tutorial 1/2 successfully. However, when we run it, there seems to be
nothing happens (no interaction from system, no response while we talking). We
do not know how to operate it. Hence, could you be able to help us to instruct
how to use the system? We look forward to hear from you



Regards,

Tran Anh Dung

Research Officer

Human Language Technology Department

A*, Singapore



PS: all the source code is downloaded as instructed on the Olympus wiki
page. The downloaded version is 2.2 (not the development version)



Institute for Infocomm Research disclaimer: "This email is confidential
and may be privileged. If you are not the intended recipient, please delete it
and notify us immediately. Please do not copy or use it for any purpose, or
disclose its contents to any other person. Thank you."















Institute for Infocomm Research disclaimer: "This email is confidential
and may be privileged. If you are not the intended recipient, please delete it
and notify us immediately. Please do not copy or use it for any purpose, or
disclose its contents to any other person. Thank you."



























Institute for Infocomm Research disclaimer: "This email
is confidential and may be privileged. If you are not the intended recipient,
please delete it and notify us immediately. Please do not copy or use it for
any purpose, or disclose its contents to any other person. Thank you."

















Institute for Infocomm Research disclaimer:  "This email is
confidential and may be privileged. If you are not the intended
recipient, please delete it and notify us immediately. Please do not
copy or use it for any purpose, or disclose its contents to any other
person. Thank you."


From tanhdung at i2r.a-star.edu.sg  Tue Aug 11 22:58:49 2009
From: tanhdung at i2r.a-star.edu.sg (Tran)
Date: Wed, 12 Aug 2009 10:58:49 +0800
Subject: [Olympus developers 138]: Re: Problem regarding Olympus
In-Reply-To: <bd80926e0908111141u2e71b005t7c6ac580110f3bb7@mail.gmail.com>
References: <000901ca10b3$85db4290$9191c7b0$@a-star.edu.sg>	
	<9C0D1A9F38D23E4290347EE31C22B0AF03549EE5@e2k3.srv.cs.cmu.edu>	
	<002e01ca10b6$aded1ad0$09c75070$@a-star.edu.sg>	
	<bd80926e0907291843w4dd44a02xbbd16e648142fa4c@mail.gmail.com>	
	<005901ca1192$6e3dc600$4ab95200$@a-star.edu.sg>	
	<bd80926e0908031641o2d734265h51a9f726ce52da95@mail.gmail.com>	
	<000901ca1a62$09559000$1c00b000$@a-star.edu.sg>
	<bd80926e0908111141u2e71b005t7c6ac580110f3bb7@mail.gmail.com>
Message-ID: <000001ca1af8$d12efe90$738cfbb0$@a-star.edu.sg>

Hi Ben,

The attached is the build log. The line 114 is the first error, which causes
subsequent errors.

Thanks, 
Tran Anh Dung

-----Original Message-----
From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
Frisch
Sent: Wednesday, 12 August, 2009 2:41 AM
To: Tran; olympus-developers at loganberry.srv.cs.cmu.edu
Subject: [Olympus developers 133]: Problem regarding Olympus

Hi,
  Can you send me your build.log, and I'll take a look.

Thanks,
Ben

On Tue, Aug 11, 2009 at 3:59 AM, Tran <tanhdung at i2r.a-star.edu.sg> wrote:














Hi Ben,



Sorry for the late reply. I was in the ACL conference last week.



Thanks for your informative email. As the problem in Vista, I
recompiled the Olympus on Windows XP. The tutorial 1 & 2 are working fine.
Thanks for your great effort. There is only a minor issue about speech
recognition due to my accent. But I guess it should be improve if I provide
more training data.



On Windows Vista, I downloaded the trunk source code to compile.
But it seems not to work. There were error while compiling as in attached
image. I did some preliminary checking and found that some files are missing
such as
Libraries\RavenClaw\DMCore\Agents\CoreAgents\InteractionEventManagerAgent.cp
p.
This file causes error while compiling RavenClaw. I don?t know what is the
exact reason, but I think you are still doing on those source code and it
might
cause the problem.



Once again, thanks for your help.



Tran Anh Dung





From: bfrisch at gmail.com
[mailto:bfrisch at gmail.com] On Behalf Of Benjamin Frisch
Sent: Tuesday, 4 August, 2009 7:42 AM
To: Tran
Cc: Olympus Developers
Subject: Re: [Olympus developers 133]: Problem regarding Olympus





Hi Tran,
? Kalliope is configured in Configurations/Desktop-SAPI/KalliopeSAPI.cfg
inside of your example system directory to use the first adult male voice it
finds.? You could change the male to female in that configuration file,
and it will use the first female voice it finds, which will probably be Anna
in
your case.? This will probably cause Kalliope to synthesize correctly, as
if the SAPI example run time application runs into an error with the male
voices, then Kalliope would as well.? I'm not sure why the voices seem to
be corrupted, but it could be a problem with the SAPI 5.1 SDK, which was
originally made for Windows xp, running on Windows Vista.? The current
Olympus trunk will detect the installation of the Windows SDK 6.1 "for
Windows Server 2008" which includes the SAPI 5.3 SDK.? I am also
sorry to hear that PocketSphinxEngine is crashing.? The PocketSphinxEngine
in the Olympus trunk was largely rewritten to support PocketSphinx 0.5.
? In light of the PocketSphinxEngine and Kalliope issues, and your use of
Windows Vista, I'd recommend that you try to use the Olympus trunk.? We
are probably a couple of weeks away from an Olympus 2.5 release from the
Olympus trunk.? As such the trunk is generally stable now.? You can
download the Windows SDK for Windows Server 2008, which includes SAPI
5.3 from
http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-
9BE5-FA919850BDBF
.? You will also need to install CMake via the Win32 Installer from
http://cmake.org/cmake/resources/software.html
.? The build scripts currently cause CMake to generate the Visual Studio
solution files in the Build/cmake directory off of the Olympus Root and off
the
root of the MeetingLine and soon to be added Madeline example system.
?? Let me know if KalliopeSAPI ends up working with SAPI 5.3
SDK.? If it still doesn't work (but doesn't crash), then I recommend that
you use the new KalliopeFlite support in the Olympus trunk instead, which
you
can use by running OlympusRebuildFlite.pl in your Olympus trunk root and
then
running SystemRunFlite.bat rather SystemRun.bat.? While I haven't recently
encountered a crash while running one of our systems for a while with the
trunk, if anything crashes for you or is not working, let me know so I can
do
my best to fix it before the release.
?? Thank you for sending in your changes to the grammar generation
scripts in the Tutorials.? I committed your changes, and I am sorry for
the trouble.

Thanks,
Ben Frisch
CMU Speech Lab Undergraduate Research Assistant for Summer 2009



On Thu, Jul 30, 2009 at 11:53 PM, Tran <tanhdung at i2r.a-star.edu.sg>
wrote:





Hi Benjamin,



I managed to run the TTY
version of MyBus successfully. It was very good. However, for the SAPI
version,
there was error. When I init_session, the console output ?Welcome to
MyBus?, but there is no voice from the system. I guess it is because of
the Kalliope has some problems with speech synthesis. After sometimes,
PocketSphinx crashes. I don?t know what is the cause. I ran an example of
Microsoft Speech. It can talk with Anna voice, but Mary and Mike voice has
error. Could that be a problem with the voice configuration in Kalliope?
Please
help me on this. Thanks



I also found that, the source
code on SVN cannot compile correctly if you don?t make some changes in
the perl script. I attach a change log file for your reference. It is nice
if
you make these changes on the source to minimize the effort of other
developers.





Regards,

Tran Anh Dung

Research Officer

Human Language Technology Department

A*, Singapore









From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
Frisch





Sent: Thursday, 30 July, 2009 9:44 AM
To: Tran
Cc: Alex Rudnicky



Subject: Re: [Olympus developers 133]: Problem
regarding Olympus









Hi Tran,



??At least from picture, it looks like you forgot to start the
session first. ?Just enter init_session and MyBus should start.
?Let's us know if you have further questions.











Thanks,





Ben



On Wed, Jul 29, 2009 at 9:40 PM, Tran <tanhdung at i2r.a-star.edu.sg>
wrote:





I forget to attached in previous email.







From: Alex Rudnicky [mailto:Alex.Rudnicky at cs.cmu.edu]

Sent: Thursday, 30 July, 2009 9:26 AM
To: Tran; olympus-developers at cs.cmu.edu
Cc: Benjamin Frisch
Subject: RE: [Olympus developers 133]: Problem regarding Olympus











These systems are pedagogical and
follow the tutorial material.

Have you tried to compile and use one
of the example systems, such as MeetingLine?



?- Alex Rudnicky









From: olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu
[mailto:olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu] On
Behalf Of Tran
Sent: Wednesday, July 29, 2009 9:18 PM
To: olympus-developers at cs.cmu.edu
Subject: [Olympus developers 133]: Problem regarding Olympus







To whom it may concerns,



We are doing research on Dialogue Management System. We found that Olympus
is an interesting system. We downloaded and manage to compile the source
code
and tutorial 1/2 successfully. However, when we run it, there seems to be
nothing happens (no interaction from system, no response while we talking).
We
do not know how to operate it. Hence, could you be able to help us to
instruct
how to use the system? We look forward to hear from you



Regards,

Tran Anh Dung

Research Officer

Human Language Technology Department

A*, Singapore



PS: all the source code is downloaded as instructed on the Olympus wiki
page. The downloaded version is 2.2 (not the development version)



Institute for Infocomm Research disclaimer: "This email is confidential
and may be privileged. If you are not the intended recipient, please delete
it
and notify us immediately. Please do not copy or use it for any purpose, or
disclose its contents to any other person. Thank you."















Institute for Infocomm Research disclaimer: "This email is confidential
and may be privileged. If you are not the intended recipient, please delete
it
and notify us immediately. Please do not copy or use it for any purpose, or
disclose its contents to any other person. Thank you."



























Institute for Infocomm Research disclaimer: "This email
is confidential and may be privileged. If you are not the intended
recipient,
please delete it and notify us immediately. Please do not copy or use it for
any purpose, or disclose its contents to any other person. Thank you."

















Institute for Infocomm Research disclaimer:  "This email is
confidential and may be privileged. If you are not the intended
recipient, please delete it and notify us immediately. Please do not
copy or use it for any purpose, or disclose its contents to any other
person. Thank you."

Institute for Infocomm Research disclaimer:  "This email is confidential and may be privileged. If you are not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any purpose, or disclose its contents to any other person. Thank you."
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: compile.txt
Url: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090811/79d22513/compile-0001.txt

From bfrisch at cs.cmu.edu  Wed Aug 12 02:17:00 2009
From: bfrisch at cs.cmu.edu (Benjamin Frisch)
Date: Wed, 12 Aug 2009 01:17:00 -0500
Subject: [Olympus developers 139]: Re: Problem regarding Olympus
In-Reply-To: <000001ca1af8$d12efe90$738cfbb0$@a-star.edu.sg>
References: <000901ca10b3$85db4290$9191c7b0$@a-star.edu.sg>
	<9C0D1A9F38D23E4290347EE31C22B0AF03549EE5@e2k3.srv.cs.cmu.edu>
	<002e01ca10b6$aded1ad0$09c75070$@a-star.edu.sg>
	<bd80926e0907291843w4dd44a02xbbd16e648142fa4c@mail.gmail.com>
	<005901ca1192$6e3dc600$4ab95200$@a-star.edu.sg>
	<bd80926e0908031641o2d734265h51a9f726ce52da95@mail.gmail.com>
	<000901ca1a62$09559000$1c00b000$@a-star.edu.sg>
	<bd80926e0908111141u2e71b005t7c6ac580110f3bb7@mail.gmail.com>
	<000001ca1af8$d12efe90$738cfbb0$@a-star.edu.sg>
Message-ID: <bd80926e0908112317x63e0f143hf6d75418a543e2b4@mail.gmail.com>

Hi Tran,
   So I encountered the reference to the non-existent
DMCore/Events/PhoenixInput.h on my computer.  You can fix it by
removing #include "DMCore/Events/PhoenixInput.h" on line 67 of
Libraries/RavenClaw/DMCore/Agents/CoreAgents/InteractionEventManagerAgent.cpp.
It was replaced by DMCore/Events/GalaxyInteractionEvent.h, and I guess
it was not automatically rebuilt after the deletion. (PhoenixInput.h
was removed as part of the fix for
http://trac.speech.cs.cmu.edu/olympus/ticket/52 .)  I apologize for
the inconvenience.  I'll try to get that fix committed by tomorrow.
  The other errors in building Olympus look exactly like
http://trac.speech.cs.cmu.edu/olympus/ticket/87 , which was fixed by
upgrading to Visual Studio 2005 SP1.  Send me your build.log if the
build is still not successful, and if there is an unexpected fatal
error, hang, or crash with the trunk, please send me the log file that
corresponds to the agent with the problem.  I'll do my best to try to
fix or help fix what is wrong.

Thanks,
Ben

On 8/11/09, Tran <tanhdung at i2r.a-star.edu.sg> wrote:
> Hi Ben,
>
> The attached is the build log. The line 114 is the first error, which causes
> subsequent errors.
>
> Thanks,
> Tran Anh Dung
>
> -----Original Message-----
> From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> Frisch
> Sent: Wednesday, 12 August, 2009 2:41 AM
> To: Tran; olympus-developers at loganberry.srv.cs.cmu.edu
> Subject: [Olympus developers 133]: Problem regarding Olympus
>
> Hi,
>   Can you send me your build.log, and I'll take a look.
>
> Thanks,
> Ben
>
> On Tue, Aug 11, 2009 at 3:59 AM, Tran <tanhdung at i2r.a-star.edu.sg> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi Ben,
>
>
>
> Sorry for the late reply. I was in the ACL conference last week.
>
>
>
> Thanks for your informative email. As the problem in Vista, I
> recompiled the Olympus on Windows XP. The tutorial 1 & 2 are working fine.
> Thanks for your great effort. There is only a minor issue about speech
> recognition due to my accent. But I guess it should be improve if I provide
> more training data.
>
>
>
> On Windows Vista, I downloaded the trunk source code to compile.
> But it seems not to work. There were error while compiling as in attached
> image. I did some preliminary checking and found that some files are missing
> such as
> Libraries\RavenClaw\DMCore\Agents\CoreAgents\InteractionEventManagerAgent.cp
> p.
> This file causes error while compiling RavenClaw. I don?t know what is the
> exact reason, but I think you are still doing on those source code and it
> might
> cause the problem.
>
>
>
> Once again, thanks for your help.
>
>
>
> Tran Anh Dung
>
>
>
>
>
> From: bfrisch at gmail.com
> [mailto:bfrisch at gmail.com] On Behalf Of Benjamin Frisch
> Sent: Tuesday, 4 August, 2009 7:42 AM
> To: Tran
> Cc: Olympus Developers
> Subject: Re: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
> Hi Tran,
> ? Kalliope is configured in Configurations/Desktop-SAPI/KalliopeSAPI.cfg
> inside of your example system directory to use the first adult male voice it
> finds.? You could change the male to female in that configuration file,
> and it will use the first female voice it finds, which will probably be Anna
> in
> your case.? This will probably cause Kalliope to synthesize correctly, as
> if the SAPI example run time application runs into an error with the male
> voices, then Kalliope would as well.? I'm not sure why the voices seem to
> be corrupted, but it could be a problem with the SAPI 5.1 SDK, which was
> originally made for Windows xp, running on Windows Vista.? The current
> Olympus trunk will detect the installation of the Windows SDK 6.1 "for
> Windows Server 2008" which includes the SAPI 5.3 SDK.? I am also
> sorry to hear that PocketSphinxEngine is crashing.? The PocketSphinxEngine
> in the Olympus trunk was largely rewritten to support PocketSphinx 0.5.
> ? In light of the PocketSphinxEngine and Kalliope issues, and your use of
> Windows Vista, I'd recommend that you try to use the Olympus trunk.? We
> are probably a couple of weeks away from an Olympus 2.5 release from the
> Olympus trunk.? As such the trunk is generally stable now.? You can
> download the Windows SDK for Windows Server 2008, which includes SAPI
> 5.3 from
> http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-
> 9BE5-FA919850BDBF
> .? You will also need to install CMake via the Win32 Installer from
> http://cmake.org/cmake/resources/software.html
> .? The build scripts currently cause CMake to generate the Visual Studio
> solution files in the Build/cmake directory off of the Olympus Root and off
> the
> root of the MeetingLine and soon to be added Madeline example system.
> ?? Let me know if KalliopeSAPI ends up working with SAPI 5.3
> SDK.? If it still doesn't work (but doesn't crash), then I recommend that
> you use the new KalliopeFlite support in the Olympus trunk instead, which
> you
> can use by running OlympusRebuildFlite.pl in your Olympus trunk root and
> then
> running SystemRunFlite.bat rather SystemRun.bat.? While I haven't recently
> encountered a crash while running one of our systems for a while with the
> trunk, if anything crashes for you or is not working, let me know so I can
> do
> my best to fix it before the release.
> ?? Thank you for sending in your changes to the grammar generation
> scripts in the Tutorials.? I committed your changes, and I am sorry for
> the trouble.
>
> Thanks,
> Ben Frisch
> CMU Speech Lab Undergraduate Research Assistant for Summer 2009
>
>
>
> On Thu, Jul 30, 2009 at 11:53 PM, Tran <tanhdung at i2r.a-star.edu.sg>
> wrote:
>
>
>
>
>
> Hi Benjamin,
>
>
>
> I managed to run the TTY
> version of MyBus successfully. It was very good. However, for the SAPI
> version,
> there was error. When I init_session, the console output ?Welcome to
> MyBus?, but there is no voice from the system. I guess it is because of
> the Kalliope has some problems with speech synthesis. After sometimes,
> PocketSphinx crashes. I don?t know what is the cause. I ran an example of
> Microsoft Speech. It can talk with Anna voice, but Mary and Mike voice has
> error. Could that be a problem with the voice configuration in Kalliope?
> Please
> help me on this. Thanks
>
>
>
> I also found that, the source
> code on SVN cannot compile correctly if you don?t make some changes in
> the perl script. I attach a change log file for your reference. It is nice
> if
> you make these changes on the source to minimize the effort of other
> developers.
>
>
>
>
>
> Regards,
>
> Tran Anh Dung
>
> Research Officer
>
> Human Language Technology Department
>
> A*, Singapore
>
>
>
>
>
>
>
>
>
> From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> Frisch
>
>
>
>
>
> Sent: Thursday, 30 July, 2009 9:44 AM
> To: Tran
> Cc: Alex Rudnicky
>
>
>
> Subject: Re: [Olympus developers 133]: Problem
> regarding Olympus
>
>
>
>
>
>
>
>
>
> Hi Tran,
>
>
>
> ??At least from picture, it looks like you forgot to start the
> session first. ?Just enter init_session and MyBus should start.
> ?Let's us know if you have further questions.
>
>
>
>
>
>
>
>
>
>
>
> Thanks,
>
>
>
>
>
> Ben
>
>
>
> On Wed, Jul 29, 2009 at 9:40 PM, Tran <tanhdung at i2r.a-star.edu.sg>
> wrote:
>
>
>
>
>
> I forget to attached in previous email.
>
>
>
>
>
>
>
> From: Alex Rudnicky [mailto:Alex.Rudnicky at cs.cmu.edu]
>
> Sent: Thursday, 30 July, 2009 9:26 AM
> To: Tran; olympus-developers at cs.cmu.edu
> Cc: Benjamin Frisch
> Subject: RE: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
>
>
>
>
>
>
> These systems are pedagogical and
> follow the tutorial material.
>
> Have you tried to compile and use one
> of the example systems, such as MeetingLine?
>
>
>
> ?- Alex Rudnicky
>
>
>
>
>
>
>
>
>
> From: olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu
> [mailto:olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu] On
> Behalf Of Tran
> Sent: Wednesday, July 29, 2009 9:18 PM
> To: olympus-developers at cs.cmu.edu
> Subject: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
>
>
> To whom it may concerns,
>
>
>
> We are doing research on Dialogue Management System. We found that Olympus
> is an interesting system. We downloaded and manage to compile the source
> code
> and tutorial 1/2 successfully. However, when we run it, there seems to be
> nothing happens (no interaction from system, no response while we talking).
> We
> do not know how to operate it. Hence, could you be able to help us to
> instruct
> how to use the system? We look forward to hear from you
>
>
>
> Regards,
>
> Tran Anh Dung
>
> Research Officer
>
> Human Language Technology Department
>
> A*, Singapore
>
>
>
> PS: all the source code is downloaded as instructed on the Olympus wiki
> page. The downloaded version is 2.2 (not the development version)
>
>
>
> Institute for Infocomm Research disclaimer: "This email is confidential
> and may be privileged. If you are not the intended recipient, please delete
> it
> and notify us immediately. Please do not copy or use it for any purpose, or
> disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer: "This email is confidential
> and may be privileged. If you are not the intended recipient, please delete
> it
> and notify us immediately. Please do not copy or use it for any purpose, or
> disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer: "This email
> is confidential and may be privileged. If you are not the intended
> recipient,
> please delete it and notify us immediately. Please do not copy or use it for
> any purpose, or disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer:  "This email is
> confidential and may be privileged. If you are not the intended
> recipient, please delete it and notify us immediately. Please do not
> copy or use it for any purpose, or disclose its contents to any other
> person. Thank you."
>
> Institute for Infocomm Research disclaimer:  "This email is confidential and
> may be privileged. If you are not the intended recipient, please delete it
> and notify us immediately. Please do not copy or use it for any purpose, or
> disclose its contents to any other person. Thank you."
>


From tanhdung at i2r.a-star.edu.sg  Thu Aug 13 23:11:36 2009
From: tanhdung at i2r.a-star.edu.sg (Tran)
Date: Fri, 14 Aug 2009 11:11:36 +0800
Subject: [Olympus developers 140]: Re: Problem regarding Olympus
In-Reply-To: <bd80926e0908112317x63e0f143hf6d75418a543e2b4@mail.gmail.com>
References: <000901ca10b3$85db4290$9191c7b0$@a-star.edu.sg>	
	<9C0D1A9F38D23E4290347EE31C22B0AF03549EE5@e2k3.srv.cs.cmu.edu>	
	<002e01ca10b6$aded1ad0$09c75070$@a-star.edu.sg>	
	<bd80926e0907291843w4dd44a02xbbd16e648142fa4c@mail.gmail.com>	
	<005901ca1192$6e3dc600$4ab95200$@a-star.edu.sg>	
	<bd80926e0908031641o2d734265h51a9f726ce52da95@mail.gmail.com>	
	<000901ca1a62$09559000$1c00b000$@a-star.edu.sg>	
	<bd80926e0908111141u2e71b005t7c6ac580110f3bb7@mail.gmail.com>	
	<000001ca1af8$d12efe90$738cfbb0$@a-star.edu.sg>
	<bd80926e0908112317x63e0f143hf6d75418a543e2b4@mail.gmail.com>
Message-ID: <001a01ca1c8c$eeed51d0$ccc7f570$@a-star.edu.sg>

Hi Ben,

I tried to compile the Olympus with WindowSDK 2008. However, there is some
error while compiling simpleaudio. The attached is log file. It says it can
not find the sapi.idl file. In fact, that file is in C:\Program
Files\Microsoft SDKs\Windows\v6.1\Include. If I open simpleaudio project on
MSVS 2005 and include that folder in MIDL settings, it says another syntax
error. I guess something wrong with this simpleaudio. Do you have any idea
on this?

Thanks
Tran Anh Dung

-----Original Message-----
From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
Frisch
Sent: Wednesday, 12 August, 2009 2:17 PM
To: Tran
Cc: olympus-developers at loganberry.srv.cs.cmu.edu
Subject: Re: [Olympus developers 138]: Re: Problem regarding Olympus

Hi Tran,
   So I encountered the reference to the non-existent
DMCore/Events/PhoenixInput.h on my computer.  You can fix it by
removing #include "DMCore/Events/PhoenixInput.h" on line 67 of
Libraries/RavenClaw/DMCore/Agents/CoreAgents/InteractionEventManagerAgent.cp
p.
It was replaced by DMCore/Events/GalaxyInteractionEvent.h, and I guess
it was not automatically rebuilt after the deletion. (PhoenixInput.h
was removed as part of the fix for
http://trac.speech.cs.cmu.edu/olympus/ticket/52 .)  I apologize for
the inconvenience.  I'll try to get that fix committed by tomorrow.
  The other errors in building Olympus look exactly like
http://trac.speech.cs.cmu.edu/olympus/ticket/87 , which was fixed by
upgrading to Visual Studio 2005 SP1.  Send me your build.log if the
build is still not successful, and if there is an unexpected fatal
error, hang, or crash with the trunk, please send me the log file that
corresponds to the agent with the problem.  I'll do my best to try to
fix or help fix what is wrong.

Thanks,
Ben

On 8/11/09, Tran <tanhdung at i2r.a-star.edu.sg> wrote:
> Hi Ben,
>
> The attached is the build log. The line 114 is the first error, which
causes
> subsequent errors.
>
> Thanks,
> Tran Anh Dung
>
> -----Original Message-----
> From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> Frisch
> Sent: Wednesday, 12 August, 2009 2:41 AM
> To: Tran; olympus-developers at loganberry.srv.cs.cmu.edu
> Subject: [Olympus developers 133]: Problem regarding Olympus
>
> Hi,
>   Can you send me your build.log, and I'll take a look.
>
> Thanks,
> Ben
>
> On Tue, Aug 11, 2009 at 3:59 AM, Tran <tanhdung at i2r.a-star.edu.sg> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi Ben,
>
>
>
> Sorry for the late reply. I was in the ACL conference last week.
>
>
>
> Thanks for your informative email. As the problem in Vista, I
> recompiled the Olympus on Windows XP. The tutorial 1 & 2 are working fine.
> Thanks for your great effort. There is only a minor issue about speech
> recognition due to my accent. But I guess it should be improve if I
provide
> more training data.
>
>
>
> On Windows Vista, I downloaded the trunk source code to compile.
> But it seems not to work. There were error while compiling as in attached
> image. I did some preliminary checking and found that some files are
missing
> such as
>
Libraries\RavenClaw\DMCore\Agents\CoreAgents\InteractionEventManagerAgent.cp
> p.
> This file causes error while compiling RavenClaw. I don?t know what is the
> exact reason, but I think you are still doing on those source code and it
> might
> cause the problem.
>
>
>
> Once again, thanks for your help.
>
>
>
> Tran Anh Dung
>
>
>
>
>
> From: bfrisch at gmail.com
> [mailto:bfrisch at gmail.com] On Behalf Of Benjamin Frisch
> Sent: Tuesday, 4 August, 2009 7:42 AM
> To: Tran
> Cc: Olympus Developers
> Subject: Re: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
> Hi Tran,
> ? Kalliope is configured in Configurations/Desktop-SAPI/KalliopeSAPI.cfg
> inside of your example system directory to use the first adult male voice
it
> finds.? You could change the male to female in that configuration file,
> and it will use the first female voice it finds, which will probably be
Anna
> in
> your case.? This will probably cause Kalliope to synthesize correctly, as
> if the SAPI example run time application runs into an error with the male
> voices, then Kalliope would as well.? I'm not sure why the voices seem to
> be corrupted, but it could be a problem with the SAPI 5.1 SDK, which was
> originally made for Windows xp, running on Windows Vista.? The current
> Olympus trunk will detect the installation of the Windows SDK 6.1 "for
> Windows Server 2008" which includes the SAPI 5.3 SDK.? I am also
> sorry to hear that PocketSphinxEngine is crashing.? The PocketSphinxEngine
> in the Olympus trunk was largely rewritten to support PocketSphinx 0.5.
> ? In light of the PocketSphinxEngine and Kalliope issues, and your use of
> Windows Vista, I'd recommend that you try to use the Olympus trunk.? We
> are probably a couple of weeks away from an Olympus 2.5 release from the
> Olympus trunk.? As such the trunk is generally stable now.? You can
> download the Windows SDK for Windows Server 2008, which includes SAPI
> 5.3 from
>
http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-
> 9BE5-FA919850BDBF
> .? You will also need to install CMake via the Win32 Installer from
> http://cmake.org/cmake/resources/software.html
> .? The build scripts currently cause CMake to generate the Visual Studio
> solution files in the Build/cmake directory off of the Olympus Root and
off
> the
> root of the MeetingLine and soon to be added Madeline example system.
> ?? Let me know if KalliopeSAPI ends up working with SAPI 5.3
> SDK.? If it still doesn't work (but doesn't crash), then I recommend that
> you use the new KalliopeFlite support in the Olympus trunk instead, which
> you
> can use by running OlympusRebuildFlite.pl in your Olympus trunk root and
> then
> running SystemRunFlite.bat rather SystemRun.bat.? While I haven't recently
> encountered a crash while running one of our systems for a while with the
> trunk, if anything crashes for you or is not working, let me know so I can
> do
> my best to fix it before the release.
> ?? Thank you for sending in your changes to the grammar generation
> scripts in the Tutorials.? I committed your changes, and I am sorry for
> the trouble.
>
> Thanks,
> Ben Frisch
> CMU Speech Lab Undergraduate Research Assistant for Summer 2009
>
>
>
> On Thu, Jul 30, 2009 at 11:53 PM, Tran <tanhdung at i2r.a-star.edu.sg>
> wrote:
>
>
>
>
>
> Hi Benjamin,
>
>
>
> I managed to run the TTY
> version of MyBus successfully. It was very good. However, for the SAPI
> version,
> there was error. When I init_session, the console output ?Welcome to
> MyBus?, but there is no voice from the system. I guess it is because of
> the Kalliope has some problems with speech synthesis. After sometimes,
> PocketSphinx crashes. I don?t know what is the cause. I ran an example of
> Microsoft Speech. It can talk with Anna voice, but Mary and Mike voice has
> error. Could that be a problem with the voice configuration in Kalliope?
> Please
> help me on this. Thanks
>
>
>
> I also found that, the source
> code on SVN cannot compile correctly if you don?t make some changes in
> the perl script. I attach a change log file for your reference. It is nice
> if
> you make these changes on the source to minimize the effort of other
> developers.
>
>
>
>
>
> Regards,
>
> Tran Anh Dung
>
> Research Officer
>
> Human Language Technology Department
>
> A*, Singapore
>
>
>
>
>
>
>
>
>
> From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> Frisch
>
>
>
>
>
> Sent: Thursday, 30 July, 2009 9:44 AM
> To: Tran
> Cc: Alex Rudnicky
>
>
>
> Subject: Re: [Olympus developers 133]: Problem
> regarding Olympus
>
>
>
>
>
>
>
>
>
> Hi Tran,
>
>
>
> ??At least from picture, it looks like you forgot to start the
> session first. ?Just enter init_session and MyBus should start.
> ?Let's us know if you have further questions.
>
>
>
>
>
>
>
>
>
>
>
> Thanks,
>
>
>
>
>
> Ben
>
>
>
> On Wed, Jul 29, 2009 at 9:40 PM, Tran <tanhdung at i2r.a-star.edu.sg>
> wrote:
>
>
>
>
>
> I forget to attached in previous email.
>
>
>
>
>
>
>
> From: Alex Rudnicky [mailto:Alex.Rudnicky at cs.cmu.edu]
>
> Sent: Thursday, 30 July, 2009 9:26 AM
> To: Tran; olympus-developers at cs.cmu.edu
> Cc: Benjamin Frisch
> Subject: RE: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
>
>
>
>
>
>
> These systems are pedagogical and
> follow the tutorial material.
>
> Have you tried to compile and use one
> of the example systems, such as MeetingLine?
>
>
>
> ?- Alex Rudnicky
>
>
>
>
>
>
>
>
>
> From: olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu
> [mailto:olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu] On
> Behalf Of Tran
> Sent: Wednesday, July 29, 2009 9:18 PM
> To: olympus-developers at cs.cmu.edu
> Subject: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
>
>
> To whom it may concerns,
>
>
>
> We are doing research on Dialogue Management System. We found that Olympus
> is an interesting system. We downloaded and manage to compile the source
> code
> and tutorial 1/2 successfully. However, when we run it, there seems to be
> nothing happens (no interaction from system, no response while we
talking).
> We
> do not know how to operate it. Hence, could you be able to help us to
> instruct
> how to use the system? We look forward to hear from you
>
>
>
> Regards,
>
> Tran Anh Dung
>
> Research Officer
>
> Human Language Technology Department
>
> A*, Singapore
>
>
>
> PS: all the source code is downloaded as instructed on the Olympus wiki
> page. The downloaded version is 2.2 (not the development version)
>
>
>
> Institute for Infocomm Research disclaimer: "This email is confidential
> and may be privileged. If you are not the intended recipient, please
delete
> it
> and notify us immediately. Please do not copy or use it for any purpose,
or
> disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer: "This email is confidential
> and may be privileged. If you are not the intended recipient, please
delete
> it
> and notify us immediately. Please do not copy or use it for any purpose,
or
> disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer: "This email
> is confidential and may be privileged. If you are not the intended
> recipient,
> please delete it and notify us immediately. Please do not copy or use it
for
> any purpose, or disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer:  "This email is
> confidential and may be privileged. If you are not the intended
> recipient, please delete it and notify us immediately. Please do not
> copy or use it for any purpose, or disclose its contents to any other
> person. Thank you."
>
> Institute for Infocomm Research disclaimer:  "This email is confidential
and
> may be privileged. If you are not the intended recipient, please delete it
> and notify us immediately. Please do not copy or use it for any purpose,
or
> disclose its contents to any other person. Thank you."
>

Institute for Infocomm Research disclaimer:  "This email is confidential and may be privileged. If you are not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any purpose, or disclose its contents to any other person. Thank you."


From tanhdung at i2r.a-star.edu.sg  Thu Aug 13 23:12:09 2009
From: tanhdung at i2r.a-star.edu.sg (Tran)
Date: Fri, 14 Aug 2009 11:12:09 +0800
Subject: [Olympus developers 141]: Re: Problem regarding Olympus
In-Reply-To: <bd80926e0908112317x63e0f143hf6d75418a543e2b4@mail.gmail.com>
References: <000901ca10b3$85db4290$9191c7b0$@a-star.edu.sg>	
	<9C0D1A9F38D23E4290347EE31C22B0AF03549EE5@e2k3.srv.cs.cmu.edu>	
	<002e01ca10b6$aded1ad0$09c75070$@a-star.edu.sg>	
	<bd80926e0907291843w4dd44a02xbbd16e648142fa4c@mail.gmail.com>	
	<005901ca1192$6e3dc600$4ab95200$@a-star.edu.sg>	
	<bd80926e0908031641o2d734265h51a9f726ce52da95@mail.gmail.com>	
	<000901ca1a62$09559000$1c00b000$@a-star.edu.sg>	
	<bd80926e0908111141u2e71b005t7c6ac580110f3bb7@mail.gmail.com>	
	<000001ca1af8$d12efe90$738cfbb0$@a-star.edu.sg>
	<bd80926e0908112317x63e0f143hf6d75418a543e2b4@mail.gmail.com>
Message-ID: <002001ca1c8d$028c0e20$07a42a60$@a-star.edu.sg>

Sorry, attached file

-----Original Message-----
From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
Frisch
Sent: Wednesday, 12 August, 2009 2:17 PM
To: Tran
Cc: olympus-developers at loganberry.srv.cs.cmu.edu
Subject: Re: [Olympus developers 138]: Re: Problem regarding Olympus

Hi Tran,
   So I encountered the reference to the non-existent
DMCore/Events/PhoenixInput.h on my computer.  You can fix it by
removing #include "DMCore/Events/PhoenixInput.h" on line 67 of
Libraries/RavenClaw/DMCore/Agents/CoreAgents/InteractionEventManagerAgent.cp
p.
It was replaced by DMCore/Events/GalaxyInteractionEvent.h, and I guess
it was not automatically rebuilt after the deletion. (PhoenixInput.h
was removed as part of the fix for
http://trac.speech.cs.cmu.edu/olympus/ticket/52 .)  I apologize for
the inconvenience.  I'll try to get that fix committed by tomorrow.
  The other errors in building Olympus look exactly like
http://trac.speech.cs.cmu.edu/olympus/ticket/87 , which was fixed by
upgrading to Visual Studio 2005 SP1.  Send me your build.log if the
build is still not successful, and if there is an unexpected fatal
error, hang, or crash with the trunk, please send me the log file that
corresponds to the agent with the problem.  I'll do my best to try to
fix or help fix what is wrong.

Thanks,
Ben

On 8/11/09, Tran <tanhdung at i2r.a-star.edu.sg> wrote:
> Hi Ben,
>
> The attached is the build log. The line 114 is the first error, which
causes
> subsequent errors.
>
> Thanks,
> Tran Anh Dung
>
> -----Original Message-----
> From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> Frisch
> Sent: Wednesday, 12 August, 2009 2:41 AM
> To: Tran; olympus-developers at loganberry.srv.cs.cmu.edu
> Subject: [Olympus developers 133]: Problem regarding Olympus
>
> Hi,
>   Can you send me your build.log, and I'll take a look.
>
> Thanks,
> Ben
>
> On Tue, Aug 11, 2009 at 3:59 AM, Tran <tanhdung at i2r.a-star.edu.sg> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi Ben,
>
>
>
> Sorry for the late reply. I was in the ACL conference last week.
>
>
>
> Thanks for your informative email. As the problem in Vista, I
> recompiled the Olympus on Windows XP. The tutorial 1 & 2 are working fine.
> Thanks for your great effort. There is only a minor issue about speech
> recognition due to my accent. But I guess it should be improve if I
provide
> more training data.
>
>
>
> On Windows Vista, I downloaded the trunk source code to compile.
> But it seems not to work. There were error while compiling as in attached
> image. I did some preliminary checking and found that some files are
missing
> such as
>
Libraries\RavenClaw\DMCore\Agents\CoreAgents\InteractionEventManagerAgent.cp
> p.
> This file causes error while compiling RavenClaw. I don?t know what is the
> exact reason, but I think you are still doing on those source code and it
> might
> cause the problem.
>
>
>
> Once again, thanks for your help.
>
>
>
> Tran Anh Dung
>
>
>
>
>
> From: bfrisch at gmail.com
> [mailto:bfrisch at gmail.com] On Behalf Of Benjamin Frisch
> Sent: Tuesday, 4 August, 2009 7:42 AM
> To: Tran
> Cc: Olympus Developers
> Subject: Re: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
> Hi Tran,
> ? Kalliope is configured in Configurations/Desktop-SAPI/KalliopeSAPI.cfg
> inside of your example system directory to use the first adult male voice
it
> finds.? You could change the male to female in that configuration file,
> and it will use the first female voice it finds, which will probably be
Anna
> in
> your case.? This will probably cause Kalliope to synthesize correctly, as
> if the SAPI example run time application runs into an error with the male
> voices, then Kalliope would as well.? I'm not sure why the voices seem to
> be corrupted, but it could be a problem with the SAPI 5.1 SDK, which was
> originally made for Windows xp, running on Windows Vista.? The current
> Olympus trunk will detect the installation of the Windows SDK 6.1 "for
> Windows Server 2008" which includes the SAPI 5.3 SDK.? I am also
> sorry to hear that PocketSphinxEngine is crashing.? The PocketSphinxEngine
> in the Olympus trunk was largely rewritten to support PocketSphinx 0.5.
> ? In light of the PocketSphinxEngine and Kalliope issues, and your use of
> Windows Vista, I'd recommend that you try to use the Olympus trunk.? We
> are probably a couple of weeks away from an Olympus 2.5 release from the
> Olympus trunk.? As such the trunk is generally stable now.? You can
> download the Windows SDK for Windows Server 2008, which includes SAPI
> 5.3 from
>
http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-
> 9BE5-FA919850BDBF
> .? You will also need to install CMake via the Win32 Installer from
> http://cmake.org/cmake/resources/software.html
> .? The build scripts currently cause CMake to generate the Visual Studio
> solution files in the Build/cmake directory off of the Olympus Root and
off
> the
> root of the MeetingLine and soon to be added Madeline example system.
> ?? Let me know if KalliopeSAPI ends up working with SAPI 5.3
> SDK.? If it still doesn't work (but doesn't crash), then I recommend that
> you use the new KalliopeFlite support in the Olympus trunk instead, which
> you
> can use by running OlympusRebuildFlite.pl in your Olympus trunk root and
> then
> running SystemRunFlite.bat rather SystemRun.bat.? While I haven't recently
> encountered a crash while running one of our systems for a while with the
> trunk, if anything crashes for you or is not working, let me know so I can
> do
> my best to fix it before the release.
> ?? Thank you for sending in your changes to the grammar generation
> scripts in the Tutorials.? I committed your changes, and I am sorry for
> the trouble.
>
> Thanks,
> Ben Frisch
> CMU Speech Lab Undergraduate Research Assistant for Summer 2009
>
>
>
> On Thu, Jul 30, 2009 at 11:53 PM, Tran <tanhdung at i2r.a-star.edu.sg>
> wrote:
>
>
>
>
>
> Hi Benjamin,
>
>
>
> I managed to run the TTY
> version of MyBus successfully. It was very good. However, for the SAPI
> version,
> there was error. When I init_session, the console output ?Welcome to
> MyBus?, but there is no voice from the system. I guess it is because of
> the Kalliope has some problems with speech synthesis. After sometimes,
> PocketSphinx crashes. I don?t know what is the cause. I ran an example of
> Microsoft Speech. It can talk with Anna voice, but Mary and Mike voice has
> error. Could that be a problem with the voice configuration in Kalliope?
> Please
> help me on this. Thanks
>
>
>
> I also found that, the source
> code on SVN cannot compile correctly if you don?t make some changes in
> the perl script. I attach a change log file for your reference. It is nice
> if
> you make these changes on the source to minimize the effort of other
> developers.
>
>
>
>
>
> Regards,
>
> Tran Anh Dung
>
> Research Officer
>
> Human Language Technology Department
>
> A*, Singapore
>
>
>
>
>
>
>
>
>
> From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> Frisch
>
>
>
>
>
> Sent: Thursday, 30 July, 2009 9:44 AM
> To: Tran
> Cc: Alex Rudnicky
>
>
>
> Subject: Re: [Olympus developers 133]: Problem
> regarding Olympus
>
>
>
>
>
>
>
>
>
> Hi Tran,
>
>
>
> ??At least from picture, it looks like you forgot to start the
> session first. ?Just enter init_session and MyBus should start.
> ?Let's us know if you have further questions.
>
>
>
>
>
>
>
>
>
>
>
> Thanks,
>
>
>
>
>
> Ben
>
>
>
> On Wed, Jul 29, 2009 at 9:40 PM, Tran <tanhdung at i2r.a-star.edu.sg>
> wrote:
>
>
>
>
>
> I forget to attached in previous email.
>
>
>
>
>
>
>
> From: Alex Rudnicky [mailto:Alex.Rudnicky at cs.cmu.edu]
>
> Sent: Thursday, 30 July, 2009 9:26 AM
> To: Tran; olympus-developers at cs.cmu.edu
> Cc: Benjamin Frisch
> Subject: RE: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
>
>
>
>
>
>
> These systems are pedagogical and
> follow the tutorial material.
>
> Have you tried to compile and use one
> of the example systems, such as MeetingLine?
>
>
>
> ?- Alex Rudnicky
>
>
>
>
>
>
>
>
>
> From: olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu
> [mailto:olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu] On
> Behalf Of Tran
> Sent: Wednesday, July 29, 2009 9:18 PM
> To: olympus-developers at cs.cmu.edu
> Subject: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
>
>
> To whom it may concerns,
>
>
>
> We are doing research on Dialogue Management System. We found that Olympus
> is an interesting system. We downloaded and manage to compile the source
> code
> and tutorial 1/2 successfully. However, when we run it, there seems to be
> nothing happens (no interaction from system, no response while we
talking).
> We
> do not know how to operate it. Hence, could you be able to help us to
> instruct
> how to use the system? We look forward to hear from you
>
>
>
> Regards,
>
> Tran Anh Dung
>
> Research Officer
>
> Human Language Technology Department
>
> A*, Singapore
>
>
>
> PS: all the source code is downloaded as instructed on the Olympus wiki
> page. The downloaded version is 2.2 (not the development version)
>
>
>
> Institute for Infocomm Research disclaimer: "This email is confidential
> and may be privileged. If you are not the intended recipient, please
delete
> it
> and notify us immediately. Please do not copy or use it for any purpose,
or
> disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer: "This email is confidential
> and may be privileged. If you are not the intended recipient, please
delete
> it
> and notify us immediately. Please do not copy or use it for any purpose,
or
> disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer: "This email
> is confidential and may be privileged. If you are not the intended
> recipient,
> please delete it and notify us immediately. Please do not copy or use it
for
> any purpose, or disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer:  "This email is
> confidential and may be privileged. If you are not the intended
> recipient, please delete it and notify us immediately. Please do not
> copy or use it for any purpose, or disclose its contents to any other
> person. Thank you."
>
> Institute for Infocomm Research disclaimer:  "This email is confidential
and
> may be privileged. If you are not the intended recipient, please delete it
> and notify us immediately. Please do not copy or use it for any purpose,
or
> disclose its contents to any other person. Thank you."
>

Institute for Infocomm Research disclaimer:  "This email is confidential and may be privileged. If you are not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any purpose, or disclose its contents to any other person. Thank you."
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: compile.txt
Url: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090813/b2c3349b/compile-0001.txt

From tanhdung at i2r.a-star.edu.sg  Thu Aug 13 23:35:52 2009
From: tanhdung at i2r.a-star.edu.sg (Tran)
Date: Fri, 14 Aug 2009 11:35:52 +0800
Subject: [Olympus developers 142]: Re: Problem regarding Olympus
In-Reply-To: <bd80926e0908112317x63e0f143hf6d75418a543e2b4@mail.gmail.com>
References: <000901ca10b3$85db4290$9191c7b0$@a-star.edu.sg>	
	<9C0D1A9F38D23E4290347EE31C22B0AF03549EE5@e2k3.srv.cs.cmu.edu>	
	<002e01ca10b6$aded1ad0$09c75070$@a-star.edu.sg>	
	<bd80926e0907291843w4dd44a02xbbd16e648142fa4c@mail.gmail.com>	
	<005901ca1192$6e3dc600$4ab95200$@a-star.edu.sg>	
	<bd80926e0908031641o2d734265h51a9f726ce52da95@mail.gmail.com>	
	<000901ca1a62$09559000$1c00b000$@a-star.edu.sg>	
	<bd80926e0908111141u2e71b005t7c6ac580110f3bb7@mail.gmail.com>	
	<000001ca1af8$d12efe90$738cfbb0$@a-star.edu.sg>
	<bd80926e0908112317x63e0f143hf6d75418a543e2b4@mail.gmail.com>
Message-ID: <002b01ca1c90$52adca30$f8095e90$@a-star.edu.sg>

Hi Ben,

I managed to compile simpleaudio successfully. I forgot to run the SDK
Configuration Tool. That's why the issue happened.

However, when I run the MeetingLine or tutorial 1, the Kalliope crashed.
Here is the log of Kalliope I found on the GUI

KALLIOPE 2.0. Compiled on Aug 11 2009, at 15:09:35. 

[GXI at 11:32:56.441] _GalSS_init_server called.
[GXI at 11:32:56.441] Reading configuration file KalliopeSAPI.cfg
[STD at 11:32:56.441 (9447345)] required_voice_attributes = Age=Adult
[STD at 11:32:56.441 (9447345)] optional_voice_attributes = Gender=Male
[STD at 11:32:56.441 (9447345)] speech_rate = 0
[STD at 11:32:56.441 (9447345)] volume = 100
[STD at 11:32:56.441 (9447345)] audio_format = 22
[STD at 11:32:56.441 (9447345)] log = true
[STD at 11:32:56.441 (9447345)] log_audio = false
[ERR at 11:32:56.847 (9447751)] Unable to create SAPI SpAudioPlug instance.
======================================

-----Original Message-----
From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
Frisch
Sent: Wednesday, 12 August, 2009 2:17 PM
To: Tran
Cc: olympus-developers at loganberry.srv.cs.cmu.edu
Subject: Re: [Olympus developers 138]: Re: Problem regarding Olympus

Hi Tran,
   So I encountered the reference to the non-existent
DMCore/Events/PhoenixInput.h on my computer.  You can fix it by
removing #include "DMCore/Events/PhoenixInput.h" on line 67 of
Libraries/RavenClaw/DMCore/Agents/CoreAgents/InteractionEventManagerAgent.cp
p.
It was replaced by DMCore/Events/GalaxyInteractionEvent.h, and I guess
it was not automatically rebuilt after the deletion. (PhoenixInput.h
was removed as part of the fix for
http://trac.speech.cs.cmu.edu/olympus/ticket/52 .)  I apologize for
the inconvenience.  I'll try to get that fix committed by tomorrow.
  The other errors in building Olympus look exactly like
http://trac.speech.cs.cmu.edu/olympus/ticket/87 , which was fixed by
upgrading to Visual Studio 2005 SP1.  Send me your build.log if the
build is still not successful, and if there is an unexpected fatal
error, hang, or crash with the trunk, please send me the log file that
corresponds to the agent with the problem.  I'll do my best to try to
fix or help fix what is wrong.

Thanks,
Ben

On 8/11/09, Tran <tanhdung at i2r.a-star.edu.sg> wrote:
> Hi Ben,
>
> The attached is the build log. The line 114 is the first error, which
causes
> subsequent errors.
>
> Thanks,
> Tran Anh Dung
>
> -----Original Message-----
> From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> Frisch
> Sent: Wednesday, 12 August, 2009 2:41 AM
> To: Tran; olympus-developers at loganberry.srv.cs.cmu.edu
> Subject: [Olympus developers 133]: Problem regarding Olympus
>
> Hi,
>   Can you send me your build.log, and I'll take a look.
>
> Thanks,
> Ben
>
> On Tue, Aug 11, 2009 at 3:59 AM, Tran <tanhdung at i2r.a-star.edu.sg> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi Ben,
>
>
>
> Sorry for the late reply. I was in the ACL conference last week.
>
>
>
> Thanks for your informative email. As the problem in Vista, I
> recompiled the Olympus on Windows XP. The tutorial 1 & 2 are working fine.
> Thanks for your great effort. There is only a minor issue about speech
> recognition due to my accent. But I guess it should be improve if I
provide
> more training data.
>
>
>
> On Windows Vista, I downloaded the trunk source code to compile.
> But it seems not to work. There were error while compiling as in attached
> image. I did some preliminary checking and found that some files are
missing
> such as
>
Libraries\RavenClaw\DMCore\Agents\CoreAgents\InteractionEventManagerAgent.cp
> p.
> This file causes error while compiling RavenClaw. I don?t know what is the
> exact reason, but I think you are still doing on those source code and it
> might
> cause the problem.
>
>
>
> Once again, thanks for your help.
>
>
>
> Tran Anh Dung
>
>
>
>
>
> From: bfrisch at gmail.com
> [mailto:bfrisch at gmail.com] On Behalf Of Benjamin Frisch
> Sent: Tuesday, 4 August, 2009 7:42 AM
> To: Tran
> Cc: Olympus Developers
> Subject: Re: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
> Hi Tran,
> ? Kalliope is configured in Configurations/Desktop-SAPI/KalliopeSAPI.cfg
> inside of your example system directory to use the first adult male voice
it
> finds.? You could change the male to female in that configuration file,
> and it will use the first female voice it finds, which will probably be
Anna
> in
> your case.? This will probably cause Kalliope to synthesize correctly, as
> if the SAPI example run time application runs into an error with the male
> voices, then Kalliope would as well.? I'm not sure why the voices seem to
> be corrupted, but it could be a problem with the SAPI 5.1 SDK, which was
> originally made for Windows xp, running on Windows Vista.? The current
> Olympus trunk will detect the installation of the Windows SDK 6.1 "for
> Windows Server 2008" which includes the SAPI 5.3 SDK.? I am also
> sorry to hear that PocketSphinxEngine is crashing.? The PocketSphinxEngine
> in the Olympus trunk was largely rewritten to support PocketSphinx 0.5.
> ? In light of the PocketSphinxEngine and Kalliope issues, and your use of
> Windows Vista, I'd recommend that you try to use the Olympus trunk.? We
> are probably a couple of weeks away from an Olympus 2.5 release from the
> Olympus trunk.? As such the trunk is generally stable now.? You can
> download the Windows SDK for Windows Server 2008, which includes SAPI
> 5.3 from
>
http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-
> 9BE5-FA919850BDBF
> .? You will also need to install CMake via the Win32 Installer from
> http://cmake.org/cmake/resources/software.html
> .? The build scripts currently cause CMake to generate the Visual Studio
> solution files in the Build/cmake directory off of the Olympus Root and
off
> the
> root of the MeetingLine and soon to be added Madeline example system.
> ?? Let me know if KalliopeSAPI ends up working with SAPI 5.3
> SDK.? If it still doesn't work (but doesn't crash), then I recommend that
> you use the new KalliopeFlite support in the Olympus trunk instead, which
> you
> can use by running OlympusRebuildFlite.pl in your Olympus trunk root and
> then
> running SystemRunFlite.bat rather SystemRun.bat.? While I haven't recently
> encountered a crash while running one of our systems for a while with the
> trunk, if anything crashes for you or is not working, let me know so I can
> do
> my best to fix it before the release.
> ?? Thank you for sending in your changes to the grammar generation
> scripts in the Tutorials.? I committed your changes, and I am sorry for
> the trouble.
>
> Thanks,
> Ben Frisch
> CMU Speech Lab Undergraduate Research Assistant for Summer 2009
>
>
>
> On Thu, Jul 30, 2009 at 11:53 PM, Tran <tanhdung at i2r.a-star.edu.sg>
> wrote:
>
>
>
>
>
> Hi Benjamin,
>
>
>
> I managed to run the TTY
> version of MyBus successfully. It was very good. However, for the SAPI
> version,
> there was error. When I init_session, the console output ?Welcome to
> MyBus?, but there is no voice from the system. I guess it is because of
> the Kalliope has some problems with speech synthesis. After sometimes,
> PocketSphinx crashes. I don?t know what is the cause. I ran an example of
> Microsoft Speech. It can talk with Anna voice, but Mary and Mike voice has
> error. Could that be a problem with the voice configuration in Kalliope?
> Please
> help me on this. Thanks
>
>
>
> I also found that, the source
> code on SVN cannot compile correctly if you don?t make some changes in
> the perl script. I attach a change log file for your reference. It is nice
> if
> you make these changes on the source to minimize the effort of other
> developers.
>
>
>
>
>
> Regards,
>
> Tran Anh Dung
>
> Research Officer
>
> Human Language Technology Department
>
> A*, Singapore
>
>
>
>
>
>
>
>
>
> From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> Frisch
>
>
>
>
>
> Sent: Thursday, 30 July, 2009 9:44 AM
> To: Tran
> Cc: Alex Rudnicky
>
>
>
> Subject: Re: [Olympus developers 133]: Problem
> regarding Olympus
>
>
>
>
>
>
>
>
>
> Hi Tran,
>
>
>
> ??At least from picture, it looks like you forgot to start the
> session first. ?Just enter init_session and MyBus should start.
> ?Let's us know if you have further questions.
>
>
>
>
>
>
>
>
>
>
>
> Thanks,
>
>
>
>
>
> Ben
>
>
>
> On Wed, Jul 29, 2009 at 9:40 PM, Tran <tanhdung at i2r.a-star.edu.sg>
> wrote:
>
>
>
>
>
> I forget to attached in previous email.
>
>
>
>
>
>
>
> From: Alex Rudnicky [mailto:Alex.Rudnicky at cs.cmu.edu]
>
> Sent: Thursday, 30 July, 2009 9:26 AM
> To: Tran; olympus-developers at cs.cmu.edu
> Cc: Benjamin Frisch
> Subject: RE: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
>
>
>
>
>
>
> These systems are pedagogical and
> follow the tutorial material.
>
> Have you tried to compile and use one
> of the example systems, such as MeetingLine?
>
>
>
> ?- Alex Rudnicky
>
>
>
>
>
>
>
>
>
> From: olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu
> [mailto:olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu] On
> Behalf Of Tran
> Sent: Wednesday, July 29, 2009 9:18 PM
> To: olympus-developers at cs.cmu.edu
> Subject: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
>
>
> To whom it may concerns,
>
>
>
> We are doing research on Dialogue Management System. We found that Olympus
> is an interesting system. We downloaded and manage to compile the source
> code
> and tutorial 1/2 successfully. However, when we run it, there seems to be
> nothing happens (no interaction from system, no response while we
talking).
> We
> do not know how to operate it. Hence, could you be able to help us to
> instruct
> how to use the system? We look forward to hear from you
>
>
>
> Regards,
>
> Tran Anh Dung
>
> Research Officer
>
> Human Language Technology Department
>
> A*, Singapore
>
>
>
> PS: all the source code is downloaded as instructed on the Olympus wiki
> page. The downloaded version is 2.2 (not the development version)
>
>
>
> Institute for Infocomm Research disclaimer: "This email is confidential
> and may be privileged. If you are not the intended recipient, please
delete
> it
> and notify us immediately. Please do not copy or use it for any purpose,
or
> disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer: "This email is confidential
> and may be privileged. If you are not the intended recipient, please
delete
> it
> and notify us immediately. Please do not copy or use it for any purpose,
or
> disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer: "This email
> is confidential and may be privileged. If you are not the intended
> recipient,
> please delete it and notify us immediately. Please do not copy or use it
for
> any purpose, or disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer:  "This email is
> confidential and may be privileged. If you are not the intended
> recipient, please delete it and notify us immediately. Please do not
> copy or use it for any purpose, or disclose its contents to any other
> person. Thank you."
>
> Institute for Infocomm Research disclaimer:  "This email is confidential
and
> may be privileged. If you are not the intended recipient, please delete it
> and notify us immediately. Please do not copy or use it for any purpose,
or
> disclose its contents to any other person. Thank you."
>

Institute for Infocomm Research disclaimer:  "This email is confidential and may be privileged. If you are not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any purpose, or disclose its contents to any other person. Thank you."


From bfrisch at cs.cmu.edu  Mon Aug 17 01:31:08 2009
From: bfrisch at cs.cmu.edu (Benjamin Frisch)
Date: Mon, 17 Aug 2009 01:31:08 -0400
Subject: [Olympus developers 143]: Re: Problem regarding Olympus
In-Reply-To: <002b01ca1c90$52adca30$f8095e90$@a-star.edu.sg>
References: <000901ca10b3$85db4290$9191c7b0$@a-star.edu.sg> 
	<002e01ca10b6$aded1ad0$09c75070$@a-star.edu.sg>
	<bd80926e0907291843w4dd44a02xbbd16e648142fa4c@mail.gmail.com> 
	<005901ca1192$6e3dc600$4ab95200$@a-star.edu.sg>
	<bd80926e0908031641o2d734265h51a9f726ce52da95@mail.gmail.com> 
	<000901ca1a62$09559000$1c00b000$@a-star.edu.sg>
	<bd80926e0908111141u2e71b005t7c6ac580110f3bb7@mail.gmail.com> 
	<000001ca1af8$d12efe90$738cfbb0$@a-star.edu.sg>
	<bd80926e0908112317x63e0f143hf6d75418a543e2b4@mail.gmail.com> 
	<002b01ca1c90$52adca30$f8095e90$@a-star.edu.sg>
Message-ID: <bd80926e0908162231o9395a1bpd2f55cb1f13cd30f@mail.gmail.com>

Hi Tran,  Sorry for the delay in getting back to you.  I have been away for
the past week days, with sporadic e-mail access.  I guess Visual Studio
2008's default SDK already had the proper definition's.  I'll make sure to
document that you need to run the SDK configuration tool with Visual Studio
2005.  I'm not sure why you are "Unable to create SAPI SpAudioPlug
instance.", but I think it is because the SAPI Audio DLL is not registered
with Windows.  (It should be registered by the Visual Studio project, but
security restrictions on Vista might lead to the registration not working.)
 Try executing regsvr32 "C:\Program Files\Microsoft
SDKs\Windows\v6.1\Samples\winui\Speech\SimpleAudio\Release\SimpleAudio.dll"
in a command prompt that you launch with Administrator permissions, and then
rerun KalliopeSAPI.  If KalliopeSAPI still doesn't work, I recommend that
you use Flite instead of SAPi by first running OlympusRebuildFlite.pl (you
have to run the rebuild script to clear CMake's build configuration cache
when switching between synthesizer APIs), and once that
completes successfully, run SystemRunFlite.bat rather than SystemRun.bat in
the system directories.
  If you are unhappy with Flite as your synthesizer, you can try changing
optional_voice_attributes = Gender=Male to optional_voice_attributes =
Gender=Female in KalliopeSAPI.cfg in Configurations/Desktop in all example
systems and tutorials except for RoomLine where the configuration file is in
Configurations/Desktop-FakeDB and then, run OlympusRebuild.pl in Olympus,
and then run a system using KalliopeSAPI via the normal SystemRun.bat script
like before. With the previous configuration changes you should end up using
Microsoft Anna, which shouldn't have synthesis problems for you with
KalliopeSAPI.  Let me know how it goes.

Thanks,
Ben Frisch

On Thu, Aug 13, 2009 at 11:35 PM, Tran <tanhdung at i2r.a-star.edu.sg> wrote:

> Hi Ben,
>
> I managed to compile simpleaudio successfully. I forgot to run the SDK
> Configuration Tool. That's why the issue happened.
>
> However, when I run the MeetingLine or tutorial 1, the Kalliope crashed.
> Here is the log of Kalliope I found on the GUI
>
> KALLIOPE 2.0. Compiled on Aug 11 2009, at 15:09:35.
>
> [GXI at 11:32:56.441] _GalSS_init_server called.
> [GXI at 11:32:56.441] Reading configuration file KalliopeSAPI.cfg
> [STD at 11:32:56.441 (9447345)] required_voice_attributes = Age=Adult
> [STD at 11:32:56.441 (9447345)] optional_voice_attributes = Gender=Male
> [STD at 11:32:56.441 (9447345)] speech_rate = 0
> [STD at 11:32:56.441 (9447345)] volume = 100
> [STD at 11:32:56.441 (9447345)] audio_format = 22
> [STD at 11:32:56.441 (9447345)] log = true
> [STD at 11:32:56.441 (9447345)] log_audio = false
> [ERR at 11:32:56.847 (9447751)] Unable to create SAPI SpAudioPlug instance.
> ======================================
>
> -----Original Message-----
> From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> Frisch
> Sent: Wednesday, 12 August, 2009 2:17 PM
> To: Tran
> Cc: olympus-developers at loganberry.srv.cs.cmu.edu
> Subject: Re: [Olympus developers 138]: Re: Problem regarding Olympus
>
> Hi Tran,
>    So I encountered the reference to the non-existent
> DMCore/Events/PhoenixInput.h on my computer.  You can fix it by
> removing #include "DMCore/Events/PhoenixInput.h" on line 67 of
>
> Libraries/RavenClaw/DMCore/Agents/CoreAgents/InteractionEventManagerAgent.cp
> p.
> It was replaced by DMCore/Events/GalaxyInteractionEvent.h, and I guess
> it was not automatically rebuilt after the deletion. (PhoenixInput.h
> was removed as part of the fix for
> http://trac.speech.cs.cmu.edu/olympus/ticket/52 .)  I apologize for
> the inconvenience.  I'll try to get that fix committed by tomorrow.
>  The other errors in building Olympus look exactly like
> http://trac.speech.cs.cmu.edu/olympus/ticket/87 , which was fixed by
> upgrading to Visual Studio 2005 SP1.  Send me your build.log if the
> build is still not successful, and if there is an unexpected fatal
> error, hang, or crash with the trunk, please send me the log file that
> corresponds to the agent with the problem.  I'll do my best to try to
> fix or help fix what is wrong.
>
> Thanks,
> Ben
>
> On 8/11/09, Tran <tanhdung at i2r.a-star.edu.sg> wrote:
> > Hi Ben,
> >
> > The attached is the build log. The line 114 is the first error, which
> causes
> > subsequent errors.
> >
> > Thanks,
> > Tran Anh Dung
> >
> > -----Original Message-----
> > From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> > Frisch
> > Sent: Wednesday, 12 August, 2009 2:41 AM
> > To: Tran; olympus-developers at loganberry.srv.cs.cmu.edu
> > Subject: [Olympus developers 133]: Problem regarding Olympus
> >
> > Hi,
> >   Can you send me your build.log, and I'll take a look.
> >
> > Thanks,
> > Ben
> >
> > On Tue, Aug 11, 2009 at 3:59 AM, Tran <tanhdung at i2r.a-star.edu.sg>
> wrote:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi Ben,
> >
> >
> >
> > Sorry for the late reply. I was in the ACL conference last week.
> >
> >
> >
> > Thanks for your informative email. As the problem in Vista, I
> > recompiled the Olympus on Windows XP. The tutorial 1 & 2 are working
> fine.
> > Thanks for your great effort. There is only a minor issue about speech
> > recognition due to my accent. But I guess it should be improve if I
> provide
> > more training data.
> >
> >
> >
> > On Windows Vista, I downloaded the trunk source code to compile.
> > But it seems not to work. There were error while compiling as in attached
> > image. I did some preliminary checking and found that some files are
> missing
> > such as
> >
>
> Libraries\RavenClaw\DMCore\Agents\CoreAgents\InteractionEventManagerAgent.cp
> > p.
> > This file causes error while compiling RavenClaw. I don?t know what is
> the
> > exact reason, but I think you are still doing on those source code and it
> > might
> > cause the problem.
> >
> >
> >
> > Once again, thanks for your help.
> >
> >
> >
> > Tran Anh Dung
> >
> >
> >
> >
> >
> > From: bfrisch at gmail.com
> > [mailto:bfrisch at gmail.com] On Behalf Of Benjamin Frisch
> > Sent: Tuesday, 4 August, 2009 7:42 AM
> > To: Tran
> > Cc: Olympus Developers
> > Subject: Re: [Olympus developers 133]: Problem regarding Olympus
> >
> >
> >
> >
> >
> > Hi Tran,
> >   Kalliope is configured in Configurations/Desktop-SAPI/KalliopeSAPI.cfg
> > inside of your example system directory to use the first adult male voice
> it
> > finds.  You could change the male to female in that configuration file,
> > and it will use the first female voice it finds, which will probably be
> Anna
> > in
> > your case.  This will probably cause Kalliope to synthesize correctly, as
> > if the SAPI example run time application runs into an error with the male
> > voices, then Kalliope would as well.  I'm not sure why the voices seem to
> > be corrupted, but it could be a problem with the SAPI 5.1 SDK, which was
> > originally made for Windows xp, running on Windows Vista.  The current
> > Olympus trunk will detect the installation of the Windows SDK 6.1 "for
> > Windows Server 2008" which includes the SAPI 5.3 SDK.  I am also
> > sorry to hear that PocketSphinxEngine is crashing.  The
> PocketSphinxEngine
> > in the Olympus trunk was largely rewritten to support PocketSphinx 0.5.
> >   In light of the PocketSphinxEngine and Kalliope issues, and your use of
> > Windows Vista, I'd recommend that you try to use the Olympus trunk.  We
> > are probably a couple of weeks away from an Olympus 2.5 release from the
> > Olympus trunk.  As such the trunk is generally stable now.  You can
> > download the Windows SDK for Windows Server 2008, which includes SAPI
> > 5.3 from
> >
>
> http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-
> > 9BE5-FA919850BDBF
> > .  You will also need to install CMake via the Win32 Installer from
> > http://cmake.org/cmake/resources/software.html
> > .  The build scripts currently cause CMake to generate the Visual Studio
> > solution files in the Build/cmake directory off of the Olympus Root and
> off
> > the
> > root of the MeetingLine and soon to be added Madeline example system.
> >    Let me know if KalliopeSAPI ends up working with SAPI 5.3
> > SDK.  If it still doesn't work (but doesn't crash), then I recommend that
> > you use the new KalliopeFlite support in the Olympus trunk instead, which
> > you
> > can use by running OlympusRebuildFlite.pl in your Olympus trunk root and
> > then
> > running SystemRunFlite.bat rather SystemRun.bat.  While I haven't
> recently
> > encountered a crash while running one of our systems for a while with the
> > trunk, if anything crashes for you or is not working, let me know so I
> can
> > do
> > my best to fix it before the release.
> >    Thank you for sending in your changes to the grammar generation
> > scripts in the Tutorials.  I committed your changes, and I am sorry for
> > the trouble.
> >
> > Thanks,
> > Ben Frisch
> > CMU Speech Lab Undergraduate Research Assistant for Summer 2009
> >
> >
> >
> > On Thu, Jul 30, 2009 at 11:53 PM, Tran <tanhdung at i2r.a-star.edu.sg>
> > wrote:
> >
> >
> >
> >
> >
> > Hi Benjamin,
> >
> >
> >
> > I managed to run the TTY
> > version of MyBus successfully. It was very good. However, for the SAPI
> > version,
> > there was error. When I init_session, the console output ?Welcome to
> > MyBus?, but there is no voice from the system. I guess it is because of
> > the Kalliope has some problems with speech synthesis. After sometimes,
> > PocketSphinx crashes. I don?t know what is the cause. I ran an example of
> > Microsoft Speech. It can talk with Anna voice, but Mary and Mike voice
> has
> > error. Could that be a problem with the voice configuration in Kalliope?
> > Please
> > help me on this. Thanks
> >
> >
> >
> > I also found that, the source
> > code on SVN cannot compile correctly if you don?t make some changes in
> > the perl script. I attach a change log file for your reference. It is
> nice
> > if
> > you make these changes on the source to minimize the effort of other
> > developers.
> >
> >
> >
> >
> >
> > Regards,
> >
> > Tran Anh Dung
> >
> > Research Officer
> >
> > Human Language Technology Department
> >
> > A*, Singapore
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> > Frisch
> >
> >
> >
> >
> >
> > Sent: Thursday, 30 July, 2009 9:44 AM
> > To: Tran
> > Cc: Alex Rudnicky
> >
> >
> >
> > Subject: Re: [Olympus developers 133]: Problem
> > regarding Olympus
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi Tran,
> >
> >
> >
> >   At least from picture, it looks like you forgot to start the
> > session first.  Just enter init_session and MyBus should start.
> >  Let's us know if you have further questions.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Thanks,
> >
> >
> >
> >
> >
> > Ben
> >
> >
> >
> > On Wed, Jul 29, 2009 at 9:40 PM, Tran <tanhdung at i2r.a-star.edu.sg>
> > wrote:
> >
> >
> >
> >
> >
> > I forget to attached in previous email.
> >
> >
> >
> >
> >
> >
> >
> > From: Alex Rudnicky [mailto:Alex.Rudnicky at cs.cmu.edu]
> >
> > Sent: Thursday, 30 July, 2009 9:26 AM
> > To: Tran; olympus-developers at cs.cmu.edu
> > Cc: Benjamin Frisch
> > Subject: RE: [Olympus developers 133]: Problem regarding Olympus
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > These systems are pedagogical and
> > follow the tutorial material.
> >
> > Have you tried to compile and use one
> > of the example systems, such as MeetingLine?
> >
> >
> >
> >  - Alex Rudnicky
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > From: olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu
> > [mailto:olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu] On
> > Behalf Of Tran
> > Sent: Wednesday, July 29, 2009 9:18 PM
> > To: olympus-developers at cs.cmu.edu
> > Subject: [Olympus developers 133]: Problem regarding Olympus
> >
> >
> >
> >
> >
> >
> >
> > To whom it may concerns,
> >
> >
> >
> > We are doing research on Dialogue Management System. We found that
> Olympus
> > is an interesting system. We downloaded and manage to compile the source
> > code
> > and tutorial 1/2 successfully. However, when we run it, there seems to be
> > nothing happens (no interaction from system, no response while we
> talking).
> > We
> > do not know how to operate it. Hence, could you be able to help us to
> > instruct
> > how to use the system? We look forward to hear from you
> >
> >
> >
> > Regards,
> >
> > Tran Anh Dung
> >
> > Research Officer
> >
> > Human Language Technology Department
> >
> > A*, Singapore
> >
> >
> >
> > PS: all the source code is downloaded as instructed on the Olympus wiki
> > page. The downloaded version is 2.2 (not the development version)
> >
> >
> >
> > Institute for Infocomm Research disclaimer: "This email is confidential
> > and may be privileged. If you are not the intended recipient, please
> delete
> > it
> > and notify us immediately. Please do not copy or use it for any purpose,
> or
> > disclose its contents to any other person. Thank you."
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Institute for Infocomm Research disclaimer: "This email is confidential
> > and may be privileged. If you are not the intended recipient, please
> delete
> > it
> > and notify us immediately. Please do not copy or use it for any purpose,
> or
> > disclose its contents to any other person. Thank you."
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Institute for Infocomm Research disclaimer: "This email
> > is confidential and may be privileged. If you are not the intended
> > recipient,
> > please delete it and notify us immediately. Please do not copy or use it
> for
> > any purpose, or disclose its contents to any other person. Thank you."
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Institute for Infocomm Research disclaimer:  "This email is
> > confidential and may be privileged. If you are not the intended
> > recipient, please delete it and notify us immediately. Please do not
> > copy or use it for any purpose, or disclose its contents to any other
> > person. Thank you."
> >
> > Institute for Infocomm Research disclaimer:  "This email is confidential
> and
> > may be privileged. If you are not the intended recipient, please delete
> it
> > and notify us immediately. Please do not copy or use it for any purpose,
> or
> > disclose its contents to any other person. Thank you."
> >
>
> Institute for Infocomm Research disclaimer:  "This email is confidential
> and may be privileged. If you are not the intended recipient, please delete
> it and notify us immediately. Please do not copy or use it for any purpose,
> or disclose its contents to any other person. Thank you."
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090817/dc12735f/attachment-0001.html

From tanhdung at i2r.a-star.edu.sg  Mon Aug 17 01:53:40 2009
From: tanhdung at i2r.a-star.edu.sg (Tran)
Date: Mon, 17 Aug 2009 13:53:40 +0800
Subject: [Olympus developers 144]: Re: Problem regarding Olympus
In-Reply-To: <bd80926e0908162231o9395a1bpd2f55cb1f13cd30f@mail.gmail.com>
References: <000901ca10b3$85db4290$9191c7b0$@a-star.edu.sg>
	<002e01ca10b6$aded1ad0$09c75070$@a-star.edu.sg>
	<bd80926e0907291843w4dd44a02xbbd16e648142fa4c@mail.gmail.com>
	<005901ca1192$6e3dc600$4ab95200$@a-star.edu.sg>
	<bd80926e0908031641o2d734265h51a9f726ce52da95@mail.gmail.com>
	<000901ca1a62$09559000$1c00b000$@a-star.edu.sg>
	<bd80926e0908111141u2e71b005t7c6ac580110f3bb7@mail.gmail.com>
	<000001ca1af8$d12efe90$738cfbb0$@a-star.edu.sg>
	<bd80926e0908112317x63e0f143hf6d75418a543e2b4@mail.gmail.com>
	<002b01ca1c90$52adca30$f8095e90$@a-star.edu.sg>
	<bd80926e0908162231o9395a1bpd2f55cb1f13cd30f@mail.gmail.com>
Message-ID: <001e01ca1eff$129b93c0$37d2bb40$@a-star.edu.sg>

Hi Ben

 

Thanks for your response. I resolved that problem. In fact, Vista prevented
my login account to access some system files. After I ran it with admin
privilege, the problem was disappeared. Now, I'm studying your code to
understand how you implemented the system. Once again thanks for your kind
helping.

 

Tran Anh Dung

 

From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
Frisch
Sent: Monday, 17 August, 2009 1:31 PM
To: Tran
Cc: olympus-developers at loganberry.srv.cs.cmu.edu
Subject: Re: [Olympus developers 138]: Re: Problem regarding Olympus

 

Hi Tran,

  Sorry for the delay in getting back to you.  I have been away for the past
week days, with sporadic e-mail access.  I guess Visual Studio 2008's
default SDK already had the proper definition's.  I'll make sure to document
that you need to run the SDK configuration tool with Visual Studio 2005.
I'm not sure why you are "Unable to create SAPI SpAudioPlug instance.", but
I think it is because the SAPI Audio DLL is not registered with Windows.
(It should be registered by the Visual Studio project, but security
restrictions on Vista might lead to the registration not working.)  Try
executing regsvr32 "C:\Program Files\Microsoft
SDKs\Windows\v6.1\Samples\winui\Speech\SimpleAudio\Release\SimpleAudio.dll"
in a command prompt that you launch with Administrator permissions, and then
rerun KalliopeSAPI.  If KalliopeSAPI still doesn't work, I recommend that
you use Flite instead of SAPi by first running OlympusRebuildFlite.pl (you
have to run the rebuild script to clear CMake's build configuration cache
when switching between synthesizer APIs), and once that completes
successfully, run SystemRunFlite.bat rather than SystemRun.bat in the system
directories.  

  If you are unhappy with Flite as your synthesizer, you can try changing
optional_voice_attributes = Gender=Male to optional_voice_attributes =
Gender=Female in KalliopeSAPI.cfg in Configurations/Desktop in all example
systems and tutorials except for RoomLine where the configuration file is in
Configurations/Desktop-FakeDB and then, run OlympusRebuild.pl in Olympus,
and then run a system using KalliopeSAPI via the normal SystemRun.bat script
like before. With the previous configuration changes you should end up using
Microsoft Anna, which shouldn't have synthesis problems for you with
KalliopeSAPI.  Let me know how it goes.

 

Thanks,

Ben Frisch

 

On Thu, Aug 13, 2009 at 11:35 PM, Tran <tanhdung at i2r.a-star.edu.sg> wrote:

Hi Ben,

I managed to compile simpleaudio successfully. I forgot to run the SDK
Configuration Tool. That's why the issue happened.

However, when I run the MeetingLine or tutorial 1, the Kalliope crashed.
Here is the log of Kalliope I found on the GUI

KALLIOPE 2.0. Compiled on Aug 11 2009, at 15:09:35.

[GXI at 11:32:56.441] _GalSS_init_server called.
[GXI at 11:32:56.441] Reading configuration file KalliopeSAPI.cfg
[STD at 11:32:56.441 (9447345)] required_voice_attributes = Age=Adult
[STD at 11:32:56.441 (9447345)] optional_voice_attributes = Gender=Male
[STD at 11:32:56.441 (9447345)] speech_rate = 0
[STD at 11:32:56.441 (9447345)] volume = 100
[STD at 11:32:56.441 (9447345)] audio_format = 22
[STD at 11:32:56.441 (9447345)] log = true
[STD at 11:32:56.441 (9447345)] log_audio = false
[ERR at 11:32:56.847 (9447751)] Unable to create SAPI SpAudioPlug instance.
======================================


-----Original Message-----
From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
Frisch

Sent: Wednesday, 12 August, 2009 2:17 PM
To: Tran
Cc: olympus-developers at loganberry.srv.cs.cmu.edu

Subject: Re: [Olympus developers 138]: Re: Problem regarding Olympus

Hi Tran,

  So I encountered the reference to the non-existent
DMCore/Events/PhoenixInput.h on my computer.  You can fix it by
removing #include "DMCore/Events/PhoenixInput.h" on line 67 of
Libraries/RavenClaw/DMCore/Agents/CoreAgents/InteractionEventManagerAgent.cp
p.
It was replaced by DMCore/Events/GalaxyInteractionEvent.h, and I guess
it was not automatically rebuilt after the deletion. (PhoenixInput.h
was removed as part of the fix for
http://trac.speech.cs.cmu.edu/olympus/ticket/52 .)  I apologize for
the inconvenience.  I'll try to get that fix committed by tomorrow.
 The other errors in building Olympus look exactly like
http://trac.speech.cs.cmu.edu/olympus/ticket/87 , which was fixed by
upgrading to Visual Studio 2005 SP1.  Send me your build.log if the
build is still not successful, and if there is an unexpected fatal
error, hang, or crash with the trunk, please send me the log file that
corresponds to the agent with the problem.  I'll do my best to try to
fix or help fix what is wrong.

Thanks,
Ben

On 8/11/09, Tran <tanhdung at i2r.a-star.edu.sg> wrote:
> Hi Ben,
>
> The attached is the build log. The line 114 is the first error, which
causes
> subsequent errors.
>
> Thanks,
> Tran Anh Dung
>
> -----Original Message-----
> From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> Frisch
> Sent: Wednesday, 12 August, 2009 2:41 AM
> To: Tran; olympus-developers at loganberry.srv.cs.cmu.edu
> Subject: [Olympus developers 133]: Problem regarding Olympus
>
> Hi,
>   Can you send me your build.log, and I'll take a look.
>
> Thanks,
> Ben
>
> On Tue, Aug 11, 2009 at 3:59 AM, Tran <tanhdung at i2r.a-star.edu.sg> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi Ben,
>
>
>
> Sorry for the late reply. I was in the ACL conference last week.
>
>
>
> Thanks for your informative email. As the problem in Vista, I
> recompiled the Olympus on Windows XP. The tutorial 1 & 2 are working fine.
> Thanks for your great effort. There is only a minor issue about speech
> recognition due to my accent. But I guess it should be improve if I
provide
> more training data.
>
>
>
> On Windows Vista, I downloaded the trunk source code to compile.
> But it seems not to work. There were error while compiling as in attached
> image. I did some preliminary checking and found that some files are
missing
> such as
>
Libraries\RavenClaw\DMCore\Agents\CoreAgents\InteractionEventManagerAgent.cp
> p.
> This file causes error while compiling RavenClaw. I don't know what is the
> exact reason, but I think you are still doing on those source code and it
> might
> cause the problem.
>
>
>
> Once again, thanks for your help.
>
>
>
> Tran Anh Dung
>
>
>
>
>
> From: bfrisch at gmail.com
> [mailto:bfrisch at gmail.com] On Behalf Of Benjamin Frisch
> Sent: Tuesday, 4 August, 2009 7:42 AM
> To: Tran
> Cc: Olympus Developers
> Subject: Re: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
> Hi Tran,
>   Kalliope is configured in Configurations/Desktop-SAPI/KalliopeSAPI.cfg
> inside of your example system directory to use the first adult male voice
it
> finds.  You could change the male to female in that configuration file,
> and it will use the first female voice it finds, which will probably be
Anna
> in
> your case.  This will probably cause Kalliope to synthesize correctly, as
> if the SAPI example run time application runs into an error with the male
> voices, then Kalliope would as well.  I'm not sure why the voices seem to
> be corrupted, but it could be a problem with the SAPI 5.1 SDK, which was
> originally made for Windows xp, running on Windows Vista.  The current
> Olympus trunk will detect the installation of the Windows SDK 6.1 "for
> Windows Server 2008" which includes the SAPI 5.3 SDK.  I am also
> sorry to hear that PocketSphinxEngine is crashing.  The PocketSphinxEngine
> in the Olympus trunk was largely rewritten to support PocketSphinx 0.5.
>   In light of the PocketSphinxEngine and Kalliope issues, and your use of
> Windows Vista, I'd recommend that you try to use the Olympus trunk.  We
> are probably a couple of weeks away from an Olympus 2.5 release from the
> Olympus trunk.  As such the trunk is generally stable now.  You can
> download the Windows SDK for Windows Server 2008, which includes SAPI
> 5.3 from
>
http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-
> 9BE5-FA919850BDBF
> .  You will also need to install CMake via the Win32 Installer from
> http://cmake.org/cmake/resources/software.html
> .  The build scripts currently cause CMake to generate the Visual Studio
> solution files in the Build/cmake directory off of the Olympus Root and
off
> the
> root of the MeetingLine and soon to be added Madeline example system.
>    Let me know if KalliopeSAPI ends up working with SAPI 5.3
> SDK.  If it still doesn't work (but doesn't crash), then I recommend that
> you use the new KalliopeFlite support in the Olympus trunk instead, which
> you
> can use by running OlympusRebuildFlite.pl in your Olympus trunk root and
> then
> running SystemRunFlite.bat rather SystemRun.bat.  While I haven't recently
> encountered a crash while running one of our systems for a while with the
> trunk, if anything crashes for you or is not working, let me know so I can
> do
> my best to fix it before the release.
>    Thank you for sending in your changes to the grammar generation
> scripts in the Tutorials.  I committed your changes, and I am sorry for
> the trouble.
>
> Thanks,
> Ben Frisch
> CMU Speech Lab Undergraduate Research Assistant for Summer 2009
>
>
>
> On Thu, Jul 30, 2009 at 11:53 PM, Tran <tanhdung at i2r.a-star.edu.sg>
> wrote:
>
>
>
>
>
> Hi Benjamin,
>
>
>
> I managed to run the TTY
> version of MyBus successfully. It was very good. However, for the SAPI
> version,
> there was error. When I init_session, the console output "Welcome to
> MyBus", but there is no voice from the system. I guess it is because of
> the Kalliope has some problems with speech synthesis. After sometimes,
> PocketSphinx crashes. I don't know what is the cause. I ran an example of
> Microsoft Speech. It can talk with Anna voice, but Mary and Mike voice has
> error. Could that be a problem with the voice configuration in Kalliope?
> Please
> help me on this. Thanks
>
>
>
> I also found that, the source
> code on SVN cannot compile correctly if you don't make some changes in
> the perl script. I attach a change log file for your reference. It is nice
> if
> you make these changes on the source to minimize the effort of other
> developers.
>
>
>
>
>
> Regards,
>
> Tran Anh Dung
>
> Research Officer
>
> Human Language Technology Department
>
> A*, Singapore
>
>
>
>
>
>
>
>
>
> From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> Frisch
>
>
>
>
>
> Sent: Thursday, 30 July, 2009 9:44 AM
> To: Tran
> Cc: Alex Rudnicky
>
>
>
> Subject: Re: [Olympus developers 133]: Problem
> regarding Olympus
>
>
>
>
>
>
>
>
>
> Hi Tran,
>
>
>
>   At least from picture, it looks like you forgot to start the
> session first.  Just enter init_session and MyBus should start.
>  Let's us know if you have further questions.
>
>
>
>
>
>
>
>
>
>
>
> Thanks,
>
>
>
>
>
> Ben
>
>
>
> On Wed, Jul 29, 2009 at 9:40 PM, Tran <tanhdung at i2r.a-star.edu.sg>
> wrote:
>
>
>
>
>
> I forget to attached in previous email.
>
>
>
>
>
>
>
> From: Alex Rudnicky [mailto:Alex.Rudnicky at cs.cmu.edu]
>
> Sent: Thursday, 30 July, 2009 9:26 AM
> To: Tran; olympus-developers at cs.cmu.edu
> Cc: Benjamin Frisch
> Subject: RE: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
>
>
>
>
>
>
> These systems are pedagogical and
> follow the tutorial material.
>
> Have you tried to compile and use one
> of the example systems, such as MeetingLine?
>
>
>
>  - Alex Rudnicky
>
>
>
>
>
>
>
>
>
> From: olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu
> [mailto:olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu] On
> Behalf Of Tran
> Sent: Wednesday, July 29, 2009 9:18 PM
> To: olympus-developers at cs.cmu.edu
> Subject: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
>
>
> To whom it may concerns,
>
>
>
> We are doing research on Dialogue Management System. We found that Olympus
> is an interesting system. We downloaded and manage to compile the source
> code
> and tutorial 1/2 successfully. However, when we run it, there seems to be
> nothing happens (no interaction from system, no response while we
talking).
> We
> do not know how to operate it. Hence, could you be able to help us to
> instruct
> how to use the system? We look forward to hear from you
>
>
>
> Regards,
>
> Tran Anh Dung
>
> Research Officer
>
> Human Language Technology Department
>
> A*, Singapore
>
>
>
> PS: all the source code is downloaded as instructed on the Olympus wiki
> page. The downloaded version is 2.2 (not the development version)
>
>
>
> Institute for Infocomm Research disclaimer: "This email is confidential
> and may be privileged. If you are not the intended recipient, please
delete
> it
> and notify us immediately. Please do not copy or use it for any purpose,
or
> disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer: "This email is confidential
> and may be privileged. If you are not the intended recipient, please
delete
> it
> and notify us immediately. Please do not copy or use it for any purpose,
or
> disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer: "This email
> is confidential and may be privileged. If you are not the intended
> recipient,
> please delete it and notify us immediately. Please do not copy or use it
for
> any purpose, or disclose its contents to any other person. Thank you."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Institute for Infocomm Research disclaimer:  "This email is
> confidential and may be privileged. If you are not the intended
> recipient, please delete it and notify us immediately. Please do not
> copy or use it for any purpose, or disclose its contents to any other
> person. Thank you."
>
> Institute for Infocomm Research disclaimer:  "This email is confidential
and
> may be privileged. If you are not the intended recipient, please delete it
> and notify us immediately. Please do not copy or use it for any purpose,
or
> disclose its contents to any other person. Thank you."
>

Institute for Infocomm Research disclaimer:  "This email is confidential and
may be privileged. If you are not the intended recipient, please delete it
and notify us immediately. Please do not copy or use it for any purpose, or
disclose its contents to any other person. Thank you."

 

Institute for Infocomm Research disclaimer:  "This email is confidential and may be privileged. If you are not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any purpose, or disclose its contents to any other person. Thank you."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090817/4d152cb7/attachment-0001.html

From dhawaljshah at gmail.com  Mon Aug 17 04:31:37 2009
From: dhawaljshah at gmail.com (Dhawal Shah)
Date: Mon, 17 Aug 2009 16:31:37 +0800
Subject: [Olympus developers 145]:  Link does not work
Message-ID: <bdea07120908170131t6fdafdeav982a5e87da09d1c4@mail.gmail.com>

I was attempting to download the Roomline system found at this link:
http://www.cs.cmu.edu/~dbohus/ravenclaw-olympus/download.html

However, the zip file link provided doesn't seem to work. Can someone look
into this and get the link up and working?
http://fife.speech.cs.cmu.edu/RavenClaw/RoomLine%20-%20Release%201.00%20(2006-07-07).zip

Thanks a lot!

Dhawal Shah
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090817/9dc2c4e1/attachment.html

From bfrisch at cs.cmu.edu  Mon Aug 17 19:35:35 2009
From: bfrisch at cs.cmu.edu (Benjamin Frisch)
Date: Mon, 17 Aug 2009 19:35:35 -0400
Subject: [Olympus developers 146]: Re: Link does not work
In-Reply-To: <bdea07120908170131t6fdafdeav982a5e87da09d1c4@mail.gmail.com>
References: <bdea07120908170131t6fdafdeav982a5e87da09d1c4@mail.gmail.com>
Message-ID: <bd80926e0908171635m19d604ddn72d2ac7101808412@mail.gmail.com>

Hi Dhawal,
  The reason the link doesn't work is because fife.speech.cs.cmu.edu doesn't
exist anymore.  If you want to take a look at RoomLine it is in the RoomLine
directory inside of the Olympus example systems directory in the repository
as described at the bottom of
http://wiki.speech.cs.cmu.edu/olympus/index.php/Download .  It is currently
updated to work with the Olympus trunk from which Olympus 2.5 will be
released in a week or two.  Let us know if you have any problems with the
multimodal RoomLine example system or the now stable Olympus trunk.

Thanks,
Ben Frisch

On Mon, Aug 17, 2009 at 4:31 AM, Dhawal Shah <dhawaljshah at gmail.com> wrote:

> I was attempting to download the Roomline system found at this link:
> http://www.cs.cmu.edu/~dbohus/ravenclaw-olympus/download.html<http://www.cs.cmu.edu/%7Edbohus/ravenclaw-olympus/download.html>
>
> However, the zip file link provided doesn't seem to work. Can someone look
> into this and get the link up and working?
>
> http://fife.speech.cs.cmu.edu/RavenClaw/RoomLine%20-%20Release%201.00%20(2006-07-07).zip<http://fife.speech.cs.cmu.edu/RavenClaw/RoomLine%20-%20Release%201.00%20%282006-07-07%29.zip>
>
> Thanks a lot!
>
> Dhawal Shah
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090817/fd4cd3e6/attachment.html

From dhawaljshah at gmail.com  Wed Aug 19 05:24:31 2009
From: dhawaljshah at gmail.com (Dhawal Shah)
Date: Wed, 19 Aug 2009 17:24:31 +0800
Subject: [Olympus developers 147]:  Error building Olympus from trunk
In-Reply-To: <bdea07120908180644n28a52bb5pe569edf0570bc516@mail.gmail.com>
References: <bdea07120908180644n28a52bb5pe569edf0570bc516@mail.gmail.com>
Message-ID: <bdea07120908190224t775e9f1cqedee7e841066afa1@mail.gmail.com>

Hi,
I downloaded the latest Olympus from trunk, installed CMake and then ran
OlympusBuild.pl, which resulted in this error straight up: Writing the
current checked out SVN branch and revision to Build\SVN_Data.h failed.

The build continued thereafter but there were errors all the way. Could
someone explain how to get around this?
I attached the build.log file in a separate email which is awaiting
moderator approval.

Thanks in advance!

Dhawal Shah


-----------------------------------------------------------------------------------------------
I have never let my schooling interfere with my education. - Mark Twain
======================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090819/12dbb615/attachment.html

From bfrisch at cs.cmu.edu  Wed Aug 19 13:05:17 2009
From: bfrisch at cs.cmu.edu (Benjamin Frisch)
Date: Wed, 19 Aug 2009 13:05:17 -0400
Subject: [Olympus developers 148]: Re: Error building Olympus from trunk
In-Reply-To: <bdea07120908190926k75ae821r81c22227bcbe5746@mail.gmail.com>
References: <bdea07120908180644n28a52bb5pe569edf0570bc516@mail.gmail.com> 
	<bdea07120908190926k75ae821r81c22227bcbe5746@mail.gmail.com>
Message-ID: <bd80926e0908191005l7fed2441qa2d5643ec8954486@mail.gmail.com>

Hi Dhawal,  Can you replace your OlympusBuild.pm in C:\olympus\Build on your
computer with the attached OlympusBuild.pm, run OlympusBuild.pl again, and
let me know if the solution build is successful (you'll still get the
warning, but the solution build won't fail).  If it is, I'll commit the fix.
 If not, send me your new build.log.  I then recommend that you do an SVN
checkout rather than an SVN export of the Olympus trunk and RoomLine, and
there will likely be some changes to the trunk and there will definitely be
changes to RoomLine before the official release.  (An single SVN update of
both every day until release should be sufficient to keep up with changes.)

Thanks,
Ben

On Wed, Aug 19, 2009 at 12:26 PM, Dhawal Shah <dhawaljshah at gmail.com> wrote:

> Hey Benjamin,
>
> Here is my build log. Thanks for taking a look! Appreciate it.
>
> Regards,
> Dhawal Shah
>
>
>
> -----------------------------------------------------------------------------------------------
> I have never let my schooling interfere with my education. - Mark Twain
> ======================================================
>
> I enjoy the massacre of ads. This sentence will slaughter ads without a
> messy bloodbath.
>
>
> ---------- Forwarded message ----------
> From: Dhawal Shah <dhawaljshah at gmail.com>
> Date: Tue, Aug 18, 2009 at 9:44 PM
> Subject: Error building Olympus from trunk
> To: olympus-developers at cs.cmu.edu
>
>
> Hi,
> I downloaded the latest Olympus from trunk, got CMake and then ran the
> OlympusBuild, which resulted in this error straight up: Writing the current
> checked out SVN branch and revision to Build\SVN_Data.h failed.
>
> The build continued thereafter but there were errors all the way. I am
> attaching the build.log file. Could someone explain how to get around this?
>
> Thanks in advance!
>
>
> Dhawal Shah
>
>
>
> -----------------------------------------------------------------------------------------------
> I have never let my schooling interfere with my education. - Mark Twain
> ======================================================
>
> I enjoy the massacre of ads. This sentence will slaughter ads without a
> messy bloodbath.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090819/31333611/attachment.html

From subi.gupta at gmail.com  Thu Aug 27 00:16:10 2009
From: subi.gupta at gmail.com (subi gupta)
Date: Thu, 27 Aug 2009 09:46:10 +0530
Subject: [Olympus developers 149]:  Be a part of Anuja's network..
Message-ID: <45a18c9b0908262116o745f7de8n931925a4b102362e@mail.gmail.com>

           SiliconIndia <http://siliconindia.com/>- Empowering Professionals
               <http://www.siliconindia.com/register.php?id=6V8n0F96>  Anuja
Mishra
Fashion Designer
  Hi ,

I would like to invite you to my professional network on SiliconIndia. It
allows us to invite trusted contacts and stay connected with ease.

Thanks,
Anuja

Let us connect and stay in touch.* Click here to
join<http://www.siliconindia.com/register.php?id=6V8n0F96>
*
 <http://siliconindia.com/profiles/var+yahoocoin-b3NfTgY9>
 Kick Start Your CAT '09 Preparation - *Take a Free Mock
Test*<http://www.siliconindia.com/education/mbaindia.html>

If you do not wish to receive future mailings from SiliconIndia, please opt
out. <http://www.siliconindia.com/network/optoutemails.php>
Info Connect WTI Pvt. Ltd. 124, Surya Chambers, Airport Main Road, Bangalore
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090827/28c560b5/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 2474 bytes
Desc: not available
Url : http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090827/28c560b5/attachment-0001.jpe

From anuja.mishra46 at gmail.com  Thu Aug 27 00:20:14 2009
From: anuja.mishra46 at gmail.com (Anuja Mishra)
Date: Thu, 27 Aug 2009 09:50:14 +0530
Subject: [Olympus developers 150]:  Anuja has added you to stay connected
Message-ID: <cb11e020908262120w257beb6amd20351b80f405890@mail.gmail.com>

       SiliconIndia <http://siliconindia.com/>- Empowering Professionals
         <http://www.siliconindia.com/register.php?id=6V8n0F96>   Anuja
Mishra
Fashion Designer
  Hi ,

I would like to invite you to my professional network on SiliconIndia. It
allows us to invite trusted contacts and stay connected with ease.

Thanks,
Anuja

Let us connect and stay in touch.* Click here to
join<http://www.siliconindia.com/register.php?id=6V8n0F96>
*
  <http://siliconindia.com/profiles/var+yahoocoin-b3NfTgY9>
 Kick Start Your CAT '09 Preparation - *Take a Free Mock
Test*<http://siliconindia.com/education/cat_test/index.php>

If you do not wish to receive future mailings from SiliconIndia, please opt
out. <http://www.siliconindia.com/network/optoutemails.php>
Info Connect WTI Pvt. Ltd. 124, Surya Chambers, Airport Main Road, Bangalore
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090827/42cc4020/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 2474 bytes
Desc: not available
Url : http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090827/42cc4020/attachment.jpe

From marziehrazavi at gmail.com  Mon Aug 31 04:12:44 2009
From: marziehrazavi at gmail.com (marzieh razavi)
Date: Mon, 31 Aug 2009 12:42:44 +0430
Subject: [Olympus developers 151]:  Agents in RavenClaw
Message-ID: <15cfc7ea0908310112j5781be42te34edf8fe2ee14f3@mail.gmail.com>

Hello,
I am using the Olympus architecture  and I was wondering if you could give
some information about the agents in RavenClaw.
Best Regards,
Marzieh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090831/d79fcfc7/attachment.html

From Alex.Rudnicky at cs.cmu.edu  Mon Aug 31 08:16:08 2009
From: Alex.Rudnicky at cs.cmu.edu (Alex Rudnicky)
Date: Mon, 31 Aug 2009 08:16:08 -0400
Subject: [Olympus developers 152]: Re: Agents in RavenClaw
In-Reply-To: <15cfc7ea0908310112j5781be42te34edf8fe2ee14f3@mail.gmail.com>
References: <15cfc7ea0908310112j5781be42te34edf8fe2ee14f3@mail.gmail.com>
Message-ID: <9C0D1A9F38D23E4290347EE31C22B0AF0354A3AE@e2k3.srv.cs.cmu.edu>

The best way to see how they are used is to look at the examples from
the distribution. Look in the trunk.

This paper provides a high-level overview:

Bohus, D., & Rudnicky, A. I. (2009). The RavenClaw dialog management
framework: Architecture and systems. Computer Speech and Language , 23
(3), 332-361.

 

 

From: olympus-developers-bounces at mailman.srv.cs.cmu.edu
[mailto:olympus-developers-bounces at mailman.srv.cs.cmu.edu] On Behalf Of
marzieh razavi
Sent: Monday, August 31, 2009 4:13 AM
To: olympus-developers at cs.cmu.edu
Subject: [Olympus developers 151]: Agents in RavenClaw

 

Hello,
I am using the Olympus architecture  and I was wondering if you could
give some information about the agents in RavenClaw.
Best Regards,
Marzieh

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090831/4e52418b/attachment.html

From aasishp at gmail.com  Mon Aug 31 08:25:41 2009
From: aasishp at gmail.com (Aasish Pappu)
Date: Mon, 31 Aug 2009 08:25:41 -0400
Subject: [Olympus developers 153]: Re: Agents in RavenClaw
In-Reply-To: <9C0D1A9F38D23E4290347EE31C22B0AF0354A3AE@e2k3.srv.cs.cmu.edu>
References: <15cfc7ea0908310112j5781be42te34edf8fe2ee14f3@mail.gmail.com> 
	<9C0D1A9F38D23E4290347EE31C22B0AF0354A3AE@e2k3.srv.cs.cmu.edu>
Message-ID: <2c769a360908310525g6b45034fk2ffdbfbb7b25fa1a@mail.gmail.com>

A detailed documentation is available under the RavenClaw library with
Olympus..

http://trac.speech.cs.cmu.edu/olympus/browser/trunk/Libraries/RavenClaw/Documentation

-Aasish
2009/8/31 Alex Rudnicky <Alex.Rudnicky at cs.cmu.edu>

>  The best way to see how they are used is to look at the examples from the
> distribution. Look in the trunk.
>
> This paper provides a high-level overview:
>
> Bohus, D., & Rudnicky, A. I. (2009). The RavenClaw dialog management
> framework: Architecture and systems. Computer Speech and Language , 23 (3),
> 332-361.
>
>
>
>
>
> *From:* olympus-developers-bounces at mailman.srv.cs.cmu.edu [mailto:
> olympus-developers-bounces at mailman.srv.cs.cmu.edu] *On Behalf Of *marzieh
> razavi
> *Sent:* Monday, August 31, 2009 4:13 AM
> *To:* olympus-developers at cs.cmu.edu
> *Subject:* [Olympus developers 151]: Agents in RavenClaw
>
>
>
> Hello,
> I am using the Olympus architecture  and I was wondering if you could give
> some information about the agents in RavenClaw.
> Best Regards,
> Marzieh
>



-- 
Aasish Kumar Pappu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090831/93f4f4b3/attachment-0001.html

From dhawaljshah at gmail.com  Tue Aug 18 09:44:52 2009
From: dhawaljshah at gmail.com (Dhawal Shah)
Date: Tue, 18 Aug 2009 13:44:52 -0000
Subject: [Olympus developers 298]:  Error building Olympus from trunk
Message-ID: <bdea07120908180644n28a52bb5pe569edf0570bc516@mail.gmail.com>

Hi,
I downloaded the latest Olympus from trunk, got CMake and then ran the
OlympusBuild, which resulted in this error straight up: Writing the current
checked out SVN branch and revision to Build\SVN_Data.h failed.

The build continued thereafter but there were errors all the way. I am
attaching the build.log file. Could someone explain how to get around this?

Thanks in advance!


Dhawal Shah


-----------------------------------------------------------------------------------------------
I have never let my schooling interfere with my education. - Mark Twain
======================================================

I enjoy the massacre of ads. This sentence will slaughter ads without a
messy bloodbath.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090818/98105aec/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: build.log
Type: application/octet-stream
Size: 42430 bytes
Desc: not available
Url : http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090818/98105aec/build-0001.obj

From bfrisch at cs.cmu.edu  Wed Aug 19 13:06:20 2009
From: bfrisch at cs.cmu.edu (Benjamin Frisch)
Date: Wed, 19 Aug 2009 17:06:20 -0000
Subject: [Olympus developers 299]: Re: Error building Olympus from trunk
In-Reply-To: <bd80926e0908191005l7fed2441qa2d5643ec8954486@mail.gmail.com>
References: <bdea07120908180644n28a52bb5pe569edf0570bc516@mail.gmail.com> 
	<bdea07120908190926k75ae821r81c22227bcbe5746@mail.gmail.com> 
	<bd80926e0908191005l7fed2441qa2d5643ec8954486@mail.gmail.com>
Message-ID: <bd80926e0908191005p3f9aa2beqbb53bcc9e028466a@mail.gmail.com>

Hi Dhawal,  Here's the OlympusBuild.pm.

Thanks,
Ben

On Wed, Aug 19, 2009 at 1:05 PM, Benjamin Frisch <bfrisch at cs.cmu.edu> wrote:

> Hi Dhawal,  Can you replace your OlympusBuild.pm in C:\olympus\Build on
> your computer with the attached OlympusBuild.pm, run OlympusBuild.pl again,
> and let me know if the solution build is successful (you'll still get the
> warning, but the solution build won't fail).  If it is, I'll commit the fix.
>  If not, send me your new build.log.  I then recommend that you do an SVN
> checkout rather than an SVN export of the Olympus trunk and RoomLine, and
> there will likely be some changes to the trunk and there will definitely be
> changes to RoomLine before the official release.  (An single SVN update of
> both every day until release should be sufficient to keep up with changes.)
>
> Thanks,
> Ben
>
>
> On Wed, Aug 19, 2009 at 12:26 PM, Dhawal Shah <dhawaljshah at gmail.com>wrote:
>
>> Hey Benjamin,
>>
>> Here is my build log. Thanks for taking a look! Appreciate it.
>>
>> Regards,
>> Dhawal Shah
>>
>>
>>
>> -----------------------------------------------------------------------------------------------
>> I have never let my schooling interfere with my education. - Mark Twain
>> ======================================================
>>
>> I enjoy the massacre of ads. This sentence will slaughter ads without a
>> messy bloodbath.
>>
>>
>> ---------- Forwarded message ----------
>> From: Dhawal Shah <dhawaljshah at gmail.com>
>> Date: Tue, Aug 18, 2009 at 9:44 PM
>> Subject: Error building Olympus from trunk
>> To: olympus-developers at cs.cmu.edu
>>
>>
>> Hi,
>> I downloaded the latest Olympus from trunk, got CMake and then ran the
>> OlympusBuild, which resulted in this error straight up: Writing the current
>> checked out SVN branch and revision to Build\SVN_Data.h failed.
>>
>> The build continued thereafter but there were errors all the way. I am
>> attaching the build.log file. Could someone explain how to get around this?
>>
>> Thanks in advance!
>>
>>
>> Dhawal Shah
>>
>>
>>
>> -----------------------------------------------------------------------------------------------
>> I have never let my schooling interfere with my education. - Mark Twain
>> ======================================================
>>
>> I enjoy the massacre of ads. This sentence will slaughter ads without a
>> messy bloodbath.
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090819/a3f51a05/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OlympusBuild.pm
Type: application/octet-stream
Size: 45673 bytes
Desc: not available
Url : http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090819/a3f51a05/OlympusBuild-0001.obj