automatika_embodied_agents: 0.3.2-1 in 'rolling/distribution.yaml' [bloom]

[aleph-ra]

Increasing version of package(s) in repository automatika_embodied_agents to 0.3.2-1:

• upstream repository: https://github.com/automatika-robotics/ros-agents.git
• release repository: https://github.com/ros2-gbp/automatika_embodied_agents-release.git
• distro file: rolling/distribution.yaml
• bloom version: 0.12.0
• previous version for package: null

automatika_embodied_agents

* (docs) Updates docs for conversational agent and SpeechToTextConfig
* (feature) Adds vad, audio feautres and wakeword classification classes based local onnx models
* (feature) Adds utility function for downloading models and status classes for speech processing
* (feature) Adds configuration for wakeword detections in speechtotext component
* (fix) Fixes error in ollama client where tool calls are received without output content
* (fix) Adds a fix to map encoding where it can start with a single detections layer
* (refactor) Makes component name non-optional in components to avoid name conflicts
* (fix) Fixes error for long prompts when checking if prompt is a filename
* (refactor) Removes pytorch as a dependency and runs VAD model with onnxruntime
* (refactor) Makes warmup a property of model components that defaults to false
* (feature) Adds utility method to download onnx model files
* (refactor) Replaces info with debug to reduce logging spam
* (fix) Fixes getting logging severity level for jazzy onwards
* (fix) Adds minor improvements to branching for llm and mllm components
* (chore) Cleansup dependencies for packaging
* (chore) Adds dependency for sugar and removes unnecessary python dependencies from packaging
* (fix) Corrects import of Topic class
* (docs) Removes redefinition of Topic and corrects links to ROS Sugar
* (fix) Changes topic in base component to be directly inherited from ROS Sugar for consistency accross packages
* (feature) Adds warmup functions to all model based components
* (refactor) Removes pillow as a dependancy
* (refactor) Removes overrrides from components and adds custom meathods instead
* (feature) Adds warmup to vision component for displaying stats on init
* (fix) Adds fix for correct colors in cv2 visualization
* (fix) Adds node name as window name for visualization in vision component
* (feature) Adds cv2 based visualization option to vision component
* (refactor) Reduces branching in execution step for components
* (chore) Combines agents and agents_interfaces to one package
* (chore) Changes deb package name
* (fix) Fixes raising error in model initialization for roboml clients
* (refactor) Adds passing additional agent types to ros sugar
* (fix) Fixes error messages when wrong component inputs/outputs are passed
* (feature) Adds support for CompressedImage msg type in components
* (feature) Adds option to deploy vision models using tensorrt
  Works with roboml
* (fix) Fixes check on sufficient topics in component validation
* (fix) Fixes a bug in topic validation
* (fix) Fixes validation of topics in components
* (refactor) Changes handling of image messages for publication
  - Adds support for CompressedImage messages
  - Gathers image messages directly in vision component instead of getting them back from clients
* (feature) Adds frame_id to trackings publisher and updates msg and callback
* (feature) Adds boxes to vision tracking message
* Contributors: ahr, mkabtoul

[github-actions]

Thanks for sending a pull request to ROS distro!

This is an automated tool that helps check your pull request for correctness.
This tool checks a number of attributes associated with your ROS package and generates a report that helps our reviewers merge your pull request in a timely fashion. Here are a few things to consider when sending adding or updating a package to ROS Distro.
ROS Distro includes a very helpful CONTRIBUTING.md file that we recommend reading if it is your first time submitting a package.
Please also read the ROS Distro review guidelines which summarizes this release process.

ROS Distro Considerations

• ROS Distributions are created using REP-134 Standards Track as a guide.
• Your package name should comply to REP-144 ROS Package Naming
• Your package must build for all platforms and architectures on the ROS buildfarm. See REP-2000 ROS Releases and Supported Platforms for all supported platforms for your ROS Distro.
• Your package must contain an OSI approved license. Your package.xml file must also include that license in a machine readable format. See REP-149 Package Manifest Format Three Specification for additional details.
• A publicly available, open source, repository for your ROS package.
• While not required, we recommend that you create an account for ROS Discourse and subscribe to the appropriate release topic.
• If you would like, you may join our Discord Server and ask questions in the #infra-help channel.

Package Considerations

Having your package included in a ROS Distro is a badge of quality, and we recommend that package developers strive to create packages of the highest quality. We recommend package developers review the following resources before submitting their package.

• REP-2004 Package Quality Declaration-- The ROS 2 TSC has created a quality rating system for ROS packages. These ratings should serve as a guide for package developers. We recommend package developers achieve a quality level of three or higher.
• Documentation -- it is recommended that ROS packages include an extensive README.md file, and API level documentation using the Sphinx documentation system.
• Maintainer Responsibilities -- the ROS 2 documentation includes a guide to ROS package maintainer responsibilities that summarizes your responsibilities as an open source maintainer. While we do not enforce these requirements on package maintainers they should be considered best practices.
• We recommend that your package should strive to conform to the ROS 2 Developer Guide and the ROS 2 Style Guide.

Need Help?

Please post your questions to Robotics Stack Exchange or refer to the #infra-help channel on our Discord server.

---

For changes related to yamllint:

• ✅ All new lines of YAML pass linter checks