# fzi-forschungszentrum-informatik/manipulation_pipeline architecture

> Architecture diagram of the GitHub repository fzi-forschungszentrum-informatik/manipulation_pipeline, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-04-01). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/fzi-forschungszentrum-informatik/manipulation_pipeline
- Repository: https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline

## Overview

1. This repository is split into two ROS 2 packages with a clear boundary:
   - `manipulation_pipeline_interfaces`: the external API contract.
   - `manipulation_pipeline`: the MoveIt 2–based implementation that serves that API.

2. The public-facing contract is action-centric. The interfaces package defines actions for the main manipulation primitives: `MoveToPose`, `MoveToNamedPose`, `MoveToConfiguration`, `ExecutePath`, `Grasp`, `Place`, and `ActuateTool`. These are the entry points a client would use to request motion planning or manipulation.

3. The same interfaces package also defines the supporting data model used by those actions: motion parameters, cartesian/linear motion limits, progress reporting, state reporting, tool commands, collision pairs, and object composition metadata. This is the stable boundary between external clients and the planner/executor internals.

4. The implementation package is organized as a layered planning-and-execution pipeline rather than a single monolithic node. The main orchestration classes are `manipulation_pipeline`, `planning_pipeline`, `planning_interface`, `planner`, and `execution_pipeline`, which together turn an incoming request into a plan and then into executed robot motion.

5. Planning is split into reusable “planning steps.” The `planning_steps` directory contains step implementations such as `move_to_pose`, `move_to_named_pose`, `move_to_configuration`, `grasp`, `place`, `actuate_tool`, and `execute_path`. This suggests the system composes multi-stage manipulation behaviors from smaller steps instead of hardcoding each behavior into a separate node.

6. Execution is its own subsystem. `execution_pipeline` and the action-specific execution helpers under `src/actions` handle sending trajectories or commands downstream after planning succeeds. The `execute_trajectory` and `execute_path` pieces indicate a clear separation between trajectory generation and controller execution.

7. World and robot state management is another core subsystem. `robot_model`, `robot_model_monitor`, and `collision_object_manager` manage the robot description and collision scene, including runtime changes. The README explicitly calls out support for URDF/SRDF changes during runtime, which is important for tool-changer or reconfiguration scenarios.

8. The package exposes object-scene manipulation through services in the interfaces package: spawn, remove, remove multiple, split, and combine objects. That means the pipeline is not limited to pure motion goals; it also maintains the planning world model as part of the interaction loop.

9. Several internal utility components support this architecture:
   - `ik_sampler` for inverse-kinematics sampling,
   - `planning_context` for carrying request-specific state,
   - `goal_handle` for tracking action lifecycles,
   - `worker_thread` for background/asynchronous processing,
   - `visualization_interface` for publishing or updating visualization state.

10. The data flow is typically: client sends a ROS 2 action or service request → `manipulation_pipeline` interprets it into a planning context and step sequence → planning uses MoveIt 2/MoveItCpp plus the current robot/world model → execution pipeline sends the resulting motion to controllers → progress and state are reported back through the action result/feedback channels and state messages.

11. The main external dependency is MoveIt 2, and the README makes it clear the repo expects a working `_moveit_config` package with normal MoveIt concepts and default controller selection. So the architecture is intentionally lightweight around MoveIt rather than replacing it.

12. In diagram terms, the key boundaries are:
   - external consumers vs. ROS interface package,
   - interface package vs. implementation package,
   - planning vs. execution,
   - robot/world state management vs. motion generation,
   - internal step composition vs. action-level API.

Main entry points: [`manipulation_pipeline/include/manipulation_pipeline/planning_pipeline.h`](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_pipeline.h) (Planning pipeline), [`manipulation_pipeline/include/manipulation_pipeline/execution_pipeline.h`](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/execution_pipeline.h) (Execution pipeline), [`manipulation_pipeline/include/manipulation_pipeline/manipulation_pipeline.h`](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/manipulation_pipeline.h) (Pipeline entry), [`manipulation_pipeline/include/manipulation_pipeline/planner.h`](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planner.h) (Planner)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_group_interfaces["ROS 2 Interfaces"]
  node_node_interfaces_api["Action API<br/>interfaces pkg"]
  node_node_interfaces_msgs["Shared data<br/>interfaces pkg"]
  node_node_interfaces_srvs["Scene services<br/>interfaces pkg"]
end

subgraph group_group_impl["Pipeline Implementation"]
  node_node_manipulation_pipeline["Pipeline entry<br/>impl orchestrator"]
  node_node_planning_interface["Planning interface<br/>request adapter"]
  node_node_planning_pipeline["Planning pipeline<br/>planner flow"]
  node_node_planner["Planner<br/>[planner.h]"]
  node_node_planning_context["Planning context<br/>request state<br/>[planning_context.h]"]
  node_node_execution_pipeline["Execution pipeline<br/>execution flow"]
  node_node_robot_model[("Robot model<br/>state manager<br/>[robot_model.h]")]
  node_node_robot_model_monitor["Model monitor<br/>state sync"]
  node_node_collision_object_manager[("Collision scene<br/>world manager")]
  node_node_ik_sampler{{"IK sampler<br/>sampling<br/>[ik_sampler.h]"}}
  node_node_visualization_interface["Visualization<br/>publishing"]
  node_node_worker_thread["Worker thread<br/>async runtime<br/>[worker_thread.h]"]
end

subgraph group_group_planning_steps["Planning Steps"]
  node_node_step_move_pose["Move pose<br/>planning step<br/>[move_to_pose.h]"]
  node_node_step_move_named["Move named<br/>planning step"]
  node_node_step_move_config["Move config<br/>planning step"]
  node_node_step_grasp["Grasp<br/>planning step<br/>[grasp.h]"]
  node_node_step_place["Place<br/>planning step<br/>[place.h]"]
  node_node_step_actuate_tool["Actuate tool<br/>planning step<br/>[actuate_tool.h]"]
  node_node_step_execute_path["Execute path<br/>planning step<br/>[execute_path.h]"]
end

subgraph group_group_actions["Action Helpers"]
  node_node_action_execute_trajectory["Exec trajectory<br/>action helper"]
  node_node_action_dwell["Dwell<br/>action helper<br/>[dwell.h]"]
  node_node_action_change_attached["Attach change<br/>action helper"]
end

node_node_external_clients(("External clients<br/>consumer"))

node_node_external_clients -->|"calls"| node_node_interfaces_api
node_node_external_clients -->|"updates world"| node_node_interfaces_srvs
node_node_interfaces_api -->|"requests"| node_node_manipulation_pipeline
node_node_interfaces_msgs -->|"contracts"| node_node_manipulation_pipeline
node_node_interfaces_srvs -->|"scene ops"| node_node_collision_object_manager
node_node_manipulation_pipeline -->|"adapts"| node_node_planning_interface
node_node_planning_interface -->|"builds"| node_node_planning_context
node_node_planning_interface -->|"dispatches"| node_node_planning_pipeline
node_node_planning_pipeline -->|"plans"| node_node_planner
node_node_planning_pipeline -->|"composes"| node_node_step_move_pose
node_node_planning_pipeline -->|"composes"| node_node_step_move_named
node_node_planning_pipeline -->|"composes"| node_node_step_move_config
node_node_planning_pipeline -->|"composes"| node_node_step_grasp
node_node_planning_pipeline -->|"composes"| node_node_step_place
node_node_planning_pipeline -->|"composes"| node_node_step_actuate_tool
node_node_planning_pipeline -->|"composes"| node_node_step_execute_path
node_node_planner -->|"samples"| node_node_ik_sampler
node_node_planner -->|"reads model"| node_node_robot_model
node_node_planner -->|"uses scene"| node_node_collision_object_manager
node_node_robot_model_monitor -->|"syncs"| node_node_robot_model
node_node_robot_model_monitor -->|"syncs"| node_node_collision_object_manager
node_node_planning_pipeline -->|"hands off"| node_node_execution_pipeline
node_node_execution_pipeline -->|"executes"| node_node_action_execute_trajectory
node_node_execution_pipeline -->|"coordinates"| node_node_action_dwell
node_node_execution_pipeline -->|"coordinates"| node_node_action_change_attached
node_node_execution_pipeline -->|"reports"| node_node_visualization_interface
node_node_manipulation_pipeline -->|"runs async"| node_node_worker_thread
node_node_manipulation_pipeline -->|"publishes state"| node_node_visualization_interface

click node_node_interfaces_api "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/tree/main/manipulation_pipeline_interfaces/action"
click node_node_interfaces_msgs "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/tree/main/manipulation_pipeline_interfaces/msg"
click node_node_interfaces_srvs "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/tree/main/manipulation_pipeline_interfaces/srv"
click node_node_manipulation_pipeline "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/manipulation_pipeline.h"
click node_node_planning_interface "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_interface.h"
click node_node_planning_pipeline "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_pipeline.h"
click node_node_planner "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planner.h"
click node_node_planning_context "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_context.h"
click node_node_execution_pipeline "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/execution_pipeline.h"
click node_node_robot_model "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/robot_model.h"
click node_node_robot_model_monitor "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/robot_model_monitor.h"
click node_node_collision_object_manager "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/collision_object_manager.h"
click node_node_ik_sampler "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/ik_sampler.h"
click node_node_visualization_interface "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/visualization_interface.h"
click node_node_worker_thread "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/worker_thread.h"
click node_node_step_move_pose "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_steps/move_to_pose.h"
click node_node_step_move_named "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_steps/move_to_named_pose.h"
click node_node_step_move_config "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_steps/move_to_configuration.h"
click node_node_step_grasp "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_steps/grasp.h"
click node_node_step_place "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_steps/place.h"
click node_node_step_actuate_tool "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_steps/actuate_tool.h"
click node_node_step_execute_path "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_steps/execute_path.h"
click node_node_action_execute_trajectory "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/actions/execute_trajectory.h"
click node_node_action_dwell "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/actions/dwell.h"
click node_node_action_change_attached "https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/actions/change_attached_object.h"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_node_interfaces_api,node_node_interfaces_msgs,node_node_interfaces_srvs toneBlue
class node_node_manipulation_pipeline,node_node_planning_interface,node_node_planning_pipeline,node_node_planner,node_node_planning_context,node_node_execution_pipeline,node_node_robot_model,node_node_robot_model_monitor,node_node_collision_object_manager,node_node_ik_sampler,node_node_visualization_interface,node_node_worker_thread toneAmber
class node_node_step_move_pose,node_node_step_move_named,node_node_step_move_config,node_node_step_grasp,node_node_step_place,node_node_step_actuate_tool,node_node_step_execute_path toneMint
class node_node_action_execute_trajectory,node_node_action_dwell,node_node_action_change_attached toneRose
class node_node_external_clients toneNeutral
```

## Components

### ROS 2 Interfaces

Public action, message, and service contract for external clients.

- [Action API](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/tree/main/manipulation_pipeline_interfaces/action): interfaces pkg · Public manipulation actions for motion and task requests. · `manipulation_pipeline_interfaces/action`
- [Shared data](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/tree/main/manipulation_pipeline_interfaces/msg): interfaces pkg · Motion parameters, progress/state reporting, tool commands, and scene metadata. · `manipulation_pipeline_interfaces/msg`
- [Scene services](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/tree/main/manipulation_pipeline_interfaces/srv): interfaces pkg · Spawn, remove, split, and combine object services for world updates. · `manipulation_pipeline_interfaces/srv`

### Pipeline Implementation

MoveIt 2–based planning, state management, and execution layers.

- [Pipeline entry](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/manipulation_pipeline.h): impl orchestrator · Top-level ROS 2 entry point that receives requests and drives planning/execution. · `manipulation_pipeline/include/manipulation_pipeline/manipulation_pipeline.h`
- [Planning interface](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_interface.h): request adapter · Adapts incoming ROS requests into internal planning operations. · `manipulation_pipeline/include/manipulation_pipeline/planning_interface.h`
- [Planning pipeline](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_pipeline.h): planner flow · Coordinates the sequence of planning stages for a manipulation request. · `manipulation_pipeline/include/manipulation_pipeline/planning_pipeline.h`
- [Planner](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planner.h): moveit planner · Central planning logic built on MoveIt 2 / MoveItCpp concepts. · `manipulation_pipeline/include/manipulation_pipeline/planner.h`
- [Planning context](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_context.h): request state · Carries request-specific state through the planning stages. · `manipulation_pipeline/include/manipulation_pipeline/planning_context.h`
- [Execution pipeline](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/execution_pipeline.h): execution flow · Turns successful plans into controller-facing execution. · `manipulation_pipeline/include/manipulation_pipeline/execution_pipeline.h`
- [Robot model](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/robot_model.h): state manager · Maintains robot description and runtime model changes. · `manipulation_pipeline/include/manipulation_pipeline/robot_model.h`
- [Model monitor](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/robot_model_monitor.h): state sync · Observes and updates robot/world model state at runtime. · `manipulation_pipeline/include/manipulation_pipeline/robot_model_monitor.h`
- [Collision scene](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/collision_object_manager.h): world manager · Manages collision objects and planning-scene updates. · `manipulation_pipeline/include/manipulation_pipeline/collision_object_manager.h`
- [IK sampler](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/ik_sampler.h): sampling · Samples inverse-kinematics solutions for planning steps. · `manipulation_pipeline/include/manipulation_pipeline/ik_sampler.h`
- [Visualization](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/visualization_interface.h): publishing · Publishes or updates visualization state for operators and tools. · `manipulation_pipeline/include/manipulation_pipeline/visualization_interface.h`
- [Worker thread](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/worker_thread.h): async runtime · Background/asynchronous work support for pipeline tasks. · `manipulation_pipeline/include/manipulation_pipeline/worker_thread.h`

### Planning Steps

Composable manipulation behaviors used by the planner.

- [Move pose](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_steps/move_to_pose.h): planning step · Planning step for reaching a Cartesian pose. · `manipulation_pipeline/include/manipulation_pipeline/planning_steps/move_to_pose.h`
- [Move named](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_steps/move_to_named_pose.h): planning step · Planning step for moving to a named configuration. · `manipulation_pipeline/include/manipulation_pipeline/planning_steps/move_to_named_pose.h`
- [Move config](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_steps/move_to_configuration.h): planning step · Planning step for moving to an explicit joint configuration. · `manipulation_pipeline/include/manipulation_pipeline/planning_steps/move_to_configuration.h`
- [Grasp](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_steps/grasp.h): planning step · Planning step for grasp approach and closure. · `manipulation_pipeline/include/manipulation_pipeline/planning_steps/grasp.h`
- [Place](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_steps/place.h): planning step · Planning step for placement behavior. · `manipulation_pipeline/include/manipulation_pipeline/planning_steps/place.h`
- [Actuate tool](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_steps/actuate_tool.h): planning step · Planning step for tool command execution. · `manipulation_pipeline/include/manipulation_pipeline/planning_steps/actuate_tool.h`
- [Execute path](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/planning_steps/execute_path.h): planning step · Planning step for following a precomputed path. · `manipulation_pipeline/include/manipulation_pipeline/planning_steps/execute_path.h`

### Action Helpers

Execution-side helpers for action-specific downstream behavior.

- [Exec trajectory](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/actions/execute_trajectory.h): action helper · Sends planned trajectories downstream for execution. · `manipulation_pipeline/include/manipulation_pipeline/actions/execute_trajectory.h`
- [Dwell](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/actions/dwell.h): action helper · Represents waiting or pause behavior during action execution. · `manipulation_pipeline/include/manipulation_pipeline/actions/dwell.h`
- [Attach change](https://github.com/fzi-forschungszentrum-informatik/manipulation_pipeline/blob/main/manipulation_pipeline/include/manipulation_pipeline/actions/change_attached_object.h): action helper · Updates attached-object state during execution. · `manipulation_pipeline/include/manipulation_pipeline/actions/change_attached_object.h`

### Other components

- **External clients**: consumer · ROS 2 nodes or systems that call the manipulation API.

## Connections

- External clients → Action API: calls · Clients invoke manipulation actions.
- External clients → Scene services: updates world · Clients manage objects through services.
- Action API → Pipeline entry: requests · Action goals enter the implementation layer.
- Shared data → Pipeline entry: contracts · Shared messages define request, feedback, and state payloads.
- Scene services → Collision scene: scene ops · Object lifecycle services affect the planning scene.
- Pipeline entry → Planning interface: adapts · Top-level orchestration converts API calls into internal requests.
- Planning interface → Planning context: builds · Request data is assembled into planning context.
- Planning interface → Planning pipeline: dispatches · Prepared requests move into the planning flow.
- Planning pipeline → Planner: plans · The pipeline delegates core motion planning to the planner.
- Planning pipeline → Move pose: composes · Pipeline selects planning steps for a task.
- Planning pipeline → Move named: composes · Pipeline selects planning steps for a task.
- Planning pipeline → Move config: composes · Pipeline selects planning steps for a task.
- Planning pipeline → Grasp: composes · Pipeline selects planning steps for a task.
- Planning pipeline → Place: composes · Pipeline selects planning steps for a task.
- Planning pipeline → Actuate tool: composes · Pipeline selects planning steps for a task.
- Planning pipeline → Execute path: composes · Pipeline selects planning steps for a task.
- Planner → IK sampler: samples · IK sampling supports candidate pose generation.
- Planner → Robot model: reads model · Planning uses the current robot description.
- Planner → Collision scene: uses scene · Planning accounts for collision objects and scene state.
- Model monitor → Robot model: syncs · Runtime updates keep the model current.
- Model monitor → Collision scene: syncs · World and scene changes are monitored at runtime.
- Planning pipeline → Execution pipeline: hands off · Successful plans are passed to execution.
- Execution pipeline → Exec trajectory: executes · Execution pipeline sends trajectories to controller-facing helpers.
- Execution pipeline → Dwell: coordinates · Execution pipeline can include dwell/pause behavior.
- Execution pipeline → Attach change: coordinates · Execution updates attached-object state when needed.
- Execution pipeline → Visualization: reports · Execution updates visualization and operator feedback.
- Pipeline entry → Worker thread: runs async · Background work supports non-blocking request handling.
- Pipeline entry → Visualization: publishes state · Top-level pipeline exposes progress and status views.
