User Interface Service Software Developerís Guide - Hitech Projects

More documents

Recommendations

Info

January 2008 Public 3.2 Deployment 3.2.1 Implicit Speech Input 3.2.1.1 System requirements Amigo OSGI framework (amigo_core, amigo_ksoap, amigo_wsdiscovery) OSGI framework OSCAR platform (can be on either linux or windows) Refer to [OSCAR req] 3.2.1.2 Download Source code available for download at [amigo_gforge]/ius/user_interface/voice_service/implicit_speech_input/ 3.2.1.3 Install The keyword spotting module is integrated into the topic recognition bundle: you need to download this bundle and install it as any other bundle into OSCAR. Then, you need to extract and uncompress a zipfile that is stored in this bundle, and run a cygwin script file, which will launch the keyword spotting software. The precise procedure is described in the user and developer guide of the topic recognition module. 3.2.1.4 Configure The keywords spotting module reads in a configuration file that defines the list of supported keywords. The keyword spotting module further needs a pronunciation lexicon for these keywords, as well as a set of speaker-dependent acoustic models. This procedure is described in details in the user and developer guide of the topic recognition module. 3.2.1.5 Compile Two different source file packages are used for implicit speech: a “light” package, that only contains the JAVA sources and that is included into the topic recognition module. This light version handles basic keyword spotting and is fully integrated within the topic recognizer. You should compile it using the ant build script of the topic recognition module. The second package contains the full set of source codes, including the Julius C speech decoder, along with several toolkits to train adapted acoustic models: this set is stored in the implicit speech repository, and is independent from the topic recognizer. To compile it, you must first compile the Julius decoder (in cygwin) using the ./configure and./make procedure. Note that this version of the decoder has been modified for the need of the project: a blank/original Julius package will not work. Then, you can use the ant build script to compile the JAVA part. 3.2.2 2D Gesture Service 3.2.2.1 System requirements OSCAR platform (can be on either linux or windows) Amigo IST-2004-004182 75/114
January 2008 Public OSGI framework The following AMIGO OSGI services should be running from the OBR before starting 2D services : • amigo_core • amigo_ksoap_binding • amigo_ksoap_export • amigo_wsdiscovery • HTTP Service (+ Amigo mods) • Servlet • Service binder • log4 3.2.2.2 Download Source code available for download. 3.2.2.3 Install The gesture capture and interpreter services are located in /amigo/ius/user_interface/gesture_service/2D_gesture_service/. Compile the two services, and copy the bundles located in dist directory to $OSCAR_HOME/bundle. The services should be started in the following order : GestureCapture then GestureInterpreter. That is because the GestureInterpreter subscribes to the gesture events sent by the first GestureCapture it finds with the lookup. In Oscar : start file:bundle/gesture-capture.jar start file:bundle/gesture-interpreter.jar 3.2.2.4 Configure Configuring the services Once the services are running, the scene should be configured by calling the setScene method of both services using a stub. Warning : don't be confused, if a scene is displayed on GestureCapture frame, it does not imply that the GestureInterpreter is configured also. One should configure it by calling the setScene method in order to interpret the gesture. The scene could be retrieved from a file or directly from a MMILEntity. An additional service called SceneConfigurator has been provided in order to show how the scene could be configured on both services. It is located in the same directory than the interpreter and capture services. The service is an OSGI service, and is launched with (in Oscar) : start file:bundle/scene-configurator.jar Once it is started, you just have to push the configure button and choose a valid scene file. The configurator will call the setScene method of interpreter and capture services. Amigo IST-2004-004182 76/114
Page 1 and 2:
IST Amigo Project Deliverable D4.7
Page 3 and 4:
January 2008 Public Table of Conten
Page 5 and 6:
January 2008 Public 3.2.3.4 Configu
Page 7 and 8:
January 2008 Public 1 Speech based
Page 9 and 10:
January 2008 Public Bugs - Patches
Page 11 and 12:
January 2008 Public 1.2 Deployment
Page 13 and 14:
January 2008 Public SWIsvcMonPort=
Page 15 and 16:
January 2008 Public # RealSpeak por
Page 17 and 18:
January 2008 Public 6666 20 10
Page 19 and 20:
January 2008 Public true C:/Temp/
Page 21 and 22:
January 2008 Public [Recording_TCP]
Page 23 and 24:
January 2008 Public Example string
Page 25 and 26: January 2008 Public 1.3.2 Explicit
Page 27 and 28: January 2008 Public • the user sp
Page 29 and 30: January 2008 Public parameters. The
Page 31 and 32: January 2008 Public In this example
Page 33 and 34: January 2008 Public Assuming that y
Page 35 and 36: January 2008 Public Step 3 Rebuild
Page 37 and 38: January 2008 Public 1.4.1.3 Run Tra
Page 39 and 40: January 2008 Public On a successful
Page 41: January 2008 Public At the end the
Page 44 and 45: January 2008 Public At the end the
Page 46 and 47: January 2008 Public Step 5 In the S
Page 48 and 49: January 2008 Public Step 8 In Serve
Page 50 and 51: January 2008 Public 1.4.2.5 Run Voi
Page 52 and 53: January 2008 Public 1.4.2.6 Run Voi
Page 54 and 55: January 2008 Public As soon as the
Page 56 and 57: January 2008 Public • SoapBox bas
Page 58 and 59: January 2008 Public 2.2.1.1.4 Confi
Page 60 and 61: January 2008 Public The gesture ser
Page 62 and 63: January 2008 Public • Folder Volu
Page 64 and 65: January 2008 Public After installat
Page 66 and 67: January 2008 Public Up 65 In
Page 68 and 69: January 2008 Public Figure below pr
Page 70 and 71: January 2008 Public Development sta
Page 72 and 73: January 2008 Public Tools Oscar Fil
Page 74 and 75: January 2008 Public Bugs None Patch
Page 78 and 79: January 2008 Public Scene descripti
Page 80 and 81: January 2008 Public 3.2.2.5 Comp
Page 82 and 83: January 2008 Public 3.3 Component A
Page 84 and 85: January 2008 Public 3.3.3 Multimoda
Page 86 and 87: January 2008 Public Fallback soluti
Page 88 and 89: January 2008 Public 3.3.3.4 Compone
Page 90 and 91: January 2008 Public 3.4 Tutorial 3.
Page 92 and 93: January 2008 Public scene, the imag
Page 94 and 95: January 2008 Public objectDesc VCR
Page 96 and 97: January 2008 Public 3.5 Assessment
Page 98 and 99: January 2008 Public 3.6 Appendix 3.
Page 100 and 101: January 2008 Public Intended audien
Page 102 and 103: January 2008 Public 3.9 Component A
Page 104 and 105: January 2008 Public interface input
Page 106 and 107: January 2008 Public Figure 7 Classe
Page 108 and 109: January 2008 Public different sub-m
Page 110 and 111: January 2008 Public Figure 3: Menu
Page 112 and 113: January 2008 Public 30% 10% 7% 0% 5
Page 114 and 115: January 2008 Public Figure 10: Conc
show all

User Interface Service Software Developerís Guide - Hitech Projects

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?