-
Notifications
You must be signed in to change notification settings - Fork 94
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
26 additions
and
0 deletions.
There are no files selected for viewing
26 changes: 26 additions & 0 deletions
26
crane_x7_examples_py/config/crane_x7_moveit_py_examples.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
planning_scene_monitor_options: | ||
name: "planning_scene_monitor" | ||
robot_description: "robot_description" | ||
joint_state_topic: "/joint_states" | ||
attached_collision_object_topic: "/moveit_cpp/planning_scene_monitor" | ||
publish_planning_scene_topic: "/moveit_cpp/publish_planning_scene" | ||
monitored_planning_scene_topic: "/moveit_cpp/monitored_planning_scene" | ||
wait_for_initial_state_timeout: 10.0 | ||
|
||
planning_pipelines: | ||
pipeline_names: ["ompl"] | ||
|
||
plan_request_params: | ||
planning_attempts: 1 | ||
planning_pipeline: ompl | ||
max_velocity_scaling_factor: 1.0 | ||
max_acceleration_scaling_factor: 1.0 | ||
|
||
ompl_rrtc: # Namespace for individual plan request | ||
plan_request_params: # PlanRequestParameters similar to the ones that are used by the single pipeline planning of moveit_cpp | ||
planning_attempts: 1 # Number of attempts the planning pipeline tries to solve a given motion planning problem | ||
planning_pipeline: ompl # Name of the pipeline that is being used | ||
planner_id: "RRTConnectkConfigDefault:" # Name of the specific planner to be used by the pipeline | ||
max_velocity_scaling_factor: 1.0 # Velocity scaling parameter for the trajectory generation algorithm that is called (if configured) after the path planning | ||
max_acceleration_scaling_factor: 1.0 # Acceleration scaling parameter for the trajectory generation algorithm that is called (if configured) after the path planning | ||
planning_time: 5.0 # Time budget for the motion plan request. If the planning problem cannot be solved within this time, an empty solution with error code is returned |