-
Notifications
You must be signed in to change notification settings - Fork 63
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
[Feature Req] Python test_competitor #194
Comments
We would like to include a python version of the test competitor but unfortunately the python bindings for MoveIt2 are not yet available. There is an open pull request on the MoveIt2 repo that seems close to being merged. Once that is merged (and hopefully back-ported to galactic) we can explore a python version of the test competitor. In the meantime we welcome any pull requests from the community for a python based test competitor. |
Thanks for the clarification on the blocker with moveit_py. And also, that brings up another concern (Apology on bringing it here let me know if it warrants a separate discussion) Any specific reason to stick to galactic especially now that it's at EOL? Let's hope any future enhancements to moveit_py etc would still be backported anyway. |
Yeah the original plan with the port was to use humble but there is a bug with gazebo/ros2_control with the UR robots that makes them unusable in simulation. The issue is being tracked here: UniversalRobots/Universal_Robots_ROS2_Gazebo_Simulation#19 |
We are working to add tutorials that show how to perform many ARIAC tasks using python (outside of controlling the robots). Hopefully this will be a good starting point for competitors who are more comfortable with python. Any feedback on these tutorials is appreciated. Also It seems that the moveit_py pull request has now been merged into the main branch of moveit2. Hopefully they choose to backport it. I just tried to build the package on galactic and it does not immediately work so there will be some effort. I would not rely on it being ready for this years competition. My advice for this year is to separate the system that is controlling the robots from your main system. That will allow your software to be mostly written in python and the node to control the robots to be written in C++. When tutorial 5 is finished this should be helpful in getting that started. |
Will it be possible to provide a python version of test_competitor for the benefit of teams using python as primarily?
It necessary not need to come up from the organizers, may be PR from a competitor already familiar with ROS2 python would also do. (Strictly restricted to the capability on par or below the level of capability in CPP version of test_competitor. After all no need to spoon feed everything)
The text was updated successfully, but these errors were encountered: