Closed jsbyysheng closed 4 years ago
The planning_adapters of ompl_planning_pipeline.launch.xml in panda_moveit_config(kinetic-devel) is the order of the following:
planning_adapters
ompl_planning_pipeline.launch.xml
default_planner_request_adapters/AddTimeParameterization default_planner_request_adapters/FixWorkspaceBounds default_planner_request_adapters/FixStartStateBounds default_planner_request_adapters/FixStartStateCollision default_planner_request_adapters/FixStartStatePathConstraints
However, The planning_adapters of ompl_planning_pipeline.launch.xml in panda_moveit_config(melodic-devel) is the order of the following:
default_planner_request_adapters/FixWorkspaceBounds default_planner_request_adapters/FixStartStateBounds default_planner_request_adapters/FixStartStateCollision default_planner_request_adapters/FixStartStatePathConstraints default_planner_request_adapters/ResolveConstraintFrames default_planner_request_adapters/AddTimeParameterization"
I am very confused about why default_planner_request_adapters/AddTimeParameterization changes the order in planning_adapters ? Is that a bug ?
default_planner_request_adapters/AddTimeParameterization
No, actually it works both ways around because the adapters choose themselves whether to run before or after the actual planner.
The
planning_adapters
ofompl_planning_pipeline.launch.xml
in panda_moveit_config(kinetic-devel) is the order of the following:However, The
planning_adapters
ofompl_planning_pipeline.launch.xml
in panda_moveit_config(melodic-devel) is the order of the following:I am very confused about why
default_planner_request_adapters/AddTimeParameterization
changes the order inplanning_adapters
? Is that a bug ?