-
 

soar_ros package from soar_ros repo

soar_ros

Package Summary

Tags No category tags.
Version 0.0.1
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/THA-Embedded-Systems-Lab/soar_ros.git
VCS Type git
VCS Version main
Last Updated 2024-11-15
Dev Status UNMAINTAINED
CI status No Continuous Integration
Released UNRELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

An interface library to connect ROS2 with the Soar cognitive architecture.

Additional Links

No additional links.

Maintainers

  • Moritz Schmidt

Authors

No additional authors.

soar_ros: A ROS 2 Interface for Soar

This ROS2 package provides an interface for the Soar cognitive architecture by creating wrappers for ROS2 messages and handling the Soar kernel in a continuos mode.

Soar is a cognitive architecture developed at the University of Michigan. It is used in the field of cognitive robotics in different projects, e.g. a drone or a robot. However, the integration of Soar and ROS 2 is currently difficult for complex projects, which include multiple publishers, subscribers, services or clients. The main limitation orginates from the synchronous callback model used by Soar which inspired the creation of this wrapper. A detailed explanation about the reason for the development of the package can be read in the software architecture.

The package relies on a forked version of Soar. The major changes include a cmake-based build instead of scons and removal of SWIG language interfaces. For a detailed comparison have a look at the commit history of the fork.

Features

The library is developed targeting ROS 2 Humble on Ubuntu 22.04. Other configurations were not tested. It provides

  • Non blocking Soar kernel
  • Publisher
  • Subscriber
  • Service
  • Client

The following features are not supported, yet.

  • Action Server and Client
  • Multiple Soar agents

Definition and description of the public API

The API documentation is generated via rosdoc2, cf. how to build documentation.

Examples

The following examples are an extract of the test cases in test/test_soar_ros.cpp.

Publisher

The soar_ros::Publisher extends the ROS Publisher so the user only needs to define how data are converted between ROS data types and Soar data types.

``` {.sourceCode .cpp}
class TestOutput : public soar_ros::Publisher<std_msgs::msg::String>
{
public:
TestOutput(sml::Agent * agent, rclcpp::Node::SharedPtr node, const std::string & topic)
Publisher<std_msgs::msg::String>(agent, node, topic) {} ~TestOutput() {} std_msgs::msg::String parse(sml::Identifier * id) override { std_msgs::msg::String msg; msg.data = id->GetParameterValue(“data”); std::cout « id->GetCommandName() « ” “ « msg.data « std::endl; return msg; } };

### Service

In the following example, the ROS2 example `AddTwoInts` is implemented.
Soar adds two integers and sends the result as a ROS2 Service, based on
the `soar_ros::Service` class. The code is from
[test/test\_soar\_ros.cpp](./test/test_soar_ros.cpp).


``` {.sourceCode .cpp}
class TestService : public soar_ros::Service<example_interfaces::srv::AddTwoInts>
{
public:
  TestService(sml::Agent * agent, rclcpp::Node::SharedPtr node, const std::string & topic)
  : Service<example_interfaces::srv::AddTwoInts>(agent, node, topic) {}
  ~TestService() {}

  example_interfaces::srv::AddTwoInts::Response::SharedPtr parse(sml::Identifier * id) override
  {
    example_interfaces::srv::AddTwoInts::Response::SharedPtr response =
      std::make_shared<example_interfaces::srv::AddTwoInts::Response>();
    auto sum = id->GetParameterValue("sum");
    int32_t num = std::stoi(sum);
    response.get()->sum = num;
    RCLCPP_INFO(m_node->get_logger(), "Computed: Sum=%ld", response.get()->sum);
    std::cout << "Sum=" << response.get()->sum << std::endl;
    return response;
  }

  void parse(example_interfaces::srv::AddTwoInts::Request::SharedPtr msg) override
  {
    sml::Identifier * il = getAgent()->GetInputLink();
    sml::Identifier * pId = il->CreateIdWME("AddTwoInts");
    pId->CreateIntWME("a", msg.get()->a);
    pId->CreateIntWME("b", msg.get()->b);
  }
}

A second step is required to actually make this interface available -adding it to the node similar to a builder pattern, cf. tes_soar_ros.cpp.

``` {.sourceCode .cpp} auto node = std::make_shared<soar_ros::SoarRunner>(“Test Agent”, soar_path);

std::shared_ptr<soar_ros::Service<example_interfaces::srv::AddTwoInts» service = std::make_shared(node.get()->getAgent(), node, "AddTwoInts"); node->addService(service);

node->startThread();

rclcpp::executors::MultiThreadedExecutor executor; executor.add_node(node); executor.spin();


These rules use an operator to add two integer numbers and provide the
sum at the output link. The following rules are availabe in
[main.soar](Soar/main.soar).


``` {.sourceCode .soar}
sp {any*propose*add_two_ints
   (state <s> ^io.input-link.AddTwoInts <pAddTwoInts>)
   -(<pAddTwoInts> ^status complete)
-->
   (<s> ^operator <o> + =)
   (<o> ^name add_two_ints
      ^pAddTwoInts <pAddTwoInts>)
}

sp {any*apply*add_two_ints
   (state <s> ^operator <o>
      ^io.output-link <ol>)
   (<o> ^name add_two_ints
   ^pAddTwoInts <pAddTwoInts>)
   (<pAddTwoInts> ^a <a>
      ^b <b>)
-->
   (<ol> ^AddTwoInts.sum (+ <a> <b>))
   (<pAddTwoInts> ^status complete)
}

How to build and install

Prerequisite: A ROS2 installation is available.

  1. Clone this repository in your workspace
  2. Build via colcon build --packages-select soar_ros
  3. Source the ROS workspace
  4. Run the test executable via ros2 run soar_ros test_example. The output should look similar to the following:

``` {.sourceCode .shell} $ ros2 run soar_ros test_example [INFO] [1721823668.516038530] [SoarRunner]: Starting runThread [INFO] [1721823668.516344554] [SoarRunner]: Test Agent: 1: O: O1 (init-agent) [INFO] [1721823668.516466911] [SoarRunner]: Test Agent: 2: ==>S: S2 (state no-change) [WARN] [1721823669.516121281] [SoarRunner]: AddTwoIntsClient service not available, waiting again…


::: {.warning}
::: {.admonition-title}
Warning
:::

If you would like to use the Java-based debugger, the installation of
the official Soar release is requried: Download and install the latest
Soar release from their [repository](https://github.com/SoarGroup/Soar).
Setting the `SOAR_HOME` environment variable to the `bin/` directory of
the insalltion could help to open the debugger.
:::

How to build and run tests
--------------------------

The packages relies on the `colcon test` procedure, including launch
testing which is automatically triggered by `colcon test`.


``` {.sourceCode .shell}
colcon test
colcon test-result --verbose

How to build documentation

The documentation is generated via rosdoc2. Execute the following commands in the cloned repository or adjust the path of rosdoc2 build accordingly.

``` {.sourceCode .shell} rosdoc2 build –package-path . rosdoc2 open docs_output/soar_ros/index.html


How to develop
--------------

Clone the package in your ROS2 workspace.

Usage
-----

Include this package as dependency in your `CMakeLists.txt` and clone it
your ROS2 workspace.


``` {.sourceCode .cmake}
find_package(soar_ros REQUIRED)
ament_target_dependencies(<executable_name> soar_ros)

For code references have a look at the examples.

License

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License

Refer to the license file. The respective Soar license is available at their repository.

Acknowledgements

This project was developed as part of the AI Production Network Augsburg funded by the Bavarian State Ministry of Science and the Arts and the Bavarian Ministry of Economic Affairs, Regional Development and Energy, cf. about.

Imprint & privacy

CHANGELOG

Changelog for package soar_ros

0.0.1 (2024-09-13)

  • Initial commit
  • Contributors: Moritz Schmidt

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged soar_ros at Robotics Stack Exchange

No version for distro iron. Known supported distros are highlighted in the buttons above.
No version for distro jazzy. Known supported distros are highlighted in the buttons above.
No version for distro rolling. Known supported distros are highlighted in the buttons above.
No version for distro noetic. Known supported distros are highlighted in the buttons above.
No version for distro ardent. Known supported distros are highlighted in the buttons above.
No version for distro bouncy. Known supported distros are highlighted in the buttons above.
No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro eloquent. Known supported distros are highlighted in the buttons above.
No version for distro dashing. Known supported distros are highlighted in the buttons above.
No version for distro galactic. Known supported distros are highlighted in the buttons above.
No version for distro foxy. Known supported distros are highlighted in the buttons above.
No version for distro lunar. Known supported distros are highlighted in the buttons above.
No version for distro jade. Known supported distros are highlighted in the buttons above.
No version for distro indigo. Known supported distros are highlighted in the buttons above.
No version for distro hydro. Known supported distros are highlighted in the buttons above.
No version for distro kinetic. Known supported distros are highlighted in the buttons above.
No version for distro melodic. Known supported distros are highlighted in the buttons above.