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
{{ message }}
This repository was archived by the owner on Apr 11, 2026. It is now read-only.
Currently, the setf joint method in the bullet-reasoning package calls update-link. This is understandable, since a joint may be updated independently of others, but it does have an unfortunate consequence: if the robot is holding something, then updating the arm configuration with something like moving-tcp will result in the held object doing an unreasonable ballet around the robot, because every time one link is updated, so is the rest of the arm and the attached objects.
This is especially visually annoying when the robot holds a large object like a tray. (Functionally annoying in my branch also, as I'm implementing some proper support testing for carrying things on trays, and it doesn't like it at all when the tray flips over during a partial arm configuration update.)
Currently, the setf joint method in the bullet-reasoning package calls update-link. This is understandable, since a joint may be updated independently of others, but it does have an unfortunate consequence: if the robot is holding something, then updating the arm configuration with something like moving-tcp will result in the held object doing an unreasonable ballet around the robot, because every time one link is updated, so is the rest of the arm and the attached objects.
This is especially visually annoying when the robot holds a large object like a tray. (Functionally annoying in my branch also, as I'm implementing some proper support testing for carrying things on trays, and it doesn't like it at all when the tray flips over during a partial arm configuration update.)