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
I've had a look in the code for a constraint to minimise the Cartesian path length but the closest I've found is "type": "cart_pose" which has a completely different use. I would expect it to be called cart_pos and operate in the same way as cart_vel.
Does this type of constraint exist?
Thanks,
Austin
The text was updated successfully, but these errors were encountered:
Cartesian velocity should minimize cartesian path length as it just assumes the timestep is 1. That said, I have not personally used it too much. It looks like the coeffs are not exposed for that cost at the moment. If it is not working, that could be the issue. They are set to all ones in problem_description at prob.addCost
If you want to set a true cartesian velocity, you would need to set TT_USE_TIME, but time parameterization has been implemented for cartesian moves yet.
So far I've been using cart_vel and and joint_vel constraints to minimise the path length.
I've had a look in the code for a constraint to minimise the Cartesian path length but the closest I've found is
"type": "cart_pose"
which has a completely different use. I would expect it to be calledcart_pos
and operate in the same way as cart_vel.Does this type of constraint exist?
Thanks,
Austin
The text was updated successfully, but these errors were encountered: