|
emotion_analyzer package from jsk_3rdparty repovoicevox chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools respeaker_ros ros_speech_recognition rospatlite sesame_ros switchbot_ros |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-13 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kei Okada
- Yoshiki Obinata
Authors
- Ayaha Nagata
Emotion Analyzer Service using Hume API (ROS1)
This ROS1 package provides a service to analyze emotions from a given text using the Hume AI API.
Requirements
- ROS1 Noetic
- Python 3.8+
- An API key from Hume AI
Installation
Clone this repository and move to this directory
rosdep install -iry --from-paths .
catkin build --this
then source your workspace
Usage (Quick)
Using your microphone
roslaunch emotion_analyzer sample_emotion_analyzer.launch api_key:=<your_api_key>
Usage
1. Launch Emotion_Analyzer
roslaunch emotion_analyzer emotion_analyzer.launch api_key:=<your_api_key>
2. Call the service
For text,
rosservice call /analyze_text "text: '<text you want to analyze>'"
For prepared audio (up to 5 seconds),
rosservice call /analyze_audio "audio_file: <audio_file_path>"
As a sample, you can use '/home/leus/ros/catkin_ws/src/jsk_3rdparty/emotion_analyzer/data/purugacha_short.wav' as
For audio from microphone,
roslaunch audio_capture capture.launch format:=wave
rosservice call /analyze_audio "audio_file: ''"
You can check the device information by arecord -l.
Sometimes you need to replace “hw” with “plughw”:
for example, roslaunch audio_capture capture.launch format:=wave device:=plughw:1,0.
When the device is busy, you can try fuser -v /dev/snd/* to get PID and kill it by kill -9 <PID>.
ROS2
catkin_virtualenv is not available on ROS2, so the Hume SDK is installed into a venv (share/emotion_analyzer/venv) from pyproject.toml/uv.lock at build time instead (jsk_ros1_ros2_compat_generate_uv_venv()). Run uv lock after changing pyproject.toml. The scripts use the legacy streaming API (HumeStreamClient), which was removed in hume 0.7, so it is pinned below 0.7.
colcon build --packages-up-to emotion_analyzer
ros2 launch emotion_analyzer emotion_analyzer.launch.xml api_key:=<your_api_key>
# or, with audio_capture
ros2 launch emotion_analyzer sample_emotion_analyzer.launch.xml api_key:=<your_api_key>
ros2 service call /analyze_text emotion_analyzer/srv/AnalyzeText "{text: '<text you want to analyze>'}"
Changelog for package emotion_analyzer
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[emotion_analyzer] use python3-soundfile from apt instead of the uv venv The numpy wheel pulled by soundfile fails dh_strip of the buildfarm binary job (libscipy_openblas64_*.so). python3-soundfile is already an exec_depend and the venv sees the system site-packages. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[emotion_analyzer] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the emotion_analyzer python package, so src/emotion_analyzer/utils is installed into it instead of a second ament_python_install_package().
- package.xml: format 3 for conditions; audio_common_msgs (imported by the scripts but only pulled in by audio_capture before) is listed explicitly. hume has no rosdep key and catkin_virtualenv has no ROS2 port, so ROS2 users pip install it (README.md).
- analyze_{text,audio}_service.py, utils/audio_buffer.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only).
- launch/emotion_analyzer.launch.xml: ROS2 version of emotion_analyzer.launch.
- Catch exceptions from the Hume request and return {"error": ...} (same format as the existing no-audio case): rospy only returned a service error, but an exception in a service callback kills the rclpy node.
- hume (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), and both services are installed with jsk_ros1_ros2_compat_install_python(... USE_VENV) to run with it, instead of asking users to [pip install hume[stream]]{.title-ref}. hume is pinned below 0.7, since the scripts use the legacy HumeStreamClient that 0.7 removed (the latest hume, 0.14, can not
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/emotion_analyzer.launch
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch
-
- api_key [default: ]
- format [default: wave]
- launch/emotion_analyzer.launch.xml
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch.xml
-
- api_key [default: ]
- device [default: ]
Messages
Services
Plugins
Recent questions tagged emotion_analyzer at Robotics Stack Exchange
|
emotion_analyzer package from jsk_3rdparty repovoicevox chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools respeaker_ros ros_speech_recognition rospatlite sesame_ros switchbot_ros |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-13 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kei Okada
- Yoshiki Obinata
Authors
- Ayaha Nagata
Emotion Analyzer Service using Hume API (ROS1)
This ROS1 package provides a service to analyze emotions from a given text using the Hume AI API.
Requirements
- ROS1 Noetic
- Python 3.8+
- An API key from Hume AI
Installation
Clone this repository and move to this directory
rosdep install -iry --from-paths .
catkin build --this
then source your workspace
Usage (Quick)
Using your microphone
roslaunch emotion_analyzer sample_emotion_analyzer.launch api_key:=<your_api_key>
Usage
1. Launch Emotion_Analyzer
roslaunch emotion_analyzer emotion_analyzer.launch api_key:=<your_api_key>
2. Call the service
For text,
rosservice call /analyze_text "text: '<text you want to analyze>'"
For prepared audio (up to 5 seconds),
rosservice call /analyze_audio "audio_file: <audio_file_path>"
As a sample, you can use '/home/leus/ros/catkin_ws/src/jsk_3rdparty/emotion_analyzer/data/purugacha_short.wav' as
For audio from microphone,
roslaunch audio_capture capture.launch format:=wave
rosservice call /analyze_audio "audio_file: ''"
You can check the device information by arecord -l.
Sometimes you need to replace “hw” with “plughw”:
for example, roslaunch audio_capture capture.launch format:=wave device:=plughw:1,0.
When the device is busy, you can try fuser -v /dev/snd/* to get PID and kill it by kill -9 <PID>.
ROS2
catkin_virtualenv is not available on ROS2, so the Hume SDK is installed into a venv (share/emotion_analyzer/venv) from pyproject.toml/uv.lock at build time instead (jsk_ros1_ros2_compat_generate_uv_venv()). Run uv lock after changing pyproject.toml. The scripts use the legacy streaming API (HumeStreamClient), which was removed in hume 0.7, so it is pinned below 0.7.
colcon build --packages-up-to emotion_analyzer
ros2 launch emotion_analyzer emotion_analyzer.launch.xml api_key:=<your_api_key>
# or, with audio_capture
ros2 launch emotion_analyzer sample_emotion_analyzer.launch.xml api_key:=<your_api_key>
ros2 service call /analyze_text emotion_analyzer/srv/AnalyzeText "{text: '<text you want to analyze>'}"
Changelog for package emotion_analyzer
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[emotion_analyzer] use python3-soundfile from apt instead of the uv venv The numpy wheel pulled by soundfile fails dh_strip of the buildfarm binary job (libscipy_openblas64_*.so). python3-soundfile is already an exec_depend and the venv sees the system site-packages. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[emotion_analyzer] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the emotion_analyzer python package, so src/emotion_analyzer/utils is installed into it instead of a second ament_python_install_package().
- package.xml: format 3 for conditions; audio_common_msgs (imported by the scripts but only pulled in by audio_capture before) is listed explicitly. hume has no rosdep key and catkin_virtualenv has no ROS2 port, so ROS2 users pip install it (README.md).
- analyze_{text,audio}_service.py, utils/audio_buffer.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only).
- launch/emotion_analyzer.launch.xml: ROS2 version of emotion_analyzer.launch.
- Catch exceptions from the Hume request and return {"error": ...} (same format as the existing no-audio case): rospy only returned a service error, but an exception in a service callback kills the rclpy node.
- hume (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), and both services are installed with jsk_ros1_ros2_compat_install_python(... USE_VENV) to run with it, instead of asking users to [pip install hume[stream]]{.title-ref}. hume is pinned below 0.7, since the scripts use the legacy HumeStreamClient that 0.7 removed (the latest hume, 0.14, can not
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/emotion_analyzer.launch
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch
-
- api_key [default: ]
- format [default: wave]
- launch/emotion_analyzer.launch.xml
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch.xml
-
- api_key [default: ]
- device [default: ]
Messages
Services
Plugins
Recent questions tagged emotion_analyzer at Robotics Stack Exchange
|
emotion_analyzer package from jsk_3rdparty repovoicevox chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools respeaker_ros ros_speech_recognition rospatlite sesame_ros switchbot_ros |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-13 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kei Okada
- Yoshiki Obinata
Authors
- Ayaha Nagata
Emotion Analyzer Service using Hume API (ROS1)
This ROS1 package provides a service to analyze emotions from a given text using the Hume AI API.
Requirements
- ROS1 Noetic
- Python 3.8+
- An API key from Hume AI
Installation
Clone this repository and move to this directory
rosdep install -iry --from-paths .
catkin build --this
then source your workspace
Usage (Quick)
Using your microphone
roslaunch emotion_analyzer sample_emotion_analyzer.launch api_key:=<your_api_key>
Usage
1. Launch Emotion_Analyzer
roslaunch emotion_analyzer emotion_analyzer.launch api_key:=<your_api_key>
2. Call the service
For text,
rosservice call /analyze_text "text: '<text you want to analyze>'"
For prepared audio (up to 5 seconds),
rosservice call /analyze_audio "audio_file: <audio_file_path>"
As a sample, you can use '/home/leus/ros/catkin_ws/src/jsk_3rdparty/emotion_analyzer/data/purugacha_short.wav' as
For audio from microphone,
roslaunch audio_capture capture.launch format:=wave
rosservice call /analyze_audio "audio_file: ''"
You can check the device information by arecord -l.
Sometimes you need to replace “hw” with “plughw”:
for example, roslaunch audio_capture capture.launch format:=wave device:=plughw:1,0.
When the device is busy, you can try fuser -v /dev/snd/* to get PID and kill it by kill -9 <PID>.
ROS2
catkin_virtualenv is not available on ROS2, so the Hume SDK is installed into a venv (share/emotion_analyzer/venv) from pyproject.toml/uv.lock at build time instead (jsk_ros1_ros2_compat_generate_uv_venv()). Run uv lock after changing pyproject.toml. The scripts use the legacy streaming API (HumeStreamClient), which was removed in hume 0.7, so it is pinned below 0.7.
colcon build --packages-up-to emotion_analyzer
ros2 launch emotion_analyzer emotion_analyzer.launch.xml api_key:=<your_api_key>
# or, with audio_capture
ros2 launch emotion_analyzer sample_emotion_analyzer.launch.xml api_key:=<your_api_key>
ros2 service call /analyze_text emotion_analyzer/srv/AnalyzeText "{text: '<text you want to analyze>'}"
Changelog for package emotion_analyzer
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[emotion_analyzer] use python3-soundfile from apt instead of the uv venv The numpy wheel pulled by soundfile fails dh_strip of the buildfarm binary job (libscipy_openblas64_*.so). python3-soundfile is already an exec_depend and the venv sees the system site-packages. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[emotion_analyzer] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the emotion_analyzer python package, so src/emotion_analyzer/utils is installed into it instead of a second ament_python_install_package().
- package.xml: format 3 for conditions; audio_common_msgs (imported by the scripts but only pulled in by audio_capture before) is listed explicitly. hume has no rosdep key and catkin_virtualenv has no ROS2 port, so ROS2 users pip install it (README.md).
- analyze_{text,audio}_service.py, utils/audio_buffer.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only).
- launch/emotion_analyzer.launch.xml: ROS2 version of emotion_analyzer.launch.
- Catch exceptions from the Hume request and return {"error": ...} (same format as the existing no-audio case): rospy only returned a service error, but an exception in a service callback kills the rclpy node.
- hume (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), and both services are installed with jsk_ros1_ros2_compat_install_python(... USE_VENV) to run with it, instead of asking users to [pip install hume[stream]]{.title-ref}. hume is pinned below 0.7, since the scripts use the legacy HumeStreamClient that 0.7 removed (the latest hume, 0.14, can not
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/emotion_analyzer.launch
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch
-
- api_key [default: ]
- format [default: wave]
- launch/emotion_analyzer.launch.xml
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch.xml
-
- api_key [default: ]
- device [default: ]
Messages
Services
Plugins
Recent questions tagged emotion_analyzer at Robotics Stack Exchange
|
emotion_analyzer package from jsk_3rdparty repovoicevox chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools respeaker_ros ros_speech_recognition rospatlite sesame_ros switchbot_ros |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-13 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kei Okada
- Yoshiki Obinata
Authors
- Ayaha Nagata
Emotion Analyzer Service using Hume API (ROS1)
This ROS1 package provides a service to analyze emotions from a given text using the Hume AI API.
Requirements
- ROS1 Noetic
- Python 3.8+
- An API key from Hume AI
Installation
Clone this repository and move to this directory
rosdep install -iry --from-paths .
catkin build --this
then source your workspace
Usage (Quick)
Using your microphone
roslaunch emotion_analyzer sample_emotion_analyzer.launch api_key:=<your_api_key>
Usage
1. Launch Emotion_Analyzer
roslaunch emotion_analyzer emotion_analyzer.launch api_key:=<your_api_key>
2. Call the service
For text,
rosservice call /analyze_text "text: '<text you want to analyze>'"
For prepared audio (up to 5 seconds),
rosservice call /analyze_audio "audio_file: <audio_file_path>"
As a sample, you can use '/home/leus/ros/catkin_ws/src/jsk_3rdparty/emotion_analyzer/data/purugacha_short.wav' as
For audio from microphone,
roslaunch audio_capture capture.launch format:=wave
rosservice call /analyze_audio "audio_file: ''"
You can check the device information by arecord -l.
Sometimes you need to replace “hw” with “plughw”:
for example, roslaunch audio_capture capture.launch format:=wave device:=plughw:1,0.
When the device is busy, you can try fuser -v /dev/snd/* to get PID and kill it by kill -9 <PID>.
ROS2
catkin_virtualenv is not available on ROS2, so the Hume SDK is installed into a venv (share/emotion_analyzer/venv) from pyproject.toml/uv.lock at build time instead (jsk_ros1_ros2_compat_generate_uv_venv()). Run uv lock after changing pyproject.toml. The scripts use the legacy streaming API (HumeStreamClient), which was removed in hume 0.7, so it is pinned below 0.7.
colcon build --packages-up-to emotion_analyzer
ros2 launch emotion_analyzer emotion_analyzer.launch.xml api_key:=<your_api_key>
# or, with audio_capture
ros2 launch emotion_analyzer sample_emotion_analyzer.launch.xml api_key:=<your_api_key>
ros2 service call /analyze_text emotion_analyzer/srv/AnalyzeText "{text: '<text you want to analyze>'}"
Changelog for package emotion_analyzer
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[emotion_analyzer] use python3-soundfile from apt instead of the uv venv The numpy wheel pulled by soundfile fails dh_strip of the buildfarm binary job (libscipy_openblas64_*.so). python3-soundfile is already an exec_depend and the venv sees the system site-packages. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[emotion_analyzer] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the emotion_analyzer python package, so src/emotion_analyzer/utils is installed into it instead of a second ament_python_install_package().
- package.xml: format 3 for conditions; audio_common_msgs (imported by the scripts but only pulled in by audio_capture before) is listed explicitly. hume has no rosdep key and catkin_virtualenv has no ROS2 port, so ROS2 users pip install it (README.md).
- analyze_{text,audio}_service.py, utils/audio_buffer.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only).
- launch/emotion_analyzer.launch.xml: ROS2 version of emotion_analyzer.launch.
- Catch exceptions from the Hume request and return {"error": ...} (same format as the existing no-audio case): rospy only returned a service error, but an exception in a service callback kills the rclpy node.
- hume (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), and both services are installed with jsk_ros1_ros2_compat_install_python(... USE_VENV) to run with it, instead of asking users to [pip install hume[stream]]{.title-ref}. hume is pinned below 0.7, since the scripts use the legacy HumeStreamClient that 0.7 removed (the latest hume, 0.14, can not
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/emotion_analyzer.launch
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch
-
- api_key [default: ]
- format [default: wave]
- launch/emotion_analyzer.launch.xml
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch.xml
-
- api_key [default: ]
- device [default: ]
Messages
Services
Plugins
Recent questions tagged emotion_analyzer at Robotics Stack Exchange
|
emotion_analyzer package from jsk_3rdparty repovoicevox chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools respeaker_ros ros_speech_recognition rospatlite sesame_ros switchbot_ros |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-13 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kei Okada
- Yoshiki Obinata
Authors
- Ayaha Nagata
Emotion Analyzer Service using Hume API (ROS1)
This ROS1 package provides a service to analyze emotions from a given text using the Hume AI API.
Requirements
- ROS1 Noetic
- Python 3.8+
- An API key from Hume AI
Installation
Clone this repository and move to this directory
rosdep install -iry --from-paths .
catkin build --this
then source your workspace
Usage (Quick)
Using your microphone
roslaunch emotion_analyzer sample_emotion_analyzer.launch api_key:=<your_api_key>
Usage
1. Launch Emotion_Analyzer
roslaunch emotion_analyzer emotion_analyzer.launch api_key:=<your_api_key>
2. Call the service
For text,
rosservice call /analyze_text "text: '<text you want to analyze>'"
For prepared audio (up to 5 seconds),
rosservice call /analyze_audio "audio_file: <audio_file_path>"
As a sample, you can use '/home/leus/ros/catkin_ws/src/jsk_3rdparty/emotion_analyzer/data/purugacha_short.wav' as
For audio from microphone,
roslaunch audio_capture capture.launch format:=wave
rosservice call /analyze_audio "audio_file: ''"
You can check the device information by arecord -l.
Sometimes you need to replace “hw” with “plughw”:
for example, roslaunch audio_capture capture.launch format:=wave device:=plughw:1,0.
When the device is busy, you can try fuser -v /dev/snd/* to get PID and kill it by kill -9 <PID>.
ROS2
catkin_virtualenv is not available on ROS2, so the Hume SDK is installed into a venv (share/emotion_analyzer/venv) from pyproject.toml/uv.lock at build time instead (jsk_ros1_ros2_compat_generate_uv_venv()). Run uv lock after changing pyproject.toml. The scripts use the legacy streaming API (HumeStreamClient), which was removed in hume 0.7, so it is pinned below 0.7.
colcon build --packages-up-to emotion_analyzer
ros2 launch emotion_analyzer emotion_analyzer.launch.xml api_key:=<your_api_key>
# or, with audio_capture
ros2 launch emotion_analyzer sample_emotion_analyzer.launch.xml api_key:=<your_api_key>
ros2 service call /analyze_text emotion_analyzer/srv/AnalyzeText "{text: '<text you want to analyze>'}"
Changelog for package emotion_analyzer
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[emotion_analyzer] use python3-soundfile from apt instead of the uv venv The numpy wheel pulled by soundfile fails dh_strip of the buildfarm binary job (libscipy_openblas64_*.so). python3-soundfile is already an exec_depend and the venv sees the system site-packages. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[emotion_analyzer] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the emotion_analyzer python package, so src/emotion_analyzer/utils is installed into it instead of a second ament_python_install_package().
- package.xml: format 3 for conditions; audio_common_msgs (imported by the scripts but only pulled in by audio_capture before) is listed explicitly. hume has no rosdep key and catkin_virtualenv has no ROS2 port, so ROS2 users pip install it (README.md).
- analyze_{text,audio}_service.py, utils/audio_buffer.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only).
- launch/emotion_analyzer.launch.xml: ROS2 version of emotion_analyzer.launch.
- Catch exceptions from the Hume request and return {"error": ...} (same format as the existing no-audio case): rospy only returned a service error, but an exception in a service callback kills the rclpy node.
- hume (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), and both services are installed with jsk_ros1_ros2_compat_install_python(... USE_VENV) to run with it, instead of asking users to [pip install hume[stream]]{.title-ref}. hume is pinned below 0.7, since the scripts use the legacy HumeStreamClient that 0.7 removed (the latest hume, 0.14, can not
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/emotion_analyzer.launch
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch
-
- api_key [default: ]
- format [default: wave]
- launch/emotion_analyzer.launch.xml
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch.xml
-
- api_key [default: ]
- device [default: ]
Messages
Services
Plugins
Recent questions tagged emotion_analyzer at Robotics Stack Exchange
|
emotion_analyzer package from jsk_3rdparty repovoicevox chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools respeaker_ros ros_speech_recognition rospatlite sesame_ros switchbot_ros |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-13 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kei Okada
- Yoshiki Obinata
Authors
- Ayaha Nagata
Emotion Analyzer Service using Hume API (ROS1)
This ROS1 package provides a service to analyze emotions from a given text using the Hume AI API.
Requirements
- ROS1 Noetic
- Python 3.8+
- An API key from Hume AI
Installation
Clone this repository and move to this directory
rosdep install -iry --from-paths .
catkin build --this
then source your workspace
Usage (Quick)
Using your microphone
roslaunch emotion_analyzer sample_emotion_analyzer.launch api_key:=<your_api_key>
Usage
1. Launch Emotion_Analyzer
roslaunch emotion_analyzer emotion_analyzer.launch api_key:=<your_api_key>
2. Call the service
For text,
rosservice call /analyze_text "text: '<text you want to analyze>'"
For prepared audio (up to 5 seconds),
rosservice call /analyze_audio "audio_file: <audio_file_path>"
As a sample, you can use '/home/leus/ros/catkin_ws/src/jsk_3rdparty/emotion_analyzer/data/purugacha_short.wav' as
For audio from microphone,
roslaunch audio_capture capture.launch format:=wave
rosservice call /analyze_audio "audio_file: ''"
You can check the device information by arecord -l.
Sometimes you need to replace “hw” with “plughw”:
for example, roslaunch audio_capture capture.launch format:=wave device:=plughw:1,0.
When the device is busy, you can try fuser -v /dev/snd/* to get PID and kill it by kill -9 <PID>.
ROS2
catkin_virtualenv is not available on ROS2, so the Hume SDK is installed into a venv (share/emotion_analyzer/venv) from pyproject.toml/uv.lock at build time instead (jsk_ros1_ros2_compat_generate_uv_venv()). Run uv lock after changing pyproject.toml. The scripts use the legacy streaming API (HumeStreamClient), which was removed in hume 0.7, so it is pinned below 0.7.
colcon build --packages-up-to emotion_analyzer
ros2 launch emotion_analyzer emotion_analyzer.launch.xml api_key:=<your_api_key>
# or, with audio_capture
ros2 launch emotion_analyzer sample_emotion_analyzer.launch.xml api_key:=<your_api_key>
ros2 service call /analyze_text emotion_analyzer/srv/AnalyzeText "{text: '<text you want to analyze>'}"
Changelog for package emotion_analyzer
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[emotion_analyzer] use python3-soundfile from apt instead of the uv venv The numpy wheel pulled by soundfile fails dh_strip of the buildfarm binary job (libscipy_openblas64_*.so). python3-soundfile is already an exec_depend and the venv sees the system site-packages. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[emotion_analyzer] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the emotion_analyzer python package, so src/emotion_analyzer/utils is installed into it instead of a second ament_python_install_package().
- package.xml: format 3 for conditions; audio_common_msgs (imported by the scripts but only pulled in by audio_capture before) is listed explicitly. hume has no rosdep key and catkin_virtualenv has no ROS2 port, so ROS2 users pip install it (README.md).
- analyze_{text,audio}_service.py, utils/audio_buffer.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only).
- launch/emotion_analyzer.launch.xml: ROS2 version of emotion_analyzer.launch.
- Catch exceptions from the Hume request and return {"error": ...} (same format as the existing no-audio case): rospy only returned a service error, but an exception in a service callback kills the rclpy node.
- hume (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), and both services are installed with jsk_ros1_ros2_compat_install_python(... USE_VENV) to run with it, instead of asking users to [pip install hume[stream]]{.title-ref}. hume is pinned below 0.7, since the scripts use the legacy HumeStreamClient that 0.7 removed (the latest hume, 0.14, can not
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/emotion_analyzer.launch
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch
-
- api_key [default: ]
- format [default: wave]
- launch/emotion_analyzer.launch.xml
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch.xml
-
- api_key [default: ]
- device [default: ]
Messages
Services
Plugins
Recent questions tagged emotion_analyzer at Robotics Stack Exchange
|
emotion_analyzer package from jsk_3rdparty repovoicevox chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools respeaker_ros ros_speech_recognition rospatlite sesame_ros switchbot_ros |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-13 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kei Okada
- Yoshiki Obinata
Authors
- Ayaha Nagata
Emotion Analyzer Service using Hume API (ROS1)
This ROS1 package provides a service to analyze emotions from a given text using the Hume AI API.
Requirements
- ROS1 Noetic
- Python 3.8+
- An API key from Hume AI
Installation
Clone this repository and move to this directory
rosdep install -iry --from-paths .
catkin build --this
then source your workspace
Usage (Quick)
Using your microphone
roslaunch emotion_analyzer sample_emotion_analyzer.launch api_key:=<your_api_key>
Usage
1. Launch Emotion_Analyzer
roslaunch emotion_analyzer emotion_analyzer.launch api_key:=<your_api_key>
2. Call the service
For text,
rosservice call /analyze_text "text: '<text you want to analyze>'"
For prepared audio (up to 5 seconds),
rosservice call /analyze_audio "audio_file: <audio_file_path>"
As a sample, you can use '/home/leus/ros/catkin_ws/src/jsk_3rdparty/emotion_analyzer/data/purugacha_short.wav' as
For audio from microphone,
roslaunch audio_capture capture.launch format:=wave
rosservice call /analyze_audio "audio_file: ''"
You can check the device information by arecord -l.
Sometimes you need to replace “hw” with “plughw”:
for example, roslaunch audio_capture capture.launch format:=wave device:=plughw:1,0.
When the device is busy, you can try fuser -v /dev/snd/* to get PID and kill it by kill -9 <PID>.
ROS2
catkin_virtualenv is not available on ROS2, so the Hume SDK is installed into a venv (share/emotion_analyzer/venv) from pyproject.toml/uv.lock at build time instead (jsk_ros1_ros2_compat_generate_uv_venv()). Run uv lock after changing pyproject.toml. The scripts use the legacy streaming API (HumeStreamClient), which was removed in hume 0.7, so it is pinned below 0.7.
colcon build --packages-up-to emotion_analyzer
ros2 launch emotion_analyzer emotion_analyzer.launch.xml api_key:=<your_api_key>
# or, with audio_capture
ros2 launch emotion_analyzer sample_emotion_analyzer.launch.xml api_key:=<your_api_key>
ros2 service call /analyze_text emotion_analyzer/srv/AnalyzeText "{text: '<text you want to analyze>'}"
Changelog for package emotion_analyzer
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[emotion_analyzer] use python3-soundfile from apt instead of the uv venv The numpy wheel pulled by soundfile fails dh_strip of the buildfarm binary job (libscipy_openblas64_*.so). python3-soundfile is already an exec_depend and the venv sees the system site-packages. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[emotion_analyzer] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the emotion_analyzer python package, so src/emotion_analyzer/utils is installed into it instead of a second ament_python_install_package().
- package.xml: format 3 for conditions; audio_common_msgs (imported by the scripts but only pulled in by audio_capture before) is listed explicitly. hume has no rosdep key and catkin_virtualenv has no ROS2 port, so ROS2 users pip install it (README.md).
- analyze_{text,audio}_service.py, utils/audio_buffer.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only).
- launch/emotion_analyzer.launch.xml: ROS2 version of emotion_analyzer.launch.
- Catch exceptions from the Hume request and return {"error": ...} (same format as the existing no-audio case): rospy only returned a service error, but an exception in a service callback kills the rclpy node.
- hume (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), and both services are installed with jsk_ros1_ros2_compat_install_python(... USE_VENV) to run with it, instead of asking users to [pip install hume[stream]]{.title-ref}. hume is pinned below 0.7, since the scripts use the legacy HumeStreamClient that 0.7 removed (the latest hume, 0.14, can not
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/emotion_analyzer.launch
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch
-
- api_key [default: ]
- format [default: wave]
- launch/emotion_analyzer.launch.xml
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch.xml
-
- api_key [default: ]
- device [default: ]
Messages
Services
Plugins
Recent questions tagged emotion_analyzer at Robotics Stack Exchange
|
emotion_analyzer package from jsk_3rdparty repovoicevox chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools respeaker_ros ros_speech_recognition rospatlite sesame_ros switchbot_ros |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-13 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kei Okada
- Yoshiki Obinata
Authors
- Ayaha Nagata
Emotion Analyzer Service using Hume API (ROS1)
This ROS1 package provides a service to analyze emotions from a given text using the Hume AI API.
Requirements
- ROS1 Noetic
- Python 3.8+
- An API key from Hume AI
Installation
Clone this repository and move to this directory
rosdep install -iry --from-paths .
catkin build --this
then source your workspace
Usage (Quick)
Using your microphone
roslaunch emotion_analyzer sample_emotion_analyzer.launch api_key:=<your_api_key>
Usage
1. Launch Emotion_Analyzer
roslaunch emotion_analyzer emotion_analyzer.launch api_key:=<your_api_key>
2. Call the service
For text,
rosservice call /analyze_text "text: '<text you want to analyze>'"
For prepared audio (up to 5 seconds),
rosservice call /analyze_audio "audio_file: <audio_file_path>"
As a sample, you can use '/home/leus/ros/catkin_ws/src/jsk_3rdparty/emotion_analyzer/data/purugacha_short.wav' as
For audio from microphone,
roslaunch audio_capture capture.launch format:=wave
rosservice call /analyze_audio "audio_file: ''"
You can check the device information by arecord -l.
Sometimes you need to replace “hw” with “plughw”:
for example, roslaunch audio_capture capture.launch format:=wave device:=plughw:1,0.
When the device is busy, you can try fuser -v /dev/snd/* to get PID and kill it by kill -9 <PID>.
ROS2
catkin_virtualenv is not available on ROS2, so the Hume SDK is installed into a venv (share/emotion_analyzer/venv) from pyproject.toml/uv.lock at build time instead (jsk_ros1_ros2_compat_generate_uv_venv()). Run uv lock after changing pyproject.toml. The scripts use the legacy streaming API (HumeStreamClient), which was removed in hume 0.7, so it is pinned below 0.7.
colcon build --packages-up-to emotion_analyzer
ros2 launch emotion_analyzer emotion_analyzer.launch.xml api_key:=<your_api_key>
# or, with audio_capture
ros2 launch emotion_analyzer sample_emotion_analyzer.launch.xml api_key:=<your_api_key>
ros2 service call /analyze_text emotion_analyzer/srv/AnalyzeText "{text: '<text you want to analyze>'}"
Changelog for package emotion_analyzer
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[emotion_analyzer] use python3-soundfile from apt instead of the uv venv The numpy wheel pulled by soundfile fails dh_strip of the buildfarm binary job (libscipy_openblas64_*.so). python3-soundfile is already an exec_depend and the venv sees the system site-packages. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[emotion_analyzer] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the emotion_analyzer python package, so src/emotion_analyzer/utils is installed into it instead of a second ament_python_install_package().
- package.xml: format 3 for conditions; audio_common_msgs (imported by the scripts but only pulled in by audio_capture before) is listed explicitly. hume has no rosdep key and catkin_virtualenv has no ROS2 port, so ROS2 users pip install it (README.md).
- analyze_{text,audio}_service.py, utils/audio_buffer.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only).
- launch/emotion_analyzer.launch.xml: ROS2 version of emotion_analyzer.launch.
- Catch exceptions from the Hume request and return {"error": ...} (same format as the existing no-audio case): rospy only returned a service error, but an exception in a service callback kills the rclpy node.
- hume (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), and both services are installed with jsk_ros1_ros2_compat_install_python(... USE_VENV) to run with it, instead of asking users to [pip install hume[stream]]{.title-ref}. hume is pinned below 0.7, since the scripts use the legacy HumeStreamClient that 0.7 removed (the latest hume, 0.14, can not
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/emotion_analyzer.launch
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch
-
- api_key [default: ]
- format [default: wave]
- launch/emotion_analyzer.launch.xml
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch.xml
-
- api_key [default: ]
- device [default: ]
Messages
Services
Plugins
Recent questions tagged emotion_analyzer at Robotics Stack Exchange
|
emotion_analyzer package from jsk_3rdparty repovoicevox chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools respeaker_ros ros_speech_recognition rospatlite sesame_ros switchbot_ros |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-13 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kei Okada
- Yoshiki Obinata
Authors
- Ayaha Nagata
Emotion Analyzer Service using Hume API (ROS1)
This ROS1 package provides a service to analyze emotions from a given text using the Hume AI API.
Requirements
- ROS1 Noetic
- Python 3.8+
- An API key from Hume AI
Installation
Clone this repository and move to this directory
rosdep install -iry --from-paths .
catkin build --this
then source your workspace
Usage (Quick)
Using your microphone
roslaunch emotion_analyzer sample_emotion_analyzer.launch api_key:=<your_api_key>
Usage
1. Launch Emotion_Analyzer
roslaunch emotion_analyzer emotion_analyzer.launch api_key:=<your_api_key>
2. Call the service
For text,
rosservice call /analyze_text "text: '<text you want to analyze>'"
For prepared audio (up to 5 seconds),
rosservice call /analyze_audio "audio_file: <audio_file_path>"
As a sample, you can use '/home/leus/ros/catkin_ws/src/jsk_3rdparty/emotion_analyzer/data/purugacha_short.wav' as
For audio from microphone,
roslaunch audio_capture capture.launch format:=wave
rosservice call /analyze_audio "audio_file: ''"
You can check the device information by arecord -l.
Sometimes you need to replace “hw” with “plughw”:
for example, roslaunch audio_capture capture.launch format:=wave device:=plughw:1,0.
When the device is busy, you can try fuser -v /dev/snd/* to get PID and kill it by kill -9 <PID>.
ROS2
catkin_virtualenv is not available on ROS2, so the Hume SDK is installed into a venv (share/emotion_analyzer/venv) from pyproject.toml/uv.lock at build time instead (jsk_ros1_ros2_compat_generate_uv_venv()). Run uv lock after changing pyproject.toml. The scripts use the legacy streaming API (HumeStreamClient), which was removed in hume 0.7, so it is pinned below 0.7.
colcon build --packages-up-to emotion_analyzer
ros2 launch emotion_analyzer emotion_analyzer.launch.xml api_key:=<your_api_key>
# or, with audio_capture
ros2 launch emotion_analyzer sample_emotion_analyzer.launch.xml api_key:=<your_api_key>
ros2 service call /analyze_text emotion_analyzer/srv/AnalyzeText "{text: '<text you want to analyze>'}"
Changelog for package emotion_analyzer
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[emotion_analyzer] use python3-soundfile from apt instead of the uv venv The numpy wheel pulled by soundfile fails dh_strip of the buildfarm binary job (libscipy_openblas64_*.so). python3-soundfile is already an exec_depend and the venv sees the system site-packages. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[emotion_analyzer] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the emotion_analyzer python package, so src/emotion_analyzer/utils is installed into it instead of a second ament_python_install_package().
- package.xml: format 3 for conditions; audio_common_msgs (imported by the scripts but only pulled in by audio_capture before) is listed explicitly. hume has no rosdep key and catkin_virtualenv has no ROS2 port, so ROS2 users pip install it (README.md).
- analyze_{text,audio}_service.py, utils/audio_buffer.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only).
- launch/emotion_analyzer.launch.xml: ROS2 version of emotion_analyzer.launch.
- Catch exceptions from the Hume request and return {"error": ...} (same format as the existing no-audio case): rospy only returned a service error, but an exception in a service callback kills the rclpy node.
- hume (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), and both services are installed with jsk_ros1_ros2_compat_install_python(... USE_VENV) to run with it, instead of asking users to [pip install hume[stream]]{.title-ref}. hume is pinned below 0.7, since the scripts use the legacy HumeStreamClient that 0.7 removed (the latest hume, 0.14, can not
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/emotion_analyzer.launch
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch
-
- api_key [default: ]
- format [default: wave]
- launch/emotion_analyzer.launch.xml
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch.xml
-
- api_key [default: ]
- device [default: ]
Messages
Services
Plugins
Recent questions tagged emotion_analyzer at Robotics Stack Exchange
|
emotion_analyzer package from jsk_3rdparty repovoicevox chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools respeaker_ros ros_speech_recognition rospatlite sesame_ros switchbot_ros |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-13 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kei Okada
- Yoshiki Obinata
Authors
- Ayaha Nagata
Emotion Analyzer Service using Hume API (ROS1)
This ROS1 package provides a service to analyze emotions from a given text using the Hume AI API.
Requirements
- ROS1 Noetic
- Python 3.8+
- An API key from Hume AI
Installation
Clone this repository and move to this directory
rosdep install -iry --from-paths .
catkin build --this
then source your workspace
Usage (Quick)
Using your microphone
roslaunch emotion_analyzer sample_emotion_analyzer.launch api_key:=<your_api_key>
Usage
1. Launch Emotion_Analyzer
roslaunch emotion_analyzer emotion_analyzer.launch api_key:=<your_api_key>
2. Call the service
For text,
rosservice call /analyze_text "text: '<text you want to analyze>'"
For prepared audio (up to 5 seconds),
rosservice call /analyze_audio "audio_file: <audio_file_path>"
As a sample, you can use '/home/leus/ros/catkin_ws/src/jsk_3rdparty/emotion_analyzer/data/purugacha_short.wav' as
For audio from microphone,
roslaunch audio_capture capture.launch format:=wave
rosservice call /analyze_audio "audio_file: ''"
You can check the device information by arecord -l.
Sometimes you need to replace “hw” with “plughw”:
for example, roslaunch audio_capture capture.launch format:=wave device:=plughw:1,0.
When the device is busy, you can try fuser -v /dev/snd/* to get PID and kill it by kill -9 <PID>.
ROS2
catkin_virtualenv is not available on ROS2, so the Hume SDK is installed into a venv (share/emotion_analyzer/venv) from pyproject.toml/uv.lock at build time instead (jsk_ros1_ros2_compat_generate_uv_venv()). Run uv lock after changing pyproject.toml. The scripts use the legacy streaming API (HumeStreamClient), which was removed in hume 0.7, so it is pinned below 0.7.
colcon build --packages-up-to emotion_analyzer
ros2 launch emotion_analyzer emotion_analyzer.launch.xml api_key:=<your_api_key>
# or, with audio_capture
ros2 launch emotion_analyzer sample_emotion_analyzer.launch.xml api_key:=<your_api_key>
ros2 service call /analyze_text emotion_analyzer/srv/AnalyzeText "{text: '<text you want to analyze>'}"
Changelog for package emotion_analyzer
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[emotion_analyzer] use python3-soundfile from apt instead of the uv venv The numpy wheel pulled by soundfile fails dh_strip of the buildfarm binary job (libscipy_openblas64_*.so). python3-soundfile is already an exec_depend and the venv sees the system site-packages. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[emotion_analyzer] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the emotion_analyzer python package, so src/emotion_analyzer/utils is installed into it instead of a second ament_python_install_package().
- package.xml: format 3 for conditions; audio_common_msgs (imported by the scripts but only pulled in by audio_capture before) is listed explicitly. hume has no rosdep key and catkin_virtualenv has no ROS2 port, so ROS2 users pip install it (README.md).
- analyze_{text,audio}_service.py, utils/audio_buffer.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only).
- launch/emotion_analyzer.launch.xml: ROS2 version of emotion_analyzer.launch.
- Catch exceptions from the Hume request and return {"error": ...} (same format as the existing no-audio case): rospy only returned a service error, but an exception in a service callback kills the rclpy node.
- hume (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), and both services are installed with jsk_ros1_ros2_compat_install_python(... USE_VENV) to run with it, instead of asking users to [pip install hume[stream]]{.title-ref}. hume is pinned below 0.7, since the scripts use the legacy HumeStreamClient that 0.7 removed (the latest hume, 0.14, can not
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/emotion_analyzer.launch
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch
-
- api_key [default: ]
- format [default: wave]
- launch/emotion_analyzer.launch.xml
-
- input_audio [default: /audio/audio]
- api_key [default: ]
- launch/sample_emotion_analyzer.launch.xml
-
- api_key [default: ]
- device [default: ]