Skip to content

Commit

Permalink
Document discretization behavior in KinematicsBase (#1602)
Browse files Browse the repository at this point in the history
  • Loading branch information
davetcoleman authored and mlautman committed Aug 8, 2019
1 parent 5199813 commit 9cf3e34
Showing 1 changed file with 8 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -174,12 +174,18 @@ class KinematicsBase
/**
* @brief Given the desired poses of all end-effectors, compute joint angles that are able to reach it.
*
* This is a default implementation that returns only one solution and so its result is equivalent to calling
* The default implementation returns only one solution and so its result is equivalent to calling
* 'getPositionIK(...)' with a zero initialized seed.
*
* Some planners (e.g. IKFast) support getting multiple joint solutions for a single pose.
* This can be enabled using the |DiscretizationMethods| enum and choosing an option that is not |NO_DISCRETIZATION|.
*
* @param ik_poses The desired pose of each tip link
* @param ik_seed_state an initial guess solution for the inverse kinematics
* @param solutions A vector of vectors where each entry is a valid joint solution
* @param solutions A vector of valid joint vectors. This return has two variant behaviors:
* 1) Return a joint solution for every input |ik_poses|, e.g. multi-arm support
* 2) Return multiple joint solutions for a single |ik_poses| input, e.g. underconstrained IK
* TODO(dave): This dual behavior is confusing and should be changed in a future refactor of this API
* @param result A struct that reports the results of the query
* @param options An option struct which contains the type of redundancy discretization used. This default
* implementation only supports the KinematicSearches::NO_DISCRETIZATION method; requesting any
Expand Down

0 comments on commit 9cf3e34

Please sign in to comment.