Executor

The Executor module is responsible for requesting a plan to the Planner, and carry it out, calling to the nodes in the client application that implements the actions. While executing each action, it checks the requisites (At Start, At End and Over all, in case of durative Actions). If the requirements are not meet, it cancels the plan execution. It also is responsible for applying the effects of the actions, requesting updates to the Problem Expert.

The main class of Executor is plansys2::ExecutorNode, which is instantiated from executor_node.cpp.

The executions of plans are carried out using ROS2 actions, in particular, plansys2_msgs::action::ExecutePlan. Take note that the goal must be already in the Domain Expert.

ExecutorNode ask for the domain and problem, and ask for a plan to the Planner. For each action in the plan, ExecuterNode creates a plansys2::ActionExecutor. The lifetime of this object is only one action. This object calls the actions implemented in the client appliciation using the ROS2 actions plansys2_msgs::action::ExecuteAction. Each client action implementation can use the class plansys2::ActionExecutorClient to avoid the complexity of managing ROS2 actions.

Using the feedback information from plansys2_msgs::action::ExecuteAction, feedback for plansys2::ExecutorNode is composed and returned to plansys2::ExecutorClient. It contains the current action in the plan and the progress in the currently executing action.

Next graph shows an example of the execution flow:

Actions:

• /execute_plan [plansys2_msgs::action::ExecutePlan]

(in ActionExecutorClient)

• /${ACTION_NAME}[plansys2_msgs::action::ExecuteAction]

Subscribed topics:

(in ActionExecutor)

• /problem_expert/update_notify [std_msgs::msg::Empty]

Changelog for package plansys2_executor

0.0.7 (2020-03-26)

• ActionExecutorClient is cascade_lifecycle Signed-off-by: Francisco Martin Rico <fmrico@gmail.com>
• Contributors: Francisco Martin Rico, Francisco Mart