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
There used to be a streaming pose command: 7af8fc7 (#117). Before its deprecation at 469d103, the documentation stated:
/** * @brief Achieve pose (velocity control) * * Move to desired position, computing the error with respect to the current pose. Then, * perform numerical differentiation and obtain the final velocity increment (as in @ref twist). * * @param x 6-element vector describing desired instantaneous pose in cartesian space; * first three elements denote translation (meters), last three denote rotation (radians). * @param interval Time interval between successive command invocations, expressed in seconds * and used for numerical differentiation with desired/current poses.*/voidpose(const std::vector<double> & x, double interval);
The movi command was introduced later (87a9c94) with the following description:
/** * @brief Achieve pose * * Move to desired position instantaneously, no further intermediate calculations are * expected other than computing the inverse kinematics. * * @param x 6-element vector describing desired instantaneous pose in cartesian space; * first three elements denote translation (meters), last three denote rotation (radians).*/voidmovi(const std::vector<double> & x);
I find the movi name a bit difficult to understand at first glance. Also, ROS users may question the naming of this command due to the existence of Pose, Twist and Wrench geometry message types (ref). Since the information conveyed is in fact a pose, then why not use this name instead?
There used to be a streaming
pose
command: 7af8fc7 (#117). Before its deprecation at 469d103, the documentation stated:The
movi
command was introduced later (87a9c94) with the following description:I find the
movi
name a bit difficult to understand at first glance. Also, ROS users may question the naming of this command due to the existence of Pose, Twist and Wrench geometry message types (ref). Since the information conveyed is in fact a pose, then why not use this name instead?cc @jgvictores @mercerebo1
The text was updated successfully, but these errors were encountered: