-
Notifications
You must be signed in to change notification settings - Fork 129
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
How to get the coordinates of obstacle area? #154
Comments
Yes that seems correct. We do not want goals to be located too close to the obstacles so we hardcode zones around them where a goal and robots starting position should not be located. To get the coordinates you can either look up the positions of obstacles in the world file or simply estimate them even from this image (each square is 1x1 meter and the origin is the blue line) |
You mean to add it as a dynamic obstacle? Sorry, that is outside the scope of this repo and I do not know off the top of my head. I am sure there is some tutorial out there on that. |
Are you sure a collision is detected here? What you see is a laser state representation. But we only use velodyne lidar to detect collisions. Check the min value of the collision check to see if any collision is actually detected here. |
Hello, how can I get the coordinates of the obstacle area, such as the first area
if -3.8 > x > -6.2 and 6.2 > y > 3.8:
goal_ok = False
I didn't understand what it meant by the obstruction area.
Is that the red area in the picture?
The text was updated successfully, but these errors were encountered: