Loading...
Searching...
No Matches
ompl::base::PlannerSpecs Struct Reference

Properties that planners may have. More...

#include <ompl/base/Planner.h>

Public Attributes

GoalType recognizedGoal {GOAL_ANY}
 The type of goal specification the planner can use.
 
bool multithreaded {false}
 Flag indicating whether multiple threads are used in the computation of the planner.
 
bool approximateSolutions {false}
 Flag indicating whether the planner is able to compute approximate solutions.
 
bool optimizingPaths {false}
 Flag indicating whether the planner attempts to optimize the path and reduce its length until the maximum path length specified by the goal representation is satisfied.
 
bool directed {false}
 Flag indicating whether the planner is able to account for the fact that the validity of a motion from A to B may not be the same as the validity of a motion from B to A. If this flag is true, the planner will return solutions that do not make this assumption. Usually roadmap-based planners make this assumption and tree-based planners do not.
 
bool provingSolutionNonExistence {false}
 Flag indicating whether the planner is able to prove that no solution path exists.
 
bool canReportIntermediateSolutions {false}
 Flag indicating whether the planner is able to report the computation of intermediate paths.
 

Detailed Description

Properties that planners may have.

Definition at line 184 of file Planner.h.

Member Data Documentation

◆ approximateSolutions

bool ompl::base::PlannerSpecs::approximateSolutions {false}

Flag indicating whether the planner is able to compute approximate solutions.

Definition at line 195 of file Planner.h.

◆ canReportIntermediateSolutions

bool ompl::base::PlannerSpecs::canReportIntermediateSolutions {false}

Flag indicating whether the planner is able to report the computation of intermediate paths.

Definition at line 211 of file Planner.h.

◆ directed

bool ompl::base::PlannerSpecs::directed {false}

Flag indicating whether the planner is able to account for the fact that the validity of a motion from A to B may not be the same as the validity of a motion from B to A. If this flag is true, the planner will return solutions that do not make this assumption. Usually roadmap-based planners make this assumption and tree-based planners do not.

Definition at line 205 of file Planner.h.

◆ multithreaded

bool ompl::base::PlannerSpecs::multithreaded {false}

Flag indicating whether multiple threads are used in the computation of the planner.

Definition at line 192 of file Planner.h.

◆ optimizingPaths

bool ompl::base::PlannerSpecs::optimizingPaths {false}

Flag indicating whether the planner attempts to optimize the path and reduce its length until the maximum path length specified by the goal representation is satisfied.

Definition at line 199 of file Planner.h.

◆ provingSolutionNonExistence

bool ompl::base::PlannerSpecs::provingSolutionNonExistence {false}

Flag indicating whether the planner is able to prove that no solution path exists.

Definition at line 208 of file Planner.h.

◆ recognizedGoal

GoalType ompl::base::PlannerSpecs::recognizedGoal {GOAL_ANY}

The type of goal specification the planner can use.

Definition at line 189 of file Planner.h.


The documentation for this struct was generated from the following file: