Skip to content
Discussion options

You must be logged in to vote

IMO it's a fallacy to look for a "behavior tree library for ROS 2".

ROS is a communication framework, while a behavior tree is a model to plan the execution of tasks.
The main purpose of ROS is to abstract the connection between different components, but it does not care what these components do internally.
You don't need a "behavior tree library for ROS 2", but rather you need to take any generic behavior tree library and "wrap it" inside ROS 2 APIs.
Writing a behavior tree library that is heavily dependent on ROS and meant to be only used through it would be a bad design choice and that's why you will likely not find it.

Having said that, considering the popularity of ROS 2 and the rece…

Replies: 1 comment 4 replies

Comment options

You must be logged in to vote
4 replies
@framlin
Comment options

@alsora
Comment options

@framlin
Comment options

@alsora
Comment options

Answer selected by framlin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants