You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently using SE2MultiRigidBodyPlanning.cpp for multi-agent planning. When I increase the number of agents from the default 2 to 5, even if collisions with obstacles occur, "Exact Solution" is still output, and the path planning is judged as successful.
I have created obstacle and agent files in accordance with the default settings for SE2MultiRigidBodyPlanning.cpp.
I'd like to know the cause of this issue. Also, can this program truly be extended to handle more than 3 agents?
The text was updated successfully, but these errors were encountered:
yhiroya
changed the title
Problem on mukti-agent planning with SE2MultiRigidBodyPlanning
Problem on multi-agent planning with SE2MultiRigidBodyPlanning
Apr 28, 2024
Can you describe the output exact solution path? If the robots are "teleporting" through obstacles or each other this is probably an issue with the valid segment resolution. See https://ompl.kavrakilab.org/stateValidation.html for more information (the paragraph on validity checking resolution) for how to tune these values.
I'm sorry.
Due to my mistake, the program wasn't functioning properly, but after fixing it, I was able to run SE2MultiRigidBodyPlanning.cpp correctly even with three or more instances.
I apologize for any inconvenience caused.
I'm currently using SE2MultiRigidBodyPlanning.cpp for multi-agent planning. When I increase the number of agents from the default 2 to 5, even if collisions with obstacles occur, "Exact Solution" is still output, and the path planning is judged as successful.
I have created obstacle and agent files in accordance with the default settings for SE2MultiRigidBodyPlanning.cpp.
I'd like to know the cause of this issue. Also, can this program truly be extended to handle more than 3 agents?
The text was updated successfully, but these errors were encountered: