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

Unable to place goal pose when start pose is given inside parking lot spaces #6511

Open
3 tasks done
4swinv opened this issue Feb 29, 2024 · 1 comment
Open
3 tasks done
Assignees
Labels
status:stale Inactive or outdated issues. (auto-assigned) type:bug Software flaws or errors.

Comments

@4swinv
Copy link
Contributor

4swinv commented Feb 29, 2024

Checklist

  • I've read the contribution guidelines.
  • I've searched other issues and no duplicate issues were found.
  • I'm convinced that this is not my fault but a bug.

Description

Setting start pose inside parking space then setting the goal pose leads to error. Goal pose cannot be placed anywhere. Moving start pose to one of the lanes allows placing goal pose. Issue only when start pose is inside parking space, outside parking space but inside parking lot still allows goal placement.

The issue is consistent when setting start and goal pose on initial autoware start up. During replanning it seems to be inconsistent depending on start pose of ego vehicle.

Video:

out.mp4

Expected behavior

Freespace planning algorithm outputs trajectory after placing goal pose.

Actual behavior

Unable to place goal pose anywhere when start pose is inside parking space.

Steps to reproduce

  1. Place start pose inside parking space (orange boxes), ego vehicle being fully inside.
  2. set goal pose at any location.

Versions

No response

Possible causes

Error log:

[rviz2-42] [INFO] [1709166781.399727790] [rviz2]: Setting goal pose: Frame:map, Position(3724.46, 73754.1, 0), Orientation(0, 0, -0.529324, 0.84842) = Angle: -1.11561
[component_container_mt-25] [ERROR] [1709166781.661750762] [route_handler]: Failed to find a proper route!
[component_container_mt-25]  - start checkpoint: (3727.25, 73755.7,19.4987)
[component_container_mt-25]  - goal checkpoint: (3724.46, 73754.1,0)
[component_container_mt-25]  - start lane id: 9428
[component_container_mt-25]  - goal lane id: 9428
[component_container_mt-25] 
[component_container_mt-25] [WARN] [1709166781.661786924] [planning.mission_planning.mission_planner]: Failed to plan route.
[service_log_checker-3] [ERROR] [1709166781.662298218] [system.service_log_checker]: /planning/mission_planning/route_selector/main/set_waypoint_route: status code 3 'The planned route is empty.' (/default_ad_api/node/routing)
[service_log_checker-3] [ERROR] [1709166781.662358040] [system.service_log_checker]: /api/routing/set_route_points: status code 3 'The planned route is empty.' (/default_ad_api/node/routing)
[service_log_checker-3] [ERROR] [1709166781.662486600] [system.service_log_checker]: /api/routing/set_route_points: status code 3 'The planned route is empty.' (/default_ad_api/helpers/routing_adaptor)

Additional context

No response

Copy link

stale bot commented Jul 7, 2024

This pull request has been automatically marked as stale because it has not had recent activity.

@stale stale bot added the status:stale Inactive or outdated issues. (auto-assigned) label Jul 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:stale Inactive or outdated issues. (auto-assigned) type:bug Software flaws or errors.
Development

No branches or pull requests

4 participants