Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility issues with ROS1 #416

Open
DarkJoker9817 opened this issue Mar 3, 2023 · 1 comment
Open

Compatibility issues with ROS1 #416

DarkJoker9817 opened this issue Mar 3, 2023 · 1 comment
Assignees
Milestone

Comments

@DarkJoker9817
Copy link

Hello everyone, I have to evolve an FSM behavior model into BT on an already existent architecture that uses ROS1 for interaction and navigation on Pepper robot. Now I have designed the behavior tree and I have to use a lot of Sequence node without memory to ensure reactivity of the robot, but these are are not supported in py_trees 0.7 which is the version that is automatically installed when I install ros-noetic-py-trees-ros.
Is py-trees-ros mandatory in my case? Or I can use only py_trees 2.2 for having Sequence node without memory and other stuffs?

@stonier
Copy link
Member

stonier commented Mar 13, 2023

YMMV, but py_trees is almost pure python, so problems would be limited

  • Python compatibility - noetic is py3 I believe, so a node dependening on py_trees 2.2 should be possible
  • package.xml - unsure if this will be compatible, worst case, you'll have to patch it with a ros1 equivalent or bring in the pypi package as a dependency and treat it as a pure python package
  • Behaviours - you may want to recreate some of the py_trees_ros behaviours in a library of your own
  • Tools - the biggest miss will probably be the tooling, i.e. blackboard/tree watcher, ros viewer, hard to recreate that

@stonier stonier added this to the 2.2.x milestone Mar 13, 2023
@stonier stonier self-assigned this Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants