Make trajectory monitoring optional (#17)

Co-authored-by: Mario Prats <[email protected]>

Author: sjahr

capabilities/src/execute_task_solution_capability.cpp

@@ -151,6 +151,7 @@ bool ExecuteTaskSolutionCapability::constructMotionPlan(const moveit_task_constr
 		// define individual variable for use in closure below
 		const std::string description = std::to_string(i + 1) + "/" + std::to_string(solution.sub_trajectory.size());
 		exec_traj.description = description;
+		exec_traj.trajectory_monitoring = sub_traj.execution_info.trajectory_monitoring;
 
 		const moveit::core::JointModelGroup* group = nullptr;
 		{

msgs/msg/TrajectoryExecutionInfo.msg

@@ -1,2 +1,5 @@
 # List of controllers to use when executing the trajectory
 string[] controller_names
+# MoveIt's PlanExecution capability that is used to execute MTC solutions has the ability to monitor a trajectory for collisions while it's being executed. This is useful in dynamic environments where obstacles may change between the time the plan was computed and its execution, or even during execution. If this flag is set to true, MoveIt's online collision monitor will be enabled, which can stop the trajectory at any point during execution if a collision is predicted.
+bool trajectory_monitoring
+