moveit / moveit_drake

Experimental repository for Moveit2 - Drake integration
BSD 3-Clause "New" or "Revised" License
11 stars 4 forks source link

Kinematic Trajectory Optimization Skeleton PR #8

Closed kamiradi closed 1 week ago

kamiradi commented 3 weeks ago

This PR aims to transcribe a basic Kinematic Trajectory Optimization problem from Moveit to Drake

sea-bass commented 3 weeks ago

Made more updates to the Dockerfile. Now I can do:

And there are still no moveit apt packages installed. Ever! No need to remove any extra ones either :)

sea-bass commented 2 weeks ago

@sea-bass, I see that you have added the relevant bits to report the motion plan response. Were you able to test this on the demo?

I was, but it's far from complete. There are no actual costs/constraints added, and the Drake trajectory needs to be converted to a MoveIt RobotTrajectory ans packed up into the result.

sjahr commented 2 weeks ago

@kamiradi Can you ping when you addressed all comments for another review round? You can resolve the conversation you addressed and comment on the ones where you might be unsure/ have questions or commetns

kamiradi commented 1 week ago

@sjahr, I remember you pointing me towards a specific yaml file that needs to have a _planning suffix to be loaded by the class loader. Could you point me towards an example? I believe this is needed for the drake planning plugin to be loaded during runtime.

sjahr commented 1 week ago

@sjahr, I remember you pointing me towards a specific yaml file that needs to have a _planning suffix to be loaded by the class loader. Could you point me towards an example? I believe this is needed for the drake planning plugin to be loaded during runtime.

@kamiradi The file is specified per moveit config, for example in panda_moveit_config for stomp: https://github.com/moveit/moveit_resources/blob/ros2/panda_moveit_config/config/stomp_planning.yaml

The content is equivalent with the section you've added to the launch file and either the yaml file or the launch file section can be used (although the .yaml file is best practices for fleshed out plugins).

kamiradi commented 1 week ago

Ah I see, so this is an alternative to the launch file config mentioned in the launch file. Is there a runtime requirement for the yaml file also to be present? Can I defer this to the next PR?

So the requirement now is to:

  1. Declare a similar ktopt_planning.yaml file (where should I be doing this? should I create a new config folder within the repository?)
  2. And the class loader automagically loads this at runtime.