MTC功能包
Go to file
Robert Haschke 97bb6ef2c6 allow handling of failures
- store "failure" solutions to facilitate debugging
- Introspection assigns solution IDs as soon as they are created in a stage
  Thus, solution IDs represent their creation order.
  In contrast, the order of publishing (in StageStatistics) should
  represent the cost order.
- Storing failures is disabled if Introspection is not available.
2018-02-12 22:35:58 +01:00
core allow handling of failures 2018-02-12 22:35:58 +01:00
msgs introducing process_id 2018-02-04 09:01:40 +01:00
rviz_marker_tools rviz marker tools 2018-02-04 09:00:54 +01:00
visualization allow handling of failures 2018-02-12 22:35:58 +01:00
.gitignore add gitignore for vim swp 2017-02-28 11:12:18 +01:00
.travis.yml add myself as maintainer & travis recipient 2017-11-13 15:39:30 +01:00
LICENSE.txt add full license information 2017-12-12 21:24:32 +01:00
README.md provide a minimalistic README.md 2017-12-08 21:29:48 +01:00

moveit_task_constructor

An approach to forward multi-step manipulation planning

The framework is currently under development. The API is unstable and incomplete.

Feedback is very welcome.

This project enables the user to specify and plan complex manipulation actions in terms of successive planning stages.

Individual stages compute robot trajectories relative to their expected start or end. The resulting planning pipeline, i.e. Task, extends different candidate trajectories from key states (Generator stages) until it generated feasible trajectories that extend through all stages.

The current aim is to replace MoveIt's old pick&place pipeline and provide a transparent mechanism to enable and debug complex motion sequences.