-
Notifications
You must be signed in to change notification settings - Fork 40
JointWaypoints and StateWaypoints as planning result #366
Replies: 3 comments · 6 replies
-
Can you post the contents of your task composer config file? There are a few places where you can tell the planners to "format_result_as_input" (which makes them return original types of waypoints (i.e. Changing your URDF shouldn't have any affect on the output of the motion planners. There may also be a bug in the Python bindings that's not handling the |
Beta Was this translation helpful? Give feedback.
All reactions
-
Thanks for the quick reply!
But to be honest I am not sure which one of them I am using. |
Beta Was this translation helpful? Give feedback.
All reactions
-
I tried adding the "format_result_as_input" statement, but sadly that did not have any visible effect. |
Beta Was this translation helpful? Give feedback.
All reactions
-
You are using the FreespacePipeline |
Beta Was this translation helpful? Give feedback.
All reactions
-
Looking at your code you are not checking if it was successful so I assume it is failing and you are just getting the output of the simple planner which would be joint waypoints. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Thanks for the hint but sadly that does not seem to be the problem. I just checked, the behavior you described is true for the abb urdf, there it gives me JointWaypoints when no solution is found and StateWaypoints when it was successful. But for the custom urdf it gives me JointWaypoints even in those cases that succeed. |
Beta Was this translation helpful? Give feedback.
All reactions
-
The urdf should have no impact on the behavior of the task_composer pipeline in this regard, so I am not sure. Have you tried using the c++ version? |
Beta Was this translation helpful? Give feedback.
All reactions
-
I have not yet tried the c++ version. Thank you for your time. |
Beta Was this translation helpful? Give feedback.
All reactions
-
What did you change? |
Beta Was this translation helpful? Give feedback.
-
Hello tesseract community!
I am currently working on my first ever tesseract project and am getting some confusing results. I am planning a path between two points. When I do this using the abb_irb2400 urdf I am getting a trajectory consisting of StateWaypoints. But when I use a custom urdf (containing an UR5) the planned trajectory consists of JointWaypoints.
So my question is what could be the reason for this behavior, why is the type of waypoint changing?
In the end I actually do not really care whether or not it is a StateWaypoint, as long as I can extract cartesian coordiantes from it, which I so far have only managed to do for the StateWaypoints. In case you can't help me with my question above I would also be glad if you could tell me if there is a solution for that.
The code I am using (mostly copied from the tesseract_python example):
ABB urdf:
ABB srdf:
Custom urdf:
Custom srdf:
Thank you for reading this!
Best regards,
Kai
Beta Was this translation helpful? Give feedback.
All reactions