Hello,
Using a
Motion
orientation_loss_weigh
desired_motion = jacobi.Motion("my_motion", robot, start=start, goal=goal)
desired_motion.orientation_loss_weight = 0.5
desired_motion.orientation_target = [x_euler, y_euler, z_euler]
Unfortunately, I couldn't see any impact on the optimized trajectory. And this was true even for very large values of
orientation_loss_weight
Thanks
1 year ago
9 months ago
10 months ago
10 months ago
Sorry for the late response here - this should be fixed already (by v0.0.24).
There was an issue when the orientation constraint was sometimes ignored when a direct point-to-point motion was possible.
0 10 months ago Reply
I tried again on v0.0.26 and
still has no effect for me.orientation_loss_weigh
However, I just tried in Studio and the constraint there is working as expected. So, maybe I am not using the API properly.
Here is what I do:
Is that correct?
0 10 months ago Reply
@Alban Laflaquiere:
Ah, I see. The
should be a vector in world coordinates, pointing in the desired direction of the TCP. I'll make this more clear in the docs.orientation_target
0 10 months ago Reply
@Lars Berscheid:
Do you mean that
should be a plainorientation_target
list instead of a[x, y, z, qw, qx, qy, qz]
?jacobi.Frame
0 10 months ago Reply
@Lars Berscheid:
Nvm, I managed to get it working. You meant the euler angles in the world frame.
0 9 months ago Reply
@Alban Laflaquiere:
Great. I'm closing this issue.
0 9 months ago Reply
1 year ago
This will be fixed in the upcoming release!
0 1 year ago Reply