moveit2
moveit2 copied to clipboard
:robot: MoveIt for ROS 2
### Description Right now it is not possible to use planners other than OMPL with the moveit_cpp interface. The reason for this is the following: When the plan() method of...
## Description This PR adds a first implementation of @mamoll proposal in #1200 to run multiple planning pipelines in parallel to improve the path quality through creating multiple solutions and...
Adresses #1435 by creating a new hpp-fcl plugin for MoveIt. Binaries of hpp-fcl are due to be available on tomorrow's sync so I would wait for that at least.
### Description Attempt to solve https://github.com/ros-planning/moveit2/issues/1328 by checking if Pilz is being used before trying to load pilz_cartesian_limits.yaml. If Pilz is not being used, there shouldn't be a need to...
### Description MoveIt Setup Assistant should write the controller namespace to the yaml file, like this: ``` arm_controller: type: FollowJointTrajectory action_ns: follow_joint_trajectory joints: - J1 ... - J6 ``` Fixes...
MoveIt has way too many parameters and in most cases, many of the parameters are always the same between MoveIt configs. These parameters should be identified, have defaults set in...
A single node should receive the robot_description config and all other nodes that share the need for that parameter should get it from that one node. The way this works...
Co-authored-by: Sebastian Jahr Signed-off-by: Tyler Weaver
As reported in issue #1506, the default `moveit_controllers.yaml` created by MSA is missing a few lines: ``` action_ns: follow_joint_trajectory default: true ```
### Description I've been trying to use CHOMP to post-process some trajectories, but I found it was always exiting after the first iteration, despite having a collision cost over the...