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

Planning fails to calculate trajectory in a certain map. #9740

Open
3 tasks done
mitsudome-r opened this issue Dec 23, 2024 · 1 comment
Open
3 tasks done

Planning fails to calculate trajectory in a certain map. #9740

mitsudome-r opened this issue Dec 23, 2024 · 1 comment
Labels
component:planning Route planning, decision-making, and navigation. (auto-assigned) status:stale Inactive or outdated issues. (auto-assigned)

Comments

@mitsudome-r
Copy link
Member

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

Autoware fails to calculate trajectory in a certain map.

image

Expected behavior

Autoware succeeds to calculate a trajectory.

Actual behavior

Autoware fails to calculate trajectory in a certain map.

Steps to reproduce

  1. Download the map shalun_map.zip
  2. Set the initial pose and goal position as in the image

Versions

  • Autoware: 0.39.0

Possible causes

It seems like it is hanging in intersection module.
If I modify the attention_area_length to 50.0 from the default 200.0, it successfully calculate trajectory.

I did a deeper look in the code, but I'm doubting that getPrecedingLaneletsUptoIntersectionRecursive() might be causing some issues with the map with roundabout.

Additional context

No response

@mitsudome-r mitsudome-r added the component:planning Route planning, decision-making, and navigation. (auto-assigned) label Dec 23, 2024
@idorobotics idorobotics moved this from To Triage to Backlog in Software Working Group Feb 17, 2025
Copy link

stale bot commented Feb 21, 2025

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 Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component:planning Route planning, decision-making, and navigation. (auto-assigned) status:stale Inactive or outdated issues. (auto-assigned)
Projects
Status: Backlog
Development

No branches or pull requests

1 participant