Trajopt trajectory optimization #270
Replies: 2 comments
-
To be clear, addlinearmotion is not a function in this repository. It is a function in the example I send you a while ago. That example was/is still in development, so I can't even guarantee the version I have is the same as what I sent you. For this issue and any others, it is always useful to include a minimum repeatable example if possible. In this case, a small piece of code that shows how you are setting up your problem and then solving it without any of your other non-trajopt things in it. Many times in making those examples you will find the issue yourself. We certainly welcome questions, and we are excited that you are using TrajOpt. However, it is impossible for us to help with issues like this that basically just say "it doesn't work". To answer your last point, you should be able to get much closer than that with the default box size (also, box size is not in cartesian space) |
Beta Was this translation helpful? Give feedback.
-
I understand your point, Actually I got the forward kinematics of two points in a straight line using ros moveit with respect to a frame. Then costs are set as shown below:
I didn't understand how does plotting_cb and file_write_cb can be used for tesseract. Kindly please help me to understand. planning_response is given to /follow_joint_trajectory using ROS moveit IPTP. I checked with the end point joint values of the joint trajectory obtained by trajopt and my robot is at almost that position. So I feel something is wrong while optimizing trajectory(like 50% of trajectory is optimized or something). Kindly please let me know If I am wrong at any point. |
Beta Was this translation helpful? Give feedback.
-
I gave start and end point to addlinearmotion(approach_pose, final_pose, num_steps) but my robot arm moves to a different position as shown below when compare the joint_values obtained to the pose reached by the manipulator are same but my end_pose is different . So I dont know how I can make it reach to the specified end_pose. The values are different.
The robot should go this target_pose. But it reaches a point as below.
pose.position.x = -0.590;
pose.position.y = 0.399;
pose.position.z = 0.108
I tried using moveit it reaches exact position.
Is this because optimization assumes a box size for converging the point ?
Beta Was this translation helpful? Give feedback.
All reactions