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

Plan_single_js Generate Collision Trajectory #450

Open
Alice-ly opened this issue Dec 31, 2024 · 2 comments
Open

Plan_single_js Generate Collision Trajectory #450

Alice-ly opened this issue Dec 31, 2024 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@Alice-ly
Copy link

Hi, I have been using curobo for months and it performs quite well when there is no obstacle in the world, but when I add an obstacle in the world(for example a box from Rviz scene objects), curobo will generate trajectory that does not avoid the obstacle totally.

And I have tried several parameters to fix the bug (shown below), some parameters do make a difference, but it still can't avoid obstacles in all cases.
This is the function I use :
image

These are parameters I have tried to change:
particle_trajopt.yml
image
gradient_trajopt.yml
image

And I feel that only activation distance changed the trajectory, when activation distance raises, the trajectory will avoid the obstacles but sometimes it still move through the obstacle directly.
Could you please offer some more ideas on how to fix this problem? thank you very much !


Issue Details

@balakumar-s
Copy link
Collaborator

Are you using it though ROS or directly in python? If through python, can you provide a minimal example of the issue?

If through ROS, can you ask your question here: https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_cumotion/issues

@balakumar-s balakumar-s added the question Further information is requested label Jan 4, 2025
@Alice-ly
Copy link
Author

Alice-ly commented Jan 8, 2025

Are you using it though ROS or directly in python? If through python, can you provide a minimal example of the issue?

If through ROS, can you ask your question here: https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_cumotion/issues
Thank you !
And I have figured out what the problem is!
It's because the base_frame set in my XRDF file is wrong, what I use in my XRDF file is different from the one the world model use, so that the manipulator's place the code calculated is not what I see in Rviz.

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

No branches or pull requests

2 participants