-
Notifications
You must be signed in to change notification settings - Fork 0
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
Pedsim agent avoid robot #1
Comments
Hi, sorry for the late reply. The navigation is unfortunately out of the scope of this package. However, I am planning to release some examples using Nav2 in a separate repository in the near future :) |
@NamTruongTran0: I saw that you edited your comment with the original asking "The pedsim agents always avoiding the robot while walking. Where can i change this setting? I want that the agent not avoiding the robot." I had a similar question. My problem is that the agents (from the simulation) do not even see human. I also do not see in change in the social force, when they are near. This leads to the agents colliding with the robot. Have you fixed this issue? Or maybe @stephenadhi can help solving this? I have looked at other git issues from the original repo, but those proposed solutions did not work for me: |
Nevermind, I found the solution to the problem. In case anyone else encounters this issue, you should consider these things:
The waypoints do not seem to matter that much. I am using nav2 for the robot controller and planner and it works even when not considering any of the waypoints set in the scenario file.
pedsim_simulator:
|
Hey Stephen,
thank you so much for your help. I fixed the issue. Now i can start your house example.
do you know which parameter should i change to update the global costmap more frequently? In my video you can see the agent walking from point A to point B but the path is very short thats why the global costmap always mark the path of the agent as an obstacle.
Link to the video: https://streamable.com/f3f3k6
Thank you in advance stephen ;)
The text was updated successfully, but these errors were encountered: