From HemeraBook
Revision as of 18:59, 16 May 2011 by Projettwk (Talk | contribs) (Introduction)

Jump to: navigation, search


You must have installed Hemera, and third-party tools.
All command lines are given assuming Hemera scripts directories are in PATH, which is the case if you have setup Hemera.
If it is not the case, you can follow this instruction:

source HEMERA_ROOT_PATH/scripts/updatePath.sh


Environment and third-party tools

Ensure you have well updated your configuration file.
You can launch the following script to help you:


Core module

To quickly test some core module, you may consider following the Hemera Quick Start.


Before using Hemera, you must ensure hardware is well configured.


You must ensure you can record with your microphone.

If you are using directly ALSA project, you may find interesting information:

If you are using Pulse Audio, you may find interesting information:

You may need to use pavucontrol to ensure:

  • output AND input are defined
  • the good input is the default one (in case you have several)
  • the good input is NOT in 'mute'
  • sox/rec (which is used by Hemera) uses the good input (it must NOT use "monitor")

In any case, you may test your microphone with a recording tool like Audacity.


(will come later)

Use Hemera

Hemera accessibility


To start Hemera:

hemera.sh -S

Output sample:

14/05/11 16:51.26  [hemera]  LogFile: /home/projettwk/programmation/projects/hemera/Hemera/run/log/2011-05-14-16-51-26-hemera.log
14/05/11 16:51.26  [inputMonitor]  Launched input monitor.
14/05/11 16:51.26  [IOProcessor]  Launched input/output processor.
14/05/11 16:51.26  [soundRecorder]  Launched sound recorder.
14/05/11 16:51.26  [hemera]  Found: Apache Tomcat Version 7.0.12
14/05/11 16:51.26  [hemera]  Apache Tomcat start ... ok


At any time, you can get Hemera status:

hemera.sh -T

Output sample:

14/05/11 16:55.48  [hemera]  LogFile: /home/projettwk/programmation/projects/hemera/Hemera/run/log/2011-05-14-16-55-48-hemera.log
14/05/11 16:55.48  [hemera]  Hemera uptime: 00d 00h:04m.22s
14/05/11 16:55.48  [hemera]  Hemera mode: local
14/05/11 16:55.48  [hemera]  Recognized commands mode: normal
14/05/11 16:55.48  [inputMonitor]  input monitor is running.
14/05/11 16:55.48  [IOProcessor]  input/output processor is running.
14/05/11 16:55.48  [soundRecorder]  sound recorder is running.

Obviously, Hemera status can be requested even if it is not started, output sample:

14/05/11 16:57.05  [hemera]  LogFile: /home/projettwk/programmation/projects/hemera/Hemera/run/log/2011-05-14-16-57-05-hemera.log
14/05/11 16:57.05  [hemera]  Hemera uptime: not started
14/05/11 16:57.05  [hemera]  Hemera mode: local
14/05/11 16:57.05  [inputMonitor]  input monitor is stopped.
14/05/11 16:57.05  [IOProcessor]  input/output processor is stopped.
14/05/11 16:57.06  [soundRecorder]  sound recorder is stopped.


At any time, you can stop all Hemera activities:

hemera.sh -K

Output sample:

14/05/11 16:56.56  [hemera]  LogFile: /home/projettwk/programmation/projects/hemera/Hemera/run/log/2011-05-14-16-56-56-hemera.log
14/05/11 16:56.56  [inputMonitor]  Stopped input monitor.
14/05/11 16:56.57  [IOProcessor]  Stopped input/output processor.
14/05/11 16:56.58  [soundRecorder]  Stopped sound recorder.
14/05/11 16:56.58  [hemera]  Found: Apache Tomcat Version 7.0.12
14/05/11 16:56.58  [hemera]  Apache Tomcat stop ... ok

Hemera functionalities

Web module

If Hemera has been launched in "local" mode, you can use the Web module (address must be adapted to your configuration):


Speech synthesis & Speech recognition

You can use your microphone to give command to Hemera.
You can test/use any of the recognized commands.

For instance, you can request to search definition of Intelligence.
Another interesting test is to activate the parrot mode, and then to say what you want.

In any case, Hemera will give you an acknowledgment or an answer.
If a command is not understood, Hemera will say an error message.