You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One reason why libraries use both the kdl_parser and directly the robot model is the representation of the joint limits (which are not represented in KDL).
I was wondering whether there would be interest that I implement an interface to extract both the KDL kinematic chain and joint limits (represents by a base::JointLimits). I was thinking of something along the lines of:
One reason why libraries use both the kdl_parser and directly the robot model is the representation of the joint limits (which are not represented in KDL).
I was wondering whether there would be interest that I implement an interface to extract both the KDL kinematic chain and joint limits (represents by a
base::JointLimits
). I was thinking of something along the lines of:and then an API that maps the one already present in kdl_parser.hpp, but that would fill a
KinematicChainModel
instead of only aKDL::Tree
.Do you think that it would be a good idea ? @maltewi ?
The text was updated successfully, but these errors were encountered: