[Olympus developers 83]: Re: memory footprint of ravenclaw framework

[Antoine Raux]

Yes, PocketSphinx and Flite are both designed to work on handheld
devices (hence the "Pocket" in PocketSphinx and the "lite" in Flite). 

Now this is not the case for the rest of Olympus (parser, dialog
manager, natural language generation, and last but not least, Galaxy
Hub). 

My guess is that you'd have to find (or create) a lightweight
alternative to Galaxy (to let your modules talk to each other), and at
least a new version of RavenClaw, which is really not optimized for
performance (or memory usage). Now depending on your application, you
might not need all the bells and whistles of RavenClaw (and god knows
there are quite a few), so if you can get away with a much simpler
dialog manager (in which case, NLU and NLG should not be a problem
either), I assume you'd be able to fit a whole system on a (reasonably
powerful) handheld device.

antoine


On Mon, 2009-01-12 at 09:08 -0500, Thomas Harris wrote:
> Fortunately, PocketSphinx and Flight both have integer-only modes, so
> you can manage without a floating-point unit if you need to.
> 
> -Thomas
> 
> On Mon, Jan 12, 2009 at 1:57 AM, Chandrakanth Reddy Dargula
> <Chandrakanth.Dargula at infotech-enterprises.com> wrote:
>         Antoine,
>         
>         Thanks for your inputs. Could any one let me know what are key
>         challenges that will come across to develop similar kind of
>         system in handheld devices.
>         
>         Regards,
>         Chandrakanth.
>         ________________________________________
>         
>         From: Antoine Raux [antoine.raux at polytechnique.org]
>         Sent: Saturday, January 10, 2009 6:25 AM
>         To: Chandrakanth Reddy Dargula
>         Cc: olympus-developers at cs.cmu.edu
>         Subject: Re: [Olympus developers 76]:  memory footprint of
>         ravenclaw    framework
>         
>         
>         Hi Chandrakanth,
>         
>         Thank you for your interest in Olympus. I'm not exactly sure
>         of the
>         memory footprint of Olympus applications (I'm no longer at CMU
>         and do
>         not have an Olympus set up at hand to check) but I know that
>         we are
>         running the full Let's Go system (including speech
>         recognition,
>         synthesis, interaction and dialog management, etc) on a single
>         PC (3GHz
>         dual-core with 4GB of memory, although slightly less powerful
>         configurations would probably work too).
>         
>         Hope this helps a bit... If anyone else cares to share their
>         own
>         experience...
>         
>         antoine
>         
>         
>         On Fri, 2009-01-09 at 18:08 +0530, Chandrakanth Reddy Dargula
>         wrote:
>         > Hi,
>         > Could you please let me know approximate memory foot print
>         of any
>         > application developed using this olympus/ravenclaw dialog
>         framework.
>         > Speed requirement of any processor required to run
>         application built
>         > based on this framework.
>         >
>         > Thanking you.
>         >
>         > Regards,
>         > Chandrakanth.
>         >
>         >
>         >
>         >
>         ______________________________________________________________________
>         > DISCLAIMER:
>         >
>         > This email may contain confidential information and is
>         intended only
>         > for the use of the specific individual(s) to which it is
>         addressed. If
>         > you are not the intended recipient of this email, you are
>         hereby
>         > notified that any unauthorized use, dissemination or copying
>         of this
>         > email or the information contained in it or attached to it
>         is strictly
>         > prohibited. If you received this message in error, please
>         immediately
>         > notify the sender at Infotech or
>         Mail.Admin at infotech-enterprises.com
>         > and delete the original message.
>         
>         
>