Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some questions on the planning code #5

Open
RanDing2000 opened this issue Dec 13, 2024 · 1 comment
Open

Some questions on the planning code #5

RanDing2000 opened this issue Dec 13, 2024 · 1 comment

Comments

@RanDing2000
Copy link

Hello,
I have a couple of questions regarding the planning process:

  1. Does the MLPlanner support gripper width as a parameter or constraint?
  2. What is the purpose of the obstacle_pc? I noticed it remains constant for every scene, so why is it necessary to update it?

Thank you!

@chisarie
Copy link
Collaborator

Hello, and thank you for your interest in our work.

  1. I assume you mean the MPLibPlanner. This is only use to plan the motion of the arm, so the gripper has nothing to do with it. You could have different gripper widths, or even different gripper shapes, and it would be the same. This is only planning for the arm motion.
  2. obstacle_pc is the pointcloud we pass to the planner, so that it can do obstacle avoidance. It is needed so that you don't crash in the table for example. This is not constant for every scene, it changes depending on the observed scene, you can see this here:
    self.planner.update_obstacle_pc(obstacle_pc)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants